INF5120 Modellbasert Systemutvikling Modelbased System development

Transcription

1 INF5120 Modellbasert Systemutvikling Modelbased System development Lecture 14: Arne-Jørgen Berre or 1

2 INF Lecture plan (19/1): Introduction MDA principles, class models, EA, BAE, SAE, MDE 2 (26/1): BAE-1: BM, VDML, BMC/VPC, Strategyzer, Oblig 1&2 intro, establish groups Guest lecture, Prof. Peter Lindgren, Aarhus University, Sensing Business Model 3: (2/2): MDE-1 Method Engineering, Essence, Process/Practices for BE and SE Symphonical Guest lecture, Bjørn Haugland, CEO, Symphonical, The Symphonical platform 4 (9/2): BAE-2: Service Design AT ONE, Smaply, ExperienceFellow 5 (16/2): BAE-3: EA, BA, BPMN, VDML, Class/Term models- MagicDraw and Cameo Enterprise Guest lecture, Ragnhild Halvorsrud, SINTEF, Visual Service Design language 6 (23/2): BAE-4: Agile user stories and use cases Symphonical/MD&Cameo 7 (2/3): BAE-5: User experience and Interaction/UI Design Balsamiq and WebRatio installation 8 (9/3): SAE-1 IFML and Webratio and Mobile App development, Oblig 2 intro 9 (16/3): SAE-2 Domain/information modeling more IFML Server development, Oblig 1 delivery and presentations Guest lecture, Vidar Mortensen/Assulv Tønnesland, SunSense, Evje, Norway 10(23/3): MDE-2 Metamodels, EMF, Oblig 2 discussion and Oblig 3 intro EASTER 11(13/4): MDE-3 Graphical Editors Sirius - Oblig 2 issues and Oblig 3 Sirius demo 12(20/4): MDE-4 Model transformations 13(27/4): SAE-3 Service and system architecture modeling, Patterns, Non functional requirements - Oblig 2 delivery and presentations 14(4/5): SAE-4: EA modeling = BA + SA - Oblig 3 issues 15(11/5): MDE-5: DSL lexical example ThingML, future MDE - Oblig 3 delivery and presentations Guest lecture, Franck Fleurey, SINTEF, ThingML DSL language 16(18/5): Conclusion preparation for the exam with discussion of earlier exam sets 2

3 INF Obligs (19/1): Introduction Presentation of teaching assistants 2 (26/1): Strategyzer demo, Oblig 1&2 intro, establish groups 3: (2/2): Symphonical demo, Oblig 1 SenseIT text, finalise groups 4 (9/2): Smaply demo, Oblig 1 App demo, Group: Strategyzer BMC/VPC, Symphonical plan 5 (16/2): MagicDraw and Cameo Enterprise demo, Group: Smaply 6 (23/2): User stories/use cases templates demo 7 (2/3): Symphonical/MD&Cameo, Group: MagicDraw BPMN process, UML class diagram Group: User stories/use cases templates' 8 (9/3): IFML and Webratio and Mobile App development demo, Oblig 2 intro, Group: Balsamiq 9 (16/3): Webratio II, Oblig 1 delivery discussion and presentations 10(23/3): EMF and Sirius demo EASTER 11(13/4): Sirius demo 12(20/4): Oblig 2 support 13(27/4): Oblig 2 delivery and presentations 14(4/5): Oblig 3 issues and support 15(11/5): Oblig 3 delivery and presentations 16(18/5): Earlier exams 3

4 Content Oblig 2 (comments) and 3 (questions) Enterprise Architecture - MagicDraw ISO RM/ODP UPDM for MODAF/DODAF/(NAF) EuroControl SJU TOGAF ArchiMate og Archi INF5120: EA = BA (BMC, SD) + SA (IFML, UML) Data Model Patterns Ontologies Linked Data RDF/OWL SSN Semantic Sensor Network Ontology 4

5 MagicDraw Cameo Enterprise Architecture 5

6 6

7 7

8 8

