1 / 29

INF5120 – Model-based System Development

INF5120 – Model-based System Development. Lecture #10-2: Introduction to Model-driven interoperability and Semantics April 12 th , 2010 Arne J. Berre, SINTEF ICT. Based on material developed in the ATHENA (IST-507849),

michon
Télécharger la présentation

INF5120 – Model-based System Development

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. INF5120 – Model-based System Development Lecture #10-2: Introduction to Model-driven interoperability and Semantics April 12th, 2010 Arne J. Berre, SINTEF ICT Based on material developed in the ATHENA (IST-507849), INTEROP (IST-508011), SHAPE, SWING, COIN and EMPOWER/MEMPOWER, JANUS-3 research projects.

  2. Outline • Introduction • Some existing interoperability framework(EIF) • European SHAPE project (Service-Oriented Heterganeous architecture and platform engineering) • BMM • SoaML • Alignment with BMM and SoaML • Other on going cases of SoaML and BMM

  3. Introduction • Organizations are collaborating with other organizations in order to meet their business objectives. • For business optimization, organizations re-structure their business realizations by creating new constellations within an enterprise and across the organizational border that need to interoperate. • Key issue: service network, who is to produce the service, who is to consume the service，business goals. • It seems BMM and SoaML can combine these issues through: • Align goals with service-centric approach.

  4. Introduction • BMM: Business motivation model • The Business Motivation Model specification provides a scheme or structure for developing, communicating, and managing business plans in an organized manner. Specifically, the Business Motivation Model does all of the following: • It identifies factors that motivate the establishing of business plans.• It identifies and defines the elements of business plans.• It indicates how all these factors and elements inter-relate. Among these elements are those that provide governance for and guidance to the business — Business Policies and Business Rules. • SoaML: Service-Oriented Architecture Modeling Language • OMG-backed, meant to bring a new type of modeling capability to the service-oriented world (talk in detail later).

  5. Reference • Latest BMM specification. • Latest UPMS specification. • SoaML community: http://www.soaml.org/

  6. Interoperability Framework • ATHENA Interoperability Framework ( each system is described by enterprise models and different viewpoints, such as business, process, service, information)

  7. EIF version 2.0 (2009)European Interoperability Framework

  8. Definition: Interoperability(Revised in 2008 in EIF v2, to include common goals !)

  9. EIF - Dimensions of Interoperability

  10. Interoperability chain and levels

  11. Interoperability levels

  12. Reference model for Interoperability- Link to areas in IT architecture Admin, Business, Citizen A Admin, Business, Citizen B Organisational interoperability Workprocess Goals Organisation Product Concepts Workprocess Goals Organisation Product Concepts Organisational interoperability Organisational interoperability Organisational harmonisation, in particular around process Semantic interoperability Semantic interoperability, Informasjons Innhold med mening for: Semantic interoperability, Informasjons Innhold med mening for: Presentation Process, rules Services Information/Data Presentation Process, rules Services Information/Data Shared understanding of the meaning/semantics i innhold ved bruk av teknologier for presentasjon/prosess/tjeneste/data Technical interoperabilitet (Technicall standards) Presentation Process, rules Services Data Communikasjon Adm/Metadat Security Techn. sem/org Technical interoperability Technical interoperabilitet (Technicall standards) Presentation Process, rules Services Data Communikasjon Adm/Metadat Security Techn. sem/org Interoperable technologies Communikation Communikation

  13. Admin, Business, Citizen A Admin, Business, Citizen B Organisational interoperability Workprocess Goals Organisation Product Concepts Workprocess Goals Organisation Product Concepts Organisational interoperability Organisational interoperability Semantic interoperability Semantic interoperability, Informasjons Innhold med mening for: Semantic interoperability, Informasjons Innhold med mening for: Presentation Process, rules Services Information/Data Presentation Process, rules Services Information/Data Technical interoperabilitet (Technicall standards) Presentation Process, rules Services Data Communikasjon Adm/Metadat Security Techn. sem/org Technical interoperabilitet (Technicall standards) Presentation Process, rules Services Data Communikasjon Adm/Metadat Security Techn. sem/org Technical interoperability Communikation Communikation Organisational Interoperablilitet Semantic Interoperability Technical Interoperability Reference model for Interoperability vs IDAbc EIF version 1

  14. SwApp#1 SwApp#2 Local Software & Data Local Software & Data Architecture for semantic annotation and reconciliation Reference Ontology Sem Annot Set #2 Sem Annot Set #1 Design-time Run-time Internet Sem Rec Rules#1 Sem Rec Rules#2 Reconciliation

  15. SHAPE project

  16. Goals EPC CIM Business rules POP* Flexible Business Flexible Business Business processes BPDM, BPMN according to flexible Business business models metamodels business models Business services BMM metamodels Business Models metamodels E - contracts … … transformation engine Transformer Transformation (engine) rules PIM Flexible Executable business Business Models oriented aspects to capture in models processes Web Grid Service interfaces Services Unified and Semantically - Service contracts according to standardised enabled Service enactment Which metamodels and languages to use Service UPMSHA Agents metamodel for heterogeneous Business rules Variability SLAs SOA & SHA SOA model Parameterized Semantic Web P2P Services services Heterogeneous … Platforms transformation - engine Transformer Transformation (engine) rules PSM What service Executable artefacts Heterogeneous XSD, WSDL, BPEL service platforms Teams and plans WSA Semantically - Semantically - Resource JXTA Interconnected enabled enabled Interconnected according to Heterogeneous management OGSA Heterogeneous heterogeneous heterogeneous heterogeneous heterogeneous SOA platforms Semantic Web JACK, JADE SOA platforms SOA platform SOA platform SOA platform SOA platform metamodels Services WSMO, WSMX metamodels models metamodels models models … … MDE for SOA / SHA – using OMG MDA principles

  17. From CIM to PIM with BMM and SoaML CIM Business Models … BPMN BPDM BMM EPC SoaML-SHA PIM System Models Core SoaML Service Variability PIMs for different PIM4 PIM4 PIM4 P2P/Grid/ Architectural Styles Components WS-A SWS Agents PSM - S, JACK, JADE, JXTA, OGSA, J2EE, CORBA WSDL, WSMO, OWL Implementation Models Realization Technologies J2EE, NetWeaver , .Net, …

  18. BMM • There are three main parts in the BMM. • Firstly, an End comprises things that the enterprise aims at achieving, for example Goals and Objectives. • Secondly, the Means are what the enterprise will employ to achieve Ends, for example Strategies, Tactics, Business Policies, and Business Rules. • Finally, Influencers can change the elements of the business plans through Assessments. The Ends, Means and Influencers are related to each other in order to answer the following fundamental question: What is needed to achieve what the enterprise wants to achieve?

  19. BMM and goal modeling • Objective: • reduce in cost and time, while ensuring sufficient quality of the analyses • Means • Establish platform secure exchange of information between health enterprises. • Consume analysis service with lowest cost and shortest process time with sufficient quality. • Influencers

  20. BMM summary • The values of BMM: • Secures a holistic assessment of possible actions and consequences, from business goal, business processes to technology. • Simpler options for following up decisions critical to business. What decisions have been made? Who made these decisions? When were the decisions made? • Enables simpler communication across large enterprises, between people in leading roles. • Enhanced traceability between strategy and actions ensures quicker and more correct decisions. Why do we need to do something about this? Which decisions are necessary? What are our business requirements? • Right hand picture is the companies that support BMM in Norway and UK

  21. SoaML Profile (part of SoaML - UPMS)

  22. Service models - health care examples • collaboration diagram used for representing contracts between the participants that interoperate.

  23. Service models - health care examples • Service network

  24. Goal alignment with BMM and service collaboration with SoaML Figure on the left shows an example of a business motivation model that captures the following business requirements concerning the processing of purchase orders: · Establish a common means of processing purchase orders. · Ensure orders are processed in a timely manner, and deliver the required goods. · Help minimize stock on hand. · Minimize production and shipping costs This example of a BMM model shows the business vision, the goals that amplify that vision, and the objectives that quantify the goals. It also shows the business mission, the strategies that are part of the mission plan, and the tactics that implement the strategies. Finally the strategies are tied to the goals they support. The example also shows a Process Purchase Order contract that formalizes the requirements into specific roles, responsibilities, and interactions. The Contract indicates what motivation elements it realizes through MeansRealizations.

  25. Conclusion • What we have done: • We want to show the capability of SoaML in the organizational interoperability level. The example is service identification from the Norwegian national Health ICT architecture. • What we want to convince: • OMG standard BMM, SoaML can be used not only by business people but also people in the public health and many other domains to reach agreement on the provided and required service, the goals matching them, which support the organizational interoperability.

  26. Conclusion • We suggest a : • Organisational Interoperability –by Goal alignment with BMM and service collaboration with SoaML - • requires mutually shared service related goals (ref. Recent EIF v2.0 definition) - we suggest to model goals with BMM and Services with SoaML, and to relate these by fulfillment relationship, in order to provide a concrete basis for the discussion and resolution of organisational interoperability. • More on the current status of the other development • On going industrial cases include one from the Norwegian oil company: • StatoilHydro: Production and process optimizationcases • One iron producing company from Germany: • Saarstahl -Manufacturing planning and control system, Creation and Optimization of Heats and Sequences,

  27. Article 1:Organizational interoperability supported through goal alignment with BMM and service collaboration with SoaML I-ESA 2009 paper Han Fenglin, NTNU Arne J. Berre, SINTEF Espen Møller, Oslo University Hospital 22. April. 2009

  28. Article 2:Model Driven Service Interoperability through use of Semantic Annotations I-ESA 2009 paper Arne-Jørgen Berre Fangning Liu Jiucheng Xu Brian Elvesæter SINTEF ICT

More Related