1. OO Process Steps • Ø      Define requirements • Allocate and Derive requirements • Map requirements to use cases • Map requirements to classes • Ø      Define use cases • Draw Diagrams • Write use case summary &ID flow of events • Include requirements & External Interfaces • Ø      Define domain model class diagram • Add attributes when known • ØReview requirements • Ø      Define use case scenarios • Include a summary • Ø      Define first level decomposition class diagram • Take from domain class diagram • Include boundary objects, controllers and entities • ØReview Preliminary Design • Ø     Create a sequence diagram for each scenario • Use only objects in the class diagram • Update scenario documentation to include details • Ø      Update class diagram • Add methods to classes when known (Internal interfaces) • Ø     Update Documentation (interfaces etc.) • Ø    Review Design R

2. Project (part 1) • Project summary • Requirements table • Prototypes (if applicable) • Domain Model • Use cases • Diagram and summary text • Flow of events identified Everything up to Review Requirements

3. The Store shall: • Take orders over the internet • Allow the buyer to pay with credit card • Allow online users to search the product catalog by type, product ID, keyword • Allow the management of a product catalog • Maintain store information automatically; accounts receivable, inventory • Printout shipping information automatically • Maintain user reviews and ratings on products • Allow users to input reviews and ratings • Manage up to 1,000,000 accounts

4. Homework • Read Boggs Chap 4 • Finish Requirements Analysis part of the project E-mail to me before noon Sept 29 • Subject: Project Requirements • Cover letter • Paper • Intro, problem def, org & sys def, Req table, use case summary & flow of events • Schedule embedded • Use case model diagrams embedded

5. Introduction • Problem Definition • Organization and system definition • Organization • System Definition • Include prototype screens if applicable. • Use cases • Summary for each use case • Flow of events identified for each use case (include alternate flows as well as exception flows) • Requirements Table • Team Recommendation