Page 343 -

13.1 Business Process Maps 325

Fig. 13.3 A WF-net consisting of 12 atomic activities partitioned over three subprocesses x, y,
and z. The average frequency of each activity is shown. For instance, activity h is executed for
60% of the cases

Fig. 13.4 Top-level view on
the hierarchical WF-net
showninFig. 13.3

languages such as BPMN, YAWL and EPCs. From a design point of view, hierar-
chical decomposition makes perfect sense. When designing a system it is important
to ensure consistency between different levels and the possibility to “flatten” models
provides clear execution semantics.
However, when viewing a process model it is important to be able to zoom out
to see fewer details and zoom in to see more details. This implies that the view is
not static, i.e., activities should not be statically bound to a particular level chosen
at design time. Moreover, when abstracting from infrequent low-level behavior the
corresponding connections at higher levels should also be removed. For instance,