INFS1000 Lecture Notes - Lecture 8: Business Process Model And Notation, Lead Time
4 Jun 2018
School
Department
Course
Professor
WEEK 8: BUSINESS PROCESS MODELLING (BPMN)
BPMN IMPORTANT RULES
Task
- Atomic activity
- Represent work performed in this process step
- Usually requires some input and creates an output
Sub Process
- Part of activity image
- Represents a complex activity à Plus symbol indicates it can be
opened for more detail
- Can be detailed in a separate model
Data Object
- Represents flow of physical documents + electronic data across
activities
- Attached to process + message flows
Process Flow
- Aka sequence flow
- Models order of activities (normal flow)
- Activities happen strictly in the order they are connected by
sequence flow events
Message Flow / Data
Flow
- Represents flow of data objects
- Data objects can be attached to process flow arrows à no
separate message is needed
- Message flow only needed when data flows separate from
sequence flow
Start Event
- Every process begins with this
End Event
- Every process ends with at least one end event
Timer Event
- Intermediate event, which can happen anywhere in the process
- Event waits for something to happen (e.g. a specified time to
pass), can be used to model a delay/pause
Parallel Fork / Join
- Read symbol as “AND”
- Outgoing: all paths must be followed + completed
simeltaneously
- Incoming: all activities leading to join need to be fulfilled for
process to proceed
Exclusive Decision /
Merge
- Read symbol as “X-clusive”
- Outgoing: only one path will be followed
- Incoming: process will proceed when any of incoming activities
have been fulfilled
Pools
- Act as containers for processes
- Each pool represents one participant e.g. customer, supplier
- We can leave external pools empty, depending on scope of
narrative and model
Swim Lanes
- Represent internal business roles in a BP
- Used to better visualise the activities carried out by these roles
• NOTE: gateways control the process flow
o Distinguish between splits and merges
§ Split: divides process flow into separate paths –
multiple outgoing flows
§ Merge: brings together process paths – multiple
incoming flows
Document Summary
Usually requires some input and creates an output. Represents a complex activity plus symbol indicates it can be opened for more detail. Represents flow of physical documents + electronic data across activities. Activities happen strictly in the order they are connected by sequence flow events. Data objects can be attached to process flow arrows no separate message is needed. Message flow only needed when data flows separate from sequence flow. Every process ends with at least one end event. Intermediate event, which can happen anywhere in the process. Event waits for something to happen (e. g. a specified time to pass), can be used to model a delay/pause. Outgoing: all paths must be followed + completed simeltaneously. Incoming: all activities leading to join need to be fulfilled for process to proceed. Outgoing: only one path will be followed. Incoming: process will proceed when any of incoming activities have been fulfilled. Each pool represents one participant e. g. customer, supplier.
