INF5120 Modellbasert Systemutvikling Modelbased System development

Transcription

1 INF5120 Modellbasert Systemutvikling Modelbased System development Lecture 1: Arne-Jørgen Berre 1 Welcome to INF5120 Model based System development Model based System Development Earlier: Modellering med objekter, Modeling with objects Lecturers: Arne-Jørgen Berre Franck Fleurey Brian Elvesæter Gøran Olsen, Dumitru Roman, and Guest lecturers inf5120-forelesere@ifi.uio.no Responsible for Obligatory exercises: Weiqing Zhang, Tore Vatnan inf5120-oppgaver@ifi.uio.no 2 1

2 INF Lecture plan : 24/1: Introduction to Model Based System Development (INF5120) Part I: MDE Model Driven Engineering 2: 31/1: MDE I: Metamodels, Domain specific languages and UML profiles, (EMF, Kermeta) 3: 7/2: MDE II: Metamodeling, MDLE and DSL Tools (EMF, GMF, ATL, Kermeta) 4: 14/2: MDE III: Model transformations - MOFScript, 6: 28/2: MDE IV: Method Engineering with SPEM / EPF/SEMAT (Note date and lecture number!) Part II: SSI Service Innovation and Engineering 5 :21/2: SIE I: Service Innovation and CSI, Enterprise Architecture and Service methodologies 7: 7/3: SIE II::Business Process Modeling with BPMN 2.0 8: 14/3: SIE III: User-oriented design with Use cases and UI models 9: 21/3: SIE IV: Service modeling with SoaML, 10: 28/3: SIE V: Internet Service Architectures - with BPM/BPEL and SOA/Cloud Part IV Model Driven Interoperability 11: 4/4: MDI I: Semantic technologies, Ontologies and Semantic annotations 12: 11/4: MDI II: Model Driven Service Interoperability EASTER 13: 2/5: MDE III: ADM and Migration to Cloud computing 14: 9/5: Conclusion and Summary for INF Preparation for Exam Exam: May 30th, 2011 (Monday), (4 hours) Lecturers (from SINTEF): Arne J. Berre, Franck Fleurey, Brian Elvesæter, Dumitru Roman, and Guest lectures 3 Obligatory Exercises : 24/1: Introducing links to Eclipse, EMF, GMF, Eugenia, Kermeta and Modelio 2: 31/1: Introduction to Oblig 1, Individual - Eclipse and EMF tutorial, Kermeta 3: 7/2: EMF and GMF tutorial, Kermeta 4 :14/2: MOFScript in practice, Kermeta 5: 21/2: Preparations/Questions for Oblig 1 delivery, Establish groups for Oblig 2 (25/2: Delivery of Oblig 1) 6: 28/2: Going through Oblig 1, Intro to Oblig 2, EPF-SPEM tools 7: 7/3: BPMN and SoaML tools 8: 14/3: Preparations /Questions for Oblig 2a delivery 9: 21/3: UML2, SoaML tools 10: 28/3: tools for SOA/BPM realisation Generation of code from Modelio etc. (1/4: Delivery of Oblig 2a) 11: 4/4: Going through Oblig 2a delivery, Semantic web/ontology/mdi tools 12: 11/4: Oblig 2B intro, Preparations /Questions for Oblig 2b delivery 29/4: Delivery of Oblig 2b 13: 2/5: Going through Oblig 2B 14: 9/5: Going through old Exams, 2009, 2010 INF9120 Extra Oblig: essay on Model based system development related to thesis topic or similar 2

