1. 6

2. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain how events can be used to identify use cases that define requirements  Identify and analyze events and resulting use cases  Read, interpret, and create a Unified Modeling Language (UML) domain model class diagram and design class diagram

3. 3Object-Oriented Analysis and Design with the Unified Process Events and Use Cases  Event  occurrence at a specific time and place  Event decomposition: help identify use cases, first focusing on the events a system must respond to and then looking at how s system responds Figure 1: Identifying use cases by focusing on users and their goals

4. 4Object-Oriented Analysis and Design with the Unified Process Types of Events  External Events  Occur outside the system  Usually caused by external agent

5. 5Object-Oriented Analysis and Design with the Unified Process Temporal Events - Occurs when system reaches a point (deadline) in time Types of Events (con’t)

6. 6Object-Oriented Analysis and Design with the Unified Process State Events - When something happens inside the system that triggers the need for processing Types of Events (con’t)

7. 7Object-Oriented Analysis and Design with the Unified Process External events in the Rocky Mountain Outfitters: Customer support system

8. 8Object-Oriented Analysis and Design with the Unified Process Temporal events in the Rocky Mountain Outfitters: Customer support system

9. 9Object-Oriented Analysis and Design with the Unified Process Event Table

10. 10Object-Oriented Analysis and Design with the Unified Process The Complete Event Table for the RMO Customer Support System

11. 11Object-Oriented Analysis and Design with the Unified Process Types of Things

12. 12Object-Oriented Analysis and Design with the Unified Process Associations among Things  Analyst document entity associations ( relationships)  Example: “Is placed by” and “works in”  Associations apply in two directions  Customer places an order  An order is placed by a customer  Multiplicity: the number of associations  One to one or one to many

13. 13Object-Oriented Analysis and Design with the Unified Process Associations Naturally Occur between Things

14. 14Object-Oriented Analysis and Design with the Unified Process Multiplicity of Relationships

15. 15Object-Oriented Analysis and Design with the Unified Process Attributes of Things

16. 16Object-Oriented Analysis and Design with the Unified Process The UML Class Diagram The UML class symbol with three sections for name, attributes and methods

17. 17Object-Oriented Analysis and Design with the Unified Process The UML Class Diagram (con’t) Multiplicity of associations

18. 18Object-Oriented Analysis and Design with the Unified Process A Generalization/Specialization Hierarchy Notation for Motor Vehicles The UML Class Diagram (con’t)

19. 19Object-Oriented Analysis and Design with the Unified Process The UML Class Diagram (con’t) Whole-part (Aggregation) Associations Between a Computer and Its Parts

20. 20Object-Oriented Analysis and Design with the Unified Process University Course Enrollment Design Class Diagram (With Methods) The UML Class Diagram (con’t)

21. 21Object-Oriented Analysis and Design with the Unified Process The UML Class Diagram (con’t) Expanded course enrollment design class diagram (with methods)

22. 22Object-Oriented Analysis and Design with the Unified Process Summary  Requirements discipline defines business functions  Key concepts: use cases and problem domain classes  Use cases derive from elementary business processes (EBPs)  Three event types: external, temporal, and state  Attributes: specific information about a thing  Actual software classes include behaviors (methods) and attributes  UML class diagrams show classes, attributes, methods, and associations 

23. 23Object-Oriented Analysis and Design with the Unified Process Summary (continued)  Design class diagram models software classes  Generalization/specialization hierarchies allow inheritance from a superclass to a subclass  Whole-part hierarchies allow a collection of objects to be associated as a whole and its parts