1. pick of the day 30 Jan 2003 Lecture 13 Mini Case Study

2. January 30 2003Lecture 132 Outline Lecture Contents mini case study pulling everything together New Business Office hours today: 5:15 – 6:15 Midterm Exam: Tomorrow in class Open book, closed notes Bring TAOO

3. January 30 2003Lecture 133 Real world examples … Are more complicated than our small textbook examples so make sure basic principles are clear Will change without asking for your permission so make sure you do your best to plan for extension and flexibility

4. January 30 2003Lecture 134 Sample Use Cases Book buyers travel each day to buy or sell Each laptop contains latest inventory synchronized each night between 10:00 PM and 12:00 Midnight Prior to a sale, buyer confirms with central inventory and reserves book for sale Sold books are removed from inventory after midnight Reports generated nightly record activity Extensive search capabilities supported

5. January 30 2003Lecture 135 Initial Class Model UML short form [first pass] BookItem *1 ItemCollection BookManager * 1 * 1 Could be used for sold books, but also for other ‘sets’

6. January 30 2003Lecture 136 Initial Class Model review Explain why each relationship exists Explain the association and links that will support the relationships Design inheritance hierarchies OR composite patterns Do you want subclasses “FairBook” and “NewBook”?

7. January 30 2003Lecture 137 Detailed Class Model UML Long Form think of the way associations are to be implemented creation and ownership of objects Decide upon responsibilities of objects and their operations

8. January 30 2003Lecture 138 E/B/C analysis The UML diagrams earlier typically form the basis for the entities The Boundaries are typically the interface forms used by actors, such as users The Controllers encapsulate activities these may cut across classes and involve numerous objects these may be long lived, but typically are of short duration

9. January 30 2003Lecture 139 E/B/C analysis continued Controllers should be relatively independent of each other when necessary, they may communicate through clearly-defined interfaces

10. January 30 2003Lecture 1310 References