Service Modelling and Representation Techniques


Published on

Service Modelling and Representation Techniques - a holistic Enterprise Architecture perspective on using and influencing the emerging standards of VDM, USDL and SoaML

Dr. Arne-Jørgen Berre
Networked Systems and Services

ServiceWave Conference 2010 -FIA
Future Internet Conference week 2010 Ghent
13 december 2010

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • ICT Proposer's Day 01.02.2007
  • INF5120 Modellbasert Systemutvikling 27.01.2005
  • The Value Delivery Modeling Language is under development in response to the OMG Value Delivery Metamodel (VDM) RFP issued March 27, 2009. This PPT provides an overview of the current concepts and capabilities of the specification.
  • This diagram illustrates the role of value propositions in exchanges between business entities, typically independent companies. The relationship between these business entities is defined as a value exchange. Each participant gives and receives a value proposition with each of the other participants with which they interact. The illustration incorporates an Internet business relationship between three participants. An Internet Publisher provides an information service of interest to customers. An advertiser pays the publisher to include advertisements for its products along with the information sought by the customer. The customer then clicks on ads of interest and potentially purchases goods from the advertiser. For this business relationship to survive, each of the participants must experience a net gain. In this case, each participant provides two value propositions and receives two value propositions. There may not be a net gain between any two participants, alone, but each has a net gain for the overall exchange.
  • These are the primary dimensions represented by a VDML model. The activity network defines the roles of activities. Activities are linked by the transfer of deliverables, so the nature of each deliverable and its producers and consumers are of interest. Organization relationships define how capabilities are managed and coordinated. The contributions to value propositions define the sources of value and their impact on value propositions. Exchange networks represent the relationships between business entities. Performance monitoring provides visibility of the composite performance and the effects of changes in the model.
  • These are business design and modeling techniques that are influencing the development of VDML. We hope to integrate the best aspects of these techniques.
  • A BPMN Collaboration diagram describes the messages exchanged between the participants. The Collaboration diagram provides an ungrouped view of the messages exchanged between the participants. A Communication diagram can be used to show how the messages are grouped. The BPMN 2.0 FTF is in the process of merging the Collaboration and Conversation diagrams.
  • A BPMN Conversation shows the grouping of messages between collaborating participants and provides a means to correlate interactions between specific instances of these participants at runtime. These groupings correspond to the messages shown in the collaboration diagram. The choreography of these groups of messages can be shown using a Choreography diagram The grouping of messages, plus the corresponding choreography corresponds to the ServiceInterface in SoaML. The connections between the communication and participants in a communication diagram corresponds to the service and request ports in SoaML.
  • This is a new type of drill down into a Conversation. It not only shows the Message Flow, it shows a Choreography of the Conversation. We will have to consider if we need BPMN 2.0 FTF issues to do this, since there could be a Choreography for each Conversation. The convergence of Collaboration and Conversation will help, but only one Choreography is allowed in a Collaboration. But that Choreography could have multiple Start Events. What is needed is a way to visually and semantically connect the messages, their grouping and their sequencing captured in a BPMN collaboration, communication and choreography. One possible approach is to support drill-down into a communication to see the messages and their choreography. This could be done through naming conventions where the names of the communication and collaboration are the same, as well as the start activity in the choreography.
  • Participant is a definition in SoaML. A part (or typed element) is a reference to some instance of a participant, the actual instance would be established by an assignment statement that usually happens at runtime and is not usually modeled. Again the normalization of message-oriented vs procedure-call-oriented is not yet covered by BPMN. These are currently completely separate concepts in BPMN with message-oriented interactions being covered by collaboration, communication and choreography, and specific send and receive message activities in an orchestration. Procedure-call-oriented is covered by interface and service activity in an orchestration. BPMN’s modeling of services is limited to simple interfaces as in WSDL. Service protocols and complex service interactions would have to be modeled using the message-oriented approach.
  • Rollen erklären, mit Beispiel (Entwickler, solution Manager) Vokabeln klären: modeldriven, basemodel…
  • Service Modelling and Representation Techniques

    1. 1. Service Modelling and Representation Techniques - a holistic Enterprise Architecture perspective on using and influencing the emerging standards of VDM, USDL and SoaML Dr. Arne-Jørgen Berre SINTEF Networked Systems and Services Keynote at SMART’2010, Ghent, December 13 th , 2010
    2. 2. Agenda <ul><li>Service science, Enterprise architecture and Services life cycle </li></ul><ul><ul><li>Zachman, RM-ODP and other EA frameworks </li></ul></ul><ul><ul><li>Business architecture and IT architecture – and standards (OMG, W3C, ...) </li></ul></ul><ul><ul><li>Service – definitions (SoaML ++), NEFFICS and SHAPE projects </li></ul></ul><ul><li>Business architecture and Service Innovation </li></ul><ul><ul><li>(Open) Services innovation (CSI, NEFFICS, CINEX, Chesbrough) </li></ul></ul><ul><ul><li>Service Design – Service experiences (AT-ONE) </li></ul></ul><ul><ul><li>Business Model Innovation (NEFFICS) </li></ul></ul><ul><ul><li>Value Models and Value Networks (VDM) </li></ul></ul><ul><ul><li>OOram and Role Modeling, e3Value and REA modeling </li></ul></ul><ul><ul><li>USDL – Universal Service Description Language (W3C) </li></ul></ul><ul><li>System and IT architecture </li></ul><ul><ul><li>SoaML Service Model – background/history </li></ul></ul><ul><ul><li>SoaML - SHAPE, .. </li></ul></ul><ul><li>Composition, Deployment, Runtime, </li></ul><ul><ul><li>Service Composition tool (ENVISION) </li></ul></ul><ul><ul><li>Service variability, CVL, and configuration (SHAPE) </li></ul></ul><ul><li>Your Future Impact on Standards </li></ul><ul><ul><li>VDM, SoaML, USDL, BPMN, CVL, ... </li></ul></ul>
    3. 3. The emerging importance of Services
    4. 4. Porter’s Value Chain
    5. 5. Open Services Innovation Book : January 2011
    6. 6. A Services Value Web
    7. 7. SMART - Service Modelling and Representation Techniques <ul><li>Enterprise Architecture perspective </li></ul><ul><ul><li>Service – definitions </li></ul></ul><ul><ul><li>OOram and Role Modeling </li></ul></ul><ul><ul><li>RM ODP – services view, SWING/ENVISION/CM </li></ul></ul><ul><li>VDM </li></ul><ul><ul><li>e3Value and REA modeling </li></ul></ul><ul><ul><li>SoaML Service Model – and background/history </li></ul></ul><ul><li>USDL </li></ul><ul><ul><li>VDM workshops </li></ul></ul><ul><li>SoaML </li></ul><ul><ul><li>OMG standard VDM workshops </li></ul></ul>
    8. 8. NEFFICS (2010-2012) <ul><li>36 Months </li></ul><ul><li>Cost: </li></ul><ul><ul><li>4.147 M € </li></ul></ul><ul><ul><li>2.898 M € requested EU </li></ul></ul><ul><li>323 man-months </li></ul><ul><li>Started Sept. 1 st , 2010 </li></ul><ul><li>Partners: </li></ul><ul><ul><li>2 case owners </li></ul></ul><ul><ul><li>2 technology providers </li></ul></ul><ul><ul><li>3 research partners </li></ul></ul>`
    9. 9. NEFFICS Community of highly innovative networked enterprises Networked innovation community services (Induct) Applications for highly innovative networked enterprises Virtual Factory Network (Vlastuin) Connected Retail Network (Telecom Italia) Enterprise SaaS Cloud business operations and orchestration platform (Cordys) Google Apps/Waves, Cloud computing & Web 2.0 platform Networked Enterprises on Internet of Services (COIN) and Things (ASPIRE) Networked enterprises MashApp applications and process support (Cordys) Networked process and service models (SINTEF) BPMN 2.0, SoaML, OSM, CMPM Networked business value analysis models (IC Focus) VDM BEI Networked innovation models, leadership and management processes (ICI) CEN/389
    10. 10. SHAPE (2008-2010)
    11. 11. REMICS (2010-2012) SoaML VDM SoaML Recover Legacy Artifacts Source Architecture Migrate Target Architecture for Service Cloud platform Forward MDA through PIM 4 Cloud Service Cloud Implementa tion Model Driven Interoperability Validate , Control and Supervise Knowledge : REMICS KDM Business Process and Rules Components : SoaML Implementation : UML , U 2 TP Knowledge Discovery , Reverse Engineering Source code , binaries , documentation , users knowledge , configuration files , execution logs and traces . SOA and Cloud Computing Patterns applied , Legacy Components Replacement and Wrapping , Design by Service Composition Service mediation for adaptation SoaML with REMICS extensions for Service Clouds , Links to Business Models Model Transformation , Code Generation , Traceability RESERVOIR , Joyant , Amazon , Google , Microsoft Models @ Runtime for application management , Model Checking , Model - based Testing for validation
    12. 12. ENVISION (2010-2012) SoaML VDM
    13. 13. Zachman Framework – for Enterprise Architecture (IBM, 1987)
    14. 14. OMG Model-Driven Architecture (MDA)
    15. 15. Use of OMG metamodels <ul><li>Business Architecture </li></ul><ul><ul><li>UPDM, BMM </li></ul></ul><ul><ul><li>BPMN 2.0 </li></ul></ul><ul><ul><li>VDM, OSM (Value Networks, Value Chain, REA, e3Value, …) </li></ul></ul><ul><ul><li>SoaML </li></ul></ul><ul><ul><li>USDL (Theseus TEXOS, SAP) (W3C) </li></ul></ul><ul><li>IT Architecture </li></ul><ul><ul><li>SoaML </li></ul></ul><ul><ul><li>SBVR, ODM </li></ul></ul><ul><li>Deployment, Configuration </li></ul><ul><ul><li>CVL, ServiceVariability, PIM4Cloud/CloudML </li></ul></ul><ul><li>Conclusion </li></ul><ul><ul><li>VDM, SoaML, USDL </li></ul></ul>
    16. 16. Zachman with OMG standards USDL (TEXO, W3C) USDL USDL USDL USDL
    17. 17. OMG standards coverage USDL
    18. 18. Modeling the Business <ul><li>A business is a complex, multidimensional organism </li></ul><ul><li>A metaphor for a multi-dimensional representation is the multi-hedron shown below, representing some of the most important dimensions, like process, application, data and of course the customer </li></ul><ul><li>Each dimension has linkages with every other dimension </li></ul><ul><li>The goal of modeling is to optimally represent just enough of these dimensions and linkages (without devolving into infinite possibilities) so that we model the problems and solutions at hand </li></ul>13 Dec 2010 The Business The Business Architecture
    19. 19. Elements of a Business Architecture
    20. 20. CSI – Center for Service Innovation Norwegian national initiative
    21. 21. CSI planned Activities
    22. 22. Business model innovation Timmers, 1998 “ Business model stands for the architecture for the product, service and information flows, including a description of the various business actors and their roles, the potential benefits for these actors and the sources of revenues……… the business model includes competition and stakeholders” Stewart and Zao, 2000 “ Business model is a statement of how a firm will make money and sustain its profit stream over time”. Weill and Vitale, 2001 “ A description of the roles and relationships among a firm’s consumers, customers, allies and suppliers that identifies major flows of product, information and money and the major benefits to participants”. Osterwalder et al. 2004 “ A blueprint of how a company does business. It is a conceptual tool that contains a set of elements and their relationships and allows expressing a company’s logic of earning money. It is a description of the value a company offers to one or several segments of customers and the architecture of the firm and its network of partners for creating, marketing and delivering this value and relationship capital, in order to generate profitable and sustainable revenue stream” Chesbrough 2006 “… is a useful framework to link ideas and technologies to economic outcomes”… “It also has value in understanding how companies of all sizes can convert technological potential [e.g. products, feasibility, and performance] into economic value [price and profits]”….. “Every company has a business model, whether that model is articulated or not”. Skarzynski and Gibson 2008 “… is a conceptual framework for identifying how a company creates, delivers, and extracts value. It typically includes a whole set of integrated components, all of which can be looked on as opportunities for innovation and competitive advantage”.
    23. 23. Sample Customer Experience Model
    24. 24.
    25. 25. Value Delivery Modeling Language (OMG RFP) (2009 – 2011 – 2012) Ongoing work on a Value Delivery Metamodel RFP to OMG – with initial submission in May 2011 VDM - Value Delivery Metamodel
    26. 26. Business partner relationships Merchant Customer Internet Publisher Participation Participation Participation Value Prop’n Value Prop’n Value Prop’n Value Prop’n Value Prop’n Value Prop’n Each business entity must realize a net gain Diagram for illustration, not a proposed notation Value Exchange Provide Content Purchase Goods Clicks Purchase Ad Publish Ad Sell Goods
    27. 27. VDML Dimensions <ul><li>Activity network: roles of capabilities </li></ul><ul><li>Deliverable producers and consumers </li></ul><ul><li>Organizational relationships </li></ul><ul><li>Contributions to value propositions </li></ul><ul><li>Exchange networks </li></ul><ul><li>Performance monitoring </li></ul>12/13/10
    28. 28. Related Techniques <ul><li>Porter Value Chain </li></ul><ul><li>Value Chain Group, Value Reference Model (VRM) </li></ul><ul><li>Verna Allee, value networks </li></ul><ul><li>e3Value e-Commerce analysis </li></ul><ul><li>Business model generation (Osterwalder) </li></ul><ul><li>Value stream mapping </li></ul><ul><li>Capability mapping </li></ul><ul><li>Service Oriented Architecture (SOA) analysis </li></ul>
    29. 29. OMG - Business Motivation Model (BMM)
    30. 30. People naturally network as they work. So why not model the work itself as a network? December 13, 2010 Value Network Analysis models value creation with a powerful human network approach to managing any business activity.
    31. 31. How Networks Create Value © The emergent purpose of the value network is revealed through the pattern of roles and value exchanges that support an economic or social goal or output. Sustainability depends on a consistent high level of both transactional and network perceived value . Allee, Journal of Intellectual Capital, January 2008 Value Creating Network
    32. 32. VNA Fills An Analytical Gap December 13, 2010 © 1997-2009 Value Networks, LLC All rights reserved. Formal Organization Social Networks Business Process Modeling Asset Management
    33. 33. Value Network Modeling December 13, 2010 © 1997-2010 Value Networks, LLC All rights reserved. Roles Intangible (Informal) Interactions Tangible (Formal) Deliverables
    34. 34. Realizing Value for Network Participants December 13, 2010 Impact Analysis How do we grow financial and intangible assets from our inputs?
    35. 35. A Network View of the Work Itself Confidential Information – Do Not Distribute. Copyright © 2000-2008 All rights reserved. CITAP Inputer - RO_IDS SOW Inputer - RO BCA SOW final validator Integrator of test requirements Authorized management SOW approver(s) Technical Designer-finalizer PO coordinator IDS requirements researcher-author - SOW Initiator Communication convener Functional resource estimator RO SOW Final Approver Resource Owner FOTV-BCA PO info advisor ITAR_EAR Analyst-Determiner RO RFP Creator BCA RFP Reviewer PIW Creator Non-FTO_V estimate collector-checker-coordinator SOW technical evaluator-reviewer Non-FTOV estimate collector-checker-coordinator Functional SME Authorized management PIW approver PoP Adjuster Coordinator BCA SOW estimate and PoP validator Test estimate reasonableness assessor Test estimate collector-checker-documenter Functional estimate approver Test estimate requester BCA estimate integrator BCA Pricer BCA Price approver Expiration date assigner BCA Proposal Creator BCA cost policy reviewer CITAP Project Manager BCA work performer BCA proposal implementer Chargeline assigner Job Number Assigner IDS Proposal evaluator-acceptor authorized management approver IDS financial analyst IDS Technical Analyst IDS Cost Analyst 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 December 13, 2010 Complex Procurement Activity Showing both tangible and intangible value creation!
    36. 36. e 3 value : A formal ontology for designing and evaluating networked value constellations
    37. 37. e3value Ontology
    38. 38. e3value business model illustration … can be integated with SoaML …
    39. 39. Examples of Services Related to a Service ~ Product ~ Business Process as a Unique Asset Service ~ Product ~ Business Process Analyse Design Simulate Sell Buy Rent Lease Finance Execute Monitor Implement
    40. 40. REA (Resources, Events, Agents) The Nucleus of Every Value-Adding Process <ul><ul><li>Small set of archetypes: Resource, Event, Agent, Commitment, Contract, that allows to effectively model any value-adding process </li></ul></ul><ul><ul><li>An ontology for economic systems and a generalized framework for modeling business processes, developed by William E. McCarthy and Guido Geerts, since1982. </li></ul></ul><ul><ul><li>UMM Modeling Methodology </li></ul></ul>
    41. 41. An Example of an REA for Capability to Produce Product or Provide a Service <ul><ul><li>Use – resource still exists after the economic event </li></ul></ul><ul><ul><li>Consume – resource does not exist after the economic event </li></ul></ul><ul><ul><li>Produce – resource is created by the event or a service is provided by the economic event </li></ul></ul>Value Chain Level REA Level
    42. 42. USDL – The Unified Service Description Language (USDL) See: See also:
    43. 49. See also:
    44. 50. What is SoaML? <ul><li>Service oriented architecture Modeling Language (SoaML) </li></ul><ul><ul><li>Extensions to UML2 to support service concepts – as a UML Profile and a corresponding metamodel </li></ul></ul><ul><ul><li>Focuses on basic service modelling concepts. </li></ul></ul><ul><ul><li>A foundation for further extensions and integration with BPMN, BMM and other metamodels. </li></ul></ul>
    45. 51. SoaML – History
    46. 52. SoaML – Goals <ul><li>Model Driven Architecture (MDA). </li></ul><ul><li>Intuitive and complete service modelling in UML. </li></ul><ul><li>Bi-directional asynchronous services. </li></ul><ul><li>Services architectures where parties provide and use multiple services. </li></ul><ul><li>Services defined to contain other services. </li></ul><ul><li>Mapped to and part of a business process specification. </li></ul><ul><li>Compatibility with UML and BPMN. </li></ul><ul><li>Direct mapping to Web services. </li></ul><ul><li>Top-down, bottom up or meet-in-the-middle modelling. </li></ul><ul><li>Design by contract or dynamic adaptation of services. </li></ul><ul><li>Service capability and its contract. </li></ul><ul><li>No changes to UML. </li></ul>
    47. 53. SoaML – Capabilities <ul><li>UML extensions to support service modelling: </li></ul><ul><ul><li>identifying services </li></ul></ul><ul><ul><li>specifying services </li></ul></ul><ul><ul><li>defining service consumers and providers </li></ul></ul><ul><ul><li>policies for using and providing services. </li></ul></ul><ul><ul><li>defining classification schemes </li></ul></ul><ul><ul><li>defining service and service usage requirements and linking them to related OMG metamodels such as the BMM and BPMN. </li></ul></ul>
    48. 54. SoaML – Concepts <ul><li>Agent </li></ul><ul><li>Attachment </li></ul><ul><li>Capability </li></ul><ul><li>Consumer </li></ul><ul><li>Collaboration </li></ul><ul><li>CollaborationUse </li></ul><ul><li>Expose </li></ul><ul><li>MessageType </li></ul><ul><li>Milestone </li></ul><ul><li>Participant </li></ul><ul><li>Port </li></ul><ul><li>Property </li></ul><ul><li>Provider </li></ul><ul><li>Request </li></ul><ul><li>ServiceChannel </li></ul><ul><li>ServiceContract </li></ul><ul><li>ServiceInterface </li></ul><ul><li>Service </li></ul><ul><li>ServicesArchitecture </li></ul>
    49. 55. SOA in Model Driven Architecture (MDA) Business Concerns Goals Policy Customers Costs Agility Technology Specification JMS, JEE, Web Services WSDL, BPEL, XML Schema Logical System Model Technology Services (t-SOA) Software Components Interfaces, Messages & Data Business Model Enterprise Services (e-SOA) Roles, Collaborations & Interactions Process & Information Refinement & Automation Line-Of-Sight Computation Independent Model Platform Independent Model Platform Specific Model MDA Terms
    50. 56. SoaML – Service and SOA <ul><li>” A service is value delivered to another through a well-defined interface and available to a community (which may be the general public). A service results in work provided to one by another. “ </li></ul><ul><li>Service Oriented Architecture (SOA) is a way of describing and understanding organizations, communities and systems to maximize agility, scale and interoperability. </li></ul><ul><li>SOA is an architectural paradigm for defining how people, organizations and systems provide and use services to achieve results. </li></ul><ul><li>SoaML provides a standard way to architect and model SOA solutions using the Unified Modeling Language (UML). </li></ul>
    51. 57. SoaML Metamodel, Service/Request Port
    52. 58. SoaML Metamodel ServiceArchitecture and ServiceContract
    53. 59. UML Profile - Collaboration
    54. 60. UML Profile – ServiceInterface, Port
    55. 61. Marketplace Services Example Order Conformation Ship Req Shipped Shipped Delivered Status Provider Consumer Provider Consumer Consumer Provider Mechanics Are Us Dealer Acme Industries Manufacturer GetItThere Freight Shipper Physical Delivery
    56. 62. Business process overview
    57. 63. Services architecture (Community-level) <ul><li>Services architecture: </li></ul><ul><li>High level description of how participants work together for a purpose by providing and using services expressed as service contracts . </li></ul><ul><li>UML collaboration stereotyped « ServicesArchitecture » . </li></ul>Community-level services architecture for the Dealer Network Shipping Request service Ship Status service Place Order service
    58. 64. Participants and service contracts <ul><li>Service contract: </li></ul><ul><li>Service specifications that define the roles each participant plays in the service and the interfaces they implement to play that role. </li></ul><ul><li>UML collaboration stereotyped « ServiceContract » . </li></ul><ul><li>Participant: </li></ul><ul><li>Represent logical or real people or organizational units that participate in services architectures and/or business processes. </li></ul><ul><li>UML class stereotyped « Participant » . </li></ul>type collaboration use role binding role binding
    59. 65. Services architecture (Participant-level) Order Conformation Shipped Ship Req Shipped Delivered Participant-level services architecture for the Manufacturer OrderHandler Invoicing Productions
    60. 66. Choreography: Place order (Service contract behaviour) (Service interface behaviour) Service choreography can be specified using any UML behaviour, e.g, interaction or activity Service choreography can be specified using any UML behaviour, e.g, interaction or activity
    61. 67. Service and request ports: Place order <ul><li>Service: </li></ul><ul><li>Specifies a feature of a participant that is the offer of a service by one participant to others using well defined terms, conditions and interfaces. </li></ul><ul><li>UML port stereotyped « Service » on a participant or component. </li></ul><ul><li>Request: </li></ul><ul><li>Specifies a feature of a participant that represents a service the participant needs and consumes from other participants. </li></ul><ul><li>UML port stereotyped « Request » on a participant or component. </li></ul>type type Request port Service port
    62. 68. <ul><li>Components implement the service interfaces providing the link to systems. Participants and services may be used in multiple architectures. </li></ul>Logical system components: Dealer Network Architecture
    63. 69. Software components: Manufacturer Architecture Mapped to software components
    64. 70. BPMN 2.0 and SoaML tools today <ul><li>BPMN 2.0 </li></ul><ul><ul><li>Signavio has 2.0 Conversation and Choreography diagrams – a SaaS solution </li></ul></ul><ul><ul><li>Most BPMN 1.2 are doing stepwise migration, making existing parts 2.0 compliant </li></ul></ul><ul><li>SoaML (in most UML tools) </li></ul><ul><ul><li>Magic Draw (Cameo), Enterprise Architect, IBM RSA/RSM, Modelio, … </li></ul></ul>
    65. 71. Associated BPMN 2.0 Collaboration
    66. 72. Associated BPMN 2.0 Conversation
    67. 73. Associated BPMN 2.0 Conversation (showing mini-Choreography)
    68. 74. Mappings SoaML Term BPMN Mapping ServicesArchitecture (a UML Collaboration) or a specification Participant Overview Choreography Participant Participant representing PartnerEntity (within definitional collaboration Service Port One end of a communication between participants in a communication diagram: Interface of the above participant Request Port The other end of the communication, the one sending the first message ServiceInterface (defining the type of a Service or Request Port) Interface, but doesn’t support service protocols. Alternatively, a communication in a communication diagram, including the corresponding messages in a collaboration diagram, and the choreography of those messages in a choreography diagram Interface (realized or used by a ServiceInterface) Interface, but not clear how this relates to a communication Operation or Reception (of an Interface) Operation of an Interface or Message, but not clear how this relates to an operation of an interface Parameter (of an Operation) Message inputs and outputs for an Operation
    69. 75. Service Variability Process Overview (from SHAPE) © SAP 2009 / Page © SAP 2009 / Page Customization & Personalization Variability Modelling & Pre-Configuration Design, Development, Publication Provider Domain Expert Consumer Roles Phases Artefacts Variability Specification Variability Specification Service Variability Model Service Variability Metamodel Service Variant Model resolves 1:n according to according to Service Model Service Metamodel Service Interface extends 1:n extends Service Variant Interface according to described by described by consistent & valid subset
    70. 76. © SAP 2009 / Page Example (from SHAPE) Customization & Personalization
    71. 77. References <ul><li>SoaML Beta2 -  </li></ul><ul><li>BPMN 2.0 Beta2 </li></ul><ul><li>SHAPE Methodology Paper </li></ul><ul><ul><li>M. Stollberg, B. Elvesæter, V. Shafran, R. Magarshak, “A Customizable Methodology for the Model-driven Engineering of Service-based System Landscapes”, MDA4ServiceCloud workshop, Paris, France, 15 June 2010. </li></ul></ul><ul><li>SHAPE Methodology Online </li></ul><ul><ul><li> </li></ul></ul><ul><li>SoaML wiki </li></ul><ul><ul><li> </li></ul></ul><ul><li>Business Motivation Model (BMM) </li></ul><ul><ul><li> </li></ul></ul><ul><li>Eclipse Process Framework (EPF) </li></ul><ul><ul><li> </li></ul></ul>
    72. 78. Conclusion <ul><li>Understand Services in a holistic perspective </li></ul><ul><li>Enterprise architectures (enhanced) can a provide a framework for modeling and representations </li></ul><ul><li>Evolving standardisation activities should be influenced by good ideas and research results </li></ul><ul><li>VDM (OMG) – Consider contributions in 2011 </li></ul><ul><li>USDL (W3C) – Consider contributions in 2011 </li></ul><ul><li>SoaML (OMG) – Consider contributions in 2011 </li></ul>
    73. 79. Service Modelling and Representation Techniques - a holistic Enterprise Architecture perspective on using and influencing the emerging standards of VDM, USDL and SoaML Dr. Arne-Jørgen Berre SINTEF Networked Systems and Services Keynote at SMART’2010, Ghent, December 13 th , 2010