Petri Netze

aus wikipedia: Petri-Netz:

Ein Petri-Netz ist ein mathematisches Modell von nebenläufigen Systemen. Es stellt eine formale Methode der Modellierung von Systemen bzw. Transformationsprozessen dar. Die ursprüngliche Form der Petri-Netze nennt man auch Bedingungs- oder Ereignisnetz. Endliche Automaten und Bedingungs- oder Ereignisnetze sind gleich mächtig. Petri-Netze wurden durch Carl Adam Petri in den 1960er Jahren definiert. Sie verallgemeinern wegen der Fähigkeit, nebenläufige Ereignisse darzustellen, die Automatentheorie.

YAWL – yet another workflow language

taken from the official website yawl-system:

The last decade observed an increasing number of products entering the Business Process Management (BPM) market, all claiming to address every conceivable workflow issue an organisation may face.  Yet organisations still encounter problems sourcing a BPM solution capable of capturing processes that require advanced concurrency concepts.

YAWL (Yet Another Workflow Language) is an original and sophisticated workflow language developed at QUT’s BPM research group in collaboration with Eindhoven University of Technology.  YAWL builds on the insights gained from the workflow patterns research and combines it with the powerful language of Petri-nets.  The result – the ultimate mix of theory and practice.

YAWL provides a very powerful, yet fundamentally simple language for process modellers to describe complex control flow relations between business processes.  Consequently, YAWL enables businesses to own and manage very flexible and dynamic business processes.

YAWL has many strengths that can be listed.  YAWL is expressive – it is the first language to provide comprehensive support for all of the workflow patterns.  YAWL is visual – it is composed of visual elements.  Business processes are represented graphically making them more intuitive to the viewer.  YAWL is concise – it is solution oriented, not technology oriented, hence its constructs are designed to align with the needs of the problem solver.  YAWL is flexible – YAWL models are expected to enable web service invocation in the near future.  Workflow can then occur across organisational boundaries without relying on a particular middleware or the need for complex rescripting.  YAWL is reliable – YAWL has a formal foundation, based upon Petri-nets.  This foundation almost guarantees that workflow specifications do not become ambiguous or unnecessarily complex – a characteristic generally not found in a workflow system.