3 Course literature available on web Material from all lectures and OBLIG 1 and 2 a/b Some selected articles and documents, and subset of standard documents from OMG see handbooks from last year(s). We are currently updating the handbooks for this year. A.J. Berre & B. Elvesæter: Model Driven Engineering - MDE, Handbook. Part 1 - MDA. A.J. Berre & B. Elvesæter: Service Science and Service Oriented Architectures - SOA, Handbook. Part 2 - SOA. A.J. Berre & B. Elvesæter: Model Driven Interoperability - MDI, Handbook. Part 4 - MDI. Practical use of tools (OBLIG): EMF - GMF - Kermeta: Eugenia See also: Modelio - MOFScript - BPMN ATL - og SoaML Course literature available on web Material from all lectures and OBLIG 1 and 2 a/b Some selected articles and documents, and subset of standard documents from OMG BPMN (BPMN v2 Beta 1) SoaML Latest standard document (SoaML Beta 2) Articles by Jim Amsden, IBM, on SoaML (1 to 5), Article by Cory Casanave, Model Driven Solutions, Some selected articles on MDI K. Arnarsdóttir, A.-J. Berre, A. Hahn, M. Missikoff, F. Taglino: Semantic mapping: ontology-based vs. model-based approach Alternative or complementary approaches?, EMOI06Ppaper.pdf. Arne-Jørgen Berre, Fangning Liu, Jiucheng Xu, Brian Elvesæter: Model Driven Service Interoperability through use of Semantic Annotations, I-ESA paper. Fulltext. 6 3

4 OBLIGS: MDE tools in practice Oblig 1 a/b: Design a Kermeta and GMF based editor in Eclipse with EMF and use of MOFScript etc. for transformations to Java. (TBD). OBLIG 2a Smart House with BPMN/SoaML modeling. (TBD). OBLIG 2b part 1/2 - MDI support etc. INF9120 Extra Oblig: essay on Model based system development related to thesis topic or similar 7 Exam Case-based (ref. earlier exams) All written material can be used (4 hours) Monday 30. May

5 3 parts of the course MDE I-V (Model Driven Engineering) SSS (Service Innovation and Service Engineerins) MDI I-II (Model Driven Interoperability) Each part will have a separate handbook 9 Objectives Model based System Development - through modeling with objects and services 2 roles: 1) Tool developer (Software Factory) 2) Application developer, (user of Software Factory). Object-oriented -> Componentbased -> Service oriented Reuse Learn techniques MDA Model driven architecture Meta Modeling and modelltransformation * SOA Service oriented architecture Unified Modeling Language (UML 2.0) for architecture MDI Model Driven Interoperability 10 5

6 Change in course from 2010 We will use a new Metamodel environment, Kermeta, on top of EMF, instead of only focusing on GMF. We will keep the sequence from 2010 and 2008 with a bottom up MDLE approach(rather than top down as we had in 2009) with first learning the principles and technologies for MDE in February. We will also give a short introduction to the focus area of Service Innovation, Service Science and Service Engineering, before finalising the MDE part.. In March we will focus on how to practice a model driven approach to Services (MOS), and in April we will introduce the topic of Semantic Web/services and Model Driven Interoperability (MDI) before a final conclusion of the course 11 New since last year Initial focus on Eclipse with EMF and GMF and transformation tools Use of Modelio commercial modeling tool for UML2 and BPMN 2.0 (This is a new version of Objecteering) New focus on Service Science with Service Innovation (with BI/NHH), Service Design (OAH) and Service Engineering (UIO) New standards: Focus on OMG MDA standards, and on SoaML with links to BPMN 2.0, SysML and UPDM. 12 6

7 Which OMG modeling standards will you learn? SoaML SOA Modeling Language UML 2.0 what is new in version 2 MDA Model Driven Architecture BPMN 2.0 Business Process Modeling Notation BMM _ Business Motivation Model SysML Systems Engineering Modeling Language SPEM Software Process Engineering Metamodel QVT, MOF2Text Query, View, Transformation See 13 Which tools/environments will you learn? Eclipse EMF and XMI, Principles of GMF EuGENia for GMF MOFScript (Model2Text, Model2Model) EPF/SPEM Software Process Modeler Modelio UML Modeler (BPMN, UML 2, SysML) Modelio SOA Solution (SoaML) Overview of ATL, KerMeta, OpenArchitectureWare-OAW, Microsoft OSLO Ref. also IBM RSA/RSM, Enterprise Architect, Magic Draw supporting SoaML and BPMN 14 7

