BPMN 2.
0 - Business Process Model and Notation
Events
Start Event Caught Intermediate Event Threw Non-Interrupting Boundary Event Connected Non-Interrupting SubprocessStart Event Interrupting SubprocessStart Event End Event
Innovator for Business Analysts
Gateways
Sequence Flow: Shows the flow in a process. The sequence flow cannot cross a pool boundary but can switch between lanes. Message Flow: Shows the flow of messages between two participants. It must always connect to separate pools. Sequence Flow Default Flow Message Flow Conditional Flow
Process and Collaboration
Collaboration: Describes the interaction between participants (in this example: customer, company and supplier). Process: Describes the flow of activities in an organization (in this example: quote creation). Lane: A lane is a sub-partition within a process and will extend the entire length of the pool (in this example: clerk and approver).
Exclusive (Either OR)
Parallel
Inclusive (OR/AND)
Complex
Interrupting Boundary Event Connected
Intermediate Event Caught
Intermediate Event Thrown
Event-Based Event-Based Exclusive Gateways are used to control how the process flows through sequence flows as they converge and diverge within a process. Exclusive: Only one of the paths can be taken Inclusive: None, one or more paths can be taken Parallel: Creates parallel paths without checking any conditions Complex: Can be used to model complex synchronization behavior Event-Based Parallel
Start Event
End Event
Quote Request
None Message Signal Timer Conditional Escalation Error Compensation Cancel Terminate
Quote Creation
Default Flow: Flows through gateways if all other outgoing conditional flows are not true at runtime. Conditional Flow: Enables conditions to be defined without using gateways.
Inclusive: More than one path can be taken Event-Based: Represents a branching point in the process where the alternative paths that follow the gateway are based on events that occur.
Text annotation is shown as displayed in the example.
Data
Provides information about what an activity requires for it to be performed and/or what it produces.
Activities
A task is an atomic activity within a process flow. It is used when the work in the process cannot be broken down to a finer level of detail. Is expected to be performed without the aid of any business process execution engine or any application. User Task: Is executed by a user with the assistance of a software application. Call Activity Global Task: Identifies a point in the process where a global task is used. Activation of a call activity transfers control to the called task. Call Activity Subprocess: Is an independent process that can be called from various processes. Subprocess: Is a graphical object within a process but it also can be opened up to show a lower-level process. Event Subprocess: Is started by an external event. It doesnt have any incoming or outgoing sequence flows. Ad-Hoc Subprocess: The sequence and number of performances for a set of activities is determined by the performers of the activities. Transactions: A transaction is a subprocess that is supported by a special protocol that insures that the activity is completed or canceled.
Data Object
Data Input If a process or subprocess which can be called requires information for it to be performed, this information is modeled using a data input. Data Output The data output is the opposite of the data input. Events or return values which deliver a process are modeled using data outputs. Data Store Reference Can be used as the source or target for a data association. Data Association Data associations move data between data objects and activities.
Link
Service Task: Is a task that uses some sort of service. Business Rule Task: Provides a mechanism for the process to provide input to a business rules engine. Script Task: Is executed by a business process engine. Receive Task: Is a simple task that is designed to wait for a message to arrive from an external participant. Send Task: Is a simple task that is designed to send a message to an external participant.
Markers for Tasks and Subprocesses Loop: The attributes of tasks and subprocesses will determine if they are repeated or performed once. Multi-Instance Parallel: Multiple, performed in parallel. Multi-Instance Sequential: Multiple, performed in sequence. Compensation: Undoes steps which have already been successfully completed.
2010 MID GmbH
www.mid.de