9 Zachman Framework Row 1 Scope External Requirements and Drivers Business Function Modeling Row 2 Enterprise Model Business Process Models Row 3 System Model Logical Models Requirements Definition Row 4 Technology Model Physical Models Solution Definition and Development Row 5 As Built As Built Deployment Row 6 Functioning Enterprise Functioning Enterprise Evaluation Contextual Conceptual Logical Physical As Built Functioning What What How How Where Where Who Who When When Why Why Contextual Conceptual Logical Physical As Built Functioning 9

10 Zachman Framework for Enterprise Architecture (IBM, 1987) 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 ENTERPRISE MODEL (CONCEPTU AL) Entity = Class of Business Thing Semantic Model Function = Class of Business Process Business Process Model Node = Major Business Locations Business Logistics System People = Major Organizations Work Flow Model Time = Major Business Event Master Schedule Ends/Means = Major Business Goals Business Plan Planner ENTERPRISE MODEL (CONCEPTU AL) Owner SYSTEM MODEL (LOGICAL) Ent = Business Entity Proc = Business Process Rel = Business Relationship I/O = Business Resources Logical Data Application Model Architecture Node = Business Location Link = Business Linkage Distributed System Architecture People = Organization Unit Time = Business Event Work = Work Product Cycle = Business Cycle Human Interface Processing Architecture Structure End = Business Objectiv e Means = Business Strategy Business Rule Model Owner SYSTEM MODEL (LOGICAL) Designer TECHNOLOGY MODEL (PHYSICAL) Ent = Data Entity Rel = Data Relationship Physical Data Model Proc = Application Function Node = IS Function I/O = User Views Link = Line Characteristics System Technology Design Architecture People = Role Work = Deliverable Presentation Architecture Time = System Event Cycle = Processing Cycle Control Structure End = Structural Assertion Means = Action Assertion Rule Design Designer TECHNOLOGY MODEL (PHYSICAL) Builder Ent = Segment/Table Rel = Pointer/Key DETAILED Data REPRESENTATIONS Definition (OUT-OF-CONTEXT) Proc = Computer Function I/O = Data Elements/Sets Program Node = Hardware/Softw are People = User Link = Line Specifications Work = Screen Format Netw ork Security Architecture Architecture Time = Ex ecute Cycle = Component Cycle Timing Definition End = Condition Means = Action Rule Design Builder DETAILED REPRESENTATIONS (OUT-OF-CONTEXT) Sub-Contractor FUNCTIONING ENTERPRISE Ent = Field Rel = Address Data Proc = Language Statement Node = Addresses I/O = Control Block Link = Protocols Function Netw ork People = Identity Work = Job Organization Time = Interrupt Cycle = Machine Cycle Schedule End = Sub-Condition Means = Step Strategy Sub-Contractor FUNCTIONING ENTERPRISE Ent = Rel = DATA What Proc = I/O = FUNCTION How Node = Link = NETWORK Where People = Work = PEOPLE Who Time = Cycle = TIME When End = Means = MOTIVATION Why 10

