Workflow Management Kap. 5. Architecture of Workflows Wil van der Aalst has copyrights to almost all figures in the following slideshow made by Lars Frank. Most of this slideshow is self study!

Basic idea: Separation of Control and Execution

Workflow Management Systems:

Technical infrastructure:

WFMC Reference model:

Data inside a WFS:

Users of a WFS:

Why will interfaces 3 and 4 in a WFMS give problems if more than one database are updated?

Potential problems around interface 3: The solutions are flexible transactions!

Realization of a designed workflow:

Adoptive workflows is not for sale and therefore most of the subject is self study!

Adoptive workflow systems are a research object between the two extremes. What would you do in practice if you need an adaptive workflow system and you cannot buy such a software product?

Changes: type, scope, and time. Tidshorisont

Individual changes:

Structural changes:

Problem 1: Correctness.

Correctness 2:

Errors resulting from change:

Some systems:

An WFMS example. Staffware:

End of session. Thank you !!!

Staffware icons:

Staffware icons 2:

Staffware process diagram:

Staffware process diagram 2:

Staffware definitions:

Worklists:

Workitems:

Cases:

Two other examples:

COSA Network editor:

COSA User Editor:

COSA MemoBox:

Action Workflow 1:

Action Workflow 2:

Additional tools:

BPR tool: Protos (Pallas Athena):

4 views:

Simulation tool: ExSpeect (Bakkenist):

Simulation output:

Verification tool: Woflan (ETU):

Example 1:

Example 2:

Example 3:

Example 4:

Example 5:

An integrated tooltest:

End of session Thank you !!!

Exercise 4.8 E-business: (Dvs. bevis soundness property ved hjælp af afledninger).

Which e-commerce model will you use in practice? Example with travel agency: