5
Standard
UML
models and supporting diagrams
Diagrams Models
3: Message 2: Message
5: Message Person
Component 1 Component 3
Component 3
Component 2
Component diagram
Component 1
Package 2
Deployment diagram
Component 2
1: Message
Object
2
Object
3
Collaboration diagram
Object
1
Actor 2
Case 1
Case 3
System
Use case diagram
Case 2
Actor 1
Object
3
entry/action Action
State Name
State
End
State diagram
Start
do/activity
exit/action
event/action(arguments)
4: Message
Attributes
T
Class
Bound class
Class diagram
Object 1 Object 2
Message 1 Person
Message 2
Message 3
Sequence diagram
Action
State 1
Action
State 2
Action
State 3
Action
State 4
Action
State 4
Activity diagram
<
>
Attributes
Operations
Operations
Diagrams
Use case
Analysis
Design
Implementation
Deployment
Test
Package 1
Test Planning and Management
51
By using such a model with a customer it becomes far easier to define requirements at levels satisfactory
to all stakeholders. Such a model can provide a baseline for system test objectives (Figure 4.7).
These solutions imply the following approach:
1. Specify new and reusable domains. This can include both server and client domains as well as legacy code.
2. Create Use cases using use case diagrams supported by sequence diagrams, providing a
Platform-
Independent Model
(PIM) for each domain.
3. Create static models using class diagrams for all the objects in each PIM and determine the relations
between the classes.
Pages:
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175