8 OBLIG 1: MDE tools in practice Design a GMF based editor in Eclipse with EMF and use of MOFScript for transformations: Practical use of EMF GMF EuGENia MOFScript Compare with UML profiles Individual work 15 OBLIG 2 Smart House Design increments with group presentations CIM models (BPMN) CIM models (Scope, Goal, Requirements) Requirements models SoaML models Access to web based sensor services MOFScript transformations to Java and potentially to different technologies/platforms Discussion on Model Driven Interoperability 16 8

9 Requirements for the course Student at UIO Only assumption is basic knowledge of UML and Java (but not UML 2.0) 17 Course literature Update to become available on web Material from all lectures and OBLIG Some selected articles and documents, and subset of standard documents from OMG Handbook: Model Driven Engineering - MDE, A.J. Berre & B. Elvesæter Handbook: Service Innovation and Service Engineering, A.J. Berre & B. Elvesæter Handbook: Model Driven Interoperability - MDI, A.J. Berre & B. Elvesæter Practical use of tools (OBLIG): Modelio - MOFScript - BPMN EMF - GMF - Papyrus UML2 - ATL - og JEE

10 Supporting literature Book: Model-Driven Software Development: Technology, Engineering, Management (Paperback) by Thomas Stahl, Markus Voelter, Krzysztof Czarnecki ISBN: Engineering Service Oriented Systems: A Model Driven Approach, Karakostas, Bill; Zorgios, Yannis ISBN10: ISBN13: Cover: Hardcover April Supporting literature EMF and GMF Book: Eclipse Modeling Framework (2nd Edition) (Paperback) Dave Steinberg (Author), Frank Budinsky (Author), Marcelo Paternostro (Author), Ed Merks (Author) Book: Eclipse Modeling Project: A Domain-Specific Language (DSL) Toolkit (Paperback) Richard C. Gronback 20 10

11 Kermeta 21 UML 2.0 UML 2.0 and SysML Background and Reference material See Også hos OMG: (UML) (MDA) (MOF, XMI, CWM) 22 11

12 UML 2.0 recommend books: UML 2.0 in a Nutshell by Dan Pilone (Author), Neil Pitman (Author) The Unified Modeling Language User Guide Second edition (ISBN ) (G, Booch, J. Rumbaugh, Jacobsson) 23 Open Services Innovation Book: January

13 Exam Case-based (ref. earlier exams) All written material can be used (4 hours) (Note, extended from 3 from previous years, we will, however, still keep the same amonunt of work) Monday 30. May OMG Model-Driven Architecture (MDA)

14 Automation in Software Development Requirements Requirements Requirements Manually implement Manually implement Manually implement Source in domain-specific language (DSL) High-level spec (functional and nonfunctional) Source in domain-specific language (DSL) Implement with Interactive, automated support Source in a general-purpose language, e.g., Java or C++ Compile (may generate code in Java or C++) (may generate code in Java or C++) Compile Compile Compile Compile Implementation Implementation Implementation 27 Computational Independent Model ATL CIM BPMN, POP*, ARIS, ArchiMate, GERAM, GRAI, Zachman, UEML, B.Rules MDA CIM, PIM and PSM/Code Platform Independent Model MOFScript PIM ADM BPDM, SBVR, EDOC,UPMS, PIM4SOA, ODM Platform Specific Model/Code PSM ADM BPEL, WSDL, XML, XPDL, OWL-S, WSML, WSDL-S UML profiles and metamodels for Java JEE, BPEL, WSDL, XML, XPDL, OWL-S, WSML, WSDL-S Code, Java JEE,

