1 / 27

On the Translation between BPMN and BPEL: Conceptual Mismatch between Process Modeling Languages

On the Translation between BPMN and BPEL: Conceptual Mismatch between Process Modeling Languages. Jan Recker Queensland University of Technology, Brisbane Jan Mendling Vienna University of Economics. From the BPMN Specification:.

feng
Download Presentation

On the Translation between BPMN and BPEL: Conceptual Mismatch between Process Modeling Languages

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. On the Translation between BPMN and BPEL:Conceptual Mismatch between Process Modeling Languages Jan Recker Queensland University of Technology, Brisbane Jan Mendling Vienna University of Economics

  2. From the BPMN Specification: … The primary goal of BPMN is to provide a notation that is readily understandable by all business users, from the business analysts that create the initial drafts of the processes, to the technical developers responsible for implementing the technology that will perform those processes, and finally, to the business people who will manage and monitor those processes. Thus, BPMN creates a standardized bridge for the gap between the business process design and process implementation. Another goal, but no less important, is to ensure that XML languages designed for the execution of business processes, such as BPEL4WS (Business Process Execution Language for Web Services), can be visualized with a business-oriented notation.

  3. Agenda • Introduction to BPMN and BPEL • Conceptual Mismatch • Domain Representation Capability • Control Flow Support • Process Representation Paradigm • Conclusions and Recommendations

  4. Agenda Introduction to BPMN and BPEL

  5. A BPEL Process

  6. A BPEL Process: Structured Activities

  7. A BPEL Process: Basic Activities

  8. A BPEL Process: Data Flow

  9. A BPEL Process: Partner Links

  10. The BPEL Process in BPMN

  11. BPMN explained

  12. Agenda Conceptual Mismatch

  13. Conceptual Mismatch • Is there always a mapping between arbitrary BPMN and BPEL? • Coming from the general to the specific: • Compare Domain Representation Capabilities (BWW-Model) • Compare Control Flow Support (Workflow Patterns) • Identify Transformation Strategies

  14. BWW Thing

  15. BWW Events Redundant event types in BPMN

  16. BWW Subsystem BPMN Subprocess BPEL Subprocesses Extension

  17. Domain Representation Capability

  18. Domain Representation Capability II

  19. Workflow Pattern Discriminator

  20. Workflow Pattern Arbitrary Cycles

  21. Control Flow Support

  22. Transformation Strategies:Element Preservation Mendling, Lassen, Zdun (2006)

  23. Transformation Strategies:Structure Identification

  24. Transformation Strategies

  25. Agenda Conclusions

  26. Conclusions • Framework for analysis • BPMN is richer than BPEL • Transformation from BPEL to BPMN less a problem • From BPMN to BPEL • Loss of information • Loss of design considerations • Potential Solutions • Restriction to a subset of BPMN • Extension of BPEL

  27. Agenda Thank you for your attention!

More Related