Workflow pattern
A workflow pattern is a specialized form of design pattern as defined in the area of software engineering or business process engineering.
≈ 3 min read
Names in other languages
No names in other languages are held for this entry yet.
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
A workflow pattern is a specialized form of design pattern as defined in the area of software engineering or business process engineering. Workflow patterns refer specifically to recurrent problems and proven solutions related to the development of workflow applications in particular, and more broadly, process-oriented applications.
Multiple Instances (MI)
MI without synchronizing - generate many instances of one activity without synchronizing them afterwards MI with a prior known design time knowledge - generate many instances of one activity when the number of instances is known at the design time (with synchronization) MI with a prior known runtime knowledge - generate many instances of one activity when a number of instances can be determined at some point during the runtime (as in FOR loop but in parallel) MI without a prior runtime knowledge - generate many instances of one activity when a number of instances cannot be determined (as in WHILE loop but in parallel)
State-based patterns
Deferred Choice - execute one of a number of alternative threads. The choice which thread is to be executed is not based on data that is available at the moment when the execution has reached the deferred choice, but is rather determined by an event (e.g. an application user selecting a task from the worklist, or a message being received by the process execution engine).
Interleaved Parallel Routing - execute a number of activities in any order (e.g. based on availability of resources), but do not execute any of these activities simultaneously. Milestone - allow a certain activity at any time before the milestone is reached, after which the activity can no longer be executed.
Cancellation Patterns
Cancel Activity - stop the execution of an enabled activity Cancel Case - stop the execution of a running process Cancel Wait - continue execution of a running process without prior completion event The above workflow patterns have been used to evaluate the functionality of commercial products supporting the development of process-oriented applications. They have also been used to evaluate a number of proposed standards, including BPEL, BPMN, UML Activity diagram, XPDL, etc. It has been noted that not all these patterns are relevant in all application domains, so care must be taken when using the above workflow patterns to select a particular language or system for a given application.
The workflow patterns have also been used as initial requirements in the design of a workflow language and open-source system called YAWL (Yet Another Workflow Language). Several extensions to the above set of workflow patterns have been proposed.
In particular, the same research groups that developed these patterns, have also proposed a set of Workflow Data Patterns, Workflow Resource Patterns, Workflow Exception Handling Patterns, and Service Interaction Patterns.
Text derived from https://en.wikipedia.org/w/index.php?oldid=1346297318 under CC BY-SA 4.0; modifications have been made.