○
○
●
●
○
○
○
○
○
○
○
○
●
●
●
●
●
●
●
●
●
○
●
○
●
○
●
●
●
●
●
●
●
●
●
●
●
●
●
A one task should not be responsible
for multiple message flows.
We should model it into detail using
dedicated events or tasks.
●
●
○
○
●
●
●
●
●
●
*It is totally equal only if we can change internally Check credit
Top 10 Mistakes
Inappropriate Naming
Here is a task used instead of an event.
Clumsy name of the task signals us that we are using wrong modeling concept.
Lanes should express the role which is responsible for performing task.
Not the name of task itself.
Exception Handling
The process should handle exception appropriately
(try to resolve exception, or terminate properly other tokens and inform other processes if necessary).
Messages in Pool
Variants of hidden message flow.
Boundary Events
Even task with boundary event
has to have standard outgoing
sequence flow.
Timer does not say how much time it takes to finish task. It just
says what should be done when timebox expires. Therefore,
there has to be outgoing sequence flow.
Deadlock
If after XOR gateway token flows to B then parallel gateway will wait forever for token from A.
●
●
●
●
● Create one BPMN L2 model (it is prefered when you extend your L1
process):
○ 8+ activities
○ 4+ gateways, 2 different types
○ 3+ events, 2 different types (beside start a end)
○ 1+ data object
○ 2+ text annotations
○ 2+ pools, 1 as „blackbox“, 2+ roles (swimlanes)
○ 1+ exception and appropriate handling
● Submit printed version with UČO and name of seminar group to the
box called PV207 next to entrance to room D1 (before 30.3. 5:00 PM)
● Submit electronic version of diagram in Signavio as PDF to IS MUNI to
folder "Homework 2" as <surname>_bpmn.png (before 30.3. 5:00 PM)