There is no
single recipe for fi nding the best solution. So every workshop participant would be
right. Selecting an actor or the system boundary is a pure project decision.
What interaction partner do you want to focus on? And which blocks really
belong to your system or project? Information about other potential actors won ??™ t
necessarily be lost. If this is the information you think is important, then you
should document it, e.g., in a comment.
Figure 2.20 shows you a different way. The relationship marked as fl ow
between the actors car service employee and car management system represents
an information fl ow. The car service employee transmits a status request
to the car management system. Notice that you are outside the system under
development. Your modeling focus is within the system boundaries. So don ??™ t
invest too much work into modeling relationships between actors.
If you do have a bigger modeling need between actors it might be a good idea
to move the system boundary further outward. The actors would then become
part of the system and fall within the modeling focus.
Pages:
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145