How? Common things between use case fl ows are described in secondary use cases
and embedded into the primary use cases by means of the include relationship.
Where? The non-redundant use case structure supplies useful hints for optimized,
non-redundant system design.
Guiding questions
?– Which use case steps repeat themselves in other use cases?
?– Which use cases are similar?
SysML elements
Use case diagram, use case, SYSMOD: secondary use case, include relationship,
generalization.
Model use cases
without redundancies
Use cases
[non-redundant]
Use cases
85
Several common fl ow steps between the use cases are very easy to fi nd since
the names of the respective steps are identical. However, if the essences had been
created by several people, which is normally the case, we have to deal with synonyms
and similar things. The same steps do no longer have the same names now.
This is where a glossary comes in handy, since it encourages the use of a uniform
project language. For example, we added to our glossary that our principal
uses the term car rather than auto , vehicle , or rental car .
Pages:
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203