INF5120 Modellbasert Systemutvikling Modelbased System development. Lecture 5:

Transcription

1 INF5120 Modellbasert Systemutvikling Modelbased System development Lecture 5: SIE I: Service Innovation and CSI, Enterprise and Service methodologies Arne-Jørgen Berre 1 Outline L5-1: Service Innovation (Per Pedersen, NHH) An introduction to services, service science, service innovation and new service development L5-2: Enterprise and Models (AJB) Zachman, TOGAF, DODAF-MODAF-NAF (UPDM) VDM Value Definition Metamodel BMM - Motivation Model BPMN 2.0 and CMPM Case Management Meta Model 1

2 Content Enterprise Modeling with OMG Standards Implementing Enterprise s via UML Profiles EA and the Zachman Framework Architectural Frameworks - (IEEE/ 1471/ISO 42010, ADL, UML 2.x, TOGAF, UPDM (DODAF/MODAF), (SHAPE), DSLs) UPDM Service modeling and Service oriented views Tool support, Metamodels and UML profiles No Magic, Magic Draw 3 Model Frameworks with Modeling support from NEFFICS Building block Incremental innovation Do what we do but better Radical innovation Do something different Value proposition Offering more of the same Offering something different (at least to the company) Target customer Existing market New market Value chain architecture [Internal] Competences Exploitation (e.g. internal, lean, continuous improvements) Familiar competences (e.g. improvement of existing technology, HR, organizational system, culture) Exploration (e.g. open, flexible, diversified) Disruptively new, unfamiliar, competences (e.g. new emerging technology, new HR skills, organizational systems, culture) Network Partners Familiar (fixed) network New (dynamic) networks (e.g. alliance, jointventure, community) Relations Profit formula Continuous improvements of existing relations (e.g. channels) Existing processes to generate revenues followed-by/or incremental processes of retrenchments and cost cutting New relations, relationships (e.g. channels physical, digital, virtual, personal) New processes to generate revenues followedby /or disruptive processes of retrenchments and cost cutting 4 2

3 Zachman Framework for Enterprise (IBM, 1987) VA Enterprise 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 Processes Performed locations Important Organizations Ev ents Significant to the Goals and Strategy SCOPE (CONTEXTUAL) Planner Entity = Class of Thing Function = Class of Process Node = Major Locations People = Major Organizations Time = Major Event Ends/Means = Major Goals Planner ENTERPRISE MODEL (CONCEPTU AL) Semantic Model Process Model Logistics System Work Flow Model Master Schedule Plan ENTERPRISE MODEL (CONCEPTU AL) Owner Ent = Entity Proc = Process Node = Location People = Organization Unit Time = Event Rel = Relationship I/O = Resources Link = Linkage Work = Work Product Cycle = Cycle End = Objectiv e Means = Strategy Owner SYSTEM MODEL (LOGICAL) Logical Data Model Application Distributed System Human Interface Processing Structure 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 Presentation 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 Security 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 5 TOGAF 9 6 3

4 Open Group ADM 7 8 4

5 Building block evolution 9 Service categories 10 5

6 Why and When: Historical Development of AF s. MODAF Meta-Model (M3) expressed using UML Notation NAF v NAF v DNDAF v C4ISR Framework v2.0 C4ISR Framework v MACCIS Norway DoDAF v1.0 MODAF v TOGAF1 - MODAF v Scope of UPDM 1.0 Approved Sept 2008 MODAF v DoDAF v DoDAF V Scope of UPDM 2.0 Started Sept 2009 TOGAF9 DODAF viewpoints 12 6

7 EAEA European Air Traffic Management Enterprise 13 OMG Model-Driven (MDA)

8 IEEE 1471, ISO Use of OMG metamodels BPMN (BPMN 2.0) BMM UML 2.0 OSM VDM Case Management SBVR ODM 16 8