15 Extending COMET for SOA (1) What service-oriented aspects to capture in models Reference Ontology Legend Registry Repository Internal Infrastructure Services Business Process/Agent Active (Business) Model Web/Server Component Middleware Process/Agent Middleware Component Service Wrappers (Enterprise X) Process Execution Platform (BPEL) Adaptive Distributed Resource Mgt Platform (P2P) Server-side Component Platform (.NET, J2EE) Service Wrappers (Enterprise Y) Service Wrappers (Enterprise A) Public Infrastructure Services Evaluation & Negotiation of Available Functionality Goal-oriented Adaptive Execution Platform (Agents) Intraorg. Message- Oriented Platform (MQSeries) Active Model Platform (AKMii) Composed WebService Platform (WebServices) Enhanced Service Interconnection Bus Existing Enterprise Applications Crossorg. Which metamodels and languages to use annotated with Business Requirements Analysis Enterprise Model Model to Model Transformation UML Profile for POP* Process Organisation Product Architecture Specification annotated with Service-Oriented Architecture Model Model to Model Transformation Model Transformation UML Profile for SOA Information Service Process QoS annotated with UML Profile for Web Services UML Profile for Agents Web Service Specification Model Agent Specification Model BPEL Specification Model P2P Specification Model UML Profile for BPEL UML Profile for P2P Model to Text Transformation Model Transformation annotated with OWL Ontology Web Service Execution Artefacts Agent Execution Artefacts BPEL Execution Artefacts P2P Execution Artefacts Deployment Semantic Space ATHENA Integrated Execution Infrastructure 29 Goals Business rules Business processes Business services E-contracts Flexible Flexible business Flexible business models business models models CIM according to Business Business Business metamodels metamodels metamodels EPC POP* BPDM, BPMN BMM Executable business processes Service interfaces Service contracts Service enactment Business rules SLAs Parameterized services Executable artefacts XSD, WSDL, BPEL Teams and plans Resource management Semantic Web Services input Transformer (engine) output Semanticallyenabled heterogeneous SOA model input Transformer (engine) output transformation engine PIM according to transformation engine PSM according to source Transformation rules target Unified and standardised metamodel for SOA & SHA source Transformation rules target Semanticallyenabled Interconnected Interconnected heterogeneous heterogeneous SOA SOA platform platform models models Semanticallyenabled Heterogeneous heterogeneous Heterogeneous SOA SOA platforms SOA platforms metamodels metamodels Service Variability Flexible Business Models Web Services UPMSHA Grid SoaML P2P Semantic Web Services Heterogeneous Platforms Heterogeneous service platforms WSA JXTA OGSA JACK, JADE WSMO, WSMX Agents 15

16 BPMN BPDM BMM EPC CIM Business Models UPMSHA (core) UPMS (core) UPMSHA Service Variability PIM Models UPMS WSA PIM4 SWS PIM4 Agents P2P/Grid/ Components PIMs for different Architectural Styles WS, WSMO, OWL-S, JACK, JADE, JXTA, OGSA, J2EE, CORBA PSM Models J2EE, NetWeaver,.Net Realisation Technologies CIM-K Ontologies Bus.Process Bus.Rules Goals NFA/Qualities Org BPMN, POP*, ARIS, ArchiMate, GERAM, GRAI, Zachman, UEML, B.Rules... PIM-K Information Process Services Rules NFA UI BPDM, SBVR, EDOC,UPMS, PIM4SOA, ODM PSM-K Data Wflow/Comp Interfaces Rules NFA UI UML profiles and metamodels for BPEL, WSDL, XML, XPDL, OWL-S, WSML, WSDL-S Technologies/Realisation-K XML, BPEL/XPDL, WSDL, SWRL, Security, AJAX OWL, OWL-S/WSML WSDL-S, Induction, QoS Legacy and New systems/services, ERPs/ESAs Technology Reliastion Code 32 16

17 CIM ODM, Concepts BMM BPMN PIM SoaML Information Services Process PSM Persistence API EJB 3.0, Java, XML,, Metro/WSDL BPEL/XPDL OWL,WSML OWL-S/WSML SA/WSML ASM Jack, JADE Jack, JADE Jack, JADE SAP SAP SAP Technologies/Realisation INF5120 OMG standard focus SHAPE Solution Overview Flexible Business Modelling BPMN EPC BMM CIM Business Models Core SHA-ML PIM System Models SoaML Service Variability PIM4 SWS PIM4 Agents P2P/Grid/ Components/ PIMs for different Architectural Styles WSDL, WSMO, OWLS, JACK, JADE, JXTA, OGSA, CORBA, PSM Implementation Models J2EE, NetWeaver,.Net, Execution Environments 2nd EC Review, Brussels, January 28th

