cameo business modeler analyst edition user guide...1.2.1 installing cameo business modeler analyst...

USER GUIDE

version 17.0.1

No Magic, Inc.

2012

All material contained herein is considered proprietary information owned by No Magic, Inc. and is not to be shared, copied, or reproduced by any means. All information copyright 2009-2012 by No Magic, Inc. All Rights Reserved.

CONTENTS

1 GETTING STARTED 61.1 Introduction to Cameo Business Modeler Analyst Edition 61.2 Installation 6

1.2.1 Installing Cameo Business Modeler Analyst Edition 61.3 Licensing Information 71.4 Working with BPMN 2.0 Projects 8

2 CONCEPTS 92.1 Common BPMN 2.0 Elements 10

2.1.1 Definitions 102.1.2 Artifacts 10

2.1.2.1 Anchor 102.1.2.2 Association 112.1.2.3 Group 112.1.2.4 Text Annotation 12

2.1.3 Events 122.1.3.1 Start Events 122.1.3.2 Intermediate Events 182.1.3.3 Boundary Events 222.1.3.4 End Events 26

2.1.4 Gateways 282.1.4.1 Exclusive Gateway 282.1.4.2 Inclusive Gateway 292.1.4.3 Parallel Gateway 302.1.4.4 Complex Gateway 302.1.4.5 Event Based Gateway 30

2.1.5 Error 312.1.6 Message 312.1.7 Participant 322.1.8 Sequence Flow 322.1.9 Message Flow 33

2.2 BPMN Process Diagram 362.2.1 BPMN Process 362.2.2 Activities 36

2.2.2.1 Task 382.2.2.2 SubProcess 402.2.2.3 Call Activity 42

2.2.3 Items and Data 422.2.3.1 Data Object 422.2.3.2 Data Store 432.2.3.3 Data Input and Data Output 432.2.3.4 Data Association 44

2.2.4 Compensation 442.3 BPMN Collaboration Diagram 46

2.3.1 Collaboration 482.3.2 Pool and Lane 48

Copyright © 2009-2012 No Magic, Inc.3

C O N T E N T S

2.3.3 Communication 492.3.4 SubConversation 502.3.5 Call Conversation 512.3.6 Conversation Link 51

2.4 BPMN Choreography Diagram 522.4.1 Choreography 522.4.2 Choreography Activity 53

2.4.2.1 Choreography Task 552.4.2.2 SubChoreography 562.4.2.3 Call Choreography 57

2.5 BPMN Tables 592.5.1 BPMN Processes Description Table 592.5.2 BPMN Resource Roles Description Table 592.5.3 BPMN Activities Description Table 60

2.6 BPMN Resources Usage Matrix 612.7 Elements Numbering 62

2.7.1 Numbering Schemas 622.7.2 Element Types Numbering Sequence 64

2.8 Validation Rules 672.8.1 BPMN 2.0 Correctness (Active) Validation Rules 67

3 PROCEDURES 683.1 Common BPMN Element Procedures 68

3.1.1 Specifying Element IDs 683.1.2 Defining BPMN Elements Numbers 693.1.3 Creating BPMN Elements in the Model Browser 723.1.4 Creating Participants 733.1.5 Creating a Sequence Flow 753.1.6 Creating an Event 76

3.2 BPMN Process Diagram Procedures 803.2.1 Creating a BPMN Process Diagram 803.2.2 Managing Activities 813.2.3 Creating Tasks 823.2.4 Managing SubProcesses 833.2.5 Creating Data Items 86

3.3 BPMN Collaboration Diagram Procedures 893.3.1 Creating a BPMN Collaboration Diagram 893.3.2 Creating Pool and Lane 893.3.3 Creating a Message Flow 933.3.4 Creating a Communication 963.3.5 Creating a SubConversation 97

3.4 BPMN Choreography Diagram Procedures 993.4.1 Creating a BPMN Choreography Diagram 993.4.2 Creating Choreography Activity 993.4.3 Creating a SubChoreography 1033.4.4 Creating a Choreography Task 1043.4.5 Creating a Call Choreography Activity 107

3.5 BPMN Diagram Tables and Matrices Procedures 1083.5.1 Creating a BPMN Processes Description Table 1083.5.2 Creating a BPMN Resource Roles Description Table 109

4 Copyright © 2009-2012 No Magic, Inc..

C O N T E N T S

3.5.3 Creating a BPMN Activities Description Table 1093.5.4 Modifying a BPMN Table 1113.5.5 Creating a BPMN Resources Usage Matrix 1133.5.6 Modifying a BPMN Resources Usage Matrix 114


1 GETTING STARTED

1.1 Introduction to Cameo Business Modeler Analyst EditionCameo Business Modeler Analyst Edition is a tool that provides a solution for modeling and analyzing business processes. This product allows you to represent and analyze business process models based on the Business Process Modeling and Notation (BPMN) standard.

The Business Process Modeling and Notation (BPMN) standard provides the capability of understanding inter-nal business procedures in a graphical notation and enables organizations to communicate these procedures in a standard manner. Furthermore, the standardized graphical notation facilitates the understanding of perfor-mance collaborations and business transactions between organizations. This ensures that businesses will understand themselves and other business participants better.

Cameo Business Modeler Analyst Edition provides support for BPMN 2.0 profile, diagrams, usability featuresfor BPMN modeling, and BPMN model validation. It also includes reports, manuals, and samples that havebeen created with Cameo Business Modeler Analyst Edition.

The following three BPMN 2.0 diagrams are supported:

(i) BPMN Process Diagram

(ii) BPMN Collaboration Diagram

(iii) BPMN Choreography Diagram

The “Getting Started” chapter contains the following sections:

• Installing Cameo Business Modeler Analyst Edition

• Licensing Information

• Working with BPMN 2.0 Projects

1.2 Installation

1.2.1 Installing Cameo Business Modeler Analyst Edition

You can download the latest version of Cameo Business Modeler Analyst Edition and the installation files from the MagicDraw homepage http://www.magicdraw.com/cameobusinessmodeler/. Because Cameo Business Modeler Analyst Edition is a Java application, you will need both Java Virtual Marchine (JVM) and the installa-tion file to run the tool successfully. If you do not have a JVM installed on your computer, you can install JVM together with Cameo Business Modeler Analyst Edition. Information about the latest Java ports is available at http://www.magicdraw.com/jvm_list.htm.

NOTE If your OS is Windows and a JVM is installed, you can install Cameo Business Modeler Analyst Edition immediately.


GETTING STARTEDLicensing Information1

You can install or run Cameo Business Modeler Analyst Edition using either (i) an installer file or (ii) a non-installation version.

(i) To install Cameo Business Modeler Analyst Edition using an installer file:

(a) On Windows 2000, 2003, NT, XP, Vista*, or Windows 7:

• Double-click Cameo_Business_Modeler_<version>_win.exe. The Setup Wizard will automatically add the Cameo Business Modeler Analyst Edition shortcuts to the Start menu and desktop. The shortcut is also available in the installation directory.

(b) On Unix:

1. Open a shell and go to the directory where you have downloaded the installer.2. At the prompt, type: sh./Cameo_Business_Modeler_<version>_unix.sh.

(c) on Mac OS X (Leopard or Snow Leopard and Java 1.6.0_24 for both 32-bit and 64-bit Mac OS X are recommended):

• Double-click Cameo_Business_Modeler_<version>_mac.dmg and drag the launcher to the Applications folder (or to any folder) to install the application.

You may want to create additional folders for different Cameo Business Modeler Analyst Edition versions in the MAC OS X Applications folder so that the old client will not be overwritten by a new one. After installing Cameo Business Modeler Analyst Edition to several folders, you will be able to import the previous Cameo Business Modeler Analyst Edition versions configuration.

To install MagicDraw to a newly created folder on Mac:

1. Create a folder and name it, for example, Cameo Business Modeler Analyst Edition 17.0.1.2. Drag Cameo_Business_Modeler_Analyst_<version>_mac.dmg to Applications/Cameo

Business Modeler 17.0.1.

(ii) To run Cameo Business Modeler Analyst Edition using a non-installation version:

1. Download Cameo_Business_Modeler_<version>_no_install.zip.2. Extract the files.3. Run Cameo Business Modeler Analyst Edition (be sure a JVM has been installed):

(a) on Windows:

• Launch cbm.exe in the bin directory.

(b) on Unix or Mac OS X:

• Launch ./cbm in the bin directory.

1.3 Licensing InformationFor detailed information about the licensing mechanism description, see the Getting Started section in “Magic-Draw UserManual.pdf”

Related section

“MagicDraw UserManual.pdf”


GETTING STARTEDWorking with BPMN 2.0 Projects1

1.4 Working with BPMN 2.0 ProjectsA BPMN2 project provides a workspace for business process modeling. The Business Process Modeling and Notation (BPMN) elements and validation rules are available in this project.

To create a new workspace for an empty project:

1. Do one of the following:

• Click File on the main menu and select New Project. • Click the New Project icon on the File toolbar.

• Press Ctrl + N.

2. In the New Project dialog, click the BPMN2 Project icon 3. Type the filename in the Name box.4. Click the “...” button to locate where to store your new project.5. Click OK.

Related section• “Working with Projects” in the MagicDraw User Manual


2 CONCEPTS

A Business Process Modeling and Notation (BPMN) standard provides the capability to understand internal business procedures in a graphical notation and gives organizations the ability to communicate these proce-dures in a standard manner. Furthermore, the graphical notation facilitates the understanding of the perfor-mance collaborations and business transactions between organizations. This will ensure that organizations understand themselves and the other business participants better.

The BPMN 2.0 standard consists of the following three major parts:

(i) Process, which shows business processes, events, and messages.

(ii) Collaboration, which shows how a process is implemented among collaborators and displays details of conversations among participants.

(iii) Choreography, which provides a view of message/information flows among participants.

Cameo Business Modeler Analyst Edition supports BPMN 2.0 profile, diagrams, usability features for business process modeling, samples, and user guides.

Cameo Business Modeler Analyst Edition provides support for all of the three BPMN 2.0 diagrams as follows:

(i) Process diagram, which shows business processes, events, and messages.

(ii) Collaboration diagram, which shows how a process is implemented among collaborators and defines conversations among participants in details.

(iii) Choreography diagram, which shows a flowchart view of messages or information among partic-ipants.

The “Concepts” chapter contains the following sections:

• “Common BPMN 2.0 Elements” on page 10

• “BPMN Process Diagram” on page 36

• “BPMN Collaboration Diagram” on page 46

• “BPMN Choreography Diagram” on page 52

• “BPMN Tables” on page 59

• “BPMN Resources Usage Matrix” on page 61

• “Elements Numbering” on page 62

• “Validation Rules” on page 67


CONCEPTSCommon BPMN 2.0 Elements2

2.1 Common BPMN 2.0 ElementsThe following section defines the BPMN elements that can be used in more than one type of BPMN diagram such as Process, Collaboration, Conversation, and Choreography diagrams.

2.1.1 Definitions

The Definitions element is a root model in a BPMN project. This element is the outermost containing object for all BPMN elements (Figure 1). It defines the visibility scope and the namespace for all of the BPMN elements in a model.

Figure 1 -- The Definitions Element in the Containment Tree

2.1.2 Artifacts

Artifacts provide modelers with the capability to show additional information about a process. This information is not directly related to a sequence or message flow of the process.

2.1.2.1 Anchor

An Anchor is used to associate a Text Annotation, Note, or Comment with the other diagram elements (Fig-ure 2).

Element Stereotype IconAnchor n/a



Figure 2 -- An Anchor Associating a Text Annotation with an Activity

Related conceptText Annotation

2.1.2.2 Association

An Association shows an Activity that is used for a compensation (Figure 3).

Figure 3 -- An Association from the Compensation Boundary Event to the Compensation Task

Related conceptsBPMN ProcessCompensation

2.1.2.3 Group

A Group element represents an informal visual grouping of the graphical elements of a diagram.

A group shows all elements that belong to the same category. This type of grouping does not affect a sequence flow within the Group. A category name will appear on the diagram as a Group label (Figure 4).

Figure 4 -- An Example of a Group Showing the Elements in the Same Category

Element Stereotype IconAssociation «Association» [Dependency]

Element Stereotype IconGroup n/a



2.1.2.4 Text Annotation

A Text Annotation allows a BPMN modeler to provide additional information on a model for the reader of a BPMN diagram.

A Text Annotation connects to a model element using an anchor (Figure 5).

Figure 5 -- A Text Annotation

Related conceptAnchor

2.1.3 Events

Events in business process modeling show what happens while a process is being performed. Events affect the flow of a process and usually have a cause or impact, and generally require or allow for a reaction. The term “event” is general enough to cover many things in a process, for example, the start or end of an activity, the change of a state of a document, and a message that arrives.

There are three main types of events as follows:

2.1.3.1 Start Events: define where a process starts.

2.1.3.2 Intermediate Events: indicate that something is happening between the start and end of a process. An Intermediate event, which can be placed on the boundary of an activ-ity, is called a Boundary Event.

2.1.3.3 Boundary Events: indicate where a path of a process ends.

2.1.3.1 Start Events

A Start Event indicates where a particular process starts. In terms of sequence flows, a Start Event starts the flow of a process, and thus cannot have any incoming sequence flows.

There are 10 types of Start Events used in business process modeling (Table 1).

Table 1 -- Types of Start Events in Business Process Modeling

Element Stereotype IconText Annotation «TextAnnotation» [Comment]

Start Event Stereotype and Description NotationNone Start Event «NoneStartEvent» [InitialNode]

A None Start Event does not have a defined trig-ger that invokes the start of a process.



