Modelling at the event response level (30%) Flashcards
What do arrows show at the event-response level compared to the enterprise level?
Event response/model: arrow shows flow betweentasks (swimlane)
Enterprise level/map: arrow show dependencies between processes
For all business processes we need to document:
- Actors
- Tasks
- Business rules
- Customer
- Events that trigger
- Outcomes
Actors
- Represent a set of responsibilities
- Perform tasks
- Represent people/groups/businesses/IT systems
- Actors become swimlanes
Business Rules
Business rules determine how the work is done and which outcomes are
achieved. They constrain how work is done and the decisions that are made
Rules are created:
External constraints e.g. legislation
Best practice
Experience
Organisation policy
Operational guidance
Customer
Receives direct benefit from the process
- Can be internal/external
- May be more than one
Business Events
Trigger processes
3 Types:
Internal
External
Timebased
Relationship between organisation/processes/tasks
The organisation is the sum of its processes
The process is the sum of its tasks
There should be minimum coupling
Relationship between levels
Process dependencies (L1) comprises of process flows (L2) each of which comprises of tasks (L3)
Why is process modelling important?
Offers a common unified language for communicating processes and the complexity of task-flow, events, rules and responsibilities
Also good for training/knowledge transfer etc
BUT: This can only happen if internal (and ideally, external) stakeholders use the same consistent, standard notation
2 Business Process Notation
BPMN
- Capable of modelling the most complex of processes
UML (Activity Diagram)
- Simpler to use than BPMN
Symbols/Notations for BPMN
Flow objects – such as events, activities (tasks) and gateways
Connecting objects – denoting sequence flow, message flow, and association
Pools and lanes – where a pool represents the process while a lane defines the activities each participant is responsible for performing
Artefacts – these encompass data objects, groups, and annotations
UML
Designed for software modelling
It can show: triggering events, actors, tasks, decisions and process flows
Swimlanes
Labelled swim lanes are used to show who or what is responsible for carrying out each task in the process
If an IT system carries out some of the tasks that will be shown as a swim lane
Initial Node
The start of the process is shown with an ‘initial node’ and the event written next to it
There should only be one start for a process
Tasks
Each task in the process is shown as a round-cornered rectangle expressed as a verb-noun phrase
A task is something done by one person (actor) in one place at one time (OPOPOT)