SUBMITTED TO

MS RADHA SARFRAZ
SUBMITTED BY
GROUP G
SUBJECT

BUSINESS PROCESS MANAGEMENT

 PROCESS
CHOREOGRAPHICS
PROCESS CHOREOGRAPHIES
• Business-to-business collaboration
• To realize these collaborations, process orchestrations interact with each
other, typically by sending and receiving messages.
• Ensuring interoperability between process orchestrations, each of which is
performed by a participant in a business-to-business collaboration.
Example: Rosetta Net for the supply chain domain.
Need and Advantage
• Companies increasingly join forces to combine their services and
products to provide added value products to the market.
• Costs for the individual companies are reduced
• New companies can join the market more easily,
• Depend on the number of interacting partners and the desired level of
automation.
The first activity to be performed by Company 1 is receive activity A1.
This activity waits to receive a message sent by activity B2. Assuming
that communication is synchronous, i.e., the receive activity A1 is
blocking, the process orchestration run by Company 1 cannot proceed.
Analogously, Company 2 waits in activity A2 to receive a message from
activity C1 to be sent by Company 1. As a result, both process
orchestrations cannot proceed: they are stuck in a permanent deadlock
situation. To avoid these kinds of problems, the partners involved in a
process choreography need to agree on the process choreography.
Deadlock of interacting process orchestrations
5.2 DEVELOPMENT PHASES
• Business engineers are mainly involved in the
choreography design phases, including scenario
modelling, domain scoping, milestone definition, and
participant identification.
• Business engineers are responsible for business-
related aspects of the process choreography; they
need to make sure that the collaboration contributes to
the goals of the enterprise, similarly to organizational
business processes.
5.3 PROCESS CHOREOGRAPHY DESIGN
• The design of process choreographies involves a series of
activities. In each of these activities, artefacts are developed.
These activities are described as follows:

1. High-level 1.Structure Design:.

High level structure design is conducted during the
Participant identification phase.is derived.
2. High-level Behavioral Design:
High-level behavioral models specify the milestones of the collaboration and the order in
which the milestones are reached.

3. Collaboration Scenarios:
Collaboration scenarios are developed during the choreography definition
phase.

4.Behavioural Interfaces:
From these collaboration scenarios, for each participant role, a behavioral
interface.
5.4 PROCESS CHOREOGRAPHY IMPLEMENTATION

• Most business processes, however, interact with business processes in other

organizations, forming process choreographies. In this phase all the processes of
choreographies are implemented . Most business processes, however, interact with
business processes in other organizations, forming process choreographies. In this phase

all the processes of choreographies are implemented .

• The relationship between the behavioral interface and the local
process orchestration needs to be investigated, so that the
correctness of the overall collaboration can be achieved. Each local
process orchestration needs to be consistent with the respective
behavioral interface definition. This section will introduce
consistency criteria using a business-to-business collaboration
scenario.
• An implementation is consistent with a behavioral interface is
subject to consistency criteria.
• This section will introduce consistency criteria using a
business-to-business collaboration scenario.
• An implementation is consistent with a behavioral interface
is subject to consistency
criteria.
issues of process choreographies:

• Lack of collaboration

• Lack of flexibility in processes orchestrations of

choreographies

• Lack of compatibility of choreographies software

Service Interaction Patterns
• Choreographies are based on message exchange, while orchestrations are based on control
flow between the activities of a single process performed by a single organization.
• Service interaction patterns aim at filling this gap by proposing small granular types of
interactions that can be combined to process choreographies.

Service interaction patterns can be classified according to the following schemes.

• Number of participants involved:

Bilateral interactions involve two participants, whereas multilateral interactions involve
more than two participants.

• Number of messages exchanged:

Single transmission versus multi-transmission interactions.
• Variations in message receiver:
In case of two-way interactions, round-trip interaction means

that the receiver of the message is necessarily the same as the

sender, whereas routed interaction means that the receiver of
the message in general differs from the sender.
The service interaction patterns are described properly.

• Send
• Receive
• Send/Receive
SEND
The send pattern represents a one-way interaction
between• Variations in message receiver: In case
of two-way interactions, round-trip interaction
means that the receiver of the message is
necessarily the same as the sender,
whereas routed interaction means that
the receiver of the message in general
differs from the sender.
Receive
The receive pattern also describes a one-
way interaction between two participants,
but this time seen from the perspective of
the receiver.
For example the facility management
department of a company receives a
notification that the heating system in a
building does not work properly.
Send/Receive:
• The send/receive pattern, a participant sends a request to another
participant who then returns a response message.
• Both messages belong to the same conversation.
• Since there could be several send/receive interaction instances
happening in parallel, corresponding requests and responses need to be
correlated.
For example the Client server model.

•
 One-To-Many Send :
• A participant sends out several
messages to other participants in
parallel.
• It might be the case that the list of
recipients is already known at
design-time of the choreography
or, alternatively, the selection of
the recipients takes place in the
course of the conversation.
One-From-Many Receive:
In the one-from-many receive pattern, messages can be received from many
participants. In particular, one participant waits for messages to arrive from other
participants, and each of these participants can send exactly one message.

One-To-Many Send/Receive:
In the one-to-many send/receive pattern, a participant sends out several
requests to different other participants and waits for responses. Typically, notall
responses need to be waited for. The requester rather waits for a certain amount
of time or stops waiting as soon as enough responses have arrived.
5.6 Let’s Dance
Let’s Dance is a choreography language
It is based on control flow patterns and
service interaction patterns.
Let’s Dance comes with two different
diagram types for supporting
1):High-level Choreographies
In the design of high-level choreographies,
a structural, role-based view and a
behavioral milestone view can be
distinguished.
2): Modelling Interactions
• The main focus of Let’s Dance is to
capture interactions and their behavioural
dependencies.
• Elementary interactions are the building
blocks by which complex interaction rules
can be defined
Thank you