Diagrama de Proceso

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.

Sección 1

Texto. texto. texto. texto. texto. texto.

Sección 2

Texto. texto. texto. texto. texto. texto.

Otros

Proceso.

Proceso Principal, con y sin Piscina.

Subproceso Embebido colapsado y diagrama de proceso separado para el Subproceso.

Subproceso Embebido expandido. Solo cuando es "caja paralela".

Proceso Ejecutable y No Ejecutable

Proceso Público vs Privado.

Proceso Privado como Colaboración implícita.

Temporal

Texto.Texto.

Texto.Texto.

Texto.Texto.

Texto.Texto.

Especificación BPMN

Private (Internal) Business Processes

Private Business Processes are those internal to a specific organization. These Processes have been generally called workflow or BPM Processes. Another synonym typically used in the Web services area is the Orchestration of services.

There are two types of private Processes: executable and non-executable. An executable Process is a Process that has been modeled for the purpose of being executed according to the semantics defined in Clause 14. Of course, during the development cycle of the Process, there will be stages where the Process does not have enough detail to be “executable.” A non-executable Process is a private Process that has been modeled for the purpose of documenting Process behavior at a modeler-defined level of detail. Thus, information needed for execution, such as formal condition Expressions are typically not included in a non-executable Process.

If a swimlanes-like notation is used (e.g., a Collaboration, see below) then a private Business Process will be contained within a single Pool. The Process flow is therefore contained within the Pool and cannot cross the boundaries of the Pool. The flow of Messages can cross the Pool boundary to show the interactions that exist between separate private Business Processes.

Public Processes

A public Process represents the interactions between a private Business Process and another Process or Participant (see Figure 7.2). 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 in the public Process. Thus, the 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. Note that the public type of Process was named “abstract” in BPMN 1.2.

solocastellano