Embed Size (px)
Citation preview
What is new in XPDL
Robert ShapiroVP Global 360XPDL 2.2 and 3.0 Editor
BPMN 2.0 FTF Member
Denis Gagné, CEO & CTO TrisotechXPDL 2.2 and 3.0 Co-Editor
BPMN 2.0 FTF Member
What is BPMN?
What is BPMN?Business Process Model and Notation
Why BPMN matters?Readily understandable by business stakeholders
Aim to bridge the gap from modeling to subsequent implementation
What is XPDL?
What is XPDL?XML Process Definition Language
Why XPDL matters?Meant for interchange from inception
Internal model of many existing BPM tools
Backward compatibility of BPMN 1.2
BPMIBPMI
Standards Timeline - Releases
WPDLWPDL
XMLXML
BPMN 1.0BPMN 1.0
XPDL 2.0XPDL 2.0 XPDL 2.1XPDL 2.1
1994 1998 2000 2001 2008 201020072006 20092004 20052002 2003
XPDL 1.0
XPDL 1.0
BPMN 1.0BPMN 1.0 BPMN 1.1
BPMN 1.1
BPMN 2.0
XPDL 2.2
2011
XPDL 3.0
BPMN 1.2
BPMN 1.2
BPMN 2.1
- R. Shapiro, WfMC
New in BPMN 2.0
Some new concepts and constructs
A graphical notation for modeling interactions (adding choreographies and conversations)
Better standard conformance specification along with conformance sub-classes
A meta-model and accompanying interchange formats both XMI and XSD based
A diagram definition model and accompanying interchange formats both XMI and XSD based
An explicit execution semantics
A mapping from a BPMN subset to WS-BPEL
Scope of XPDL 2.2
The XPDL 2.2 effort is focused on only covering a subset of the Process Modeling Conformance class of the BPMN 2.0 specification.
Thus the XPDL 2.2 schema will offer a serialization and interchange transport for BPMN 2.0:
Process Diagrams, and
Collaboration Diagrams (Without Conversation)
(i.e. what was possible in BPMN 1.2)
Scope of XPDL 3.0
The XPDL 3.0 effort is focused on covering the complete BPMN 2.0 specification.
Thus the XPDL 3.0 schema will offer a serialization and interchange transport for BPMN 2.0:
Process Diagrams,
Collaboration Diagrams,
Conversation Diagrams,
Choreography Diagrams
And all attributes.
What is new in XPDL 2.2?
Denis Gagné, TrisotechBPMN 2.0 FTF MemberXPDL 2.2 and 3.0 Co-Editor
Goal of XPDL 2.2.
The XPDL 2.2 schema is to be backward compatible with the XPDL 2.0 and XPDL 2.1 schemas.
This backward compatibility also extends to XPDL 2.1 schema’s capability to serialize BPMN 1.2 drawings.
Guidelines
The following guidelines were followed in the production of the new XPDL 2.2 Schema:
Where possible elements and attributes of the BPMN 2.0 specification were mapped to semantically equivalent existing elements of the current XPDL 2.1 schema.
A concerted effort was made to only introduce new elements and attributes only when absolutely necessary. These new elements and attributes were introduced in a manner coherent with the existing XPDL Meta-model.
Care was taken when strongly typing elements and attributes in the XPDL 2.2 schema as some structural rules are divergent or contradictive between BPMN 1.2 and BPMN 2.0.
Annotations were inserted in the schema where appropriate to ease readability and clarify mapping intentions ( care was taken in specifying structural conformance rules in annotations, as some structural rules are divergent or contradictive between BPMN 1.2 and BPMN 2.0)
Baseline References
XPDL
The version bpmnxpdl_33 of the XPDL schema was the baseline for the creation of the XPDL 2.2 schema.
BPMN 2.0 Schema
The various schema files produced out of Beta 2 of the BPMN 2.0 specification were the baseline for the creation of the XPDL 2.2 schema.
BPMN 2.0 Specification Document
Version Beta 2 of the BPMN 2.0 specification was the reference for the creation of the XPDL 2.2 schema.
Corrections to XPDL 2.1
Added an Orientation attribute to Lane element.
Added Associations and Artifacts as possible children of ActivitySet.
Annotated as deprecated LoopCondition attribute in LoopStandard (seems to have been the intent in XPDL 2.1)
Annotated as deprecated ComplexMI_FlowCondition attribute in LoopMultiInstance as per XPDL 2.1 Spec document.
In LoopMultiInstance, annotated as deprecated MI_Condition attribute. ( Should use the MI_Condition element. This way, when the integer value is known the expression is simply the integer value.)
Added a default value of false to IsForCompensation attribute of the Activity Element
Minor edits to various annotations of the Route element
Re-ordered the enumeration of GatewayType to group deprecated values together
Changed the attribute result of EndEvent to required (to align with the trigger for both start and intermediate event which are required)
TriggerIntermediateMultiple (for multiple intermediate event)
Added TriggerResultCancel element as a possible child node (was missing)
EndEvent
Added TriggerResultCancel element as a possible child node (was missing)
ResultMultiple (for multiple end event)
Added TriggerResultCancel element as a possible child node (was missing)
Added TriggerResultCompensation element as a possible child node (was missing)
Package Definition Meta Model
Process(W. Process)
Package[Business Process
Diagram (BPD)]
Type Declaration
ApplicationParticipant
Pool
Lane
Data Field
ExternalPackage
0..1
0..10..1
0..1
0..1
0..1
*
*
*
*
*
*
**
MessageFlow
Association
Artifact
sourcetarget
sourcetarget
Activity
target
source
source
sourcetarget
target
Resource Repository or Organizational Model
System and environmental data
W. Relevant Data
Data Object
Group
Annotation
Data Store
*
Global Activity
*
Package
Process Definition Meta Model
Process(W. Process)
Type Declaration
Application
ActivitySet(Embedded Sub-Process)
(Event Sub-Process)
Data Field(Property)
Participant ActivityTransition
(Sequence Flow)to
fromperformer
performer
usesuses
uses
uses
Pool Lane BlockActivityTask/Tool
SubFlow
Event
Route
Reference
Resource Repository or Organizational Model
System and environmental data
W. Relevant Data
Gateway
Data Association
DataObjectDataInput
DataOutputFrom/to
From/to
From/to
DataStore References
ActivitySet
WorkflowProcess
Current Status of XPDL 2.2
Completed
The XPDL 2.2 schema is completed and has been validated and tested.
Remaining
The XPDL 2.2 Specification Document has been initiated (based on bpmnxpdl_39)
Current Schema Version
bpmnxpdl_40
Current Status XPDL 3.0
Completed
The XPDL 3.0 schema covering all visual elements has been completed and validated
Remaining
Non visual attributes inclusion has started but is not completed
The XPDL 3.0 Specification Document has not been started
Current Schema Version
bpmnxpdl_41
Call to Action
Immediate help is required to complete changes to the XPDL Specification Document to reflect the latest Schema
Business Process Incubator
www.BusinessProcessIncubator.com
