Service Modelling and Representation Techniques - a holistic Enterprise Architecture perspective on using and influencing the emerging standards of VDM, USDL and SoaML
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
Ghent, Dec 13th, 2010
Service Wave 2010 - FIA
Ähnlich wie Service Modelling and Representation Techniques - a holistic Enterprise Architecture perspective on using and influencing the emerging standards of VDM, USDL and SoaML
Ähnlich wie Service Modelling and Representation Techniques - a holistic Enterprise Architecture perspective on using and influencing the emerging standards of VDM, USDL and SoaML (20)
Service Modelling and Representation Techniques - a holistic Enterprise Architecture perspective on using and influencing the emerging standards of VDM, USDL and SoaML
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
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
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
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”.
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. 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
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.
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.
41.
42. USDL – The Unified Service Description Language (USDL) See: http://www.internet-of-services.com/ See also: http://www.w3.org/2005/Incubator/usdl/wiki/Main_Page
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
65. Services architecture (Participant-level) Order Conformation Shipped Ship Req Shipped Delivered Participant-level services architecture for the Manufacturer OrderHandler Invoicing Productions
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
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
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
Hinweis der Redaktion
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…