• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Retire Early Inc : Use Case Enhancement?

 
Chris Bicnal
Ranch Hand
Posts: 99
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

I'm starting to look at the Retire Early Inc assignment and have a ton of questions, but the one that's bothering me the most is about the view account.

The requirements are that when reviewing an account the account details should be returned within 8 seconds. This is fine because I need to call the PriceRight service to retrieve the latest values of assets before showing the customer the value of their accounts - after all, stock markets change.

However, the review account use case which discusses this doesn't mention anything about invoking the PriceRight.

I notice the sentence above the use cases stating "The use case specifications provided are a first pass at the use cases and provide enough detail in order for you to architect a solution" so I assume that means that I can "enhance" them in order to meet the requirements.

Is that a correct assumption? Is that what others have done?

Thanks,

Bic
 
Amritendu De
author
Ranch Hand
Posts: 188
11
Java Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can make necessary assumptions. The use cases are first pass as mentioned and needs some work to be clear.
 
Alexei Novikov
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Bic,

I had same assignment, and had a lot of painful questions too.
You are free to enhance use cases. I made some enhancements, and it was accepted. My work scored 148.
Just think twice before you do that. Use case flow is a requirement, this is what a customer stated he or she needs, even it looks like an overly simple stupid thing. Displaying latest values in the account review use case is something that you think will be nice, not the customer. Of course you can write an assumption in favour of an extended interpretation, or you can assume that the customer wants a simplistic view, both will be valid. The choice is yours, just don't forget to document it.

I think what is important is a spirit of a respectful attitude to customers business needs. Assignment specs leave a lot of space for interpretation. As software developers, we have a natural urge to make things nicer. There are plenty of possibilities of making this stupid little assignment project look nicer, but maybe it's not what our imaginary customer wants. The project has an imaginary budget. All improvements would cost a customer extra dollars; as an architect one should be aware of that.

Regards,
Alex
 
Julio Cesar Rocha Vera
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Alexei, how do you solved it??? I recently passed 1Z0-807
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic