BPMN 2.0 Conventions - EN 1
BPMN 2.0 Conventions - EN 1
MODELING WITH
BPMN 2.0
Overview of
the conventions
Increase the competitiveness of your company and face the challenges of the digital world!
With the help of innovative business processes, digital transformation is easily established in
your everyday work.
4 | © GBTEC Software AG 2020
Business Process Management in All Its Facets
Operatives
Operative IT-based
Characteristics: Design and Characteristics: Definition of business
analysis of processes, increase of Prozessmanagement
process management process management requirements for IT processes, use of
effectiveness and efficiency in BPM as a basis for process automation
processes, use of process- Basic activities for the introduction and Design and implementation of business and digitization, introduction of ERP
oriented success potentials. operation of BPM in an organization processes with the help of information systems using business process
technology blueprinting, establishment of process-
oriented enterprise architecture
management.
Pools represent a process participant that is superior to the Pools are usually further subdivided via lanes. Lanes represent
lanes and "coordinates" the process flow within the pool. process participants and can, for example, be organizational
They cover the entire process and assign the tasks contained units (sales, personnel, etc.) or roles (department managers,
to the responsible lanes. clerks, etc.). Unlike pools, they can be arranged hierarchically.
Pools Lanes
1. Exactly one complete process is modeled in each pool. 1. Lanes are displayed above each other across the entire
2. Overlapping pools should be represented across the width of the pool.
entire model width (not necessarily in BPMN 2.0). 2. The height of the lane depends on its content.
3. The height of the pool depends on its content. 3. Lanes can be placed inside each other to show
4. Message flows are only allowed between pools. hierarchical relationships.
Sequence flows are only allowed within pools.
5. If several pools are located in one diagram, they are
connected by message flows.
Events Activities
Events are occurred, business-relevant states and can start a An activity represents a work step.
process (start event), occur or be triggered during the process
(intermediate events) or complete it (end event).
Activities are actively Events occur and are Activities and events are connected via sequence flows that
performed and formulated. passively formulated. enter on the left of the object and exit on the right.
Activities/ events are always modeled in pools/ lanes. A process usually starts with a start event and ends with one
or more end events.
Exclusive gateways are used when exactly one condition may occur
("either/or"). When merging, exactly one incoming process path must be
fulfilled.
Inclusive gateways are used when one or more process paths can be
followed ("and/or"; path combinations).
In addition to the three most used gateways, which are explained in more detail here, there are other, less common ones. A
more detailed explanation of those gateways, including modeling conventions, can be found in the conventions manual.
Labeling is usually done in the form of a Parallel gateways should not be labeled. Labeling is usually done in the form of a
question at the splitting gateway or in the question on the splitting gateway or in
form of conditions at the edges ("goods the form of conditions on the edges
are ok" or "goods are not ok"). Merging ("Customer wants product info",
gateways are not labeled. "Customer wants personal advice",
"Customer wants quote").
Merging gateways are not labeled.
Usage Pairing
Gateways should be used both when splitting into multiple Opening and closing gateway should usually be the same
process paths and when merging multiple process paths. ("pairing"). Explanations of exceptions can be found in the
(Even though BPMN 2.0 does not make this rule mandatory, it manual.
makes it easier to read).
It may be split into any number of process paths. Gateways must be used for loops and jumps back (usually the
exclusive gateway).
Annotations are textual input fields for important comments The group is a visual element that groups objects related in
that should be shown directly in the process. content. It is used only for a better understanding of the
model; it has no effect on the flow logic.
General Check
Embedding: Is the model correctly embedded in the landscape?
Content: Has only content relevant to the project's objective been modeled?
Attributs
Are the general must attributes maintained for models and objects?
General Check
Pools/ lanes: Were pools/lanes used according to the conventions? Does each pool contain
a complete process?
Sequence flow: Does the process have at least one start and one end event? Were
gateways used properly?
Special symbols: Were the special symbols used in activities, events as well as pinned
events?
Other artifacts: Have the object types been used correctly?
Are all object types (except for data objects) modeled within pools/lanes?
Have data objects been embedded in the processes according to the applicable case?
Contact
Mastering the relevant instruments
Christoph Windgassen
Training Coordinator
training@gbtec.de