Message Start Event «MessageStartEvent» [InitialNode]

A Message Start Event means that a message from a participant has arrived and triggered the start of a process.

A Message Start Event displays any of the follow-ing on a diagram:

• A Message Start Event name if the name is specified.

• A Message Ref property value if the name is unspecified.

• An Operation Ref property if the name and Message Ref are not specified.

When a Message Start Event is owned by an Event SubProcess, it can be:

• Interrupting. The Message Start Event interrupts the process contained in the Event SubProcess. The Interrupting Message Start Event is drawn with a solid border.

• Non-Interrupting. The Message Start Event does not interrupt the process contained in the Event SubProcess. The Interrupting Message Start Event is drawn with a dashed border.

Interrupting

Non-interrupting

Timer Start Event «TimerStartEvent» [InitialNode]

A Timer Start Event allows a particular time and date or cycle setting, for example, on Mondays at 9 A.M., to trigger the start of a process.

A Timer Start Event displays any of the following on a diagram:

• A Timer Start Event name if the name is specified.

• A Time Cycle property name if the name is unspecified.

• A Time Date property if the name and Time Cycle are unspecified.

When a Timer Start Event is owned by an Event SubProcess, it can be:

• Interrupting. The Timer Start Event interrupts the process contained in the Event SubProcess. The Interrupting Timer Start Event is drawn with a solid border.

• Non-Interrupting. The Timer Start Event does not interrupt the process contained in the Event SubProcess. The Interrupting Timer Start Event is drawn with a dashed border.

Interrupting

Non-interrupting

Start Event Stereotype and Description Notation



Compensation Start Event

«CompensationStartEvent» [InitialNode]

A Compensation Start Event triggers an in-line Compensation Event Sub-Process only. The event is triggered when the compensation occurs.

Conditional Start Event «ConditionalStartEvent» [InitialNode]

A Conditional Start Event is triggered when a con-dition like “S&P 500 changes by more than 10% since opening” or “Temperature above 300C,” becomes true.

A Conditional Start Event displays either of the fol-lowing on a diagram:

• A Conditional Start Event name if the name is specified.

• A Condition property value if the name is unspecified.

When a Conditional Start Event is owned by an Event SubProcess, it can be:

• Interrupting. The Conditional Start Event interrupts the process contained in the Event SubProcess. The Interrupting Conditional Start Event is drawn with a solid border.

• Non-Interrupting. The Conditional Start Event does not interrupt the process contained in the Event SubProcess. The Interrupting Conditional Start Event is drawn with a dashed border.

NOTE: A conditional expression of an event must become “false”, and then “true” before the event can be triggered again.

Interrupting

Non-interrupting




Escalation Start Event «EscalationStartEvent» [InitialNode]

An Escalation Start Event implements measures to expedite the completion of a business activity.

An Escalation Start Event displays either of the following on a diagram:

• An Escalation Start Event name if the name is specified.

•An Escalation Code property value if the name is unspecified.

When an Escalation Start Event is owned by an Event SubProcess, it can be:

• Interrupting. The Escalation Start Event interrupts the process contained in the Event SubProcess. The Interrupting Escalation Start Event is drawn with a solid border.

• Non-Interrupting. The Escalation Start Event does not interrupt the process contained in the Event SubProcess. The Interrupting Escalation Start Event is drawn with a dashed border.

NOTE: An Escalation Start Event triggers an in-line Event SubProcess only.

Interrupting

Non-interrupting

Error Start Event «ErrorStartEvent» [InitialNode]

An Error Start Event triggers an in-line Event SubProcess only.

An Error Start Event displays either of the follow-ing on the diagram:

•An Error Start Event name if the name is specified.

•An Error Ref property value if the name is unspecified.




Signal Start Event «SignalStartEvent» [InitialNode]

A Signal Start Event means that a signal, which has been broadcast from another process, has arrived and triggered the start of a process.

A Signal Start Event displays either of the follow-ing on a diagram:

•A Signal Start Event name if the name is specified.

•A Signal Ref property value if the name is unspecified.

When a Signal Start Event is owned by an Event SubProcess, it can be:

• Interrupting. The Signal Start Event interrupts the process contained in the Event SubProcess. The Interrupting Signal Start Event is drawn with a solid border.

• Non-Interrupting. The Signal Start Event does not interrupt the process contained in the Event SubProcess. The Interrupting Signal Start Event is drawn with a dashed border.

Interrupting

Non-Interrupting

Multiple Start Event «MultipleStartEvent» [InitialNode]

A Multiple Start Event indicates that there are mul-tiple ways to trigger a process. However, only one is required.

When a Multiple Start Event is owned by an Event SubProcess, it can be:

• Interrupting. The Multiple Start Event interrupts the process contained in the Event SubProcess. The Interrupting Multiple Start Event is drawn with a solid border.

• Non-Interrupting. The Multiple Start Event does not interrupt the process contained in the Event SubProcess. The Interrupting Multiple Start Event is drawn with a dashed border.

Interrupting

Non-interrupting




Parallel Multiple Start Event

«ParallelMultipleStartEvent» [InitialNode]

A Parallel Multiple Start Event indicates that there are multiple triggers required before a process can be initiated.

When a Parallel Multiple Start Event is owned by an Event SubProcess, it can be:

• Interrupting. The Parallel Multiple Start Event interrupts the process contained in the Event SubProcess. The Interrupting Parallel Multiple Start Event is drawn with a solid border.

• Non-Interrupting. The Parallel Multiple Start Event does not interrupt the process contained in the Event SubProcess. The Interrupting Parallel Multiple Start Event is drawn with a dashed border.

Interrupting

Non-Interrupting




2.1.3.2 Intermediate Events

An Intermediate Event indicates that something is happening somewhere between the start and end of a pro-cess. Intermediate Events affect the flow of a process, but do not start or directly terminate the process.

You can use Intermediate Events to:

• show where messages are expected or sent within a process.

• show delays that are expected within a process.

• interrupt normal flow through exception handling.

• show extra work required for a compensation.

The Intermediate Events can be defined in two ways:

(i) Events catching a trigger

(ii) Events showing a result

Table 2 describes the types of Intermediate Catch Events used in business process modeling.

Table 2 -- Types of Intermediate Catch Events in Business Process Modeling

Intermediate Event Stereotype and Description NotationNone Intermediate Event «NoneIntermediateEvent» [InitialNode]

A None Intermediate Event does not have a defined trigger. It is used to model methodologies that use events to indicate some changes in a state in a process.

Message Catching Inter-mediate Event

«MessageCatchIntermediateEvent» [Accept-EventAction]

A Message Catching Intermediate Event displays any of the following on a diagram:

• A Message Catching Intermediate Event name if the name is specified.



A Message Catching Intermediate Event is used to receive a message. It will cause a process to continue if it is waiting for the message.



Message Throwing Inter-mediate Event

«MessageThrowIntermediateEvent» [SendObjec-tAction]

A Message Throwing Intermediate Event is used to send a message. This Event displays any of the following on a diagram:

• A Message Throwing Intermediate Event name if the name is specified.



Timer Catching Interme-diate Event

«TimerCatchIntermediateEvent» [AcceptEven-tAction]

A Timer Catching Intermediate Event acts as a delay mechanism based on a particular time and date, or cycle, for example, on Mondays at 9 A.M.

A Timer Catching Intermediate Event displays any of the following on a diagram:

• A Timer Catching Intermediate Event name if the name is specified.



Escalation Throwing Intermediate Event

«EscalationThrowIntermediateEvent» [SendOb-jectAction]

An Escalation Throwing Intermediate Event raises an Escalation.

An Escalation Throwing Intermediate Event dis-plays either of the following on the diagram:

•An Escalation Throwing Intermediate Event name if the name is specified.

•An Escalation Code property value if then name is unspecified.

Intermediate Event Stereotype and Description Notation



Compensation Throwing Intermediate Event

«CompensationThrowIntermediateEvent» [Send-ObjectAction]

A Compensation Throwing Intermediate Event indicates that a compensation is necessary.

If an activity, which has been successfully com-pleted, is identified, then it will be compensated.

If no Activity is identified, all successfully com-pleted Activities visible from a Compensation Throwing Intermediate Event will be compen-sated in reverse order of their sequence flows. To be compensated, that Activity must have a boundary Compensation Event or contain a com-pensation Event Sub-Process.

Conditional Catching Intermediate Event

«ConditionalCatchIntermediateEvent» [Accept-EventAction]

A Conditional Catching Intermediate Event will be triggered when a condition becomes “true”.

A Conditional Catching Intermediate Event dis-plays either of the following on a diagram:

• A Conditional Catching Intermediate Event name if the name is specified.

• A Condition property value if the name is unspecified.

Link Catching Intermedi-ate Event

«LinkCatchIntermediateEvent» [AcceptEventAc-tion]

A Link Catching Intermediate Event provides the capability to connect two sections of a process. You can use this event to either:

(i) Create looping situations or to avoid long sequence flow lines, as “Off-Page Connectors” to print a Process across multiple pages, or as generic “Go To” objects within a Process level.

(ii) Catch a link from a Link Throwing Intermediate Event.

You can only use one Link Event for each single Process level, meaning that it cannot link a parent Process with a Sub-Process.

A Link Catching Intermediate Event displays either of the following:

• A Link Catching Intermediate Event name if the name is specified.

• A Source property value if the name is unspecified.




Link Throwing Intermedi-ate Event

«LinkThrowIntermediateEvent» [SendObjectAc-tion]

A Link Throwing Intermediate Event is used to throw a link to a Link Catching Intermediate Event.

A Link Throwing Intermediate Event displays either of the following:

• A Link Throwing Intermediate Event name if the name is specified.

• A Target Link Event property value if the name is unspecified

Signal Catching Interme-diate Event

«SignalCatchIntermediateEvent» [AcceptEven-tAction]

A Signal Catching Intermediate Event is used to receive a signal.

A Signal Catching Intermediate Event displays either of the following on the diagram:

•A Signal Catching Intermediate Event name if the name is specified.


Signals in business process modeling are used for general communications within and across process levels.

Signal Throwing Interme-diate Event

«SignalThrowIntermediateEvent» [SendObject-Action]

A Signal Throwing Intermediate Event is used to send a signal.

A Signal Throwing Intermediate Event displays either of the following on a diagram:

•A Signal Throwing Intermediate Event name if the name is specified.


Multiple Catching Inter-mediate Event

«MultipleCatchIntermediateEvent» [AcceptEven-tAction]

A Multiple Catching Intermediate Event signifies that multiple types of events can be caught. Only one of the defined event triggers is required.

Multiple Throwing Inter-mediate Event

«MultipleThrowIntermediateEvent» [SendObject-Action]

A Multiple Throwing Intermediate Event signifies that multiple types of events are thrown. All of the defined triggers will be thrown by this event.




Related conceptCompensation

2.1.3.3 Boundary Events

A Boundary Event (Figure 6) is a Catching Intermediate Event, which is attached to the boundary of any of the following activities:

• SubProcess, Task, or Call Activity,

• SubChoreography, Choreography Task, or Call Choreography.

Figure 6 -- An Error Boundary Event Attached to a SubProcess

Table 3 describes all of the Boundary events used in business process modeling.

Table 3 -- Types of Boundary Events in Business Process Modeling

Parallel Multiple Catch-ing Intermediate Event

«MultipleParallelCatchIntermediateEvent» [AcceptEventAction]

A Parallel Multiple Catching Intermediate Event signifies that multiple types of events are caught. All of the defined event triggers are required to trigger this event.

Boundary Event Stereotype and Description NotationMessage Boundary Event «MessageBoundaryEvent» [AcceptEventAction]

A Message Boundary Event is triggered by an arrived message. Once triggered, it changes a normal flow into an exception flow.

The boundary of a Message Event, which inter-rupts the activity to which it is attached, is solid.

The boundary of a Message Event, which does not interrupt the activity to which it is attached, is dashed.

A Message Boundary Event displays any of the following on the diagram:

• A Message Boundary Event name if the name is specified.



Interrupting

Non-interrupting




Timer Boundary Event «TimerBoundaryEvent» [AcceptEventAction]

A particular time-date or cycle, for example, on Mondays at 9 A.M., can be specified to trigger a Timer Boundary Event. A Timer Boundary Event, which is attached to the boundary of an activity, will change a normal flow into an exception flow upon being triggered.

The boundary of a Timer Boundary Event, which interrupts the activity to which it is attached, is solid.

The boundary of a Timer Event, which does not interrupt the activity to which it is attached, is dashed.

A Timer Boundary Event displays any of the fol-lowing on a diagram:

• A Timer Boundary Event name if the name is specified.



Interrupting

Non-interrupting

Escalation Boundary Event

«EscalationBoundaryEvent» [AcceptEventAction]

An Escalation Boundary Event is used to catch an escalation.

The boundary of an Escalation Event, which inter-rupts the activity to which it is attached, is solid.

The boundary of an Escalation Event, which does not interrupt the activity to which it is attached, is dashed.

Escalation Boundary Event displays either of the following on a diagram:

•An Escalation Boundary Event name if the name is specified.


Interrupting

Non-interrupting

Error Boundary Event «ErrorBoundaryEvent» [AcceptEventAction]

An Error Boundary Event reacts to (catches) a named error or any error if no name is specified. This Event always interrupts the activity to which it is attached. The boundary of the event is always solid.

An Error Boundary Event displays either of the following on a diagram:

•An Error Boundary Event name if the name is specified.


Interrupting

Boundary Event Stereotype and Description Notation



Cancel Boundary Event «CancelBoundaryEvent» [AcceptEventAction]

