BPMN 2.0 Unleashed
Ivana Trickovic
SAP AG
BPMN 2010, Potsdam, Germany
BPMN 2.0 Milestones
© SAP 2010, Template / Page 1
June 2007
BPMN 2.0 RFP
Issued
Jan 2008
BPMN 1.2 FTF/RTF
Finalized
June 2009
BPMN 2.0 Submission
and OMG Vote
Sep 2009
BPMN 2.0 FTF
Started
June 2010
BPMN 2.0 FTF
Finalized
Sep 2010
OMG DTC Approved
BPMN 2.0 FTF Report
BPMN 2.1 RTF to Start
OMG BPMN 2.0 Standard
to be Published
New Capabilities in BPMN 2.0
BPMN Metamodel
Formalized
BPMN Execution
Semantics Refined
and Formalized
New Process
Elements (e.g. Data
Objects, Non-
interrupting
Events, Service
Model, etc.)
Interaction Models
Interchange
Formats
Visual Model and
Diagram
Interchange
Format
© SAP 2010, Template / Page 2
Business Value
End-user Simplification
Shorter learning curve as it is an extension of BPMN 1.x
Skills and investment protection
Unified notation for business processes and business interactions
Enables seamless “design-to-implement”
Vendor Productivity
Portability of process definitions enabled
Extendable language for future innovations
Investment protection
© SAP 2010, Template / Page 3
Conformance Classes
• For tool vendors whose tools support modeling of
orchestration processes and reasoning and not
necessarily process execution
Process Modeling
• For tool vendors whose tools support deployment of
business process models into execution
environments
Process Execution
• As per process execution, but for BPEL
environments, aligned with the process execution
standard
BPEL Process Execution
• For tool vendors whose tools support modeling of
choreographiesChoreography
© SAP 2010, Template / Page 4
Conformance Classes - Details
© SAP 2010, Page 5
Category
Process Modeling
Conformance
Process
Execution
Conformance
BPEL Process
Execution
Conformance
Choreography
Conformance
Visual representation
of BPMN Diagrams
Process diagrams and
Collaboration
diagrams depicting
Collaborations
between Processes
N/A N/A
Choreography
diagrams and
Collaboration
diagrams depicting
Choreography within
Collaboration
Supported BPMN
Diagram elements
Defined sub-classes:
Descriptive
Analytic
Common Executable
Complete
N/A N/A
Complete set. No sub-
classes defined.
Interchange format
(BPMN 2.0
metamodel)
For Process diagrams
and Collaboration
diagrams depicting
Collaborations
between Processes
Yes for Process
diagrams
Yes for Process
diagrams
For Choreography and
Collaboration
diagrams depicting
Choreography within
Collaboration
Execution semantics N/A
Yes for Processes Yes for Processes
Yes for
Choreographies
Adoption Challenges
© SAP 2010, Template / Page 6
How to test compliance
with BPMN 2.0
Can optional elements (or)
attributes be ignored How to add additional
compliance points
Possible Improvements
Validate mandatory and optional elements and attributes
Clarify whether
An element (or attribute) is optional and does not have to be supported by
conforming implementations or
The value of the element (or attribute) is optional
Derive all static validation rules mandated by the specification
Introduce BPMN Profiles to simplify BPMN conformance points
Introduce conformance tests
© SAP 2010, Template / Page 7
Thank you!
© SAP 2010, Template / Page 8
SAP Business Process Expert Community
bpx.sap.com

Ivana Trickovic @ BPMN 2010

  • 1.
    BPMN 2.0 Unleashed IvanaTrickovic SAP AG BPMN 2010, Potsdam, Germany
  • 2.
    BPMN 2.0 Milestones ©SAP 2010, Template / Page 1 June 2007 BPMN 2.0 RFP Issued Jan 2008 BPMN 1.2 FTF/RTF Finalized June 2009 BPMN 2.0 Submission and OMG Vote Sep 2009 BPMN 2.0 FTF Started June 2010 BPMN 2.0 FTF Finalized Sep 2010 OMG DTC Approved BPMN 2.0 FTF Report BPMN 2.1 RTF to Start OMG BPMN 2.0 Standard to be Published
  • 3.
    New Capabilities inBPMN 2.0 BPMN Metamodel Formalized BPMN Execution Semantics Refined and Formalized New Process Elements (e.g. Data Objects, Non- interrupting Events, Service Model, etc.) Interaction Models Interchange Formats Visual Model and Diagram Interchange Format © SAP 2010, Template / Page 2
  • 4.
    Business Value End-user Simplification Shorterlearning curve as it is an extension of BPMN 1.x Skills and investment protection Unified notation for business processes and business interactions Enables seamless “design-to-implement” Vendor Productivity Portability of process definitions enabled Extendable language for future innovations Investment protection © SAP 2010, Template / Page 3
  • 5.
    Conformance Classes • Fortool vendors whose tools support modeling of orchestration processes and reasoning and not necessarily process execution Process Modeling • For tool vendors whose tools support deployment of business process models into execution environments Process Execution • As per process execution, but for BPEL environments, aligned with the process execution standard BPEL Process Execution • For tool vendors whose tools support modeling of choreographiesChoreography © SAP 2010, Template / Page 4
  • 6.
    Conformance Classes -Details © SAP 2010, Page 5 Category Process Modeling Conformance Process Execution Conformance BPEL Process Execution Conformance Choreography Conformance Visual representation of BPMN Diagrams Process diagrams and Collaboration diagrams depicting Collaborations between Processes N/A N/A Choreography diagrams and Collaboration diagrams depicting Choreography within Collaboration Supported BPMN Diagram elements Defined sub-classes: Descriptive Analytic Common Executable Complete N/A N/A Complete set. No sub- classes defined. Interchange format (BPMN 2.0 metamodel) For Process diagrams and Collaboration diagrams depicting Collaborations between Processes Yes for Process diagrams Yes for Process diagrams For Choreography and Collaboration diagrams depicting Choreography within Collaboration Execution semantics N/A Yes for Processes Yes for Processes Yes for Choreographies
  • 7.
    Adoption Challenges © SAP2010, Template / Page 6 How to test compliance with BPMN 2.0 Can optional elements (or) attributes be ignored How to add additional compliance points
  • 8.
    Possible Improvements Validate mandatoryand optional elements and attributes Clarify whether An element (or attribute) is optional and does not have to be supported by conforming implementations or The value of the element (or attribute) is optional Derive all static validation rules mandated by the specification Introduce BPMN Profiles to simplify BPMN conformance points Introduce conformance tests © SAP 2010, Template / Page 7
  • 9.
    Thank you! © SAP2010, Template / Page 8 SAP Business Process Expert Community bpx.sap.com