- Choose a non-trivial process:
- Approx 10-15 nodes on a diagram.
- At least 2 swimlanes, preferably some gates.
- Imagine that there is a token travelling through the graph, it should not get stuck anywhere.
- Do think about possible multiple start or end events.
- End event means that given instance of a process has ended (either successfully or unsuccessfully), so think about handling exceptions/errors inside process.
- Preferably, follow left-to-right orientation of flow (alternatively, top-to-bottom is acceptable as well).
- 1 actor from use case = 1 swimlane.
- 3rd party pool is a blackbox, only message flows interchange between pools.
- Processes do not remember anything on their own, use data stores if you need to.
Domain Understanding and Modeling
Week 3 - Business Process Modeling
- Why do we model business processes?
- BPMN 2.0 Notation
Slides in English:
Chyba: Odkazovaný objekt neexistuje nebo nemáte právo jej číst.
https://is.muni.cz/el/fi/podzim2023/PA116/um/en/DUM_05_BPMN_ENG.pdf
Recorded lecture in Czech:
Chyba: Odkazovaný objekt neexistuje nebo nemáte právo jej číst.
https://is.muni.cz/el/fi/podzim2023/PA116/um/vi/84695513/
Seminar briefing in English:
Chyba: Odkazovaný objekt neexistuje nebo nemáte právo jej číst.
https://is.muni.cz/el/fi/podzim2023/PA116/um/seminar_briefings/Business_Process_Diagram.mp4
Seminar tasks:
Principles to follow
Check BPM Notation:
Chyba: Odkazovaný objekt neexistuje nebo nemáte právo jej číst.
https://is.muni.cz/el/fi/podzim2023/PA116/um/en/DUM_05_BPMN2_0_Poster_EN.pdf
- Make a business process diagram. [2 pts]
- Make another BPD. It can be a subprocess (decomposition) of a complex task from the first process, if applicable to your diagram. [2 pts]
- For either of them, do a verbal description providing brief explanation of individual steps and context (what data are stored as an outcome of the task, details of a decision-making for a gateway, etc.). [1 pt]