9 Zachman with OMG standards Data (What) Function (How) Network (Where) People (Who) Time (When) Motivation (Why) Scope (Contexts) List of things important to business SBVR List of processes that the business performs VDM List of locations which the business operates VDM List of organizations important to the business OSM List of events/cycles important to the business DTFV List of business goals/strategies BMM (Concepts) Semantic Model ODM, IMM (CWM) Process Model BPMN, CMPM Logistics System BPMN, CMPM Workflow Model OSM, BPMN, CMPM Master Schedule BPMN, CMPM, DTFV Plan SBVR System (Logic) Logical Data Model ODM, IMM (CWM), UML Application, UML Distributed System, UML Human Interface BPMN, CMPM Process Structure BPMN, CMPM, DTFV Rule Model SBVR Technology (Physics) Physical Data Model IMM (CWM), UML System Design, UML Technology, UML Presentation Control Structure BPMN, CMPM, DTFV Rule Design SBVR Component (Assemblies) Data Definition IMM (CWM), UML Program UML Network UML Security Timing Definition DTFV Rule Definition SBVR Operation (Instances) Data Function Network Organization Schedule Strategy 17 OMG standards coverage Data (What) Function (How) Network (Where) People (Who) Time (When) Motivation (Why) Scope (Contexts) SBVR List of things important to business List of processes that the business performs VDM List of locations which the business operates OSM List of organizations important to the business List of events/cycles important to the business BMM List of business goals/strategies (Concepts) System (Logic) Semantic Model ODM Logical Data Model Process Model Application Logistics System Distributed System BPMN CMPM Workflow Model Human Interface Master Schedule Process Structure Plan SBVR Rule Model Technology (Physics) IMM (CWM) Physical Data Model System Design UML Technology Presentation Control Structure DTFV Rule Design Component (Assemblies) Data Definition Program Network Security Timing Definition Rule Definition Operation (Instances) Data Function Network Organization Schedule Strategy 18 9

10 ModelDriven (MDA,Oslo) Interoperability (MDI) UPDM coverage Data (What) Function (How) Network (Where) People (Who) Time (When) Motivation (Why) Scope (Contexts) (Concepts) System (Logic) UPDM BPMN Technology (Physics) Component (Assemblies) Operation (Instances) 19 Model Based Systems Engineering and Interoperability (SysML Context + BPMN 2.0/BMM) BMM BPMN VDM CaseMgmt OSM SBVR Enterprise (EA) for Systems of Systems (UPDM) System & IT Service oriented (UML&SysML/) UML 2.0 SysML 10

11 External References Transformations What is UPDM? - Summary UPDM 1.0 is a standardized way of expressing DoDAF 1.5 and MODAF 1.2 artefacts using UML and SysML UPDM is NOT a new Architectural Framework UPDM is not a methodology or a process UPDM 2.0 is scheduled to address DoDAF 2.0, MODAF 1.2, NAF 3.x, and DNDAF 1.7 UPDM 1.0 was developed by members of the OMG with help from industry and government domain experts. UPDM 1.0 has been implemented by multiple tool vendors. Tools supporting UPDM 1.0 are available now. UPDM: UML Profile for DoDAF and MODAF Context Stakeholders US DoD UK MOD NATO Canada/Australia OMG, INCOSE OMG XMI, UML, SysML BPMN UPMS, BMM End Users Aerospace Commercial Tool Vendors Software Systems Enterprise NAF Meta Model DoDAF 1.5 Concepts CADM 1.5 UJTL SF List CDD CONOPS SSDD etc. MODAF Meta Model UPDM Domain Meta Model UPDM Profile Meta Model UPDM Profile & Library <<import/merge>> UML4SysML SysML Extensions, BMM, SBVr Extensions DoDAF 2.0 Ontology CADM AP233 XMI IDEF UML SysML BPMN BMM Products -- Reports -- Simulations 11

12 UPDM 23 UPDM - Unified Model for DODAF and MODAF 24 12

13 UPDM Unified Model for DODAF and MODAF 25 UPDM RFC - Domain Meta Model Summary 13

