9 Collaboration

9.1General

NOTE: The contents of this clause are REQUIRED for BPMN Choreography Modeling Conformance, BPMN Process Modeling Conformance, or for BPMN Complete Conformance. However, this clause is NOT REQUIRED for BPMN

Process Execution Conformance or BPMN BPEL Process Execution Conformance. For more information about BPMN conformance types, see page 1.

The Collaboration package contains classes that are used for modeling Collaborations, which is a collection of Participants shown as Pools, their interactions as shown by Message Flows, and MAY include Processes within the Pools and/or Choreographies between the Pools (see Figure 9.1). A Choreography is an extended type of Collaboration. When a Collaboration is defined it is contained in Definitions.

Business Process Model and Notation (BPMN), v2.0.2

107

Figure 9.1 – Classes in the Collaboration package

The Collaboration element inherits the attributes and model associations of BaseElement (see Table 8.5) through its relationship to RootElement. Table 9.1 presents the additional attributes and model associations for the Collaboration element.

Table 9.1 – Collaboration Attributes and Model Associations

Attribute Name

Description/Usage

 

 

name: string

Name is a text description of the Collaboration.

 

108

Business Process Model and Notation (BPMN), v2.0.2

Table 9.1 – Collaboration Attributes and Model Associations

choreographyRef:

The choreographyRef model association defines the Choreographies that

Choreography [0..*]

can be shown between the Pools of the Collaboration. A Choreography

 

 

specifies a business contract (or the order in which messages will be

 

exchanged) between interacting Participants. See page 315 for more details

 

on Choreography.

 

The participantAssociations (see below) are used to map the

 

Participants of the Choreography to the Participants of the Collaboration.

 

The MessageFlowAssociations (see below) are used to map the

 

Message Flows of the Choreography to the Message Flows of the

 

Collaboration.

 

The conversationAssociations (see below) are used to map the

 

Conversations of the Choreography to the Conversations of the

 

Collaboration.

 

Note that this attribute is not applicable for Choreography or

 

GlobalConversation which are a subtypes of Collaboration. Thus, a

 

Choreography cannot reference another Choreography.

correlationKeys:

This association specifies CorrelationKeys used to associate Messages

CorrelationKey [0..*]

to a particular Collaboration.

 

 

 

conversationAssociations:

This attribute provides a list of mappings from the Conversations of a

ConversationAssociation [0..*]

referenced Collaboration to the Conversations of another Collaboration.

 

 

It is used when:

 

• When a Choreography is referenced by a Collaboration.

 

 

conversations:

The conversations model aggregation relationship allows a

ConversationNode [0..*]

Collaboration to contain Conversation elements, in order to group

 

 

Message Flows of the Collaboration and associate correlation information,

 

as is REQUIRED for the definitional Collaboration of a Process model. The

 

Conversation elements will be visualized if the Collaboration is a

 

Collaboration, but not for a Choreography.

 

 

conversationLinks:

This provides the Conversation Links that are used in the Collaboration.

ConversationLink [0..*]

 

 

 

artifacts: Artifact [0..*]

This attribute provides the list of Artifacts that are contained within the

 

Collaboration.

participants: Participant [0..*]

This provides the list of Participants that are used in the Collaboration.

 

Participants are visualized as Pools in a Collaboration and as Participant

 

Bands in Choreography Activities in a Choreography.

 

 

Business Process Model and Notation (BPMN), v2.0.2

109

Тут вы можете оставить комментарий к выбранному абзацу или сообщить об ошибке.

Оставленные комментарии видны всем.