Hi Doug, (c) is definately right as stated on Page 75 of Larman " Use-Case realization drives the design. That is, the team designs collaborating objects and subsystems in order to perform or realize the use cases." But I am confused between (a) and (d) since both of them use the term "generally results".
Thanks and Regards<br />Balbir Singh<br />Sun Certified Java Programmer<br />IBM Certified Administrator for WebSphere4.0
Requirements in USE CASE generally MEANS public methods in a domain model, though we don't need to highlight it in there. So, I go to (a) and (c). Yingtang [ March 25, 2002: Message edited by: Yingtang Tang ]
Hi All Yingtang is right, let's exam a very simple example, we will find out. Customer buy goods, he/she can pay in cash or credit card. in this case, We may use adaptor pattern as a solution, then we do not need a additional public method in our domain. Payment---------more alternative Payment / \ / \ CashPayment CreditCardPayment our Domain only needs deal with Payment. I hope It will help someone who chosen "D"
If I am rich, I will spend more.<p>IBM 486 (OOAD & UML) & 141 (XML) passed<br />Oracle 1Z0-007 passed<br />MCSD MCDBA MCSE <br />SCJP SCSSA<br />CCNA CNA A+
This. Exactly this. This is what my therapist has been talking about. And now with a tiny ad:
Gift giving made easy with the permaculture playing cards