When a conception of work flow is non specific to information technology, support for work flow is an integral a share of groupware software.

Distinction may be processed between "scientific" & "business" work flow paradigms. When a previous is mostly caring using throughput of information across various algorithmic rule, applications & services, a latter center scheduling project executions, ensuring dependencies which are then non necessarily information-caused & can include individual professionals.

Scientific workflows found wide acceptance in the fields of bioinformatics and cheminformatics in the early 2000s, where it with success met a require for multiple interconnected information, treating of multiple formatting & big information quantities. Likewise, a paradigm of scientific workflows was just about a easily-established tradition of Perl scripting in life-science search organization, therefore this adoption represented the natural come out towards the supplementary integrated infrastructure setup.

Business workflows come more generic, existence breathe to represent any structuring of tasks, & are equally applicable to project programming in the software system application server and organizing a paper document trail inside an organization. Their origins date back to the 1970s, when it were strictly paper-depending, & a information from either that time period processed a transition to modern IT infrastructure systems.

As a way of bridging a gap between them, important effort is existence put into defining workflow patterns that can be utilized to compare & counterpoint different work flow engines through each one domains.

Workflow systems
Workflow systems are defined as "systems that help organizations to specify, execute, monitor, and coordinate the flow of work cases within a distributed office environment".

A rules contains deuce basic components: foremost component is the work flow modeling component (every now and again known as a specification module or even a build instance body), which enables administrations & analysts to define run & activities, analyze & simulate the two, & assign the two to humans. A 2nd component is the work flow execution component, for instance known as a run-time system. It consists of a execution interface seen by prevent-users & a work flow engine, an execution environment which helps around coordination & performing the processes and activities.