A Cancel Boundary Event is used within a Trans-action SubProcess. This type of Event must be attached to the boundary of a SubProcess and will be triggered if the following two conditions are satisfied:

(i) A Cancel End Event is reached within the Transaction SubProcess.

(ii) A Transaction Protocol “Cancel” message is received while a transaction is being performed.

A Cancel Boundary Event always interrupts the activity to which it is attached. The boundary of the event is always solid.

Interrupting

Compensation Boundary Event

«CompensationBoundaryEvent» [AcceptEven-tAction]

A Compensation Boundary Event is used to "catch" a Compensation Event. The event will be triggered by a thrown compensation targeting an activity. When the event is triggered, a Compen-sation Activity, which is associated with it, will be performed.

The Compensation Boundary Event in this sense does not affect the Interrupting or non-interrupting aspect. Compensations can only be triggered after the completion of an activity to which they are attached. Thus, they cannot interrupt the activity. The boundary of the event is always solid.

Conditional Boundary Event

«ConditionalBoundaryEvent» [AcceptEventAc-tion]

A Conditional Boundary Event is triggered when a specified condition becomes true. When the event is triggered, it will change a normal flow of an activity into an exception flow.

The boundary of a Conditional Boundary Event, which interrupts the activity to which it is attached, is solid.

The boundary of a Conditional Boundary Event, which does not interrupt the activity to which it is attached, is dashed.

Interrupting

Non-interrupting




Related conceptsBPMN ProcessCompensation

Signal Boundary Event «SignalBoundaryEvent» [AcceptEventAction]

A Signal Boundary Event can receive a Signal. In this context, it will change a normal flow into an exception flow upon being triggered.

A Signal Event differs from an Error Event because it defines a more general, non-error con-dition for interrupting Activities, such as the suc-cessful completion of another Activity, and it has a larger scope than the Error Event does.

The boundary of a Signal Event, which interrupts the activity to which it is attached, is solid.

The boundary of a Signal Event, which does not interrupt the activity to which it is attached, is dashed.

Signal Boundary Event displays either of the fol-lowing on a diagram:

•A Signal Boundary Event name if the name is specified.


Interrupting

Non-Interrupting

Multiple Boundary Event «MultipleBoundaryEvent» [AcceptEventAction]

A Multiple Boundary Event indicates that there are multiple triggers assigned to the Event. Only one of the specified triggers is required. The Event that occurred changes a normal flow into an exception flow.

The boundary of a Multiple Boundary Event, which interrupts the activity to which it is attached, is solid.

The boundary of a Multiple Boundary Event, which does not interrupt the activity to which it is attached, is dashed.

Interrupting

Non-Interrupting

Parallel Multiple Bound-ary Event

«MultipleParallelBoundaryEvent» [AcceptEven-tAction]

A Parallel Multiple Boundary Event indicates that there are multiple triggers assigned to the event and all of them are required to trigger it.

The boundary of a Parallel Multiple Boundary Event, which interrupts the activity to which it is attached, is solid.

The boundary of a Parallel Multiple Boundary Event, which does not interrupt the activity to which it is attached, is dashed.

Interrupting

Non-Interrupting




2.1.3.4 End Events

An End Event indicates where a particular process will end. In terms of sequence flows, an End Event ends the flow of a process, and thus, will not have any outgoing sequence flow.

There are nine types of End Events used in business process modeling (Table 4).

Table 4 -- Types of End Events in Business Process Modeling

End Event Stereotype and Description NotationNone End Event «NoneEndEvent» [ActivityFinalNode]

A None Start Event does not have a defined result.

Message End Event «MessageEndEvent» [ActivityFinalNode]

A Message End Event indicates that a message will be sent when a process is completed.

A Message End Event displays any of the follow-ing on a diagram:

• A Message End Event name if the name is specified.



Error End Event «ErrorEndEvent» [ActivityFinalNode]

An Error End Event indicates that a named error will be generated, resulting in the termination of all of the currently active threads in a particular Sub-Process.

An Error End Event displays either of the following on a diagram:

•An Error End Event name if the name is specified.


Escalation End Event «EscalationEndEvent» [ActivityFinalNode]

An Escalation End Event indicates that an Escala-tion should be triggered. Other active threads will not be affected by this event and will continue to be executed.

An Escalation End Event displays either of the fol-lowing on a diagram:

•An Escalation End Event name if the name is specified.




Cancel End Event «CancelEndEvent» [ActivityFinalNode]

A Cancel End Event is used within a Transaction SubProcess. It indicates that the transaction should be cancelled and a Cancel Boundary Event attached to the SubProcess boundary will be triggered. It also indicates that a Transaction Protocol Cancel message should be sent to all entities involved in the transaction.

Compensation End Event «CompensationEndEvent» [ActivityFinalNode]

A Compensation End Event indicates that a com-pensation is necessary.

If an activity, which has successfully been com-pleted, is identified, that activity will be compen-sated.

If no activity is identified, all successfully com-pleted activities visible from the Compensation End Event will be compensated in reverse order of their sequence flows.

To be compensated, an activity must have a Com-pensation Boundary Event or contain a Compen-sation Event SubProcess.

Signal End Event «SignalEndEvent» [ActivityFinalNode]

A Signal End Event indicates that a signal will be broadcast when the end has been reached.

A Signal End Event displays either of the following on a diagram:

•A Signal End Event name if the name is specified.


NOTE: A signal, which is broadcast to any pro-cess that can receive it, can be sent across pro-cess levels or pools.

Terminate End Event «TerminateEndEvent» [ActivityFinalNode]

A Terminate End Event indicates that all activities in a process should be immediately ended, includ-ing all of the instances of multi-instance activities. The process will be ended without any compensa-tion or event handling.

Multiple End Event «MultipleEndEvent» [ActivityFinalNode]

A Multiple End Event shows that there are multi-ple consequences of ending a process and all of them will occur, for example, multiple messages might be sent.

End Event Stereotype and Description Notation



2.1.4 Gateways

A Gateway allows you to control the flow of a process through a sequence flow. The term “gateway” implies that there is a gating mechanism that either allows or disallows passage through the Gateway. Tokens that arrive at the gateway can be merged as inputs and/or split as outputs.

If the flow of a process does not need to be controlled, it does not need a gateway.

Table 5 describes the five types of gateways defined in business process modeling.

Table 5 -- Types of Gateways in Business Process Modeling

2.1.4.1 Exclusive Gateway

A diverging Exclusive Gateway (Decision) is used to create alternative paths within a process flow. This is basi-cally the “diversion point in the road” for a process. Only one alternative path can be taken for a given instance of the process.

A Decision can be thought of as a question that is asked at a particular point in the process. The question has a defined set of alternative answers. Each question is associated with two or more condition expressions associ-ated with the Gateway’s outgoing sequence flows (Figure 7).

Figure 7 -- A Diverging Exclusive Gateway

Gateway Type Stereotype NotationExclusive Gateway (Deci-sion)

«ExclusiveGateway» [DecisionNode]

or

Event-Based Gateway «EventBasedGateway» [ForkNode]

Inclusive Gateway «InclusiveGateway» [ForkNode]

Complex Gateway «ComplexGateway» [ForkNode]

Parallel Gateway «ParallelGateway» [ForkNode]



A converging Exclusive Gateway is used to merge alternative paths. All incoming sequence flows’ tokens will be routed to the outgoing sequence flow without synchronizing them.

Figure 8 -- An Exclusive Gateway without An Internal Marker

Figure 9 -- An Exclusive Gateway with An Internal Marker

2.1.4.2 Inclusive Gateway

A diverging Inclusive Gateway (Inclusive Decision) is used to not only create alternative but also parallel paths within a process flow. Unlike an Exclusive Gateway, it evaluates all condition expressions. The true evaluation of one condition expression does not exclude the evaluation of the other condition expressions. All of the sequence flows with true evaluation will be traversed by a token.

Since each path is considered to be independent, all combinations of the paths may be taken, from zero to all (Figure 10). However, it should be designed in such a way that at least one path is taken.

Figure 10 -- Diverging Inclusive Gateway Example

A converging Inclusive Gateway is used to merge a combination of alternative and parallel paths. A control flow token arriving at an Inclusive Gateway may be synchronized with some other tokens that arrive later at this Gateway.

NOTE: There are two icons defined for an Exclusive Gateway in the BPMN 2.0 Specification. It can be displayed with or without an internal marker.



2.1.4.3 Parallel Gateway

A Parallel Gateway is used to synchronize (combine) and create parallel flows (Figure 11).

Figure 11 -- Parallel Gateway Example

2.1.4.4 Complex Gateway

A Complex Gateway can be used to model complex synchronization behavior (Figure 12). An Activation Condi-tion is the Complex Gateway’s property, which is used to describe precise behavior. For example, the activation condition specifies that tokens on three out of five incoming sequence flows are needed to activate the gate-way. Which token the Gateway will produce is determined by the conditions on the outgoing sequence flow as in the split behavior of an Inclusive Gateway.

Figure 12 -- An Example of Complex Gateway

2.1.4.5 Event Based Gateway

An Event Based Gateway represents a branching point in a process where alternative paths that follow the gateway are based on the events that occur rather than on the evaluation of expressions using process data (as with an Exclusive or Inclusive Gateway). A specific event, usually the receipt of a message, determines which path will be taken (Figure 13). Basically, an Event Based Gateway is used when a decision made by another participant is based on data that are not visible to the process.



,

Figure 13 -- An Example of Event-Based Gateway

Related conceptIntermediate Events

2.1.5 Error

An Error represents the content of an error event or the fault of a failed operation. An Error is generated when there is a critical problem in the processing of an activity or when the execution of an operation fails.

Related conceptEvents

2.1.6 Message

A Message represents the content of communications between two participants. It is passed by a message flow and is sent or received by a message event.

Related procedureCreating a Message Flow

Related conceptsParticipantEvents

Element Stereotype IconError «Error» [Class]

Element Stereotype IconMessage «Message» [CentralBufferNode]



2.1.7 Participant

A Participant represents a specific partner entity, such as a company and a more general partner role, for example, a buyer, seller, or manufacturer who is a participant in a collaboration. A Participant is often responsi-ble for the execution of a process enclosed in a pool.

Related proceduresCreating ParticipantsCreating Pool and Lane

Related conceptsPool and LaneCommunicationChoreography Activity

2.1.8 Sequence Flow

A Sequence Flow is used to show the order of flow elements in a process or a choreography (Figure 14).

Figure 14 -- A Sequence Flow Drawn between Two Tasks

The source and target of a Sequence Flow must be from a set of the following elements:

• Events (Start, Intermediate, and End events)

• Activities (Task and Sub-Process; for Processes)

• Choreography Activities (Choreography Task and Sub-Choreography)

• Gateways

A Sequence Flow can optionally define a condition expression indicating that a token will be passed down the Sequence Flow only if the expression is evaluated to be true.

A Condition expression is typically used when the source of a Sequence Flow is a Gateway or an Activity. A conditional outgoing Sequence Flow from an Activity is drawn with a mini-diamond (indicator) at the beginning of the Sequence Flow (Figure 15).

Element Stereotype IconParticipant «Participant» [class]

Element Stereotype IconSequence Flow «SequenceFlow» [ControlFlow]



Figure 15 -- An Example of Conditional Sequence Flow

A Sequence Flow, which has an exclusive, inclusive, or complex gateway, or an activity as its source, can also be defined as a default Sequence Flow. The default Sequence Flow can be distinguished by the presence of a backslash (Figure 16).

A default Sequence Flow will be taken (a token is passed) only if all of the other outgoing Sequence Flows from an activity or gateway are not valid, meaning that their condition expressions are false.

Figure 16 -- An Example of Default Sequence Flow

Related procedureCreating a Sequence Flow

Related conceptsBPMN ProcessChoreography ActivityEventsGateways

2.1.9 Message Flow

A Message Flow is used to show the flow of messages between two participants who are prepared to send and receive them (Figure 17).

NOTE A Conditional Sequence Flow outgoing from a Gateway cannot be drawn with a mini-diamond at the beginning of the Sequence Flow.

Element Stereotype IconMessage Flow «MessageFlow» [Dependency]



Figure 17 -- Message Flows Drawn between Two Pools

Figure 18 -- Message Flows Drawn between Pools Inner Elements

Messages that are sent by a Message Flow can be displayed on a diagram in two ways: (i) associated with the Message Flow (Figure 19) and (ii) overlapping the Message Flow (Figure 20). However, they can also be hid-den.

IMPORTANT • A Message Flow must connect separate Pools. It can be connected to the pool boundary or an element inside the pool.

• A Message Flow cannot connect two elements in the same Pool.



Figure 19 -- Messages Associated with Message Flows

Figure 20 -- Messages Overlapping Message Flows

Related procedureCreating a Message Flow

Related conceptsPool and LaneMessage


CONCEPTSBPMN Process Diagram2

2.2 BPMN Process DiagramA BPMN Process Diagram describes a sequence or flow of activities in an organization that shows how the business works (Figure 21). The diagram shows activities, events, and data that trigger or feed business activi-ties. A BPMN Process Diagram is similar to the UML Activity diagram with a much richer set of default message types and business process styles of notations.

A Process diagram is based on the UML Activity diagram and includes restrictions and extensions as defined by BPMN.

Figure 21 -- A BPMN Process Diagram

Related procedureBPMN Process Diagram Procedures

2.2.1 BPMN Process

A BPMN process element describes how a process is performed. This element is a container for the BPMN Process diagram and its elements.

2.2.2 Activities

An Activity is work that is performed within a business process. An Activity can be atomic or non-atomic (com-pound). There are three types of Activities that are part of a Process:

2.2.2.1 Task

Element Stereotype IconBPMN Process «BPMNProcess» [Activity]