18 Technological Innovations SHAPE Solution MDE Technologies Purpose / Benefit Problem / State-of-Art Solution developed Future Plans 1 Flexible Business Modelling Integrated & guided business modelling Business-IT-Gap Bus. Modeling techniques not integrated Business-IT-Gap Existing techn. not integrated BPMN 2.0 support Cont. integration of bus. modelling Backward analysis 2 Service & SOA Modelling Enable MDE for services & SOA MDE for SOA highly desired UML does not support this SoaML metamodel & profile Modelling tools Methodology Disseminate SoaML Commercialization SoaML Extensions 3 Integration of Agent Technology Automated planning on top of services Services are only passive infrastruc. problem solving / planning on top Framework & Tools for integration with SoaML Enhance AOSE Standardiz. (AMP) Enhanced problem solving using services 4 Integration of SWS Technologies 5 Service Customization Handling Heterogeneity + automate service usage Customization & personalization of services Hetero. & dynamics in larger systems SWS not aligned with classic SE Complex services vs. indiv. user req. adequate techniques not existing MDE for SWS: Framework, Tool, Methodology New approach based on SPEL Metamodel, Tool, Methodology Standardization (OMG,W3C,OASIS) MDE for Semantic Technologies Standardiz. (CVL) Continue towards comprehensive serv. customization 35 SHAPE Solution Matrix MDE Infrastructure Meta- Models Model Transformations SHAPE Tool Suite SHAPE Methodology 1 Flexible Business Modelling BPMN, EPC Data, Org., Rules BMM, Ontologies CIM->CIM (mult.) CIM -> PIM (mult.) CIMFlex Modelio CIMFlex Modeling BPMN + UML Ontology Engin. 2 Service & SOA Modelling SoaML SoaML -> WS SoaML -> JEE Modelio Composition Studio SoaML & WS Modelling 3 Integration of Agent Technology SHAML Agent Extension SoaML -> PIM4Agents PIm4Agents -> PSM PIM4Agents Agent Modelling (PIM ->PIM2PSM->PSM) 4 Integration of SWS Technologies SHAML SWS Extension SoaML-> SWSPim SWSPim -> WSMO WSMT SWS Modelling (PIM ->PIM2PSM->PSM) 5 Service Customization Service Variability Metamodel SoaML-> SV-Spec. SV-Res. -> Soaml Service Variability Tools Service Variability Modelling & Variant Creation 36 18

19 Part 4: MDI Model Driven Interoperabtiliy TR/QVT CIM-K ADM Organisational Interoperability TR/QVT CIM-K ADM BPMN, POP*, ARIS, ArchiMate, GERAM, GRAI, Zachman, UEML, B.Rules PIM-K Semantic Interoperability PIM-K BPDM, SBVR, EDOC,UPMS, PIM4SOA, ODM TR/QVT ADM TR/QVT ADM TR/M2T PSM-K ADM Technical Interoperability TR/M2T PSM-K ADM UML profiles and metamodels for BPEL, WSDL, XML, XPDL, OWL-S, WSML, WSDL-S BPEL, WSDL, XML, XPDL, OWL-S, WSML, WSDL-S Code BPEL, WSDL, XML, XPDL, OWL-S, WSML, WSDL-S Code 37 EPF Composer EPF Composer is a tool platform for process engineers, project leads, project and program managers who are responsible for mainteining and implementing processes for development organizations or individual projects Aims to: provide for development practitioners a knowledge base of intelectual capital that allows them to browse, manage and deploy content. provide process engineering capabilities by supporting processe engineers and project managers in selecting, tailoring, and rapidly assembling processes for their concrete development process. 19

20 What is Enterprise Modelling? Enterprise Modelling (EM) is a capability for externalising, making and sharing enterprise knowledge. EM tools can either be: used stand-alone to produce various kinds of model views, integrated as front-ends to other systems, part of an environment providing a contextual user-environment. 39 Why Enterprise Architecture? How can I involve my people in improving the performance of the business?? How can I ensure that the IS technology helps the work of my people? How can I use best practices to ensure the success of the business?? 40 20

