4 Modeling Use Cases
object entirely intuitively. This means that we don ??™ t need object-oriented knowledge
either. Just use the word ??? data ??? if ??? object ??? irritates you. We will turn to block
modeling later in Section 2.5.
Look at the fi rst use case: What result object will identify customer produce?
Right??”a customer. In the positive case, the next step will be check usage right
( Figure 2.61 ). Within this step, an SMS with the authorization request is created and
sent to the reservation center. Of course, the SMS also contains information about
the customer, i.e., the customer object belongs to the incoming data of that step.
Moreover, the step needs information about the car in which the on-board computer
is located, since this also has to be communicated to the reservation system.
This information hides somewhere in the on-board computer. At this point we are
interested only in the fact that we need it; we are not interested in the data source,
since it has no effect on the fl ow. We use an input pin that is not connected to any
edge to express this.
Pages:
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225