Figures

Use Case Driven Object Modeling with UML:
A Practical Approach



Chapter One:

Figure 1-1: The ICONIX Unified Object Modeling Approach 1
Figure 1-2: Requirements Analysis 13
Figure 1-3: Analysis and Preliminary Design 14
Figure 1-4: Design 15
Figure 1-5: Implementation 16

Chapter Two:

Figure 2-1: Nouns in Example System Requirements 20
Figure 2-2: First Set of Candidate Classes for Example System 21
Figure 2-3: Refined Set of Candidate Classes 22
Figure 2-4: Candidate Classes After Further Refinement 23
Figure 2-5: Class Notations 24
Figure 2-6: Generalization of Trade Class 25
Figure 2-7: Generalization of Investment Class 26
Figure 2-8: Candidate Associations 27
Figure 2-9: Association Notation 28
Figure 2-10: Aggregation 29
Figure 2-11: Association Class 30
Figure 2-12: Oversize Trade Class, Ripe for Factoring 31
Figure 2-13: Helper Classes (Part 1) 32
Figure 2-14: Oversize Investment Class, Ripe for Factoring 33
Figure 2-15: Helper Classes (Part 2) 34
Figure 2-16: Analysis-Level Class Diagram 36
Figure 2-17: Requirements Analysis Checkpoint 1 38

Chapter Three:

Figure 3-1: Use Case Diagram 44
Figure 3-2: Sample Screen Mockup 47
Figure 3-3: Windows Navigation Diagram Elements 48
Figure 3-4: Sample Windows Navigation Diagram 48
Figure 3-5: Linking Files to Use Cases Within Rational Rose 49
Figure 3-6: Use Case Factoring 56
Figure 3-7: Use Case Diagram for Example System 60
Figure 3-8: Package Diagram for Example System 61
Figure 3-9: Requirements Analysis Checkpoint 2 63
Figure 3-10: Analysis and Preliminary Design Checkpoint 1 64

Chapter Four:

Figure 4-1: Robustness Diagram Symbols 74
Figure 4-2: Robustness Diagram Rules 75
Figure 4-3: Use Cases for Example System 76
Figure 4-4: Robustness Diagram for Perform Order Entry Use Case 78
Figure 4-5: Robustness Diagram for Enter Buy Trade Use Case 79
Figure 4-6: Robustness Model / Static Model Feedback Loop 82
Figure 4-7: Static Model After Robustness Analysis (Part 1) 84
Figure 4-8: Static Model After Robustness Analysis (Part 2) 85
Figure 4-9: Analysis and Preliminary Design Checkpoint 2 86

Chapter Five:

Figure 5-1: Sequence Diagram Elements 93
Figure 5-2: Building a Sequence Diagram 95
Figure 5-3: Starting the Sequence Diagram (Step 1) 97
Figure 5-4: Adding Entity Objects (Step 2) 99
Figure 5-5: Adding Actors and Boundary Objects (Step 3) 100
Figure 5-6: CRC Card 104
Figure 5-7: Sequence Diagram for Enter Buy Trade Use Case 107
Figure 5-8: Sequence Diagram for Perform Order Entry Use Case 109
Figure 5-9: Design-Level Class Diagram 114
Figure 5-10: Design Checkpoint 1 115

Chapter Six:

Figure 6-1: Collaboration Diagram 122
Figure 6-2: State Diagram 125
Figure 6-3: Design Checkpoint 2 128

Chapter Seven:

Figure 7-1: Billy Bob's Behavior 134
Figure 7-2: Objects Associated with Billy Bob 135
Figure 7-3: Requirements Tab Within Rational Rose 139
Figure 7-4: Traceability 141
Figure 7-5: Requirements Analysis Checkpoint 3 142
Figure 7-6: Design Checkpoint 2 143

Chapter Eight:

Figure 8-1: Component Diagram 149
Figure 8-2: Design-Level Class Diagram Excerpt 150
Figure 8-3: Enter Buy Trade Sequence Diagram with Headers 151
Figure 8-4: How Our Sample System Performed 155
Figure 8-5: Tracking Our Example System's Diagrams 157
Figure 8-6: Implementation Checkpoint 1 157



ICONIX Software Engineering, Inc./2800 28th Street, Suite 320/Santa Monica, CA 90405/Tel (310)458-0092/Fax (310)396-3454/email: umltraining@iconixsw.com