21 Representations of Architecture ARIS ZACHMAN GERAM EKA - POPS EN/ISO Athena OEA NIST 41 Three Views in DOD Architecture Framework and C4ISR-AF 42 21

22 To-be Operational DoDAF Architectural Standards architecture Current As is To be Target architecture To-Be Architectural models supported by the necessary tools. Hub New Form Organisationof Service-Team Organization 43 Zachman Framework for Enterprise Architecture VA Enterprise Architecture DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why Based on work by John A. Zachman SCOPE (CONTEXTUAL) Things Important to the Business Processes Performed Business locations Important Organizations Ev ents Significant to the Business Business Goals and Strategy SCOPE (CONTEXTUAL) Planner Entity = Class of Business Thing Function = Class of Business Process Node = Major Business Locations People = Major Organizations Time = Major Business Event Ends/Means = Major Business Goals Planner ENTERPRISE MODEL (CONCEPTU AL) Semantic Model Business Process Model Business Logistics System Work Flow Model Master Schedule Business Plan ENTERPRISE MODEL (CONCEPTU AL) Owner Ent = Business Entity Proc = Business Process Node = Business Location People = Organization Unit Time = Business Event Rel = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle End = Business Objectiv e Means = Business Strategy Owner SYSTEM MODEL (LOGICAL) Logical Data Model Application Architecture Distributed System Architecture Human Interface Architecture Processing Structure Business Rule Model SYSTEM MODEL (LOGICAL) Designer Ent = Data Entity Rel = Data Relationship Proc = Application Function Node = IS Function People = Role I/O = User Views Link = Line Characteristics Work = Deliverable Time = System Event End = Structural Assertion Cycle = Processing Cycle Means = Action Assertion Designer TECHNOLOGY MODEL (PHYSICAL) Physical Data Model System Design Technology Architecture Presentation Architecture Control Structure Rule Design TECHNOLOGY MODEL (PHYSICAL) Builder Ent = Segment/Table Rel = Pointer/Key Proc = Computer Function Node = Hardware/Softw are People = User I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Time = Ex ecute End = Condition Cycle = Component Cycle Means = Action Builder DETAILED Data REPRESENTATIONS Definition (OUT-OF-CONTEXT) Program Netw ork Architecture Security Architecture Timing Definition Rule Design DETAILED REPRESENTATIONS (OUT-OF-CONTEXT) Sub-Contractor Ent = Field Rel = Address Proc = Language Statement Node = Addresses I/O = Control Block Link = Protocols People = Identity Work = Job Time = Interrupt Cycle = Machine Cycle End = Sub-Condition Means = Step Sub-Contractor FUNCTIONING ENTERPRISE Data Function Netw ork Organization Schedule Strategy FUNCTIONING ENTERPRISE Ent = Rel = Proc = I/O = Node = Link = People = Work = Time = Cycle = End = Means = DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why 44 22

23 CSI Norway Center for Service Innovation led by Norwegian Business School, Bergen, SINTEF, AOH, Telenor,.. (National Center for Research Driven Innovation (SFI) 20 Meuro budget, 8 years ) CSI planned Activities 23

24 Service Modeling with SoaML and extensions (FP7 SHAPE project ++) UPMS 47 Business Motivation Model (BMM) with MeansRealizations 24

25 What is BPMN (Business Process Modeling Notation)? BPMN example 25

26 System and objects A system is a part of the real world which we choose to regard as a whole, separated from the rest of the world during some period of consideration. A whole that we choose to consider as a collection of objects, each object being characterized by attributes and by actions which may involve itself and other objects. Mental modell Real-World phenomenon Manifest Model 51 Object oriented modeling arealworld- Phenomena anobjectmodel rolemodels animplemented System Environment Model environment Mental model Real-World phenomenon System model Manifest Model 52 26