14 UPDM RFC - Domain Meta Model Summary (Packages.) Package structure organizes stereotypes by viewpoint Multiple viewpoints manage model complexity UPDM RFC - Domain Meta Model Summary (AV) 14

15 Service innovation is inherently multidisciplinary Knowledge sources driving service innovations Science & Engineering Technology Innovation Innovation Administration and Management Social Sciences Social-Organizational Innovation Demand Innovation Global Economy & Markets SSME = Service Sciences, Management, and Engineering Economic evolution of services Pre-Industrial Society Primarily agrarian economies Industrial Society Good dominate economies Post-Industrial Society Information, knowledge, and quality of life economies 1800s Classical and Neoclassic 1950s Decision marketing school 1980s Customer fulfillment and satisfaction s Early formative marketing 1970s Marketing management and experts 2000s Services dominant logic What was occurring during these time periods that may have influenced shifts in economies and changes in business? 15

16 What is a service? Per Wikipedia (2006): In economics and marketing, a service is the non-material equivalent of a good. It is claimed to be a process that creates benefits by facilitating either a change in customers, a change in their physical possessions, or a change in their intangible assets. By supplying some level of skill, ingenuity, and experience, providers of a service participate in an economy without the restrictions of carrying stock (inventory) or the need to concern themselves with bulky raw materials. On the other hand, their investment in expertise does require marketing and upgrading in the face of competition which has equally few physical restrictions. Service dominant view Three primary notions 1. Co-creation of value 2. Relationships 3. Service provisioning 16

