This document describes briefly how to translate certain workflow patterns into the simulation language Arena. The patterns used for translation are described in  and . We refer to these references to learn more about workflow patterns. Because of the complexity of the simulation program Arena, we refer to  to learn more about Arena. This document is understandable without the use of books or websites, but a bit of experience with Arena would be preferable.
Every modelling language has its own specific advantages and disadvantages. Arena has one major disadvantage when modelling workflow patterns; the way it deals with variables and attributes. The next chapter will give an explanation with an example to make this point clear.
This document describes six groups of workflow patterns that have been translated. Each group consists of a certain number of patterns with an own specific behaviour. The six groups are:
1. Basic control patterns
2. Advanced branching and synchronization patterns
3. Structural Patterns
4. Patterns involving multiple instances
5. State-based patterns
6. Cancellation patterns
For each workflow pattern a short description will be given. We used the Petri net notation to give an example of the patterns and refer to  for a flash animation of each pattern that shows the behaviour of each pattern in a very clear and understandable way. Finally each pattern will end with an explanation how to model the pattern in Arena. A short description will be given how the pattern can be modelled or why the patterns cannot be modelled in a straightforward manner in Arena. Then the graphical notation in Arena will be shown and tables with the settings for each building block will make this document reliable in a sense that it is repeatable.
After the translation of the individual patterns, a real life case study will be modelled in Arena. The case study used, is described in [4, page 179]. The workflow and properties of the workflow including the resources will be given, and the direct translation of this workflow in Arena will be described. Finally a conclusion will be derived.
|Place of Publication||Eindhoven|
|Publisher||Technische Universiteit Eindhoven|
|Number of pages||35|
|Publication status||Published - 2006|
|Name||BETA publicatie : working papers|