27 OO Programming Terminology Encapsulation Object Message Method Class Instance Inheritance Polymorphism Dynamic (Late) Binding 53 CRC Method, class, responsibilities, and collaborators Method to learn the most basic OO concepts plus OO thinking The most effective way of teaching the idiomatic way of thinking with objects is to immerse the learner in the "object-ness" of the material. To do this we must remove as much familiar material as possible, expecting that details such as syntax and programming environment operation will be picked up quickly enough once the fundamentals have been thoroughly understood. Technique also very useful during informal and creative analysis and design Created by Kent Beck and Ward Cunningham, Textronix,

28 The CRC-Card an object of paper personalizing the object Class (Name): Responsibility: Collaborators: 55 Class, responsibilities, and collaborators Class The class name of an object creates a vocabulary for discussing a design. Indeed, many people have remarked that object design has more in common with language design than with procedural program design. We urge learners (and spend considerable time ourselves while designing) to find just the right set of words to describe our objects, a set that is internally consistent and evocative in the context of the larger design environment. Responsibilities Responsibilities identify problems to be solved. The solutions will exist in many versions and refinements. A responsibility serves as a handle for discussing potential solutions. The responsibilities of an object are expressed by a handful of short verb phrases, each containing an active verb. The more that can be expressed by these phrases, the more powerful and concise the design. Again, searching for just the right words is a valuable use of time while designing. Collaborators Objects which will send or be sent messages in the course of satisfying responsibilities. Collaboration is not necessarily a symmetric relation. For example in Smalltalk, View and Controller operate as near equals while OrderedCollection offers a service with little regard or even awareness of its client

29 UML og ( R )UP Two parts of a Harmonized Whole Unified Modeling Language Process Convergence Today Unification leads to standards Convergence in the future Process frameworks through consensus 57 UML Structural Modeling Class Diagram Object Diagram Component Diagram (new in UML 2.0) Package Diagram Deployment diagram 58 29

30 UML Behavioral Modelling Use Case Diagrams Interactions Sequence diagrams (enhanced in UML 2.0) Timing diagrams (new in UML 2.0) Interaction overview diagrams (new in UML 2.0) Communication diagrams (i.e. collaboration diagram) State machine diagrams (enhanced in UML 2.0) Activity Diagrams (enhanced in UML 2.0) 59 Different kind of models Conceptual models Specification models Implementation models 60 30

31 Service Science SSME: Service Science, Management & Engineering Service systems are value cocreation configurations of people, technology, internal and external service systems connected by value propositions, and shared information (such as language, laws, measures, models, etc.). This is a multidisciplinary approach in understanding, defining, creating and delivering service systems Operations Research and Industrial Engineering More realistic models of people Computer Science and Electrical Engineering, Information Systems Software and systems that adaptively change with business strategy Economics and Business Strategy, Service Management and Operations Better models of scaling and innovation Law and Political Economy Better models of social innovation in what way is passing a law innovation Complex Systems and Systems Engineering Better model of robustness and fragility of service systems (sustainability) 61 Service Science New academic cross discipline Definition of Service: 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. (SoaML) Service Innovation Service Design Service Engineering 62 31

32 SOA Service oriented architecture From Objects ( ) To Components ( ) To Services ( ) 63 SOA Services Messages Dynamic discovery Web services 64 32

