Bernard Szlachta: /* Conversation ⌘ */

2013-06-30T12:04:03Z

Conversation ⌘

New page

{{Cat|NobleProg BPMN Certification Level 1|00}}
[[Category:Private]]
== BPMN 2.0 Purpose ⌘==
# Provide a notation that is readily understandable by business and technical people
# Create a standardized bridge for the gap between the business process design and process implementation
# To ensure that XML languages designed for the execution of business processes, such as WSBPEL, can be visualized with a business-oriented notation.
# To standardize a business process model and notation in the face of many different modeling notations and viewpoints
# To provide a means of communicating process information to other businesses, users, managers and process implementers
# To exchange BPMN definitions (both domain model and diagram layout) between different tools

== Audience of BPMN ⌘==
* Business users
** Business analysts
** Strategy analyst
** Quality managers

* Technical developers
** Process designers
** Developers
** Integrators
** Software, System and Enterprise Architects

== Conformance ⌘==
Software '''based on''' spec
* software developed only partially matching compliance/conformance

Modeling Conformance
* Process modeling
* Choreography modelling

Execution Conformance
* Process Execution
* BPEL Process Execution

Tool can comply only to one of the above or any subset of them.

'''BPMN Complete Conformance''' complies to the all 4 above.

== Sub-models within an end-to-end BPMN model ⌘==
# '''Processes''' (Orchestration)
#* Private non-executable (internal) BP
#* Private executable (internal) BP
#* Public Processes
# '''Choreographies'''
# '''Collaborations''' (can include Processes and Choreographies
#* Conversations

== BPMN 2.0 compared to BPMN 1.2 ⌘==
* Formalizes the execution semantics for all BPMN elements
* Defines an extensibility mechanism
* Refines Event composition and correlation
* Extends the definition of human interactions
* Defines a Choreography model

== BPMN Sub-models ⌘==
# Orchestration
#* Private non-executable (internal) Business Processes
#* Private executable (internal) Business Processes
#* Public Processes
# Choreographies
# Collaborations, which can include Processes and/or Choreographies
#* A view of Conversations

== Private (Internal) Business Process ⌘==
* Internal to a specific organization
* Other names:
** Workflow
** BPM Processes
** Orchestration of services
* Can be executable and non-executable
* Contained within a single Pool
* The flow of Messages can cross the Pool boundary to show the interactions that exist between separate private Business Processes

<signavio>cd1fc43dc515451c8328502b8a08b923:e475f9e2bff59ca69841041bc25a1fa541560476ca0b2913ed335cab8df34e0_7fdb1ff2ef9094223def5afde424126229ba137c1ed4d72fe416b3edf2fba2_e485bafe8e57f036e48a432ebdc8987efcdce6ebddfbb75bf170965a3975c16</signavio>

== Public Process ⌘==
* Represents the interactions between a private Business Process and another Process or Participant
* Only those Activities that are used to communicate to the other Participant(s) are included in the public Process
* All other “internal” Activities of the private Business Process are not shown
* Public Process shows to the outside world the Message Flows and the order of those Message Flows that are needed to interact with that Process
* Public Processes can be modeled separately or within a Collaboration to show the flow of Messages between the public Process Activities and other Participants
* Called “abstract” in BPMN 1.2.
* Public Process is orchestrated by the private processes (as oppose to Collaboration)

<signavio>ece7d3b879d94c79b10e41fc378e706c:46c42041b0f77d715f7b8af11ff43c9ca6c783ea09c6ec60f04f5b961b91_4967cac8dcfd832e16124cc1dfd8036682d21e8c11ac0bb9bea7d875527c615_a5f0d97f4e892962dd98ee74171e62ce8524f0ee737d927065ac95c660b524c</signavio>
{{PB}}

== Collaboration ⌘==
* Depicts the interactions between two or more business entities
* Contains two or more Pools
* Can be shown as two or more public Processes communicating with each other
* The corresponding internal (executable) Processes are likely to have much more Activity and detail than what is shown in the public Processes.

<signavio>7d4b0223cf224b37b35fddcffce16cb2:c5640bf3ae026a8b7753ae86eea1e1c31e36d3cf42be54d1f744e4a212f11ac_57f164c43cf29bd16dd03e685f163c8e61c61c2467cb5977134d9c1281d0d2_742aba653cf647ca2efea2283c688da6a8b718a946e501be2c76d94d060eeb</signavio>
{{PB}}

== Choreography ⌘==
* Definition of the expected behavior
* B procedural contract between interacting Participants
* A self-contained Choreography have no Pools or Orchestration
* Choreography exists between Pools (or Participants)
* The Choreography Activities are interactions that represent a set (1 or more) of Message exchanges, which involves two or more Participants
* '''There is no central controller''', responsible entity or observer of the Process

<signavio>600f813d53b5484e875f2e5803465cfe:6c77972c7e6356d02bb9c59224a445952c53224076fa8acaf85546a3bba74d5_494ba83449cdc5ebb1ccae4fa3504d2011bd73d3adb67a32de1ccb2d1d77182_b33c61976c55e3ada37bdab95f4e9a8333bf7cc1fcb92bfe987a99b6a507</signavio>

== Conversation ⌘==
* The Conversation diagram is a particular usage of and an informal description of a Collaboration diagram
* Pools of a Conversation usually do not contain a Process and a Choreography is usually not placed in between the Pools of a Conversation diagram
* A Conversation is the logical relation of Message exchanges
* Message exchanges are related to each other and reflect distinct business scenarios
* Conversation Diagram Provides a “bird’s eye” perspective of the different Conversations that relate to the domain
<signavio>2ec3cc87a58a41b5a253c680986a9d9d:1f7bd3da85383d0f53e4a38afeee7454d8833a24fcce6ae68f523e89c38cf8_b507aeb1c9ee295a1636355a632817d6eaab745ef12958c0f5d1abfb272fcc_f58d9b7e4729ecca1c6c46b4b992ad0d7bdea2dc81ffa2f9b35fc628fb64e</signavio>

== Quiz ==
* http://selfstudy.nobleprog.com/node/446/

BPMN 2.0 Purpose and Structure - Revision history

Bernard Szlachta: /* Conversation ⌘ */