Modelling Events
Jump to navigation
Jump to search
Start and End Events
Explicit vs Implicit start and end events
Start Event and Pools
Process Trigger
Single Event
Multiple Start Events
Timer Start Event
Multiple End Events
Terminate Event
Alternatives to Terminate Event
- Terminate event can leave data in an inconsistent state
- It should be avoided if possible
- Below an alternative to the scenario above
Intermediate Events
Timer Event
Messages
Message and Service Task
Messages Quiz
Exercise
Rewrite the scenario above using 4 intermediate messages
Link Event
- Target must have:
- outgoing sequence flows
- no incoming sequence flows
- Target and Source Link Events should have the same name
- There should be only one Source corresponding to one target of the same name
- Can be used between lanes, but cannot be used between different pools
Boundary Events
Timers
Messages
Exercise
- Model a sub-process "Write a Report". When employee cannot finish a report in 2 days, you terminate the sub-process and notify the manager
- If the message from the client arrives "report not needed", the sub-process should finish without notifying the manager
Non-Interrupting Boundary Events
Execise
- Modell a process "Bake Pizza", if the preparation goes more than 30 min, notify customer wihtout interrupting the sub-process
- If the customer (after being notified after 30min) notify the pizza company that they do not want the pizza anylonger, the pizza preparation sub-process should terminate.
Sub-process and Start Event
Exercises 1
- Map the Ordering Pizza in a restaurant processes.
- Use names: Customer, Waiter, Chef, pizza order, pizza, money, receipt
- Use lanes only (one pool)