2.2.2.2 SubProcess

2.2.2.3 Call Activity

If the Activity property Is For Compensation is true, the activity will be used for compensation, which means that this Activity will be activated only when a Compensation Event is detected and initiated under the Compen-sation Event visibility scope. The Compensation indicator (marker) is displayed for all activities that are used for the compensation (Figure 22).

Figure 22 -- Task and Collapsed SubProcess with Compensation Indicator

Activities can be repeated sequentially, essentially behaving like a loop. The presence of loop characteristics signifies that an activity has the looping behavior. There are two types of looping characteristics defined in BPMN: (a) Standard Loop and (b) MultiInstance Loop (Table 6).

Table 6 -- Characteristics of Standard and MultiInstance Loops

(a) Standard Loop

A Standard Loop indicator (marker) displayed in an activity shape shows that the looping behavior based on a boolean condition is defined for this activity (Figure 23). Additional looping characteristics can be defined, and the activity will loop as long as the boolean condition is true. The condition is evaluated for every loop iteration and can be evaluated at the beginning or end of the iteration. In addition, a numeric cap can be optionally spec-ified, but the number of iterations cannot exceed this cap.

Figure 23 -- Task and Collapsed SubProcess with Standard Loop Indicator

Characteristics Stereotype MarkerStandard Loop «StandardLoopCharacteristics» [CallBehaviourA-

ction, OpaqueAction, StructuredActivityNode]

MultiInstance Loop «MultiInstanceLoopCharacteristics» [CallBehav-iourAction, OpaqueAction, StructuredActivi-tyNode]

Non-sequential

Sequential



(b) MultiInstance Loop

A MultiInstance Loop indicator shows that a desired number of activity instances can be created. The instances can be executed in parallel (Figure 24) or sequentially (Figure 25). Either expression is used to specify the desired number of instances or a data driven setup that can be used.

Figure 24 -- Task and Collapsed SubProcess with MultiInstance Indicators for Parallel Instance Execution

Figure 25 -- Task and Collapsed SubProcess with MultiInstance Indicators for Sequential Instance Execution

Related procedureManaging Activities

2.2.2.1 Task

A Task is an atomic activity within a process flow. A Task is used when the work in a process cannot be broken down into finer levels of detail. Generally, an end-user and/or application are used to perform the task when it is executed.

Table 7 below defines the types of Tasks used in business process modeling.

Table 7 -- Types of Tasks in Business Process Modeling

IMPORTANT The Compensation, MultiInstance Loop, and Standard Loop indicators can be added to all types of activities.

Task Type Stereotype and Description NotationTask «Task» [OpaqueAction]

A Task that has no specified behavior.



Related procedureCreating Tasks

Service Task «ServiceTask» [OpaqueAction]

A Service Task is a task that uses some sort of service, which could be a Web service or an auto-mated application.

Send Task «SendTask» [OpaqueAction]

A Send Task is a simple task that is designed to send a message to an external participant. Once the message has been sent, the task is com-pleted.

Receive Task «ReceiveTask» [OpaqueAction]

A Receive Task is a simple task that is designed to wait for a message to arrive from an external participant (relative to the Process). Once the message has been received, the task is com-pleted.

User Task «UserTask» [OpaqueAction]

A User Task is a typical “workflow” task where a human performer performs the task with the assistance of an application software and is scheduled through a task list manager of some sort.

Manual Task «ManualTask» [OpaqueAction]

A Manual Task is a task that is expected to be performed without the aid of any business pro-cess execution engine or application, for example, installing a telephone at a customer location.

Business Rule Task «BusinessRuleTask» [OpaqueAction]

A Business Rule Task provides a mechanism for a process to provide inputs to a business rules engine and to get the output of calculations that the business rules engine might provide.

Script Task «ScriptTask» [OpaqueAction]

A Script Task is executed by a business process engine. A modeler or an implementer defines a script in a language that the engine can interpret. When the task is ready to start, the engine will execute the script. When the script is completed, the task will also be completed.

Task Type Stereotype and Description Notation



2.2.2.2 SubProcess

A SubProcess is an activity whose internal details have been modeled using activities, gateways, events, and sequence flows. A SubProcess is a graphical object within a process. It can be “opened up” to show a lower-level process (Figure 26). SubProcesses define a contextual scope that can be used for attribute visibility and a transactional scope for the handling exceptions of Events or for compensation.

Figure 26 -- An Expanded SubProcess Used in Sequence Flows

A collapsed view of a SubProcess hides its details while an expanded view shows its content. A collapsed Sub-Process uses a plus sign (+) to distinguish itself from a Task.

Table 8 below shows the different types of Sub-Processes used in business process modeling.

Table 8 -- Types of Sub-Processes in Business Process Modeling

SubProcess Type Stereotype and Description NotationSubProcess «SubProcess» [StructuredActivityNode]

A SubProcess is used to create a context for an excep-tion handling that applies to a group of activities.

A collapsed SubProcess can be used as a mechanism to show a compact and less clutter group of parallel activities. Expanded

Collapsed



Related procedureManaging SubProcesses

Event SubProcess «SubProcess» [StructuredActivityNode]

An Event SubProcess is an ordinary SubProcess whose Triggered By Event property is set to true.

An Event SubProcess is not a part of a normal flow of its parent process — there is no incoming or outgoing sequence flow.

An Event SubProcess may occur many times. Unlike the standard SubProcess that uses the flow of the par-ent process as a trigger, it has a Start Event as a trig-ger. Whenever the Start Event is triggered while the parent process is active, the Event SubProcess will start.

The Start Event icon of a collapsed Event SubPro-cess will be displayed on the top left corner of the Sub-Process.

Expanded

Collapsed

Collapsed (with its own Start Event)

Transaction «Transaction» [StructuredActivityNode]

A Transaction is a specialized type of SubProcess whose special behavior is controlled through a transac-tion protocol (such as WS-Transaction).

Expanded

Collapsed

AdHoc SubProcess An AdHoc SubProcess is a specialized type of SubPro-cess, which is a group of activities that have no required sequence relationships. A set of activities can be defined for the process, but the sequence and num-ber of performances for the activities are determined by the performers of the activities.

Expanded

Collapsed

SubProcess Type Stereotype and Description Notation



2.2.2.3 Call Activity

A Call Activity identifies a point in a process where a global process is used (Figure 27). The Call Activity acts as a ‘wrapper’ for the invocation of the global process within the execution. The activation of the Call Activity results in the transfer of control to the called global process.

A Call Activity shares the same notation as a Task or SubProcess with a thick line around the boundary of its shape.

Figure 27 -- Call Activities Referencing Process

The BPMN 2.0 Call Activity corresponds to the Reusable Sub-Process of BPMN 1.2, and the BPMN 2.0 Sub-Process corresponds to the Embedded Sub-Process of BPMN 1.2.

Related conceptBPMN Process

2.2.3 Items and Data

The traditional requirement of process modeling is to be able to model the items (physical or information items) that are created, manipulated, and used during the execution of a process. This requirement is fulfilled in BPMN through various constructs: Data Objects, Item Definition, Properties, Data Inputs, Data Outputs, Mes-sages, Input Sets, Output Sets, and Data Associations.

2.2.3.1 Data Object

A Data Object is an element that stores or conveys items during process execution. The Data Object elements must be contained within the process or SubProcess elements.

A Data Object element can optionally reference a DataState element, which is the state of data contained in a Data Object.

A Data Object element, which references an element marked as a collection, is visualized differently (Fig-ure 28).

Element Stereotype IconCall Activity «CallActivity» [CallBehaviorAction]

Element Stereotype IconData Object «DataObject» [CentralBufferNode]



Figure 28 -- Data Object Notations

Related procedureCreating Data Items

2.2.3.2 Data Store

A Data Store (Figure 29) provides a mechanism for activities to retrieve or update stored information that will persist beyond the scope of a process.

Figure 29 -- A Data Store Notation

2.2.3.3 Data Input and Data Output

Activities and processes often require data in order to execute. In addition, they may produce data during or as the result of the execution.

Data requirements are captured as Data Input. The produced data are captured using a Data Output notation (Figure 30).

Figure 30 -- Data Input and Data Output Notations

Element Stereotype IconData Store «DataStore» [CentralBufferNode]

Element Stereotype IconData Input «DataInput» [CentralBufferNode]

Data Output «DataOutput» [CentralBufferNode]



2.2.3.4 Data Association

A Data Association is used to model how data are pushed into or pulled from item-aware elements (Figure 31). Tokens do not flow along a Data Association. Therefore, they have no direct effect on the flow of a process.

Figure 31 -- A Data Association Showing the Flow of a Data Object

Alternatively, Data Objects can be directly associated with a Sequence Flow to represent the same input or out-put Data Associations (Figure 32). This is a visual shortcut that is stored in a model as two Data Associations: one from Activity to Data Object, and another from Data Object to Activity.

Figure 32 -- Sequence Flow Representing the Same Input/Output Data Associations

2.2.4 Compensation

A Compensation in business process modeling is concerned with undoing steps that have already been suc-cessfully completed because their results and possible side effects are no longer desired and need to be reversed. If an activity is still active, it cannot be compensated and needs to be canceled. The cancellation of a SubProcess may produce a compensation of the already successfully completed portions of an active activity.

A Compensation is performed by a compensation handler. A compensation handler performs the steps neces-sary to reverse the effects of an activity. For a SubProcess, the compensation handler will have access to the SubProcess data once they have been completed (“snapshot data”).

A compensation handler is a set of activities that is not connected to other portions of the BPMN model. The compensation handler starts with either of the Compensation Events:

(i) Compensation Boundary Event

(ii) The handler’s Start Event (in case of a Compensation Event Sub-Process)

Element Stereotype IconData Association «DataAssociation» [ObjectFlow]



A compensation handler connected through a boundary event can only perform a “black-box” compensation of the original activity. This compensation is modeled with a specialized Compensation Activity, which is con-nected to the boundary event through an association. The Compensation Activity, which can be either a Task or a Sub-Process, is marked to show that it is used for compensation only and is located outside the normal flow of the Process (Figure 33).

Figure 33 -- Compensation Handler Connected through Compensation Boundary Event

Another way to model a compensation is using a compensation handler, which starts with a Start Event of an Event SubProcess that is contained within a Process or SubProcess (Figure 34). Just like any other Compen-sation Activities, a Compensation Event SubProcess is located outside the normal flow of a process. The Event SubProcess, which is marked with a dotted line boundary, has access to data that are part of the parent, which is a snapshot at the point in time when the parent has been completed. A Compensation Event SubProcess can recursively trigger a compensation for activities contained in its parent.

Figure 34 -- Compensation Defined by Event SubProcess

Related conceptsBPMN ProcessSubProcessEvents


CONCEPTSBPMN Collaboration Diagram2

2.3 BPMN Collaboration DiagramA Collaboration represents the interactions between two or more business entities. A Collaboration diagram depicts a global point of view. It shows the interactions between participants in general.

A Collaboration contains two or more pools, representing the participants in the collaboration. Messages exchanged between the participants are shown by message flows that connect two pools together (or objects within the pools) (Figure 35).

Figure 35 -- A Collaboration Diagram with Two “Black Box” Pools

Figure 36 -- A Collaboration Diagram with Two Pools Showing a Process



A Collaboration diagram can also show distinct conversations between collaborating participants in a domain. Communications are defined by the conversations, participants, and conversation links between them (Fig-ure 37).

Figure 37 -- A BPMN Collaboration Diagram with Conversations

The elements of a BPMN Process diagram can be displayed on the BPMN Collaboration diagram.

Related procedureCreating a Communication



2.3.1 Collaboration

A Collaboration element provides a description of collaborations between pools. This element is a container for a BPMN Collaboration diagram and its elements.

2.3.2 Pool and Lane

A Pool represents a participant in a collaboration. The participant can be a specific partner entity, for example, a company, or it can be a more general partner role, such as a buyer, seller, or manufacturer. Graphically, a Pool is a container to partition a process from the other pools.

A Pool can contain a process (Figure 38), or it can be a “black box” (Figure 39).

Figure 38 -- A Pool that Contains a Process

Figure 39 -- A Pool with Suppressed Content

A Pool with suppressed content will display a multiInstance marker if the participant referenced by the pool has a minimum multiplicity value of 2 or greater (Figure 40).

Figure 40 -- A Pool with Suppressed Contents Referencing a MultiInstance Participant

Element Stereotype IconCollaboration «Collaboration» [Activity]

Element StereotypePool «Pool» [ActivityPartition]

Lane «Lane» [ActivityPartition]



A Lane is a sub-partition within a pool. Lanes are used to organize and categorize activities within a pool according to function or role. They are often used in the internal roles, for example, Manager and Associate; systems, for example, an enterprise application; or internal departments, for example, shipping or finance.

In addition, Lanes can be nested or defined in a matrix. For example, there could be an outer set of Lanes for company departments and an inner set of Lanes for the roles within each department (Figure 41).

Figure 41 -- A Pool with Nested Lanes

Related conceptsParticipantBPMN Process Diagram

2.3.3 Communication

A Communication is an atomic element for a BPMN Collaboration diagram. It represents a set of message flows that is grouped together (Figure 42).

A Communication may involve two or more Participants. A Conversation Link path will be drawn from a Com-munication to the involved Participants (Pools).

Element Stereotype IconCommunication «Communication» [StructuredActivityNode]



Figure 42 -- A Communication Notation

Related proceduresCreating a CommunicationCreating Pool and Lane

Related conceptParticipant

2.3.4 SubConversation

A SubConversation is a conversation node considered as a hierarchical division within a parent’s conversation.

