object oriented analysis and design with the unified process

6. Figure 5-1 Identifying Use Cases by Focusing on Users and their Goals

8. Figure 5-2 Events Affecting a Charge Account Processing System that Lead to Use Cases

10. Figure 5-3 External Event Checklist

11. Figure 5-4 Temporal Event Checklist

13. Figure 5-5 Temporal Event Checklist

14. Figure 5-6 The Sequence of “Transactions” for One Specific Customer Resulting in Many Events

16. Figure 5-7 Events Deferred until Later Iterations

18. Figure 5-8 External Events for the RMO Customer Support System

19. Figure 5-9 Temporal Events for the RMO Customer Support System

21. Figure 5-10 Information about each Event and the Resulting Use Case in an Event Table

22. Figure 5-11 The Complete Event Table for the RMO Customer Support System

25. Figure 5-12 Types of Things

27. Figure 5-13a Partial List of “Things” Based on Nouns for RMO

28. Figure 5-13b Partial List of “Things” Based on Nouns for RMO

29. Figure 5-13c Partial List of “Things” Based on Nouns for RMO

31. Figure 5-14 Associations Naturally Occur between Things

32. Figure 5-15 Multiplicity of Relationships

34. Figure 5-16 Attributes and Values

36. Figure 5-17 Objects Encapsulate Attributes and Methods

38. Figure 5-21 An Expanded Domain Model Class Diagram Showing Attributes

39. Figure 5-24 A Refined University Course Enrollment Domain Model Class Diagram With an Association Class

41. Figure 5-25 A Generalization/Specialization Hierarchy Notation for Motor Vehicles

43. Figure 5-27 Whole-part (Aggregation) Associations Between a Computer and Its Parts

45. Figure 5-29 University Course Enrollment Design Class Diagram (With Methods)

47. Figure 5-31 Rocky Mountain Outfitters Domain Model Class Diagram

49. Figure 5-32 Rocky Mountain Outfitters Location Diagram

50. Figure 5-33a Use Case–location Matrix for the Rocky Mountain Outfitters Customer Support System

51. Figure 5-33b Use Case–location Matrix for the Rocky Mountain Outfitters Customer Support System