BPMN
Junice B. Ilagan- Japa
Business Process Model and Notation
BPMN is a standardized, graphical notation that models business processes and workflows in a Business
Process Diagram (BPD).
The main goal of BPMN is to provide a notation that is truly understandable by all enterprise users,
from business analysts who create initial sketches of processes, through developers in charge of setting
up the technology that will run these processes, right up to enterprise users who will manage and
supervise these processes.
Originally BPMN was published by Business Process Management Initiative (BPMI). 5
BPMN
Basic Elements
✓ Flow Objects
✓ Connecting Objects
✓ Swimlanes
✓ Artifacts
6
BPMN Basic Elements
Flow objects
- represent the main elements of process diagram.
Activities
Event
Gateway
7
BPMN Basic Elements
Flow objects
- represent the main elements of process diagram.
Activities
8
BPMN Basic Elements
Flow objects
- represent the main elements of process diagram.
Event
9
BPMN Basic Elements
Flow objects
- represent the main elements of process diagram.
Gateway
10
Presentation title 13
BPMN Basic Elements
Connecting objects have the role of connecting object flows with
each other or with other object types.
Sequence Flow
Message Flow
Association /
Data Association
15
BPMN Basic Elements
Swimlanes
- BPMN uses the “swimlanes” concept to partition and organize activities.
Pools represent organizations, e.g. your own company,.
Lanes are organizational sub- structures of pools, representing departments or
roles, for instance.
16
Presentation title 17
Presentation title 18
Presentation title 19
BPMN Basic Elements
Artifacts - provide the capability to show information beyond the basic
flow-chart structure of the Process.
Data Object
Group
Annotation/
Association Text
20
BPMN Rules
1. Start and End Events: Every process must have at least
one start event and one end event.
2. Sequence Flow: Each activity should be connected to at
least one other activity or event with a sequence flow.
3. Gateways: Gateways must have multiple outgoing
sequence flows (for splits) and multiple incoming
sequence flows (for joins).
4. Pools and Lanes: Pools represent different participants
and must not overlap. Lanes can be used to subdivide
pools.
5. Message Flow: Should be used to show interactions
between different pools, not within the same pool.
6. Data Associations: Data objects should be associated
with the activities that produce or consume them.
Presentation title 22
Presentation title 23
24
BPMN Mapping to TOGAF
ADM Phases Phases B, C, and E
• are the most directly related to BPMN, where
detailed business process modeling is
essential for understanding and designing the
architecture.
26
BPMN Mapping to TOGAF
ADM Phases Phases B, C, and E
• are the most directly related to BPMN, where
detailed business process modeling is
essential for understanding and designing the
architecture.
Phases A, D, F, G, and H
• can benefit from BPMN in supporting decision-
making, planning, and ensuring alignment
between the business processes and the
architecture.
29
BPMN Mapping to TOGAF
ADM Phases Phases B, C, and E
• are the most directly related to BPMN, where
detailed business process modeling is
essential for understanding and designing the
architecture.
Phases A, D, F, G, and H
• can benefit from BPMN in supporting decision-
making, planning, and ensuring alignment
between the business processes and the
architecture.
Preliminary Phase
• is about setting the stage, where BPMN might
be established as the standard for process
modeling.
35
36
37
END
BPMN Poster:
http://www.bpmb.de/images/BPMN2_0_Poster_EN.pdf
