ME2011 presentation by Cortes Cornax

888 views

Published on

Bridging the Gap between Business Processes and Service Composition through Service Choreographies

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
888
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

ME2011 presentation by Cortes Cornax

  1. 1. Mario Cortes Cornax<br />Sophie Dupuy-Chessa<br />Dominique Rieu<br />University of Grenoble, CNRS, LIG<br />Bridging the Gap between Business Processesand Service Composition through ServiceChoreographies<br />
  2. 2. Plan<br />Service Orchestration and Service Choreography<br />The Research Problem<br />Our Proposition through a Scenario<br />Future Works & Conclusions<br />ME 2011<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />2<br />
  3. 3. Service Orchestration<br />Orchestration (BPEL)<br />service<br />service<br />service<br />service<br />…<br />http://www.denver.org/images/memberimages/Cropped_553x300/474_20081212_7450_COSymphonyOrchestra.jpg<br />ME 2011<br />3<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />
  4. 4. Service Choreography<br />There has been a previous agreement between the participants about HOW and WHEN they will interact. (Decker, G et al, 2008)<br />Orchestration<br />Orchestration<br />Orchestration<br />Orchestration<br />Orchestration<br />ME 2011<br />4<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />
  5. 5. The Problem<br />The Approach<br />Inter-organizational interactions<br />Organizational<br />Orchestration<br />Orchestration<br />Orchestration<br />Analyst<br />Graphical Notation<br />Modular solutions based on service- oriented architectures<br />ME 2011<br />5<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />Orchestration<br />?<br />Domain meta-model<br />Analysismeta-model<br />IncomprehensionAmbiguities<br /> WS-CDL Syntax<br />Operational<br />Design meta-model<br /><choreography name="ExampleChoreography" root="true"><br /> <sequence><br /> <interaction name="QuoteElicitation" operation="getQuote“channelVariable="tns:Buyer2SellerC"><br /> <participate relationshipType="tns:Buyer2Seller“<br />fromRoleTypeRef="tns:BuyerRole"<br />toRoleTypeRef="tns:SellerRole" /><br /> <exchange name="QuoteRequest"informationType="tns:QuoteRequestType" action="request"><br /> <send variable="cdl:getVariable('quoteRequest','','')" /><br /> <receive variable="cdl:getVariable('quoteRequest','','')" /><br /> </exchange><br /> <exchangename="QuoteResponse"informationType="tns:QuoteResponseTypeaction="respond"><br /> <send variable="cdl:getVariable('quoteResponse','','')" /><br /><receive variable="cdl:getVariable('quoteResponse','','')" /><br /> </exchange><br /> </interaction><br /> </sequence><br /></choreography><br />Architect<br />Developer<br />
  6. 6. Overview of the Approach<br />Domain meta-model<br />It seems that all proposals are converging to the new choreography representation proposed in BPMN 2.0<br />BehavioralView<br />Structural View<br />Analysismeta-model<br />BehavioralView<br />Structural View<br />BPMN 2.0<br />Evaluations<br />Design meta-model<br />BehavioralView<br />Structural View<br />WS-CDL<br />ME 2011<br />6<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />Deep analysis of the Web Service Choreography Description Language (WS-CDL) Brings the knowledge about choreographies. <br />
  7. 7. ME 2011<br />7<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />Scenario (in BPMN 2.0)<br />Participants<br />Interactions<br />Order Confirmation<br />Order Rejection<br />Initiating Participant<br />Initiating Message<br />Receiver Participant<br />Response<br />
  8. 8. The Domain Meta-Model<br />From a structural point of view, we consider the communication protocol (Choreography) as a set of roles (Role) linked in two by two relationships (Relationship). A participant (Participant) plays one or more roles.<br />From a behavioral point of view, a choreography is defined as a set of interactions (Interaction) between two roles. In an interaction there is a role transmitter (sourceRole), the one that starts the interaction and a role receiver (targetRole).<br />Structural View<br />BehavioralView<br />ME 2011<br />8<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />
  9. 9. ME 2011<br />9<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />Scenario – Domain Model Instance<br />Structural View<br />BehavioralView<br />MM<br />M<br />
  10. 10. The Analysis Meta-Model<br />Structural View<br />BehavioralView<br />ME 2011<br />10<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />An operation that is invoked in an interaction has to be defined in the target role’s service.<br />A participant that plays a role must provide the services (Service) defined for that role to respect the choreography. <br />
  11. 11. ME 2011<br />11<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />BehavioralView<br />Structural View<br />MM<br />M<br />Consistency<br />
  12. 12. The Design Meta-Model<br />ME 2011<br />12<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />(Barros,A et al., 2005)<br />
  13. 13. Future Works & Conclusions<br />Model Driven Engineering<br />Choreographymeta-model<br />Represented by <br />Corresponds to<br />Domain meta-model<br />Graphical Notation<br />CIM<br />Business Processes<br />Structural View<br />BehavioralView<br />Abstraction<br />Refinement<br />Represented by <br />Corresponds to<br />Analysismeta-model<br />Graphical Notation<br />PIM<br />BehavioralView<br />Structural View<br />Abstraction<br />Refinement<br />Corresponds to<br />Design meta-model<br />PSM<br />Behavioral<br />View<br />Structural <br />View<br />Service implementation<br />Modeled by<br />Represented by <br />Textual Notation (XML )<br />ChoreographyLanguage<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />ME 2011<br />13<br />
  14. 14. Future Works & Conclusions<br />Complete a choreography requirements’ framework<br />Enlarge the meta-model<br />With the Service Interaction Patterns and other choreography requirements.<br />Work in a Graphical Notation<br />Taking into account the Principles of Graphic Notations. (Moody, D, 2009)<br />Formalize transformations between models via the meta-models.<br />ME 2011<br />14<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />
  15. 15. Conclusions<br />The importance of abstraction layers (layered meta-models) and views separation (structural-behavioral).<br />A top-down approach helps to implement the executable processes for each party avoiding ambiguities.<br />A bottom-up approach helps to understand and validate a choreography.<br />Choreography notation in BPMN 2.0 <br />The notion of choreography has emerged over the past years as a foundational concept for capturing and managing collaborative business processes.<br />Correspondence with the paradigm of Model Driven Engineering (MDE).<br />Source of inspiration for future choreography languages.<br />More experimentations are considered.<br />ME 2011<br />15<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />
  16. 16. Thanks for Listening<br />ME 2011<br />16<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />
  17. 17. Decker, G., Kopp, O., Barros, A.: An introduction to service choreographies. Information Technology 50(2), 122{127 (2008)<br />Barros, A., Dumas, M., Oaks, P.: A critical overview of the web services choreography description language. BPTrends Newsletter 3 (2005)<br />Moody, D.: The Physics of Notations: Toward a Scientic Basis for ConstructingVisual Notations in Software Engineering. IEEE Transactions on Software Engineering pp. 756{779 (2009)<br />ME 2011<br />17<br />Mario CORTES CORNAX, Sophie DUPUY- CHESSA, Dominique RIEU<br />References<br />

×