Workflow pattern: Difference between revisions

Revision as of 18:46, 1 May 2014

Revision as of 13:59, 5 May 2014

Line 11:

Workflow patterns can be applied in various context, hence the conditions for use must be explicitly defined and shown in order to prevent misinterpretation.<ref>http://ceiton.com/CMS/EN/workflow/system-centric-bpms.html#Classification</ref>

== Van der Aalst classification <ref>http://www.workflowpatterns.com </ref>==

A well-known collection of workflow patterns is that proposed by [[Wil van der Aalst]] et al. (2003) in their paper ''Workflow Patterns''.<ref>[[Wil van Der Aalst]], [[Arthur H.M. Hofstede]], Bartek Kiepuszewski, and Alistair P. Barros (2003). [http://www.headlessbrick.org/mediawiki2/images/4/48/WorkflowPatterns-van_der-Aalst-2003.pdf "Workflow Patterns"]. In: ''Distributed and Parallel Databases'' 14 (1): pp. 5--51. {{doi|10.1023/A:1022883727209}}.</ref> with earlier versions published in 2000-02. This collection of patterns focuses on one specific aspect of process-oriented application development, namely the description of [[control flow]] dependencies between activities in a workflow/process. These patterns are divided into the following categories:

Line 85:

==Workflow systems implementing patterns ==

*[http://www.tavaxy.org Tavaxy] <ref>{{cite doi|10.1186/1471-2105-13-77}}</ref> is a cloud-based workflow system that implements a pattern-based approach for enabling interoperability between Galaxy and Taverna, two workflow engines popular in the bioinformatics ___domain

.,<ref>{{cite doi|10.1145/1833398.1833400}}</ref>,

*[[YAWL]], Yet An Other Workflow Language,

*[[Cameleon (programming language)]], Workflow based graphical language for functional programming.