A SubConversation is represented as a graphical object within a BPMN Conversation diagram (Figure 43), but it can also be “opened up” to show a lower-level conversation, which consists of message flows, communica-tions, and/or other SubConversations. A SubConversation shares the participants of its parent conversation.

Figure 43 -- A SubConversation Notation

Related procedureCreating a SubConversation

Related conceptCommunication

Element Stereotype IconSubConversation «SubConversation» [StructuredActivityNode]



2.3.5 Call Conversation

A Call Conversation identifies a place in a conversation where a Conversation is used (Figure 44).

Figure 44 -- A Call Conversation Calling Delivery Conversation

Figure 45 -- A Call Conversation that Does Not Call Any Conversation

Related conceptCollaboration

2.3.6 Conversation Link

A Conversation Link is used to connect conversation nodes (Communication, SubConversation, and Call Con-versation) to and from Participants (Pools).

Figure 46 -- A Conversation Link Notation

Related conceptsCollaborationSubConversationCall ConversationCommunication

Element Stereotype IconCall Conversation «CallConversation» [CallBehaviorAction]

Element Stereotype IconConversation Link «ConversationLink» [Dependency]


CONCEPTSBPMN Choreography Diagram2

2.4 BPMN Choreography DiagramA Choreography formalizes the way business participants coordinate their interactions. A Choreography is a type of process, but its purpose and behavior are different from a standard BPMN process.

A standard process defines the flow of activities of a specific partner entity or organization. In contrast, a Cho-reography formalizes the way business participants coordinate their interactions. The focus is not on the work performed within these participants, but rather on the information (messages) exchanged between them.

A Choreography is a definition of expected behavior, basically a procedural business contract between interact-ing participants. It shows the messages exchanged and their logical relations (Figure 47). This allows business partners to plan their business processes for inter-operation without introducing conflicts.

Figure 47 -- A BPMN Choreography Diagram

A BPMN Choreography diagram contains the following elements:

• Choreography Activities (Choreography Task, SubChoreography, Call Choreography)

• Start Events

• Intermediate Events

• Boundary Events

• End Events

• Gateways

• Sequence Flow

The following sections describe the element and Choreography Activity elements of a BPMN Choreography diagram.

Related procedureBPMN Choreography Diagram Procedures

2.4.1 Choreography

A Choreography is a container for a BPMN Choreography diagram and its elements.

Element Stereotype IconChoreography «Choreography» [Activity]



2.4.2 Choreography Activity

A Choreography Activity is an abstract element. It represents a point on a choreography flow where an interac-tion occurs between two or more participants.

There are three types of Choreography activities defined in business process modeling:

2.4.2.1 Choreography Task

2.4.2.2 SubChoreography

2.4.2.3 Call Choreography

The shape of a Choreography Task, SubChoreography, or Call Choreography consists of two or more partici-pant compartments and one name compartment (Figure 48). One of the participants can be selected as an ini-tiating participant. The color of the initiating participant compartment is the same as the color of the name compartment. The other participants compartments are gray.

Figure 48 -- Compartments on Choreography Activity Shape

The looping properties of a Choreography Activity can be specified. They can be repeated sequentially, essen-tially behaving like a loop. The presence of loop characteristics signifies that the Choreography Activity has looping behavior. There are two types of Looping characteristics defined in BPMN:

(a) Standard Loop


Table 9 -- Characteristics of Standard and MultiInstance Loops

Element Stereotype IconChoreography Activity «ChoreographyActivity»

Characteristics Stereotype MarkerStandard Loop «StandardLoopCharacteristics» [CallBehaviourA-

ction, OpaqueAction, StructuredActivityNode]

MultiInstance Loop «MultiInstanceLoopCharacteristics» [CallBehav-iourAction, OpaqueAction, StructuredActivi-tyNode]

Non-sequential

Sequential



(a) Standard Loop

A Standard Loop marker displayed on a name compartment of a Choreography Activity shape shows that the looping behavior based on a boolean condition is defined for this activity (Figure 49). Additional looping charac-teristics can also be defined: the activity will loop as long as the boolean condition is true. The condition is eval-uated for every loop iteration and can be evaluated at the beginning or end of the iteration. In addition, a numeric cap can be optionally specified, but the number of iterations cannot exceed this cap.

Figure 49 -- Choreography Task and SubChoreography with Standard Loop Markers


A MultiInstance Loop marker shows that a desired number of Choreography Activity instances can be created. The instances can be executed either in parallel (Figure 50) or sequentially (Figure 51) and each will be identi-fied using a different marker.

Figure 50 -- Choreography Task and SubChoreography with Parallel MultiInstance Loop Markers

Figure 51 -- Choreography Task and SubChoreography with Sequential MultiInstance Loop Markers

There are circumstances when a Choreography Activity references a multi-instance participant (the minimum multiplicity property value for a participant is 2 or greater). A multi-instance participant represents a situation where there is more than one possible related participant involved in a Choreography. If this is the case, a Mul-tiInstance marker will be displayed in the participant compartment of a Choreography Activity shape.

Related proceduresCreating Choreography Activity

IMPORTANT MultiInstance Loop and Standard Loop markers can be added to all types of Choreography activities.



Creating Participants


2.4.2.1 Choreography Task

A Choreography Task is an atomic activity in a choreography process. It represents one or more messages exchanged between two Participants (Figure 52).

Figure 52 -- A Choreography Task Corresponding to the BPMN Collaboration Diagram

A Choreography Task can display messages that are defined by the referenced Message Flows. The mes-sages connected to an Initiating Participant compartment are white and those connected to a Non-Initiating Participant compartment are gray (Figure 53).

Element Stereotype IconChoreography Task «ChoreographyTask» [Opaque-

Action]



Figure 53 -- A Choreography Task with Messages Corresponding to a BPMN Collaboration Diagram

Related procedureCreating a Choreography Task

Related conceptsParticipantBPMN Collaboration DiagramSequence Flow

2.4.2.2 SubChoreography

A SubChoreography is a compound activity that can include choreography activities and define their flows (Fig-ure 54). It can be expanded to show its details within the choreography in which it is contained.

Element Stereotype IconSubChoreography «SubChoreography» [Structure-

dActivityNode]



Figure 54 -- An Expanded SubChoreography

It can also be displayed in a collapsed view to hide its details. A collapsed SubChoreography is indicated with a plus sign (+) to distinguish itself from a Choreography Task (Figure 55).

Figure 55 -- A Collapsed SubChoreography

Related conceptsParticipantEventsGatewaysSequence Flow

2.4.2.3 Call Choreography

A Call Choreography identifies the point in a process where a global choreography is used. It acts as a place holder to include a choreography element it is calling.

A Call Choreography is drawn with a thick border (Figure 56).

Element Stereotype IconCall Choreography «CallChoreography» [CallBe-

haviorAction]



Figure 56 -- A Call Choreography Notation

A Call Choreography referencing another Choreography is marked with a plus (+) sign (Figure 57).

Figure 57 -- A Call Choreography Referencing Another Choreography

Related procedureCreating a Call Choreography Activity

Related conceptChoreography


CONCEPTSBPMN Tables2

2.5 BPMN TablesA BPMN table allows you to quickly create and enter BPMN elements, and review a description of the elements conveniently in tabular format.

There are three types of BPMN tables in Cameo Business Modeler Analyst Edition as follows:

2.5.1 BPMN Processes Description Table

2.5.2 BPMN Resource Roles Description Table

2.5.3 BPMN Activities Description Table

2.5.1 BPMN Processes Description Table

A BPMN Processes Description table allows you to display or edit processes descriptions in a table form. You can display existing processes or create new processes in this table.

Figure 58 -- A BPMN Processes Description Table


Related conceptBPMN Process

2.5.2 BPMN Resource Roles Description Table

A BPMN Resource Roles Description table allows you to display or edit resource roles descriptions in a table form. You can display existing resource roles or create new ones in this table.

BPMN defines four types of Resource Roles as follows:

(i) Human Performer

(ii) Performer

(iii) Potential Owner

(iv) Resource Role

You can display all of them in a BPMN Resource Roles Description table.


CONCEPTSBPMN Tables2

Figure 59 -- A BPMN Resource Roles Description Table


2.5.3 BPMN Activities Description Table

A BPMN Activities Description table allows you to display or edit selected process activities descriptions in a table form. A BPMN Activities Description table is created for a BPMN Process.

Figure 60 -- A BPMN Activities Description Table


Related conceptActivities


CONCEPTSBPMN Resources Usage Matrix2

2.6 BPMN Resources Usage MatrixA BPMN Resources Usage matrix allows you to review and edit an allocation of Resource Roles for BPMN Activities. The Resource Roles used in an Activity show a Resources property in a BPMN Activity specification dialog.

A BPMN Resources Usage matrix presents information about BPMN Activities in rows and Resource Roles in columns. Each arrow in the table shows if a Resource Role is used by an Activity (Figure 61).

You can define Resource Roles usage for all BPMN Activities by assigning or removing the Resource Roles to or from the Activities.

Figure 61 -- A BPMN Resource Roles Description Table




CONCEPTSElements Numbering2

2.7 Elements NumberingCameo Business Modeler Analyst Edition offers an automatic numbering feature to number specific types of BPMN elements (Figure 62). Each element number in an ID property is saved in an element specification.

Figure 62 -- A BPMN Process Diagram Showing Element Numbers

2.7.1 Numbering Schemas

There are 4 types of numbering schemas predefined for BPMN elements (Table 10):

Table 10 -- Predefined Numbering Schemas for BPMN Elements

Numbering Style DescriptionMultilevel with Owner Number

A Multilevel with Owner Number numbering schema provides multilevel element numbering. An Element owner (BPMN Process, BPMN Collaboration, or Chore-ography) number is displayed before the element number (Figure 63).

Figure 63 -- Multilevel Numbering Style with Element Owner Number

Note: A Multilevel with Owner Number numbering schema is the default schema for all BPMN diagram elements.



Multilevel without Owner Number

A Multilevel without Owner Number numbering schema provides multilevel ele-ment numbering. An Element owner (BPMN Process, BPMN Collaboration, or Choreography) number is not included in the element number.

Figure 64 -- Multilevel Numbering Style without Element Owner Number

Note: When a Multilevel without element number numbering schema is used, the numbers in a project are not unique. Elements with the same number can exist in multiple diagrams.

Consecutive with Owner Number

A Consecutive with Owner Number numbering schema provides non-multilevel element numbering. An Element owner (BPMN Process, BPMN Collaboration, or Choreography) number is displayed before the element number.

Figure 65 -- Consecutive Numbering Style with Element Owner Number

Numbering Style Description



2.7.2 Element Types Numbering Sequence

Cameo Business Modeler Analyst Edition uses a predefined sequence of numbers for specific element types as described in Table 11.

Consecutive without Owner Number

A Consecutive without Owner Number numbering schema provides non-multi-level element numbering. An Element Owner (BPMN Process, BPMN Collabora-tion, or Choreography) number is not included in the element number.

Figure 66 -- Consecutive Numbering Style without Owner Number

Numbering Style Description



Table 11 -- BPMN Elements Numbers for Specific Element Types

Element Type DescriptionBPMN Process A BPMN Process is numbered in the scope of a project. A BPMN Process

number has “P” as a prefix.

BPMN Collaboration A BPMN Collaboration is numbered in the scope of a project. A BPMN Collaboration number has “C” as a prefix.

Choreography A Choreography is numbered in the scope of a project. A Choreography number has “CH” as a prefix.

Flow Node A Flow Node element is numbered in the scope of an owner element (BPMN Process, BPMN Collaboration, or Choreography). The elements that belong to the Flow Node element type category are as follows:

• All types of tasks

• All types of subprocesses

• Call activities

• Choreography tasks

• Subchoreographies

• Call choreographies

• All types of gateways

• All types of events

Item Aware Element An Item Aware Element is numbered in the scope of an owner element. An Item Aware Element number has “D” as a prefix.

The elements that belong to the Item Aware element type category are as follows:

• Data Object

• Data Store

• Data Input

• Data Output

• Property

Conversation Node A Conversation Node element is numbered in the scope of an owner ele-ment. A Conversation Node number has “Conv” as a prefix.

The elements that belong to the Conversation Node element type cate-gory are as follows:

• Conversation

• SubConversation

• Call Conversation

Resource Role A Resource Role element is numbered in the scope of an owner element. A Resource Role number has “RR” as a prefix.

The elements that belong to the Resource Role element type category are as follows:

• Human Performer

• Performer

• Potential Owner

• Resource Role



Figure 67 -- Numbered BPMN Process, BPMN Collaboration, and Choreography in the Containment Tree

Related procedureDefining BPMN Elements Numbers


CONCEPTSValidation Rules2

2.8 Validation RulesCameo Business Modeler Analyst Edition has the functionality to check if a created BPMN model corresponds to the most important modeling rules defined in the Business Process Modeling and Notation (BPMN) standard.

Cameo Business Modeler Analyst Edition provides the following validation suite to validate BPMN models:

2.8.1 BPMN 2.0 Correctness (Active) Validation Rules suite. The active BPMN 2.0 vali-dation in MagicDraw instantly checks the most important correctness rules of a BPMN 2.0 model, displays errors in the model, and suggests solutions.

2.8.1 BPMN 2.0 Correctness (Active) Validation Rules

Table 12 describes the BPMN correctness (active) validation rules defined in Cameo Business Modeler Analyst Edition for BPMN 2.0 projects.

Table 12 -- BPMN 2.0 Correctness (Active) Validation Rules

Validation rule SeverityA Sequence Flow cannot connect the elements inside a SubProcess to the elements out-side the SubProcess.

Error

