Obviously modeling such a use
case doesn ??™ t make sense ( Figure 2.54 ).
2.4 Modeling Use Cases
FIGURE 2-54
Too abstract!
uc [package] SysML book [meaningless generalization]
Do something
{abstract}
Start car usage Add route
FIGURE 2-53
Use case relationships for ??? route. ???
uc [package] Routes
Add
route
Modify
route
Delete
route
Essence
Select route
Edit route {abstract}
Confirm edited route {abstract}
Edit
route
{abstract}
88 CHAPTER 2 The Pragmatic SYSMOD Approach
The include relationship described at the beginning of this section is much
more important than the generalization. It is always a good idea to follow the
guideline ??? the include relationship has to be searched for while the generalization
relationship is found ??? in the modeling process. This means that you should search
for potential redundancies in a targeted way, while you should model a generalization
only if you found it purely ??? by chance. ???
2.4.5 Model Use Case Flows
Modeling use case flows is shown in Table 2.13 .
The steps completed so far in our approach have provided us with a broad
overview of the system.
Pages:
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208