13 BPMN Execution Semantics

13.1 General

NOTE: The content of this clause is REQUIRED for BPMN Process Execution Conformance or for BPMN Complete Conformance. However, this clause is NOT REQUIRED for BPMN Process Modeling Conformance, BPMN Choreography Conformance, or BPMN BPEL Process Execution Conformance. For more information about BPMN conformance types, see page 1.

This sub clause defines the execution semantics for orchestrations in BPMN 2.0.2. The purpose of this execution semantics is to describe a clear and precise understanding of the operation of the elements. However, for some elements only conceptual model is provided which does not specify details needed to execute them on an engine. These elements are called non-operational. Implementations MAY extend the semantics of non-operational elements to make them executable, but this is considered to be an optional extension to BPMN. Non-operational elements MAY be ignored by implementations conforming to BPMN Process Execution Conformance type. The following elements are nonoperational:

•Manual Task

•Abstract Task

•DataState

•IORules

•Ad-Hoc Process

•ItemDefinitions with an itemKind of Physical

•the inputSetWithWhileExecuting attribute of DataInput

•the outputSetWithWhileExecuting attribute of DataOutput

•the isClosed attribute of Process

•the isImmediate attribute of Sequence Flow

The execution semantics are described informally (textually), and this is based on prior research involving the formalization of execution semantics using mathematical formalisms.

This sub clause provides the execution semantics of elements through the following structure:

•A description of the operational semantics of the element.

•Exception issues for the element where relevant.

•List of workflow patterns1supported by the element where relevant.

1.http://www.workflowpatterns.com/patterns/control/index.php