Werkvloei: Verskil tussen weergawes

As a way of bridging the gap between the two, significant effort is being put into defining ''[[workflow patterns]]'' that can be used to compare and contrast different workflow engines across both of these domains.

 

A workflow can usually be described using formal or informal flow diagramming techniques, showing directed flows between processing steps. Single processing steps or components of a workflow can basically be defined by three parameters:

#[[input]] description: the information, material and energy required to complete the step

Especially when the components are non-local services that are invoked remotely via a computer network, like [[Web service]]s, additional descriptors like [[Quality of service|QoS]], [[availability]], etc. have to be considered, too.

 

''Main article: [[Workflow application]]''

 

Many software systems to support workflows in particular domains exist. Such systems manage tasks such as automatic routing, partially automated processing and integration between different functional software applications and hardware systems that contribute to the value-addition process underlying the workflow.

 

*[[Business process management]], [[Business process modeling]]

*[[Business-driven development]]

<references/>

 

*Layna Fischer (ed.): 2007 BPM and Workflow Handbook, Future Strategies Inc., ISBN-13: 978-0-9777527-1-3

*Layna Fischer: ''Workflow Handbook 2005'', Future Strategies, ISBN 0-9703509-8-8