Douglass [12], or in Analysis
Patterns by M. Fowler [15].
I ??™ d like to introduce some modeling patterns from the area of activity diagrams at
this point. There are only few patterns from this environment yet. All patterns that I
will present have proven in practice and again, and they are independent of whether
you model system fl ows, hardware fl ows, software fl ows, or business process fl ows.
The Detour pattern describes a fl ow that frequently occurs in activities with
object fl ow. An action, A , has an output pin for object S . The object is not required
by the action immediately following, but only at a later point in time.
The rules of the token fl ow ( ??? game of marbles ??? ) enable a simple and elegant
solution ( Figure 2.94 ). Action A
gets two outgoing edges. One is the object fl ow
that transports object S to the desired destination. The other edge is a control fl ow,
which is responsible for the fl ow sequence. In our fl ow pattern in Figure 2.94 ,
action B starts after action A . The object token, S , remains in the output pin of
A , because action C ??”the target node of S ??”is not ready yet.
Pages:
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292