1 / 18

Aligning Business and IT Models in Service-Oriented Architectures using BPMN and SoaML

Aligning Business and IT Models in Service-Oriented Architectures using BPMN and SoaML. Brian Elvesæter, Dima Panfilenko , Sven Jacobi & Christian Hahn MDI’2010 Workshop 5th October 2010, Oslo, Norway. Presentation outline. SHAPE Solution Overview SoaML BPMN to SoaML Mapping Rules

taya
Download Presentation

Aligning Business and IT Models in Service-Oriented Architectures using BPMN and SoaML

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. Aligning Business and IT Models in Service-Oriented Architectures using BPMN and SoaML Brian Elvesæter, Dima Panfilenko, Sven Jacobi & Christian Hahn MDI’2010 Workshop 5th October 2010, Oslo, Norway

  2. Presentation outline • SHAPE Solution Overview • SoaML • BPMN to SoaML Mapping Rules • Tool Support • Illustrative Example • Conclusions and Future Work

  3. Solution centred around SoaML Metamodel for describing service-oriented landscapes SoaML is extended with metamodels for ShaML Semantically-enabled Heterogeneous Architecture Modelling Language other technology platforms advanced service engineering techniques Tool support provides integrated tool suite that supports the modelling encompasses the necessary model transformations methodology framework that provides role-specific guided procedures SHAPE Solution Overview

  4. Service oriented architecture Modeling Language (SoaML) Extensions to UML2.1 to support service concepts. SoaML focuses on the basic service modelling concepts. A foundation for further extensions both related to integration with other OMG metamodels like BPMN 2.0, SBVR, OSM, ODM and others. Website: http://www.soaml.org Capabilities: identifying services specifying services defining service consumers and providers policies for using and providing services. defining classification schemes defining service and service usage requirements and linking them to related OMG metamodels, such as the BMM and BPMN 2.0. SoaML

  5. SoaML – Business and IT Business Perspective on SOA Business Processes and Participants Business Goals Services Architecture Capabilities Service Contracts Business and IT alignment IT Perspective on SOA Service Interfaces Interfaces and Messages Service Choreographies Components and Ports

  6. BPMN to SoaML – Mapping Rules [0] • Mapping Rule 0: Process to Services Architecture • Mapping Rule 1: Task to UML Action • Mapping Rule 2: Sub-Process to Services Architecture • Mapping Rule 3: Pool to Participant (Community-level) • Mapping Rule 4: Lane to Participant (Participant-level) • Mapping Rule 5: Message “Begin” to Service • Mapping Rule 6: Message “End” to Request • Mapping Rule 7: Process fragment (pattern) to Service Contract • The services architecture is aligned with the business process, and the participants and service contracts can be derived from the pools or lanes and activities in the business processes respectively.

  7. Mapping Rules [1-2] • Mapping Rule 1: Task to UML Actions • BPMN: task providing a useful output for the participants • SoaML: abstract interface for the job • Mapping Rule 2: Sub-Process to Services Architecture • BPMN: more complex process than a simple task • SoaML: details the roles and tasks of the sub-process

  8. Mapping Rules [3-4] • Mapping Rule 3: Pool to Participant (Community-level) • BPMN: a business entity or a participant of a process • SoaML: role in a community-level services architecture • Mapping Rule 4: Lane to Participant (Participant-level) • BPMN: a participant or a department hierarchy • SoaML: role in a participant-level services architecture

  9. Mapping Rules [5-6] • Mapping Rule 5: Message “Begin” to Service • BPMN: starting end of the data channel between two participants • SoaML: services provision for other participants • Mapping Rule 6: Message “End” to Request • BPMN: other end of the communication channel • SoaML: reflexion of the data channel target in the service consumption

  10. Mapping Rules [7] • Mapping Rule 7: Process fragment (pattern) to Service Contract • BPMN: identification of process fragments providing and consuming services • SoaML: service specification for definition of roles of each participant

  11. Tool Support: CIMFlexMT Architecture

  12. SHAPE Model Transformation Architecture CIMFlexMM: Metamodel of CIMFlexMT CIM2PIM: Transformation to SoaML

  13. CIM level CIMFlex BPMN: ProcessOrder Process

  14. PIM level ProcessOrder: Modelio View on Output

  15. CIMFlexMT Transformation:Services & Participants Recognition CIMFlexMT Process View Modelio ServiceArchitecture Diagram

  16. CIMFlexMT Transformation: ServiceContracts Recognition CIMFlexMT Process View Modelio ServiceArchitecture Diagram

  17. Conclusions and Future Work • Conclusions • overview of the SoaML modelling language • application for describing both a business and IT perspective on SOA • set of model transformation rules for mapping BPMN onto SoaML • testing in industrial use cases in the SHAPE project with the objective of aligning business and IT models • Future Work • identification and description of additional patterns and guidelines for mapping to service contracts • mapping rules definition update and alignment with the ongoing SoaML and BPMN 2.0 specification • provision of better tool support for multi-tier service contracts • investigation of a bottom-up approach for transformations

  18. Thanks for your attention! Questions?

More Related