However, the focus is clearly on the identifi cation of use cases. This means,
for example, that we won ??™ t especially determine pertaining actors, but only add
them if we already have this information.
In the plenum, we collect the use cases on a metaplan board. This helps us
discover duplicate use cases, synonymous terms, use cases not clearly formulated,
and use cases that are too abstract, too granular, or simply wrong.
We will keep only one card each of the duplicate or synonymous use cases. We
will staple the duplicate cards to the main card each if the cards have additional
information on their back. Otherwise, we can discard them.
A use case that is too granular is part of a larger use case. Again, we will staple
the card to the larger use case if it contains additional information.
A use case that is too abstract can initially be used as a heading for a group of
use cases.
FIGURE 2-36
A use case called ??? show car usage data. ???
2.4 Modeling Use Cases
uc [package] Car usage [show car usage data]
Car
movement data
Show car
usage data
Usage data
Customer Kilometer
72 CHAPTER 2 The Pragmatic SYSMOD Approach
We then take all use cases found and put them into domain-motivated groups
on the metaplan board.
Pages:
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180