A Message Flow must connect two separate Pools or elements in separate pools. Error

A Conversation Link can be drawn either from a Participant to a Communication, a Sub-Conversation, or to a CallConversation. It can also be drawn from a Communication, a SubConversation, or a CallConversation to a Participant.

Error

An Ad Hoc SubProcess may not have a Start Event. Warning

An Ad Hoc SubProcess may not have an End Event. Warning

A Message Start Event cannot be used in a Choreography diagram. Error

An Error Start Event cannot be used in a Choreography diagram. Error

An Error Boundary Event cannot be used in a Choreography diagram. Error

A Message End Event cannot be used in a Choreography diagram. Error

An Error End Event cannot be used in a Choreography diagram. Error

An Escalation End Event cannot be used in a Choreography diagram. Error

A Cancel End Event cannot be used in a Choreography diagram. Error

A Signal End Event cannot be used in a Choreography diagram. Error

A Multiple End Event cannot be used in a Choreography diagram. Error

A Compensation End Event cannot be used in a Choreography diagram. Error

A Sequence Flow cannot cross the Pool Boundary. Error


3 PROCEDURES

This chapter provides the main procedures of Cameo Business Modeler Analyst Edition and contains the fol-lowing sections:

• “Common BPMN Element Procedures” on page 68

• “BPMN Process Diagram Procedures” on page 80

• “BPMN Collaboration Diagram Procedures” on page 89

• “BPMN Choreography Diagram Procedures” on page 99

• “BPMN Diagram Tables and Matrices Procedures” on page 108

3.1 Common BPMN Element ProceduresCommon BPMN elements are those that can be used in more than one type of BPMN diagram such as Pro-cess, Collaboration, Conversation, and Choreography diagrams. The following sections describe how to create and specify those elements and their properties.

3.1.1 Specifying Element IDs

Most elements in the BPMN specification have their element numbers or ID. The identity of an element (shown in gray) is displayed in the following places:

• In a diagram: the ID is displayed above or before an element’s name.

• In the model browser: the ID is displayed in front of an element’s name.

• In the Specification dialog: the ID is below a Name property.

An Element’s ID is automatically created for the BPMN Process, Collaboration and Choreography diagram flow elements and conversations.

To create or change a BPMN element’s ID number manually:

1. Right-click an element on a BPMN 2.0 diagram and click Specification. A Specification dia-log will open.

2. Type an ID number in the ID property text box (Figure 68).

Figure 68 -- A BPMN Element’s ID Property Field

To hide or display element numbers in a BPMN 2.0 diagram, either:

• Right-click an element on the BPMN 2.0 diagram and clear or select Show Elements Id, or

• Right-click an element on the BPMN 2.0 diagram and click Diagram Properties, and then clear or select the Show Elements Id check box.


PROCEDURESCommon BPMN Element Procedures3

Related procedure• Common BPMN 2.0 Elements

3.1.2 Defining BPMN Elements Numbers

Cameo Business Modeler Analyst Edition automatically creates a property identification number for a BPMN Process, Collaboration, or Choreography diagram flow element or conversation. This section describes how you can create, edit, and modify element numbering; number display options; and enable or disable element numbering.

To change element numbering:

1. Right-click an element on a BPMN 2.0 diagram and click Element Numbering. The Element Numbering dialog will open (Figure 69)

Figure 69 -- The Element Numbering Dialog

2. Change the element’s number and click OK.

To hide or display element numbers in a diagram:

1. Right-click a diagram and clear or select the Show Elements Id check box (Figure 70).

NOTE See the Elements Numbering section in the Concepts chapter for a detailed description of schemas numbering.



Figure 70 -- The Show Elements ID Command on the BPMN Diagram Context Menu

To hide element numbers in the Containment tree:

1. Click Options on the main menu and select Project. The Project Options dialog will open.2. Click General project options in the tree on the left-hand side of the dialog and clear the Dis-

play Element Number check box and click OK (Figure 71).

Figure 71 -- The Display Element Number Property in the Project Options Dialog

To enable or disable automatic element numbering in a project:

1. Click Options on the main menu and select Project. The Project Options dialog will open.2. Click General project options in the tree on the left-hand side of the dialog (Figure 72).



Figure 72 -- Use Element Auto-numbering Property in the Project Options Dialog

3. Select or clear the Use Element Auto-numbering check box.4. Click OK.

To change the display style for element symbols in a diagram:

1. Right-click an element in the BPMN2 diagram and select Symbol(s) Properties. The Symbol Properties dialog will open.

2. Open the Element Number Display Mode property drop-down list box and select one of the three options: (i) Above the element name, (ii) Before the element name, or (iii) Do not display on symbol (Figure 73).

NOTE The automatic element numbering feature is enabled in all projects that are created using the BPMN2 and BPMN-SoaML Project templates. If a project is created using any other template, you will need to manually enable the fea-ture.



Figure 73 -- Numbering Properties in the Symbol Properties Dialog

3. Select the Show Number Tag Name check box to add “id =” as a prefix to the element num-ber.

Related concept• Common BPMN 2.0 Elements

Related information• Creating Numbering Customizations section in MagicDraw UML Profiling and DSL

UserGuide

3.1.3 Creating BPMN Elements in the Model Browser

Some BPMN elements may not be represented in BPMN diagrams and need to be created in the model browser, which is the Containment tree. These elements will be used as the data types for specifying the values of the business modeling element properties.

To create a BPMN element in the Containment tree:

• Right-click a package in the Containment tree and click New Element > BPMN Element, and then select a BPMN element that you want to create (Figure 74).



Figure 74 -- Creating a BPMN Element in the Containment Tree

Related conceptCommon BPMN 2.0 Elements

3.1.4 Creating Participants

You can create a Participant inside a package. The participant will not be displayed in a BPMN 2.0 diagram as it is represented by a Pool and a Choreography Task. A Participant is called multiInstance if its minimum multi-plicity value is more than or equal to two.

To create a participant in the Containment tree:

• Right-click a package in the Containment tree and click New Element > BPMN Element > Participant.

To create a multiInstance participant:

1. Right-click a participant in the Containment tree and select Specification to open the Partici-pant Specification dialog.

2. Type a value (more than or equal to two) in the Minimum property text box (Figure 75).



Figure 75 -- Specifying the Minimum Multiplicity Value of a MultiInstance Participant

To review traceability information related to a Participant:

1. Right-click a participant in the Containment tree and select Specification to open the Partici-pant Specification dialog.

2. Click Traceability on the left-hand side of the dialog (Figure 76).

Figure 76 -- Traceability Information of a Participant




3.1.5 Creating a Sequence Flow

A Sequence flow connects activities, choreography activities, events, and gateways. A Conditional Sequence flow has a condition expression and is drawn with a mini-diamond marker at the beginning of the flow.

A default Sequence flow is indicated with a backslash at its start.

To create a Conditional Sequence flow:

1. Select Sequence Flow on the Process Diagram toolbar and click on an empty space on the diagram to create it (Figure 77).

Figure 77 -- Creating a Conditional Sequence Flow

2. Right-click the Sequence flow and select Specification to open the Sequence Flow Specifica-tion dialog.

3. Type an expression in the Condition Expression property text box (Figure 78).

Figure 78 -- Defining the Condition Expression Property

4. Click Close.

To make a default Sequence flow:

1. Select Sequence Flow on the Process Diagram toolbar and click on an empty space on the diagram to create it (Figure 77).

2. Click the Make Default button on the Smart Manipulator toolbar (Figure 79).

NOTE An outgoing Conditional Sequence flow from a gateway does not have a mini diamond marker.



Figure 79 -- The Make Default Button on the Smart Manipulator Toolbar

3. Right-click a Sequence flow source element, such as task, and select Specification to open the Specification dialog.

4. Select the Sequence flow from the Default property list. The selected Sequence flow will be marked as a default one.

Related conceptSequence Flow

3.1.6 Creating an Event

This section describes how to create and specify events in BPMN diagrams.

To draw an Event:

• On the Process Diagram toolbar, click the None Start Event, None Catching Intermediate Event, Message Throwing Intermediate Event, or None End Event arrow button to open its submenu (Figure 80), and select an Event type.

TIP Click the Make Default button to make a default Sequence Flow non-default.

IMPORTANT A default Sequence flow can be specified for activities (tasks, subpro-cesses, and call activities) or exclusive, inclusive, and complex gate-ways.

NOTE A default Sequence flow cannot have a condition expression.



Figure 80 -- Selecting an Event Type on the None Start Event Submenu

To draw a Boundary Event:

1. On the Process Diagram toolbar, click the Message Boundary Event arrow button, and select a type of Boundary Event.

2. Click an Activity or Choreography Activity in a diagram.

To change an Event type:

• Right-click an Event and select a new Event type (Figure 81).



Figure 81 -- Types of Event on the Event Shortcut Menu

To create a non-interrupting Start Event, either:

(i) Right-click a Start Event and select Is Interrupting > False.

(ii) Right-click a Start Event and select Specification to open its Specification dialog. Click the Is Interrupting property box and select false (Figure 82), and then click Close.

Figure 82 -- Creating a Non-Interrupting Start Event

NOTE You can change an Event type for a Start, Intermediate, Boundary, or End Event.



To make a non-interrupting Boundary Event, either:

(i) Right-click a Boundary Event, select Cancel Activity > False.

(ii) Right-click a Boundary Event and select Specification to open its Specification dialog. Click the Cancel Activity property box and select False (Figure 83), and then click Close.

Figure 83 -- Creating a Non-Interrupting Boundary Event

Related conceptsEventsActivitiesChoreography Activity

IMPORTANT Not all Start Event types can be created as non-interrupting. The command Is Interrupting is only for the following Start Event types:

• Message Start Event• Timer Start Event• Escalation Start Event• Conditional Start Event• Signal Start Event• Multiple Start Event• Parallel Multiple Start Event

IMPORTANT Not all Boundary Event types can be created as non-interrupting. The com-mand Cancel Activity is for the following Boundary Event types:

• Message Boundary Event• Timer Boundary Event• Escalation Boundary Event• Conditional Boundary Event• Signal Boundary Event• Multiple Boundary Event• Parallel Multiple Boundary Event


PROCEDURESBPMN Process Diagram Procedures3

3.2 BPMN Process Diagram ProceduresThis section describes how to create and specify a BPMN Process Diagram.

Related conceptBPMN Process Diagram

Related procedureBPMN Collaboration Diagram Procedures

3.2.1 Creating a BPMN Process Diagram

You can create a BPMN Process Diagram through the (i) main toolbar, (ii) main menu, or (iii) shortcut menu in the Containment tree.

(i) To create a new BPMN diagram through the main toolbar:

1. Click the BPMN Process Diagram icon on the BPMN 2.0 main toolbar (Figure 84). The Create Diagram dialog will open.

Figure 84 -- BPMN Process Diagram Icon on the Main Toolbar

2. Type the name and select the owner of the BPMN Process diagram, and then click OK.

(ii) To create a new BPMN diagram through the main menu:

1. On the main menu, click Diagrams > BPMN Process Diagrams. The BPMN Process Dia-grams dialog will open.

2. Click the Add button. The Create Diagram dialog will open.3. Type the name and select the owner of the BPMN Process diagram, and then click OK.

(iii) To create a new BPMN diagram through the shortcut menu in the Containment tree:

1. Right-click a package in the Containment tree to open the shortcut menu and click New Dia-gram > BPMN Process Diagram.

2. Type the name of the created BPMN Process diagram.

Related conceptBPMN Process Diagram

NOTE A BPMN Process Diagram may also contain the elements of a BPMN Collabo-ration Diagram.



3.2.2 Managing Activities

This section describes how to create and specify Activities in a BPMN Process Diagram. Activities (Tasks, Sub-processes, and Call Activities) may have the following specific markers displayed on their shapes:

• Compensation

• Standard loop

• MultiInstance loop (parallel)

• MultiInstance loop (sequential)

To add a Compensation marker to an Activity, either:

(i) Right-click an Activity and select the Is For Compensation check box.

(ii) Right-click an Activity and select Specification to open the Specification dialog. Select the Is For Compensation check box (Figure 85), and then click Close.

Figure 85 -- Adding a Compensation Marker to an Activity

To add a Standard Loop marker to an Activity:

• Right-click an Activity and select the Standard Loop check box.

To add a MultiInstance Loop (parallel) marker to an Activity:

• Right-click an Activity and select the MultiInstance Loop check box.

To display a MultiInstance Loop (sequential) marker on a MultiInstance Loop activity, either:

(i) Right-click an Activity with a MultiInstance Loop (parallel) marker to open its shortcut menu, and select the Is Sequential check box.

(ii) Right-click an Activity with a MultiInstance marker and select Specification to open the Specifica-tion dialog. Select the Is Sequential check box (Figure 86), and then click Close.

Figure 86 -- Displaying a MultiInstance Loop Marker on a MultiInstance Loop Activity



To convert an Activity to another type of Activity:

• Right-click a Task, SubProcess, or Call Activity, select Refactor > Convert To, and select an Activity type (Figure 87).

Figure 87 -- Converting an Activity Type


3.2.3 Creating Tasks

There are multiple types of Tasks that you can create in a BPMN Process diagram.

To draw a task:

• On the Process Diagram toolbar, click the Task arrow button and select a type of Task (Figure 88).

Figure 88 -- Selecting a Type of Task

To change a task type:

• Right-click a Task and select a new Task type (Figure 89).



Figure 89 -- The Task Shortcut Menu

Related conceptTask

3.2.4 Managing SubProcesses

A BPMN diagram may display subprocesses with different symbol properties:

• An expanded SubProcess can contain inner shapes.