17 Service 33 ESA Enterprise Service with BPMN and Report AV-1 Overview &Summary Information AV-2 Integrated Dictionary SOV-E2 SHAPE Service Interface Diagram (Instead of SOV-2 Service Interface Specification) All Views Report OV-7 Information Model Product Diagram Structure Ac-V1 Acquisition Clusters Ac-V2 Programme Timelines OV-1 high level Operational Concept Graphic OV-E2 Shape Service Diagram (Instead of OV-2 Operational Node Relationship Description) OV-E4 Organization Structure Metamodel(OSM) (Instead of Organizational Relationships Chart) SOV-1 Service Taxonomy SV-1 Recource Interaction Specification SV-2 Resource Comunications Description Matrix Table Behavior OV-3 Operational Information Exchange StV-E1 SHAPE OV-5 Matrix Operational Goal Activity Diagram Model Instead of StV- 1 Enterprise SOV-3 Vision Capability to OV-E6b Service SHAPE Mapping BPMN(Inste ad of OV-6b StV-2 Operational Capability State StV-6 Taxonomy Transition Operational Description) Activity to Capability Mapping StV-3 Capability Phasing OV-E6c SHAPE BPMN((Instead SV-12 Service of OV-6c Provision StV-4 Operational Capability Event-Trace Dependencies Description) SV-3 Resource Interaction Matrix StV-5 SOV-4b Capability to Service Organization State Model Deployment Mapping SOV-4c SV-5 Function Service To Operational Interaction Activity Specification Traceability SV-8 Matrix Capability Configuration Managemnet SOV-5 Service SV-11 Functionality Physical Flow SV-E10b SHAPE Schema BPMN(Insteadof SV-10b Resource State Transition Description) SV-E10c SHAPE BPMN(Instead of Resource Event-Trace Description) SV-4 Functionality Description OV-3 Operational Information Exchange Matrix OV-E6a Shape BPMN (Instead of Operational Rules Modell) SOV-4a Service Constraints SV-10a Resource Constraints Specification SV-6 Systems Data Exchange Matrix SV-7 Resource Performance Actural Parameters Matrix SV-9 Technology & Skills Forecast TV-1 Standards Profile TV-2 Standards Forecast 34 17

18 Enterprise SOA 35 CIM PIM - PSM BPMN BPDM BMM EPC CIM Models Core -SHA PIM System Models Service Variability PIM4 WS-A PIM4 SWS PIM4 Agents P2P/Grid/ Components PIMs for different Architectural Styles WSDL, WSMO, OWL - S, JACK, JADE, JXTA, OGSA, J2EE, CORBA PSM Implementation Models J2EE, NetWeaver,.Net, Realization Technologies 36 18

19 CIM PIM PSM methods Information Service Process Rules Events Organization Goals NFA Total: 40 Total: 25 Total: 23 Total: 14 Total: 4 Total: 15 Total: 17 Total: 11 Sources: Sources: SCM, SM, ISE, ESIM, SM, SCM, SAE,SCM, SM, SM, SOMA, ISE, GERAM, EUP SAE, SM, SM, SMART, SCM, SM, ESOA, Cyc, SMART, SOMA, SMART, SOAD, ESOA, Cyc, SMART, SOMA, SOMA, ISE, SOMA, ISE, CIM DILIGENT, EOnto, MethOnto, ISE, ESOA, GERAM,ARIS, SOMA, ISE, ESOA, GERAM, EUP ISE, ESOA, GERAM,ARIS, ESOA, GERAM,ARIS, ESOA, GERAM NeOn, OTK, EUP COMET-S, GERAM,ARIS, EUP EUP, COMET-S TOVE, OGSOA EUP, COMET-S, GERAM,ARIS, OGSOA EUP, COMET-S Total: 1 Total: 1 Total: 1 CIM2PIM Sources: Sources: Sources: COMET-S COMET-S COMET-S Total: 10 Total: 19 Total: 21 Total: 7 Total: 1 Total: 6 Total: 1 Total: 10 Sources: Sources: OASIS Sources: Sources: SMART SCM, SM, SAE, SCM, SAE, SCM, SMART, ISE, SMART, ESOA SCM, SMART, PIM SMART, SOMA, ISE, ESOA, SMART, SOAD, SOMA, ISE, SMART, SOAD, SOMA, ISE, ESOA SOMA, ISE, ESOA, OASIS COMET-S, ESOA, COMET- ESOA, OASIS, OASIS S, OASIS, OGSOA OGSOA Total: 1 Total: 3 Total: 2 Total: 2 Total: 1 Total: 1 Total: 1 PIM2PSM Sources: Sources: ESOA, Sources: ESOA COMET-S COMET-S ESOA Total: 11 Total: 21 Total: 19 Total: 7 Total: 1 Total: 4 Total: 1 Total: 5 Sources: SM, Sources: SOAD Sources: SAE, Sources: SOAD Sources: SM, PSM SCM, SM, SOAD, SOMA, SAE, SCM, SM, SOAD, SOMA, SAE, SCM, SM, SOAD, SOMA, SOAD, SOMA, ISE, ESOA SM, SOAD SOMA, ESOA ISE, ESOA ISE, ESOA, ISE, ESOA COMET-S COMET-S 37 CIM PIM PSM methods in this INF5120 course Information Service Process Rules Organization Goals NFA CIM SM: Dictionary OSOA: semantic model collaboration diagram BPMN SM: rules OSOA: organisation model SM: Goals SM: Requirements manual CIM2PIM UML Class UML Activitiy PIM diagram OSOA diagrams, sequence diagrams, BPMN PIM2PS M Objecteering & MOFScript Objecteering & MOFScript Objecteering & MOFScript PSM Java and Web services (XML) Java and Web services (WSDL) Java and Web services (BPEL) 38 19

20 Core concept for BMM BMM Core Concepts BMM and GRC 40 Model Systems, 20

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

22 CIM-PIM-PSM Reference Matrix 43 Historikk (Service oriented architecture modeling language) OMG RFP September initial submissions June 2007 Merge process in 2008 and ferdigstilt desember adopteres av OMG i mars 2010 FTF chairs: Arne J. Berre, SINTEF og Jim Amsden, IBM

23 VDM Metamodel 45 Value Network - Notations 46 23

24 VDM Metamodel 47 INF5120 Modellbasert Systemutvikling Modelbased System development Lecture 6: EPF, SPEM Software Engineering Metamodels (Brian Elvesæter) Lecture 7: BPMN 2.0 Arne-Jørgen Berre 48 24