33 Service Oriented Architecture (SOA) definition A set of components which can be invoked, and whose interface descriptions can be published and discovered (W3C). The policies, practices, frameworks that enable application functionality to be provided and consumed as sets of services published at a granularity relevant to the service consumer. Services can be invoked, published and discovered, and are abstracted away from the implementation using a single, standards-based form of interface. (CBDI) ( 65 Extended service-oriented architecture Market maker Role actions performs publishes uses becomes Service provider Management Market Certification Rating SLAs Operations Assurance Support Composition Coordination Conformance Monitoring QoS Description & Basic Operations Managed services Service operator Composite services Basic services Capability Inteface Behavior QoS Service client Publication Discovery Selection Binding Papazoglou and Georgakopoulos CACM, Oct Service aggregator 66 33

34 Dealing with Complexity and Change Working at the right level of abstraction OO dealing with complexity objects -> components -> services *SOA Design by contract, role composition Aspect-oriented programming Use of patterns Visual Modeling (MDA) Architecture 67 OOAD methods Class Phase Traditional SA/SD/ERA ANALYSIS DESIGN DETAILED DESIGN SA - Yordon SD - Page Jones ERA - Chen ER-Rel.db - 3NF SA-based OO ERA-based OO Hybrid SA/ERbased OO SD-basert OO Ada(C++)-based SDL-based OO OO-based OO RT SA - Wards OOA/OOD - Coad/Yordon OMT - Rumbaugh et. al OOAD - Martin/Odell Fusion - HP OOSD - Wasserman HOOD - ESA OOAD - Booch (93 w/c++) OOSE/ObjectOry - Jacobson RDOOD - Wirfs-Brock et. al OSDL-92 - CCITT/Bræk et. al CRC-cards - Cunningham OOram - Reenskaug et. al Catalysis, Syntropy, SOMA, OBA, BHS,... UML (96) Booch/OMT/ObjectOry 68 34

35 Evolution of the UML Submission of UML 1.1 to OMG for adoption, Sept 97 UML 1.0 UML 2.0 (2004) UML 1.4 UML 1.1 (Sept. 1997) Taskon, SINTEF public feedback June 96 & Oct 96 OOPSLA 95 UML 0.9 & 0.91 Unified Method 0.8 UML Partners Expertise Booch 93 OMT - 2 Other methods Booch 91 OMT - 1 OOSE 69 Evolution of methodologies OOram OMT Booch UML1.0 Objectory Catalysis 2000 UP UML1.1 UML1.2 Notation Pulse UML Components 2001 RUP UML1.3 UML1.4 KobrA UML4EDOC Process Objecteering SOA COMET COMET-S UML

36 See also: Final version of SoaML per October, SoaML UML Profile & Metamodel 36

37 Consumer Example: Marketplace Services Mechanics Are Us Dealer Consumer Physical Delivery Status Order Conformation Shipped Provider Provider GetItThere Freight Shipper Provider Ship Req Shipped Delivered Acme Industries Manufacturer Consumer Services Architecture A ServicesArchitecture (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. 37

38 Compound services Participants may be assemblies of other Participants (UML 2.0) Participant Request needs typed by ServiceInterface Service capabilities typed by ServiceInterface Participant part 38

39 MOFScript placed in the 4-layer metamodel architecture (MDE) M3 conforms to MOF conforms to M2 Source Metamodel based on MOFScript language conforms to conforms to M1 Source model MOFScript transformation executed by input MOFScript tool engine output Target text Unified Process Framework Disciplines Process Components Process Requirements Workflows Analysis Business Modeling Requirements Architecture Level Analysis Design Design Implementation Class Level Test Implementation Deployment Inception Test Supporting Workflows Supporting Components Management Project Management Conf. Mngmt Process Configuration Environment preliminary iteration(s) iter. #1 Phases Elaboration Construction Transition iter. #2 iter. #n iter. #n+1 Iterations iter. #n+2 iter. #m iter. #m

40 Business domain Technical domain Modelio SOA method and tool support 79 COMET-S and SiSaS model architecture Model world Real world Business model Domain model Risk analysis Product vision & product desc. Concepts & Artifacts Processes Requirements model Prototype System boundary model Web Services model Web Services profile model Use case Scenario model Other requirements BCE model Service-Oriented Architecture model Component structure model Service interaction model Service interface model. Web Services implementation model User Interface Tier User Service Tier Business Service Tier Resource Service Tier RA Actors RA LA LS 80 40

41 Interoperability Framework ATHENA Interoperability Framework ( each system is described by enterprise models and different viewpoints, such as business, process, service, information) Next Lecture MDE I January 31st, 2011 Metamodeling Domain specific languages Eclipse EMF and GMF, Kermeta UML profiles Intro: See Eclipse EMF/GMF tutorials Kermeta:

42 INF5120 Tools available on web Practical use of tools (OBLIG): EMF - GMF - Kermeta: Eugenia See also: Modelio - MOFScript - BPMN SoaML