Marlon Dumas University of Tartu [email protected] Slides prepared in collaboration with Marcello La Rosa (QUT) With contributions from Remco Dijkman (TU/e) From Conceptual to Executable BPMN Process Models A Step-by-Step Method
Where are we? 2
The business-engineering gap… 3
Conceptual “to-be” process models • are made by domain experts • provide a basis for communication amongst relevant stakeholders • must be understandable • must be intuitive and may leave room for interpretation • contain purely a relevant set of process information Executable process models • are made by IT experts • provide input to a process enactment system - BPMS • must be machine readable • must be unambiguous and should not contain any uncertainties • contain further details that are only relevant to implementation Two sides of the BPM story 4 “to-be executed” process model
Bridging the gap: A five-step method 1. Identify the automation boundaries 2. Review manual tasks 3. Complete the process model 4. Adjust task granularity 5. Specify execution properties 5 Adapted from teaching material of Remco Dijkman, TU/e.
Running example Customer Supplier 1 Supplier 2 Seller 6
1. Identify the automation boundaries Principle : not all parts of a process can be automated. -> Start by identifying each task’s type: Automated tasks User tasks 2 1 Manual tasks 3 8
In BPMN: specify task markers Automated tasks 9 User task Manual task
In our example… automated user manual
2. Review manual tasks Principle : if it can’t be seen by the BPMS, it doesn’t exist.
You've reached the end of your free preview.
Want to read all 35 pages?
- Fall '19
- Business process modeling