11 Content EA and the Zachman Framework Architectural Frameworks - (IEEE/ 1471/ISO 42010, ADL, UML 2.x, TOGAF, UPDM UPDM (DODAF/MODAF, NAF), NIEM TOGAF Service modeling and Service oriented views Tool support, Metamodels and UML profiles No Magic, Magic Draw 11

12 Many Architectural Frameworks. ARIS ZACHMAN GERAM EKA - POPS EN/ISO Athena OEA NIST 12

13 TOGAF 9 (The Open Group) 13

14 14

15 ISO RM/ODP (ISO 10746)

16 Why and When: Historical Development of AF s. MODAF Meta-Model (M3) expressed using UML Notation NAF v NAF v DNDAF v C4ISR Architectur e Framework v C4ISR Architectur e 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

17 Towards a Unified Architecture Framework 17

18 Three Views in DOD Architecture Framework and C4ISR-AF 18

19 DODAF viewpoints 19

20 EAEA European Air Traffic Management Enterprise Architecture 20

21 IEEE 1471, ISO

22 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 Business (Concepts) Semantic Model ODM, IMM (CWM) Business Process Model BPMN, CMPM Business Logistics System BPMN, CMPM Workflow Model OSM, BPMN, CMPM Master Schedule BPMN, CMPM, DTFV Business Plan SBVR System (Logic) Logical Data Model ODM, IMM (CWM), UML Application Architecture SoaML, UML Distributed System Architecture SoaML, UML Human Interface Architecture BPMN, CMPM Process Structure BPMN, CMPM, DTFV Business Rule Model SBVR Technology (Physics) Physical Data Model IMM (CWM), UML System Design SoaML, UML Technology Architecture SoaML, UML Presentation Architecture Control Structure BPMN, CMPM, DTFV Rule Design SBVR Component (Assemblies) Data Definition IMM (CWM), UML Program UML Network Architecture UML Security Architecture Timing Definition DTFV Rule Definition SBVR Operation (Instances) Data Function Network Organization Schedule Strategy 22

23 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 Business (Concepts) System (Logic) Semantic Model ODM Logical Data Model Business Process Model Application Architecture Business Logistics System Distributed System Architecture BPMN CMPM Workflow Model Human Interface Architecture Master Schedule Process Structure Business Plan SBVR Business Rule Model Technology (Physics) IMM (CWM) Physical Data Model SoaML System Design UML Technology Architecture Presentation Architecture Control Structure DTFV Rule Design Component (Assemblies) Data Definition Program Network Architecture Security Architecture Timing Definition Rule Definition Operation (Instances) Data Function Network Organization Schedule Strategy 23

24 UPDM coverage Data (What) Function (How) Network (Where) People (Who) Time (When) Motivation (Why) Scope (Contexts) Business (Concepts) System (Logic) BPMN UPDM SoaML Technology (Physics) Component (Assemblies) Operation (Instances) 24

25 ModelDriven Architecture (MDA,Oslo) Interoperability Architecture (MDI) Model Based Systems Engineering and Interoperability Business Architecture (SysML Context + BPMN 2.0/BMM) BMM BPMN VDM CaseMgmt OSM SBVR Enterprise Architecture (EA) for Systems of Systems (UPDM) System & IT Service oriented Architecture (UML&SysML/SoaML) UML 2.0 SoaML SysML

26 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.

27 External References Transformations UPDM: UML Profile for DoDAF and MODAF Context Stakeholders US DoD OMG UK MOD NATO Canada/Australia OMG, INCOSE 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 SoaML, BMM, SBVr Extensions Products -- Reports -- Simulations DoDAF 2.0 Ontology CADM AP233 XMI IDEF UML SysML BPMN SoaML BMM

28 UPDM - Unified Model for DODAF and MODAF 28

29 UPDM 29

30 30

31 31

32 Enterprise Architecture Modeling with UPDM

33 Introduction Enterprise Architecture modeling No rocket science! It's a standard! UPDM: Unified Profile for MODAF and DoDAF

34 What is Enterprise Architecture?

35 Enterprise Architecture Business, partners, customers Application ecosystem System of system architecture The world Not: application or device

36 UML EA Framework Semantic classification Extra rules for construction Additional data Traceability between views

37 UPDM Unified Profile for DoDAF and MODAF (UPDM) Developed by OMG with DoD support Created by multiple vendors, governments, customers Implements architecture for DoD, MOD, and others

38 UPDM 2.0 Standard Approved by the OMG September, 2011 with DoD/MOD support Implements DoDAF 2.0 guidance and traced to DM2 metamodel as a UML extension Submitted to DISR as Emerging September, 2011 (in registry 14 November 2011) Beta from existing UPDM vendors UPDM 1.0 to 2.0 conversion available now

39 Advantages of UPDM Leverages existing UML tools and capabilities Automated completeness/correctness of models Supported by multiple vendors in consistent form Customizable via standard-based methods/interoperability Supports executable architecture via executable UML

40 Structure

41 Simple Example Two things (very simple model) Presentation not in build order Key elements of UPDM used

42 High Level Operational Concept Elevator Speech of the architecture Summarizes the key concepts of the architecture Picture, not a model Usually one diagram per project, but there may be many if required. HLOC can be composite diagram

43 OV-1 Thing Concept

44 Thing HLOC

45 Operational Resource Flow (OV-2) Documents logical view of performers and logical data interactions Summarizes the architecture's business viewpoint Business, not the implementation of the business Also used to build OV-3 (Operational Exchange Matrix) and others

46 Thing World

47 A Sign of Things to Come Key concept: Integrated model Not just pretty pictures Trace to other concepts Show what you need to communicate Goal: Executable

48 More Things

49 Whole/Part Hierarchy Composite can show detailed communication paths Further details added via ports Same thing as Internal Block Diagram

50 Part Design Method

51 Operational Exchanges

52 The World

53 Operational Resource Flow Matrix (OV-3) Report of operational exchanges Business-level Interface Exchange Requirement (IER) Performance and Information Assurance parameters Shows who, what, how

54 OV-3 Operational Resource Flow Matrix

55 All Exchanges

56 Organization Chart (OV-4) Organization Structure Roles in organization Example or actual organizations Part of the system architecture

57 OV-4 Organizational Chart Typical

58 Operational Activity Decomposition Tree Hierarchy of Operational Activities Relationship of activities to sub-activities Reuse of activities Related resources

59 Decomposition of Activity

60 Other Information

61 Operational Activity Flow Behavior definition Use of other activities (calls) Logic/constraints of behavior Swimlanes for orchestration across performers (see Interaction Overview)

62 Send

63 Receive

64 Interaction Overview

65 OV-5b Overview

66 OV-6a Operational Rules Constraints of the architecture What the architecture must do UML Constrains used throughout the architecture Includes agreements, guidance, policy etc.

67 OV-6a Operational Rules

68 OV-6b Operational State Valid states of performers Owned by the subject performer UML State machine

69 Thing Two

70 OV-6c Operational Event Trace Validates operational use of architecture Roles are instances of performers Can use methods on performers for further detail Flows can be displayed from OV-2 Usually owned by a contextual performer

71 Thing World

72 Capability Related

73 CV-3 Capability Phasing

74 CV-4 Capability Dependencies

75 CV-6 Capability to Operational Activity Mapping

76 Systems Interface Description Shows how systems communicate Can include humans and organizations Physical manifestation of the Operational Resource Flow

77 Widgets

78 Implementation Matrix

79 SV-2 Widget Network

80 SV-3 System to System Matrix

81 SV-4a

82 System Overview

83 SV-5a Operational Activity to System Funtion Traceability Matrix

84 System Resource Matrix

85 SV-7 Typical Measures

86 SV-8 Evoloution of Widgets

87 Services View

88 Service Context

89 UPDM IN PRACTICAL USE Relevant approach for Enterprise Architecture Agile: Iterative model development Accepted and promoted by the DoD Reporting and traceability Integrated architecture and development Useful tool for capturing customer requirements

90 OV-1a: Operational Context Graphic OV-1a [High Level Operational Concept] Maritime Rescue control Rescue Helo : Aircraft trackinfo Yacht : Boat assistance trackinfo distresssignal Monitor Unit : Monitor Rescue Boat : Boat Naval Ship : Boat trackinfo control control C2 Center : Control Center

91 OV-1: Operational Context Graphic

92 OV-2 Operational Nodes OV-2 [Node] Search and Rescue (With Ports) TCN «PerformerRole» SN : Search POS WO : warningorder SN «PerformerRole» PoS : Place of Safety SAC RN PID Tsk : tasking Ctrl : control Stat : status «PerformerRole» RN : Rescue SAC Tsk : tasking SN DS2 : distresssignal PID TCN Ctrl : control DS3 : distresssignal RN SN1 «PerformerRole» PiD : Person in Distress SN2 DS1 : distresssignal SN RN RN PID «PerformerRole» Rqst : request SAR AC : SAR Asset Control TCN SAC «PerformerRole» TC2N : Tactical C2 MN TI : trackinfo TCN «PerformerRole» MN : Monitoring SN

93 OV-5 Activity Diagram OV-5 [Architectural Description] Operational Activities «Activity(Operational)» Search «ActivityPerformedByPerformer» «StandardOperationalActivity» Find Victim «ActivityPerformedByPerformer» «Performer» «block» Search «ActivityPerformedByPerformer» «Activity(Operational)» Receive Distress Signal «Activity(Operational)» Send Warning Order «ActivityPerformedByPerformer» «ActivityPerformedByPerformer» «StandardOperationalActivity» Monitor Health «Activity(Operational)» Rescue «StandardOperationalActivity» Recover Victim «ActivityPerformedByPerformer» «ActivityPerformedByPerformer» «ActivityPerformedByPerformer» «Performer» «block» Rescue «Activity(Operational)» Receive Distress Signal «ActivityPerformedByPerformer» «StandardOperationalActivity» Provide Medical Assistance

94 OV-5 Activity Diagram

95 SV-1: Resource Interaction Specification SV-1 [System] Maritime Rescue Unit v1 «SystemRole» MR Boat : Boat «DataExchange» «ItemFlow» BI : boatinstruction «SystemRole» MRT : Maritime Rescue Team «OrganizationRole» Driver : MRT Boat Driver «SystemRole» Beacon : Lighting Device Mon «SystemRole» Radio : Communication Device «SystemRole» Life Preserver : Life Saving Device «DataExchange» «ItemFlow» BCI : beaconinstruction Comm «DataExchange» «ItemFlow» RI : radioinstruction «DataExchange» «ItemFlow» LPI : lifepreserverinstruction «OrganizationRole» Searcher : MRT Searcher Med «OrganizationRole» Radio Operator : MRT Communicator «OrganizationRole» Rescue Swimmer : MRT Swimmer «SystemRole» MR Aircraft : Aircraft Air «DataExchange» «ItemFlow» AI : aircraftinstruction «OrganizationRole» Pilot : MRT Helicopter Pilot

96 SV-2: Resource Interaction Specification SV-2 [System] Maritime Rescue Architecture v1 «SystemRole» Rescue Unit : Maritime Rescue Unit v1 Src Rsc DS : distresssignal «SystemRole» MR Boat : Boat «SystemRole» Yacht : Boat Src Rsc «MaterielRole» dsout Distress Beacon : Lighting Device DS : distresssignal dsin «MaterielRole» Monitor : ESM System «SystemRole» MR Aircraft : Aircraft trkin TRK2 : track dsin «MaterielRole» Monitor : ESM System TRK1 : track trkin RI1 : radioinstruction transmitter receiver «MaterielRole» Radio : Communication Device RI2 : radioinstruction «MaterielRole» Radio : Communication Device trkout «MaterielRole» Digital Service : Link 16 TD1 : TDM tdmreceiver tdmtransmitter TD2 : TDM trkout «MaterielRole» Digital Service : Link 16 transmitter receiver tdmtransmitter tdmreceiver

97 SysML Example: Requirements Traceability

98 Associated Analysis Tools

99 Related Elements Traceability Matrix Dependency Matrix Related elements display Show relationships Show ports Show internal structure

100 TOGAF 9 (The Open Group) 100

101 Open Group ADM 101

102 102

103 Building block evolution 103

104 Service categories 104

105 ArchiMate 105

106 Archi 106

107 107

108 Business Product View 108

109 ArchiMate Authors : eschoolink Group - ITNLU

110 Contents 1. What s ArchiMate? 2. Why ArchiMate? 3. Main Benefits of ArchiMate 4. Layers of ArchiMate 5. ArchiMate vs UML 6. Notations of ArchiMate 7. Demo

111 What is ArchiMate? ArchiMate is a modelling technique ("language") for describing enterprise architectures. It presents a clear set of concepts within and relationships between architecture domains, and offers a simple and uniform structure for describing the contents of these domains. ArchiMate distinguishes itself from other languages such as Unified Modeling Language (UML) and Business Process Modeling Notation (BPMN) by its well defined metamodel, and wider enterprise modelling scope.

112 What is ArchiMate? ArchiMate offers a common language for describing the construction and operation of business processes, organizational structures, information flows, IT systems, and technical infrastructure. This insight helps the different stakeholders to design, assess, and communicate the consequences of decisions and changes within and between these business domains.

113 What is ArchiMate? An architecture framework is used to structure the concepts and relationships of the ArchiMate language It divides the enterprise architecture in to a business, application and technology layer. In each layer, three aspects are considered: active elements that exhibit behavior (e.g. Process and Function), an internal structure and elements that define use or communicate information.

114

115 Why ArchiMate? Enterprise architecture is an important instrument to address this company-wide integration. It is a coherent whole of principles, methods and models that are used in the design and realization of the enterprise's organizational structure, business processes, information systems, and IT infrastructure.

116 Why ArchiMate? A good architecture practice enables an organization to align business and IT operations with its strategy, quickly respond to changes in the environment, and make optimal use of technological opportunities. The development and maintenance of architectures will lead to efficiency, cost reduction and flexibility.

117 Why ArchiMate? Within companies various domain architectures can be found, like organization, business process, application, information, and technical architectures. Each architecture domain has its own concepts for the modelling and visualization of its internal coherence. These specific models and visualizations simplify communication, discussion and analysis within the domain

118 Why ArchiMate? However, the relations between the concepts in these different domains are in many cases unclear. Moreover, these domains often partially overlap but use different notions to express the same ideas, sometimes even with-out the people involved knowing this. The resulting ambiguities and confusion stand in the way of the flexibly and efficiently operating organizations we envisage.

119 Why ArchiMate? ArchiMate wants to do away with these ambiguities. It presents a unified way of modelling enterprise architectures, integrating the various domains and describing them in an easily readable way ArchiMate is of course not an isolated development. The relationships with existing methods and techniques, like modelling languages such as UML and BPMN, and methods and frameworks like TOGAF and Zachman, are well-described.

120 Main Benefits of ArchiMate 1. It is an international, vendor-independent standard of The Open Group, liberating you from the lock-in of vendor-specific tools and frameworks. There is active support from the ArchiMate Forum of The Open Group. 2. Its well-founded concepts and models provide precision. It helps you get away from the 'fuzzy pictures' image of architecture. 3. It is a lean and simple language. It contains just enough concepts for modeling enterprise architecture and is not bloated to include everything possible. Its uniform structure makes it easy to learn and apply.

121 Main Benefits of ArchiMate 4. It has clear links to existing approaches for specific architecture areas such as software or business processes. Several concepts in ArchiMate have deliberately been borrowed from other languages such as UML or BPMN, to provide an easy bridge. 5. It does not prescribe a way of working, but it is easily combined with existing methods such as TOGAF. 6. It has been tried and tested by many different user organizations and is supported by numerous consultancies and software tools.

122 Layers A layered view provides a natural way to look at service-oriented models. The higher layers use services that are provided by the lower layers. ArchiMate distinguishes three main layers: The Business layer offers products and services to external customers, which are realized in the organization by business processes performed by business actors and roles. The Application layer supports the business layer with application services which are realized by (software) application components. The Technology layer offers infrastructural services (e.g., processing, storage and communication services) needed to run applications, realized by computer and communication hardware and system software.

123 Layers

124 Layers, domains

125 Layers, domains

126 Overview of the ArchiMate concepts and main relationships.

127 ArchiMate vs UML ArchiMate ArchiMate was created to model the architecture of an enterprise (all of the systems in an organization). ArchiMate models the business, information system (application and data), and technology architectures of the environment, including how these architectures are inter-related. UML UML still functions best as a way to document the architecture of a single system UML provides 13 diagram types, providing flexibility to describe many different types of systems.

128 ArchiMate vs UML Archimate started with an understanding that these problems relate to one another; that the entire complex and difficult business of understanding IT requires a rich inter-relationship of completely different domains, from business motivation to business process to managed services to systems to infrastructure. Thus Archimate goes where UML doesn t: it defines a metamodel that allows these relationships to be constructed, and constrained, and communicated. The constraints allow analysis, traceability, governance, and consistency. UML is unconstrained between model types. Archimate is not.

129 Notations Every concept and relation should have a precise graphical notation, with a sufficient resemblance the standard ArchiMate notation. The notation in the Visio stencils can be used as a guideline Optionally, multiple notations may exist for a single concept. It should be possible to denote composition, aggregation and assignment both with their line notation and with nesting.

130 Relations The following relation types should be supported: Structural relations: composition* aggregation assignment used by realisation access association Dynamic relations: triggering flow Other relations: grouping junction specialisation*

131 Notations

132 Notations & Relations

133 Demo

134 Demo

135 Demo

136 Demo

137 Demo

138

139

140 Observations and Measurements 140

141 Observations and Measurements ISO

142 The basic O&M observation event concepts 142

143 143

144 W3C Semantic Sensor Network Ontology W3C SSN-XG ontology SSN-XG annotations What it measures makes observations of this type units SSN-XG ontologies where it is

145 O&M vs SSN 145