Books for you

Each action is defi ned
such that a modeling tool can make a runtime environment available. Describing
FIGURE 3-40
Example for limiting the pin buffer.
act Produce six-pack (section)
Fill
bottle
Bottle
[filled]
Bundle
six-pack
Bottle
{upperbound6}
Six-pack
Six-pack
FIGURE 3-41
Example for the stream property of a pin.
act Mail parcel (section)
Put stamp on
parcel {stream}
Parcel
...
{stream} {stream}
{stream}
Parcel
Parcel Parcel
179 3.6 The Activity Diagram
each of these actions here would go beyond the scope and volume of this book.
You fi nd an extensive description of all these actions in [60].
I limit my discussion of these actions here to the so-called CallBehaviorAction ,
the OpaqueAction , and the actions used to send and receive signals ( SendSignal
Action and AcceptEventAction ). They show the concept and explain why actions like
identify customer are possible in use case fl ows, and what ??™ s formally behind it.
As its name suggests, the CallBehaviorAction invokes a behavior. This can be a
state machine or an activity, for example.


Pages:
335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359