INF 5120 Modellbasert Systemutvikling Modelbased System development Lecture
INF 5120 ”Modellbasert Systemutvikling” ”Modelbased System development” Lecture 7: 08. 03. 2010 Soa. ML modeling ICT 1
INF 5120 - Lecture plan - 2010 n 1: 25/1: Introduction to MBSU, MDA, OO and Service/SOA modeling, Overall EA, 4 parts: MDE/SSS/MS/MDI (AJB) n n Part I: MDE – Model Driven Engineering 2: 1/2: MDE I: Metamodeling. DSL and UML profiles, MDA technologies (XMI, Eclipse, EMF/GMF) (AJB/BRE) n n Part II: SSS – Service Science and Service/SOA technologies 3: 8/2: SSS I: Service science (top down) - Service and SOA Technologies (bottom up) (AJB) n n n Part I continued: MDE – Model Driven Engineering 4: 15/2: MDE II: Model transformations with MOFScript, ATL and other technologies (GO/JO) 5 : 22/2: MDE III: Code generation with MOFScript, ATL and other technologies (GO/JO) n n n Part III: MOS – Modeling of Services - with Soa. ML 6: 1/3: MOS I: Business Process Modeling (CIM) - with BPMN 2. 0, and BMM, EA with UPDM (AJB) 7: 8/3: MOS II: Soaml, UML 2 and Sys. ML, Modelio SOA and Scope, –Collaboration and Component models (AJB) 8: 15/3: MOS III: Soa. ML (PIM) and Requirements modeling , CIM->PIM and Soa. ML (AJB) 9: 22/3: MOS IV: Method Engineering and SPEM / EPF - for Service systems (BRE) n n n EASTER Part IV – Model Driven Interoperability 10: 12/4: MS V: SOA and Service Design, Migration to SOA/Cloud Patterns with ADM (AJB ) 11: 19/4: MDI I: Semantic Web with Ontologies and Model Driven Interoperability (TIR) 12: 26/4: MDI II: Semantic Services and Model Driven Interoperability (TIR) 13: 3/5: MDE IV: Evolution and industrial practice of modelbased technologies (AJB++) n 14: 10/5: Course summary and preparation for Exam 31/5 (AJB) n Exam: May 31 st, 2010 (Monday), 0900 -1200 (3 hours) ICT 2
Oblig 2 (Group work) n Create CIM, PIM and PSM models for an existing. Travel agency to start to offer bookings through the web – for bookings through Internet of packaged travels (including flights, hotel, and car options). n Goals include Internet based travel reservation, optimal travel planning, improving the quality of customer satisfaction and financial optimisation, suppport automation of the accounting department and cash flow management, and to follow up on personnel load and satisfaction and collaboration between the various departments (sales, marketing, accounting, etc. ) Process support for ISO 9000 certification. ICT 3
Outline n L 7 -1: Soa. ML introduction n Soa. ML Collaboration models n Soa. ML Composite structure models n L 7 -2: Sys. ML introduction ICT
Goals Business rules Business processes Business services E-contracts … CIM Flexible flexible business models business Businessmodels Models Transformer (engine) Executable business processes Service interfaces Service contracts Service enactment Business rules SLAs Parameterized services … transformation engine PIM Business metamodels Transformation rules Flexible Business Models Web Services Semantically enabled heterogeneous SOA model according to Unified and standardised metamodel for SOA & SHA Service Variability Semantically Interconnected enabled Interconnected heterogeneous SOA platform models transformation engine PSM according to Grid UPMSHA P 2 P Transformer (engine) Executable artefacts XSD, WSDL, BPEL Teams and plans Resource management Semantic Web Services … according to EPC POP* BPDM, BPMN BMM … Agents Semantic Web Services Heterogeneous Platforms Transformation rules Semantically enabled Heterogeneous heterogeneous SOA platforms SOAplatforms SOA metamodels Heterogeneous service platforms WSA JXTA OGSA JACK, JADE WSMO, WSMX … ICT Which metamodels and languages to use What service-oriented aspects to capture in models CIM to PSM 5
Use of OMG metamodels n n n n n BPMN (BPMN 2. 0) BMM UML 2. 0 Soa. ML OSM VDM Case Management SBVR ODM ICT 6
Soa. ML Historikk (Service oriented architecture modeling language) n n n OMG RFP – September 2006 3 initial submissions – June 2007 Merge process in 2008 and 2009 Soa. ML 1. 0 ferdigstilt desember 2009 Soa. ML 1. 0 adopteres av OMG i mars 2010 FTF chairs: Arne J. Berre, SINTEF og Jim Amsden, IBM n http: //www. soaml. org 7 ICT
Service n A service is value delivered to another through a welldefined interface and available to a community (which may be the general public). A service results in work provided to one by another. ICT
Mappings between BPMN 2. 0 and Soa. ML n BPMN participants are mapped to Soa. ML participants n BPMN conversation diagrams are mapped into Soa. ML service architectures n BPMN choregraphies are mapped into process for interactions between Soa. ML particpants – a basis for services n BPMN service tasks are invocations of web services (more as an implementation level service) ICT
Service Architecture Modeling with Soa. ML collaboration models ICT
Services Architecture Ship Status service Purchasing service Shipping service A Services. Architecture (or SOA) is a network of participant roles providing and consuming services to fulfill a purpose. The services architecture defines the requirements for the types of participants and service realizations that fulfill those roles. The services architecture puts a set of services in context and shows how participants work together for a community or organization without required process management. A community Services. Architecture is defined using a UMLICTCollaboration.
Inside the Seller/Manufacturer Order Conformation Shipped Order Processing Service Accounting Ship Req Shipped Delivered ICT
Service. Contract A Service. Contract defines the terms, conditions, interfaces and choreography that interacting participants must agree to (directly or indirectly) for the service to be enacted - the full specification of a service which includes all the information, choreography and any other “terms and conditions” of the service. A Service. Contract is binding on both the providers and consumers of that service. The basis of the service contract is also a UML collaboration that is focused on the interactions involved in providing a service. A participant plays a role in the larger scope of a Services. Architecture and also plays a role as the provider or user of services specified by Service. Contracts. ICT
Service Contract Role within service Service interface corresponding to role Role within service Information processed by order processor type Service interface corresponding to role Information received by orderer The service contract specifies the details of the service – what information, assets and responsibilities are exchanged and under what rules ICT
Simple Protocol Choreography for Ordering Service Contract Could also be specified in BPMN, in principle ICT
Participants Participan t Participants represent logical or real people or organizational units that participate in services architectures and/or business processes. In Soa. ML participants provide and use services, defining their external contract ICT
Service Modelling with Soa. ML Port/Connector models – extending UML 2. 0 composite structure models ICT
Service ports and Service Participants A Service port s the offer of a service by one participant to others using well defined terms, conditions and interfaces. A Service port defines the connection point through which a Participant offers its capabilities and provides a service to clients. A Service port is a mechanism by which a provider Participant makes available services that meet the needs of consumer requests as defined by Service. Interfaces, Interfaces and Service. Contracts. A Service port is represented by a UML Port on a Participant stereotyped ICT as a «Service, .
Service. Interface a Service. Interface can be the type of a service port. The service interface has the additional feature that it can specify a bi-directional service – where both the provider and consumer have responsibilities to send and receive messages and events. The service interface is defined from the perspective of the service provider using three primary sections: the provided and required Interfaces, the Service. Interface class and the protocol Behavior. ICT
Participant with Service and Request ports The type of a Request port is also a Service. Interface, or UML Interface, as it is with a Service port The Request port is the conjugate of a Service port in that it defines the use of a service rather than its provision. This will allow us to connect service providers and consumers in a Participant. - Can be transformed to appropriate interface/implementation code. ICT
Conclusion n Both BPMN 2. 0 and Soa. ML will become final standards in 2010 n A BPMN-Soa. ML harmonisation team is working on alignment and synergy between the two specifications – they will complement each other with the process and service perspective, respectively n BPMN 2. 0 with Soa. ML enables working with services and service composition at an abstraction level suitable for business stakeholders n Tool vendors are preparing support for BPMN 2. 0 (incrementally) and Soa. ML (already) ICT
Next Lecture – March 15 th, 2010 n Soam. L n UML 2. 0 - Collaboration Diagrams, OOram n UML 2. 0 Port Connector Models and Components n Service Science – IBM, Jørn Berg Nordlund ICT 25
- Slides: 22