• A collapsed SubProcess cannot display inner shapes. A plus sign (+) marker will be displayed for a collapsed subprocess.

If the property of a SubProcess Is Triggered By Event is true, an Event SubProcess will be called and drawn with a dashed border.

There are two specific types of SubProcesses:

(i) A Transaction SubProcess, drawn with double borders.

(ii) An AdHoc SubProcess, drawn with an AdHoc marker on its shape.

To draw an expanded SubProcess:

• On the Process Diagram toolbar, click the Collapsed SubProcess arrow button and select Expanded SubProcess (Figure 90).



Figure 90 -- The Expanded SubProcess Options on the Process Diagram Toolbar

To draw a collapsed SubProcess:

• On the Process Diagram toolbar, click the Collapsed SubProcess arrow button and select Collapsed SubProcess.

To convert a collapsed SubProcess to an expanded SubProcess or vice versa, either:

(i) Right-click a SubProcess shape and select or clear the Suppress Content check box on the short-cut menu.

(ii) Right-click a SubProcess shape and click Symbol(s) Properties. Select or clear the Suppress Content check box.

To draw an event SubProcess:

• On the Process Diagram toolbar, click the Collapsed SubProcess arrow button and select Collapsed Event SubProcess or Expanded Event SubProcess (Figure 91).

Figure 91 -- Selecting an Event Subprocess

To draw a Transaction SubProcess:

• On the Process Diagram toolbar, click the Collapsed SubProcess arrow button and select Collapsed Transaction SubProcess or Expanded Transaction SubProcess (Figure 92).



Figure 92 -- Selecting a Transaction Subprocess

To draw an AdHoc SubProcess:

• On the Process Diagram toolbar, click the Collapsed SubProcess arrow button and select Collapsed AdHoc SubProcess or Expanded AdHoc SubProcess (Figure 93).

Figure 93 -- Selecting an AdHoc SubProcess

To mark a created SubProcess as an event SubProcess, either:

(i) Right-click a SubProcess and select the Triggered By Event check box.

(ii) Right-click a SubProcess and click Specification to open the its Specification dialog. Select the Triggered By Event check box on the SubProcess properties list (Figure 94).



.

Figure 94 -- Marking a Subprocess as Event Subprocess

To convert a SubProcess to a Transaction SubProcess or AdHoc SubProcess:

• Right-click a SubProcess and select Refactor > Convert To > More Specific > AdHoc SubProcess or Transaction.

To convert a Transaction SubProcess or AdHoc SubProcess to a simple SubProcess:

• Right-click an Ad Hoc SubProcess or Transaction SubProcess and click Refactor > Convert To > More General > AdHoc SubProcess or Transaction.

To display a Start Event icon on a suppressed Event SubProcess:

1. Draw an expanded Event SubProcess.2. Draw a Start Event to the Event SubProcess.3. Right-click the SubProcess and select the Suppress Content check box.

Related conceptSubProcess

3.2.5 Creating Data Items

You can create the following data items in a BPMN process diagram:

• Data Object

• Data Store

• Data Input

• Data Output

Data Associations allow you to indicate a Data Object as a collection and connect a data item to other elements of a BPMN Process diagram.

To draw a data item:

• On the Process Diagram toolbar, click the Data Object arrow button and select Data Object, Data Store, Data Input, or Data Output (Figure 95).



Figure 95 -- Drawing a Data Item

To create a new Data Object typed by a classifier:

• Select a classifier in the Containment tree and drag it to a BPMN Process or BPMN Collaboration diagram.

To mark a Data Object as a collection, either:

(i) Right-click a Data Object and select Is Collection > true.

(ii) Right-click a Data Object and select Specification to open the Specification dialog. Select the true check box on the Is Collection property drop-down list.

To draw a Data Association:

1. Click Data Association on the Process Diagram toolbar.2. Click an element, which is the source of Data Association, in a diagram.3. Click an element, which is the target of Data Association, in the diagram.

To display a Data Object connected to a Sequence Flow:

1. Draw a Data Association from an Activity to a Data Object.2. Draw another Data Association from the Data Object to another Activity.3. Draw a Sequence Flow from the first to the second Activity.4. Right-click the Data Object and select Show Connected to Sequence Flow (Figure 96).

NOTE • The source or target of a Data Association must always be a Data Object, Data Store, Data Input, or Data Output.

• The other end of a Data Association should always be an activity or event.



Figure 96 -- The Data Object Shortcut Menu.

Related conceptItems and Data

NOTE A Data Object connected to a Sequence Flow is a visual shortcut of two Data Associations. In the model, the Data Associations will still appear and the Data Object connecting to the Sequence Flow will be displayed.


PROCEDURESBPMN Collaboration Diagram Procedures3

3.3 BPMN Collaboration Diagram ProceduresThis section describes how to create and specify a BPMN Collaboration diagram.

3.3.1 Creating a BPMN Collaboration Diagram

You can create a BPMN Collaboration diagram through the (i) main toolbar, (ii) main menu, or (iii) shortcut menu in the Containment tree.

(i) To create a new BPMN Collaboration diagram through the main toolbar:

1. Click the BPMN Collaboration Diagram icon on the BPMN 2.0 toolbar (Figure 97). The Create Diagram dialog will open.

Figure 97 -- The BPMN Collaboration Diagram Icon on the Main Toolbar

2. Type the name and select the owner of the diagram.3. Click OK.

(ii) To create a new BPMN Collaboration diagram through the main menu:

1. On the Diagrams menu, click BPMN Collaboration Diagrams. The BPMN Collaboration Diagrams dialog will open.

2. Click the Add button. The Create Diagram dialog will open.3. Type the name and select the owner of the diagram, and then click OK.

(iii) To create a new BPMN Collaboration diagram through the shortcut menu in the Containment tree:

1. Right-click a package in the Containment tree and select New Diagram > BPMN Collabora-tion Diagram.

2. Type the name of the diagram.

Related conceptBPMN Collaboration Diagram

Related procedureBPMN Process Diagram Procedures

3.3.2 Creating Pool and Lane

A Pool in a BPMN collaboration diagram represents a participant of a collaboration. A Pool can have its inner process flows defined. You can add the elements from a BPMN Process diagram to a pool. You can also hide the pool details by displaying a “black box” pool. A Pool can also have inner lanes.

NOTE A BPMN Collaboration diagram can contain elements from a Process diagram.



To draw a Pool:

• On the Collaboration Diagram toolbar, click the Horizontal Pool arrow button and select either Horizontal Pool or Vertical Pool (Figure 98).

Figure 98 -- Drawing a Pool

To draw a Pool with suppressed content:

• Click Participant (Pool) on the Conversations toolbar (Figure 99).

Figure 99 -- Drawing a Suppressed Context Pool

To create a Pool that contains a representing Participant:

• Drag a Participant from the Containment tree to a BPMN Collaboration diagram.

To open a Pool Specification dialog:

• Right-click the Pool header and select Specification (Figure 100).



Figure 100 -- The Pool Shortcut Menu

To specify a model element represented by a Pool, do one of the following:

(i) Click a Pool in a diagram. The Smart Manipulators toolbar will open (Figure 101). Click the Participant button.

Figure 101 -- Selecting a Pool and the Participant Button on the Smart Manipulator Toolbar

(ii) Right-click a Pool in a diagram and select Specification to open the Specification dialog. Click the Represents drop-down list and select an element (Figure 102).



Figure 102 -- Selecting a Participant

(iii) Select a represented element in the Containment tree and drag it to the Pool header in a dia-gram.

To hide a Pool’s content in a diagram (to display a “black box” pool):

• Right-click a Pool shortcut menu, click either (i) Suppress Pool Content or (ii) Symbol(s) Properties, and select the Suppress Pool Content check box.

A Pool with suppressed content that references a multiInstance Participant will be displayed with a MultiIn-stance marker.

To display a multiInstance marker on a Pool:

• Right-click a Pool and select Specification to open the Specification dialog. Select a represented multiInstance Participant from the Represents drop-down list.

To add a lane to a Pool:

• Right-click a Pool, click either Insert Lanes or Insert Inner Lanes, and select a lane type.

To review the Pool traceability information:

• Right-click a Pool and select Specification to open the Specification dialog, and then click Traceability. A dialog showing the pool traceability information will open (Figure 103).

NOTE A Pool may represent a BPMN Participant element or a UML classifier element.

TIP! You can create a Participant in your model as described in section 3.1.3 Creat-ing BPMN Elements in the Model Browser.

NOTE A MultiInstance marker can be displayed only on a Poll with sup-pressed content.

TIP The Minimum Multiplicity value of a MultiInstance participant prop-erty must be at least 2.



Figure 103 -- Accessing Pool Traceability Information

Related conceptsParticipantPool and Lane

Related procedureCreating BPMN Elements in the Model Browser

3.3.3 Creating a Message Flow

A Message flow connects two pools or inner elements of a pool.

To draw a Message Flow:

1. Click Message Flow on the Collaboration Diagram toolbar.2. Click an element, which is the source of the Message Flow, in a diagram.3. Click another element, which is the target of the Message Flow, in the diagram.

IMPORTANT A Message Flow must connect two different Pools (or inner elements of a pool).



To create a new Message for a Message Flow:

• Drag a classifier (Class, Input Set, Output Set, or Error) from the Containment tree to a Message Flow in a Collaboration diagram.

To create a Message for a Message Flow:

1. Click a Message Flow path in a diagram and click the Referenced Messages button on the Smart Manipulators toolbar (Figure 104). The Select Message dialog will open.

Figure 104 -- The Referenced Messages Button on the Smart Manipulators Toolbar

Figure 105 -- Selecting a Message in the Select Message Dialog



2. Click the Element Creation Mode button.3. Select a Collaboration element in the model element tree and click the Create button

(Figure 106).

Figure 106 -- Creating a Collaboration Element in the Select Message Dialog

To select a Message for a Message Flow, either:

(i) Click a Message Flow path in a diagram and click the Referenced Messages button on the Smart Manipulators toolbar. The Select Message dialog will open. Select a message in the tree and click OK.

(ii) Right-click a Message Flow and select Specification. The Message Flow Specification dialog will open. Click the Message Ref “...” button (Figure 107) and select a message.

Figure 107 -- Message Ref in the Message Flow Specification Dialog



To change a Message Flow display mode:

• Right-click a Message Flow and select either (i) Show Message and select a message display mode (Do not Show, Associated with Message Flow, or Overlapping with Message Flow), or (ii) Symbol(s) Properties and select the required Show Message property value (Do not Show, Associated with Message Flow, or Overlapping with Message Flow).

Related conceptsMessageMessage Flow

3.3.4 Creating a Communication

A Communication groups messages exchanged between Participants.

To create a Communication between two Participants:

1. Draw a Communication.2. Draw a Communication Link from the Communication to a Participant.3. Draw another Communication Link from the Communication to another Participant.

To select message flows grouped by a Communication:

1. Either: (i) right-click a communication shape, select Specification, click Message Flow Refs, and then click the “...” button, or (ii) click a Communication shape in a Collaboration diagram and click the Message Flows button on the Smart Manipulators toolbar (Figure 108).

Figure 108 -- The Message Flows Button on the Smart Manipulators Toolbar

2. The Select Message Flows dialog will open showing all of the Message Flows that are grouped by a Communication (Figure 109).

NOTE You can create a Message in a BPMN Process, Collaboration, Choreography, or SubProcess element.

IMPORTANT! A Participant (pool) requires a specified Representing Participant.



Figure 109 -- Selecting Message Flows in the Select Message Flows Dialog

3. Select the Message Flows and click OK.

Related conceptCommunication

Related procedureCreating Pool and Lane

3.3.5 Creating a SubConversation

A SubConversation can contain inner Conversation nodes (Communications and SubConversations).

To create a Conversation node for a SubConversation:

1. Right-click a SubConversation and select Specification. The SubConversation Specifica-tion dialog will open (Figure 110).

NOTE: When the Show Message Flows Related to Participants check box is selected, only the message flows that exist in a project between the Represent-ing Participants of the pools connected by a communication will show. Clear the check box to see all message flows in a project.

TIP You can also assign a Message Flow to a Communication by dragging it from the browser Containment tree to a Communication shape in a BPMN Collabo-ration diagram.



Figure 110 -- Creating a Conversation Node in the SubConversation Specification Dialog

2. Click Conversation Nodes on the left-hand side of the dialog and click the Create button.3. Select either Communication or SubConversation.4. Type the name of the node and click Close.

Related conceptSubConversation


PROCEDURESBPMN Choreography Diagram Procedures3

3.4 BPMN Choreography Diagram ProceduresThis section describes how to create and specify a BPMN Choreography diagram.

3.4.1 Creating a BPMN Choreography Diagram

You can create a BPMN Choreography diagram through the (i) main toolbar, (ii) main menu, or (iii) shortcut menu in the Containment tree.

(i) To create a new BPMN Choreography diagram through the main toolbar:

1. Click the BPMN Choreography Diagram icon on the BPMN 2.0 toolbar. The Create Diagram dialog will open (Figure 111).

Figure 111 -- BPMN Choreography Icon on the Main Toolbar

2. Type the name and select the owner of the diagram, and then click OK.

(ii) To create a new BPMN Choreography diagram through the main menu:

1. On the Diagrams menu, click BPMN Choreography Diagrams. The BPMN Choreography Diagrams dialog will open.

2. Click the Add button. The Create Diagram dialog will open.3. Type the name and select the owner of the diagram, and then click OK

(iii) To create a new BPMN Collaboration diagram through the shortcut menu in the Containment tree:

1. Right-click a package in the Containment tree and click New Diagram > BPMN Choreography Diagram.

2. Type the name of the diagram.

