2. 2
Outlines
• Activity
• Subprocess
• Gateway
• Event (start , end)
• Sequence Flow and Message Flow
• Swimlanes (pool, lane)
• Data Object and Data Store
• Documentation, Text Annotation, and Group
3. 3
Activity
An activity represents a unit of work performed in the process.
Every activity is either: a task (atomic) or a subprocess (compound).
Task
A task represents an action, not a function or state. It should be labeled VERB-NOUN.
BPMN 2.0 defines task types
Activity and Task
Check stock
Send request
Receive payment
5. 5
Parallel Box and Ad-Hoc Subprocess
• denoted by a tilde marker at the
bottom.
• not all of the child activities must be
performed in order to complete the
ad-hoc subprocess
• when the subprocess starts, all of its
child activities are enabled to start in
parallel
• can be completed in any order
• subprocess must be complete
A parallel box or ad-hoc subprocess may have no start events
6. 6
Call Activity
• formerly called reusable subprocess
• call activity has a thick border, while subprocess has a thin border
• It is applied when you have some subprocess used in more than one
process
7. 7
Gateway
Gateway, the diamond shape, “controls” process flow, splitting it into
alternative paths.
Two common Types of Gateways:
• Exclusive Gateway
• Parallel Gateway
“ A gateway does not “make” a decision; it just tests a data
condition”
9. 9
Parallel Gateway
• A parallel gateway also called an AND-gateway
• Parallel paths may either be:
joined (AND-join) also known as synchronizing join or,
separate (AND-split.).
10. 10
Start Event
• Its purpose is to indicate how a process or subprocess starts, the icon in the circle, called trigger
• Message start event should be labeled
• A subprocess MUST have a None trigger
None start event
Message start event
Timer start event
Multiple start event
Multiple-Parallel Start Event
11. 11
None start event
Message start event
Timer start event
Multiple start event
Multiple-Parallel Start Event
Start Event
• Its purpose is to indicate how a process or subprocess starts, the icon in the circle, called trigger
• Message start event should be labeled
• A subprocess MUST have a None trigger
12. 12
None start event
Message start event
Timer start event
Multiple start event
Multiple-Parallel Start Event
Start Event
• Its purpose is to indicate how a process or subprocess starts, the icon in the circle, called trigger
• Message start event should be labeled
• A subprocess MUST have a None trigger
13. 13
None start event
Message start event
Timer start event
Multiple start event
Multiple-Parallel Start Event
Start Event
• Its purpose is to indicate how a process or subprocess starts, the icon in the circle, called trigger
• Message start event should be labeled
• A subprocess MUST have a None trigger
14. 14
None start event
Message start event
Timer start event
Multiple start event
Multiple-Parallel Start Event
Start Event
• Its purpose is to indicate how a process or subprocess starts, the icon in the circle, called trigger
• Message start event should be labeled
• A subprocess MUST have a None trigger
15. 15
End Event
• An end event is always represented as a circle with a single thick border.
• It indicates the end (result) of a path in a process or subprocess.
None End Event
Message End Event
Terminate End Event
Multiple End Event
16. 16
An end event is always represented as a circle with a single thick border.
It indicates the end (result) of a path in a process or subprocess.
None End Event
Message End Event
Terminate End Event
Multiple End Event
End Event
17. 17
An end event is always represented as a circle with a single thick border.
It indicates the end (result) of a path in a process or subprocess.
None End Event
Message End Event
Terminate End Event
Multiple End Event
End Event
18. 18
An end event is always represented as a circle with a single thick border.
It indicates the end (result) of a path in a process or subprocess.
None End Event
Message End Event
Terminate End Event
Multiple End Event
End Event
19. 19
Sequence Flow and Message Flow
• Sequence flow, drawn in the diagram as a solid line connector,
• represents the sequential execution of process steps
• can connect to activities, gateways, and events
• Message flow, drawn in the diagram as a dashed line connector,
• represents communication between the process and an external entity.
• message flow can connect to any type of activity, a Message (or Multiple) event, or
black-box pool.
20. 20
Swimlanes
Pool is a rectangular box
It can be either horizontal or vertical, with the label.
There are two types of pool: process pool ( white-box
pool), and an empty pool, (black-box pool)
it represents a participant in a collaboration.
Lanesare a holdover from traditional swimlane
flowcharts,
used to associate process activities with particular actors
– departments or roles
Pool could has lanesets, in the semantic model, all
associated with the same process level.
A lane in a process level may contain a child laneset. The
child lanes, also called sublanes
21. 21
Data Object and Data Store
• data objects are considered as artifacts
• It represents a local variable in a process level
• Its value is visible to other elements in the
same process level
Data object data store
Temporary Data Persistent Data
• information stored in a database
Data object and data store connect to other model elements through data associations
22. 22
Documentation, Text Annotation, and Group
Documentation
• The BPMN model as a whole and most of its individual elements each contain a
documentation element in the XML
• has no associated graphical element.
Text Annotation
• Text annotation and association are artifacts
• Used to put an annotation in the diagram
Group
• Group is also an artifact.
Task there is no internal subparts in the model
*****************************************************************************************
Subprocess it has subparts defined in the model. this subpart is child-level process.
******************************************************************************************
the child-level expansion – is defined within the parent-level process or independently. If you have some subprocess that is used in more than one process, it is best
to define it independently – in its own file – and then call it from each process that uses it, rather than replicate and embed the definition within each calling process.
Without a gateway, when a BPMN activity has more than one outgoing sequence flow, the process splits into multiple parallel paths.
“Exclusive” means only one of its outgoing sequence flows, or gates, is enabled in any instance.
trigger identifies the meaning of the process
********************************************************
A subprocess MUST have a None trigger, no icon inside, because a subprocess is not initiated by an event but by an incoming sequence flow.
*********************************************************
None trigger means the process trigger is unspecified
Message start event means that the process is triggered upon receipt of a message from outside the process
Timer start event, with a clock icon, signifies a scheduled process, should be labeled to indicate the schedule, such as Monthly or Fridays 4pm.
Multiple start event with a pentagon, means that the process could be initiated by any one of multiple triggers
Multiple parallel start event means the process requires all of the triggers to occur before instantiation.
A Message end event signifies that a message is sent upon reaching the end event /
A Terminate end event will ends the whole process or subprocess, even if other parallel paths are still running.
Data object It represents a local variable in a process level, when the process level ends, the data object goes away
******************************************************************************************************************
Data store It can be queried or updated, It does not disappear when a process level, or the process as a whole, ends
documentation has no associated graphical element. In other words, it doesn’t show up in the diagram.
*************************************************************************************************************
Text annotation and association are artifacts, meaning supporting information that does not affect process flow.
********************************************************************************************************************
Group drawn around a set of elements in the diagram to indicate some relationship between them.
