Resumen. Resumen. Resumen. Resumen. Resumen. Resumen.
Resumen. Resumen. Resumen. Resumen. Resumen. Resumen.
Texto texto texto texto texto texto texto texto texto texto texto texto texto texto texto texto. Texto texto texto texto texto texto texto texto texto texto texto texto texto texto texto texto.
Advanced
BPMN-Specification-text. BPMN-Specification-text. BPMN-Specification-text.
BPMN-Specification-text. BPMN-Specification-text. BPMN-Specification-text.
Otros
El Diagrama de Conversación es una descripción informal de un Diagrama de Colaboración. Normalmente, las Piscinas en una Conversación no contienen Procesos, es decir, son "cajas negras". Muestra Conversaciones (hexágonos) entre Participantes (Piscinas). Proporciona una perspectiva "a vista de pájaro" de las diferentes Conversaciones relacionadas con un cierto dominio.
Por ejemplo, en logística, las reposiciones de existencias involucran los siguientes escenarios: creación de órdenes de venta; asignación de transporte para los envíos combinando diferentes órdenes de venta; internación en aduanas; procesamiento de pagos y manejo de excepciones. Como se muestra en el siguiente Diagrama de Conversación.
El Diagrama de Conversación, además de las Piscinas, contiene Conversaciones y Enlaces de Conversación (líneas finas dobles).
Una Conversación es un conjunto de Flujos de Mensajes que están lógicamente relacionados, comparten un propósito particular. Usualmente, la relación lógica se refiere a una entidad manipulada en el negocio. Por ejemplo, un Pedido, una Orden Trabajo, o una Factura.
Los intercambios de Mensajes están relacionados entre sí y reflejan distintos escenarios. La relación a veces es simple, por ejemplo, una solicitud seguida de una respuesta. Sin embargo, la relación puede ser compleja, involucrando intercambios de Mensajes de larga duración, y que pueden involucrar a más de dos Participantes.
Una conversación es un elemento atómico para un diagrama de conversación (colaboración). Representa un conjunto de flujos de mensajes agrupados en función de un concepto y/o una clave de correlación. Una conversación involucrará a dos o más participantes.
Explicar someramente qué es una subconversación en el contexo del ejemplo. El marcador de subconversación es un cuadrado pequeño con un signo más (+).
Para mayor detalle remitir a la especificación.
Especificación BPMN
With publication a trigger MAY be received by any catching Events in any scope of the system where the trigger is published. Events for which publication is used are grouped to Conversations. Published Events MAY participate in several Conversations.
The Conversation diagram is a particular usage of and an informal description of a Collaboration diagram. However, the 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. The logical relation, in practice, often concerns a business object(s) of interest, e.g., “Order,” “Shipment and Delivery,” or “Invoice.”
Message exchanges are related to each other and reflect distinct business scenarios. For example, in logistics, stock replenishments involve the following type scenarios: creation of sales orders; assignment of carriers for shipments combining different sales orders; crossing customs/quarantine; processing payment, and investigating exceptions. Thus, a Conversation diagram, as shown in Figure 7.5, shows Conversations (as hexagons) between Participants (Pools). This provides a “bird’s eye” perspective of the different Conversations that relate to the domain.
A set of Messages Flow of a particular Collaboration MAY belong to a Conversation. A Conversation is a set of Message Flows that share a particular purpose (i.e., they all relate to the handling of a single order - see page 123 for more information about Conversations).
The Conversation diagram is particular usage of and an informal description of a Collaboration diagram. In general, it is a simplified version of Collaboration, but Conversation diagrams do maintain all the features of a Collaboration. In particular, Processes can appear within the Participants (Pools) of Conversation diagrams, to show how Conversation and Activities are related.
The view includes two additional graphical elements that do not exist in other BPMN views:
- Conversation Node elements (Conversation, Sub-Conversation, and Call Conversation)
- A Conversation Link
A Conversation is a logical grouping of Message exchanges (Message Flows) that can share a Correlation. A Conversation is the logical relation of Message exchanges. The logical relation, in practice, often concerns a business object(s) of interest, e.g., “Order,” “Shipment and Delivery,” and “Invoice.” Hence, a Conversation is associated with a set of name-value pairs, or a Correlation Key (e.g., “Order Identifier,” “Delivery Identifier”), which is recorded in the Messages that are exchanged. In this way, a Message can be routed to the specific Process instance responsible for receiving and processing the Message.
Message exchanges are related to each other and reflect distinct business scenarios. The relation is sometimes simple, for example, a request followed by a response, and can be described as part of a structural interface of a service (e.g., as a WSDL operation definition). However for commercial business transactions managed through Business Processes, the relation can be complex, involving long-running, reciprocal Message exchanges, and that could extend beyond bilateral to complex, multilateral Collaborations. For example, in logistics, stock replenishments involve the following types scenarios: creation of sales orders, assignment of carriers for shipments combining different sales orders, crossing customs/quarantine, processing payment, and investigating exceptions.
The Message exchanges of a Conversation will be executed ultimately through an orchestration Process.
Since Collaboration provides a top-down, design-time modeling perspective for Message exchanges and their Conversations, an abstracted view of the all Conversations pertaining to a domain being modeled is available through a Conversation diagram. A Conversation diagram, as depicted in Figure 9.18, shows Conversations (as hexagons) between Participants. This provides a “bird’s eye” perspective of the different Conversations that relate to the domain.
A Conversation is an atomic element for a Conversation (Collaboration) diagram. It represents a set of Message Flows grouped together based on a concept and/or a CorrelationKey. A Conversation will involve two or more Participants.
A Sub-Conversation is a ConversationNode that is a hierarchical division within the parent Collaboration. A Sub-Conversation is a graphical object within a Collaboration, but it also can be “opened up” to show the lower-level details of the Conversation, which consist of Message Flows, Conversations, and/or other Sub-Conversations.
The Sub-Conversation shares the Participants of its parent Conversation.
A Sub-Conversation is a hexagon that MUST be drawn with a single thin line (see Figure 9.24).
The Sub- Conversation marker MUST be a small square with a plus sign (+) inside. The square MUST be positioned at the bottom center of the shape.
Conversation Links are used to connect ConversationNodes to and from Participants (Pools -- see Figure 9.27). Conversation Links MUST be drawn with double thin lines.
Processes can appear in the Participants (Pools) of Conversation diagrams, as shown in Figure 9.28. The invoicing and ordering Conversations have links into Activities and Events of the Process in the Order Processor. The other two Conversations do not have their links “expanded.” Conversation Links into Activities that are not Send or Receive Tasks indicate that the Activity will send or receive Messages of the Conversation at some level of nesting.