Related conceptsBPMN Choreography DiagramChoreography

3.4.2 Creating Choreography Activity

This section shows you how to model choreography activities in a BPMN Choreography diagram. Choreogra-phy Activities, such as Choreography Task, SubChoreography, and Call Choreography, can have the following specific markers displayed on their shapes:

• Standard loop marker

• MultiInstance loop (parallel) marker

• MultiInstance loop (sequential) marker



Choreography Activities must have a list of specified Participants and an initiating Participant. The Participants in a Choreography Activity will be displayed in gray, and the initiating Participant will be displayed in another color.

You can specify a list of Participants in a Choreography Activity through the (i) Specification dialog, (ii) Smart Manipulators toolbar, or (iii) drag-and-drop action.

(i) To specify a list of Participants through the Specification dialog:

1. Right-click a Choreography Activity and select Specification.2. Click the Participant Refs “...“ button (Figure 112). The Select Participant dialog will open.

Figure 112 -- Participant Refs in the Choreography Activity Specification Dialog

3. Click either the Tree or List tab, select participants, and then click OK (Figure 113).



Figure 113 -- Selecting Participants in the Select Participant Dialog

(ii) To specify a list of Participants through the Smart Manipulators toolbar:

1. Click a Choreography activity in a BPMN Choreography diagram. The Smart Manipulators toolbar will open (Figure 114).

TIP • If you cannot see the participant you want on the list, click the Creation Mode icon in the Select Participant dialog to create a new participant.

• When creating a participant, select a package as the participant owner.

IMPORTANT You need to specify at least two Participants in a Choreography Activity.

NOTE A MultiInstance Participant on a Choreography shape will be displayed with a MultiInstance marker in the Participant’s compartment.



Figure 114 -- The Participants Button on the Smart Manipulators Toolbar

2. Click the Participants button (Figure 114). The Select Participant dialog will open.3. Select the Participants and click OK.

(iii) To specify a list of participants through the drag-and-drop action:

• Drag a Participant from the Containment tree to a Choreography Activity in a BPMN Choreography diagram.

To specify an initiating Participant in a Choreography Activity:

1. Right-click a Choreography Activity and select Specification to open the Specification dialog.2. Click the Initiating Participant Ref property drop-down list and select a Participant

(Figure 115).

Figure 115 -- Selecting an Initiating Participant

TIP You can press and hold down Ctrl to select more than one participant in the Containment tree.

IMPORTANT The Initiating Participant Ref property is required for a Choreography Activity.



To add a Standard Loop marker to a Choreography Activity:

• Right-click a Choreography Activity and select Standard Loop.

To add a MultiInstance Loop (parallel) marker to a Choreography Activity:

• Right-click a Choreography Activity and select MultiInstance Loop.

To display a MultiInstance Loop (sequential) marker on a MultiInstance Loop Choreography Activity, either:

(i) Right-click a Choreography Activity with a MultiInstance Loop (parallel) marker and select Is Sequential.

(ii) Right-click a Choreography Activity with a MultiInstance Loop marker and select Specification. Select the Is Sequential check box and click Close (Figure 116).

Figure 116 -- Displaying a MultiInstance Loop (Sequential) Marker

Related conceptsChoreography ActivityParticipant

Related procedureCreating BPMN Elements in the Model Browser

3.4.3 Creating a SubChoreography

A SubChoreography can be displayed with different symbol properties:

• An Expanded SubChoreography can contain inner shapes.

• A Collapsed SubChoreography cannot display inner shapes. A collapsed subprocess will have a plus sign (+) marker.

To draw an expanded SubChoreography:

• On the BPMN Choreography Diagram toolbar in a BPMN Choreography diagram, click the Collapsed Choreography SubProcess arrow button, and select Expanded Choreography SubProcess (Figure 117).

Figure 117 -- Selecting Expanded Choreography SubProcess



To draw a collapsed SubChoreography:

• On the BPMN Choreography Diagram toolbar in a BPMN Choreography diagram, click the Collapsed Choreography SubProcess arrow button, and select Collapsed Choreography SubProcess.

To convert a collapsed SubChoreography to an expanded SubChoreography or vice versa, either:

(i) Right-click a SubChoreography in a BPMN Choreography diagram and select or clear the Sup-press Content check box.

(ii) Right-click a SubChoreography in a BPMN Choreography diagram and click Symbol(s) Prop-erties. The Symbol Properties dialog will open. Either select or clear the Suppress Content check box.

Related conceptSubChoreography

3.4.4 Creating a Choreography Task

A Choreography Task can have references to message flows existing among referenced participants.

To draw a Choreography Task:

• On the BPMN Choreography Diagram toolbar, click Choreography Task, and then click the BPMN Choreography diagram (Figure 118).

Figure 118 -- The Choreography Task Button

To select Message Flows referenced by a Choreography Task:

1. Right-click a Choreography Task and select Specification to open the Choreography Task Specification dialog.

2. Click the Message Flow “...” button. The Select Message Flow dialog will open (Figure 119).



Figure 119 -- Selecting Message Flows

3. Select the Message Flows and click OK.

To specify Messages for a Choreography Task:

1. Create a BPMN Collaboration diagram.2. Draw two pools and specify the Referenced Participants of the pools.3. Draw a Message Flow between the Pools and specify a Message for Message Ref in the Mes-

sage Flow property (Figure 120).

IMPORTANT If the Message Flows, which are referenced by a Choreography Task, have the Messages specified, they will be displayed and attached to the Choreography Task on the diagram.



Figure 120 -- Pools, Participants, and Message Flow

4. Create a BPMN Choreography diagram and draw a Choreography Task. 5. Right-click the Choreography Task and select Specification to open the Choreography Task

Specification dialog.6. Specify the Participants for the Participant Refs property and a Participant for the Initiating

Participant Ref property.7. Click the Message Flow property “...” button. The Select Message Flow dialog will open.

Select the Message Flows you have created in step 3 as the Message Flow property value and click Close.

Figure 121 -- Messages Created for a Choreography Task

To hide or display messages for a Choreography Task, either:

(i) Right-click a Choreography Task and select or clear the Show Messages check box.

NOTE • Initiating messages (connected to an initiating Participant compartment) will be displayed in white.

• Non-initiating messages (connected to a non-initiating Participant compartment) will be displayed in gray.



(ii) Right-click a Choreography Task and click Symbol(s) Properties. The Symbol Properties dia-log will open. Either select or clear the Show Messages check box.

Related conceptsChoreography TaskParticipantMessageCollaboration

Related proceduresCreating Pool and LaneCreating a Message Flow

3.4.5 Creating a Call Choreography Activity

A Call Choreography Activity holds a reference to a Choreography.

To create a Call Choreography Activity:

1. Click Call Choreography Activity on the BPMN Choreography Diagram toolbar in a BPMN Choreography diagram (Figure 122) and click the diagram to draw the shape. The Select Behavior dialog will open.

.

Figure 122 -- Creating a Call Choreography Activity

2. Select a Choreography Activity and click OK.

To change an element called by a Call Choreography Activity, either:

(i) Right-click a Call Choreography Activity and click Called Element. Select a Choreography Activity from the elements list.

(ii) Right-click a Call Choreography Activity and select Specification to open the Call Choreogra-phy Specification dialog. Select a Choreography Activity as the Called Element property value.

Related conceptCall Choreography


PROCEDURESBPMN Diagram Tables and Matrices Procedures3

3.5 BPMN Diagram Tables and Matrices ProceduresThis section describes how to create and modify the following BPMN tables and matrices:

• BPMN Processes Description table

• BPMN Resource Roles Description table

• BPMN Activities Description table

• BPMN Resources Usage matrix

3.5.1 Creating a BPMN Processes Description Table

You can create a BPMN Processes Description table through the (i) main toolbar, (ii) main menu, or (iii) short-cut menu in the Containment tree.

(i) To create a new BPMN Processes Description table through the main toolbar:

1. Click the BPMN Processes Description Table icon on the BPMN 2.0 toolbar. The Create Dia-gram dialog will open (Figure 123).

Figure 123 -- BPMN Processes Description Table Icon on the BPMN 2.0 Toolbar

2. Type the name of the table and select its owner.3. Click OK.

(ii) To create a new BPMN Processes Description table through the main menu:

1. On the main menu, click Diagrams > BPMN Processes Description Tables. The BPMN Pro-cesses Description Tables dialog will open.

2. Click the Add button. The Create Diagram dialog will open.3. Type the name of the table and select its owner.4. Click OK.

(iii) To create a new BPMN Processes Description table through the shortcut menu in the Containment tree:

1. Right-click a package in the Containment tree and click New Diagram > BPMN Processes Description Table.

2. Type the name of the table.

Related conceptsBPMN Processes Description TableBPMN Process



3.5.2 Creating a BPMN Resource Roles Description Table

You can create a BPMN Resource Roles Description table through the (i) main toolbar, (ii) main menu, or (iii) shortcut menu in the Containment tree.

(i) To create a new BPMN Resource Roles Description table through the main toolbar:

1. Click the BPMN Resource Roles Description Table icon on the BPMN 2.0 toolbar. The Cre-ate Diagram dialog will open (Figure 124).

Figure 124 -- BPMN Resource Roles Description Table Icon on the Main Toolbar

2. Type the name of the table and select its owner.3. Click OK.

(ii) To create a new BPMN Resource Roles Description table through the main menu:

1. On the Diagrams menu, click BPMN Resource Roles Description Tables. The BPMN Resource Roles Description Tables dialog will open.

2. Click the Add button. The Create Diagram dialog will open.3. Type the name of the table and select its owner.4. Click OK

(iii) To create a new BPMN Resource Roles Description table through the shortcut menu in the Containment tree:

1. Right-click a package in the Containment tree and click New Diagram > BPMN Resource Roles Description Table.


Related conceptBPMN Resource Roles Description Table

3.5.3 Creating a BPMN Activities Description Table

You can create a BPMN Activities Description table through the (i) main menu or (ii) shortcut menu in the Con-tainment tree.

(i) To create a new BPMN Activities Description Table through the main menu:

1. On the Diagrams menu, click BPMN Activities Description Tables. The BPMN Activities Description Tables dialog will open.

2. Click the Add button. The Create Diagram dialog will open.3. Type the name of the table and select its owner.4. Click OK.



(ii) To create a new BPMN Activities Description table through the shortcut menu in the Containment tree:

1. Right-click a BPMN Process or Choreography in the Containment tree. Select New Diagram > BPMN Activities Description Table (Figure 125).

Figure 125 -- Selecting BPMN Activities Description Table on the Context Menu in the Containment Tree


Related conceptBPMN Activities Description Table

NOTE It is recommended that you create a BPMN Activities Description table inside a BPMN Process or Choreography Diagram.



3.5.4 Modifying a BPMN Table

To create a new element in a BPMN table:

1. Click the Add New button on the BPMN Table toolbar (Figure 126).2. Select an element type to be created.

Figure 126 -- The BPMN Table Toolbar

To add an existing element to a BPMN table:

1. Click the Add Existing button on the BPMN Table toolbar. The Select Element dialog will open.

2. Select the element(s) you want to add to the table and click OK (Figure 127).

Figure 127 -- The Select Element Dialog for Single Selection of Elements



Figure 128 -- The Select Element Dialog for Multiple Selection of Elements

• Drag the element(s) from the Containment tree to the table.

To remove an element from a BPMN table:

• Select an element in a table and click the Delete From Table button on the BPMN Table toolbar.

To delete an element from both a BPMN table and model:

• Select an element in a table and click the Delete button on the BPMN Table toolbar.

To change a column of a table:

• Click the Show Columns button on the BPMN Table toolbar and select or clear a column check box to display or hide it in the table (Figure 129).

NOTE If you want to select more than one element in the Select Element dialog, click the Multiple Selection button, which allows multiple selection of elements.



Figure 129 -- Column Selection for a BPMN Table

3.5.5 Creating a BPMN Resources Usage Matrix

You can create a BPMN Resources Usage Matrix through the (i) main toolbar, (ii) main menu, or (iii) shortcut menu in the Containment tree.

(i) To create a new BPMN Resources Usage Matrix through the main toolbar:

1. Click the BPMN Resources Usage Matrix icon on the BPMN 2.0 toolbar (Figure 130). The Create Diagram dialog will open.

Figure 130 -- The BPMN Resources Usage Matrix Icon on the BPMN 2.0 Toolbar

2. Type the name and select the owner of the matrix, and then click OK.

(ii) To create a new BPMN Resources Usage Matrix through the main menu:

1. On the Diagrams menu, click BPMN Resources Usage Matrix. The BPMN Resources Usage Matrixes dialog will open.

2. Click the Add button. The Create Diagram dialog will open.3. Type the name and select the owner of the matrix, and then click OK

(iii) To create a new BPMN Resources Usage Matrix through the shortcut menu in the Containment tree:

1. Right-click a package in the Containment tree and click New Diagram > BPMN Resources Usage Matrix.

2. Type the name of the matrix.

Related conceptsBPMN Resources Usage MatrixActivities



3.5.6 Modifying a BPMN Resources Usage Matrix

To change the scope of elements of a matrix row or column:

1. Click the Row Scope / Column Scope property “...” button.2. Select package elements to be displayed in a matrix row or column.

To change a resource assignment to an Activity, either:

(i) Double-click a cell, which is the intersection of an Activity and a resource, to add or remove a rela-tion.

(ii) Right-click a cell, which is the intersection of an Activity and a resource and select New Relation > Row to Column, and then click either resources to add a relation or Delete Relation > resources to remove a relation.


cameo business modeler analyst edition user guide...1.2.1 installing cameo business modeler analyst...

Documents