Conceptual Framework

Size: px

Start display at page:

Download "Conceptual Framework"

Britton Whitehead
5 years ago
Views:

1 ArchiMate in a Nutshell v11 Conceptual Framework Generic Meta Model / Framework / Meta Model Creative Commons Attribution-No Derivative Works Licence 2.0 Attribution: You may copy, distribute and display this copyrighted work only if you include this note at the start and end. No Derivative Works: You may copy, distribute, display only complete and verbatim copies of this work, not derivative works based upon it. For more information about the licence, see

2 Enterprise architecture To support, enable and improve business roles and processes that are repetitive and deterministic enough to be systematised and digitised. EA describes enterprises as systems. "Enterprise architecture...regards the enterprise as a system or system of systems." TOGAF 9.1 ArchiMate focuses on information-intensive organizations The organisation is regarded as a system of systems.

3 The enterprise as a system Enterprise and solution architects are concerned with: Operational systems cf. buildings, both already built and to be built Descriptions of systems architect's drawings, for detailed designers and builders to follow Contextual information business drivers, goals and plans; principles, time, cost and benefits; system stakeholders and their concerns.

4 So What kinds of system are we interested in? What is the architecture of a system? What elements appear in architecture descriptions?

5 What kinds of system? The buildings are human and computer activity systems. Dynamic systems whose interrelated components must cooperate in processes not simply connected in a passive structure. The principal heuristic innovation of the systems approach is what may be called reduction to dynamics as contrasted with reduction to components Laszlo and Krippner.

6 What is the architecture of a system? architecture system fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution. ISO Elements to be defined include not only components, but also the processes they execute use cases flow charts or service contracts.

7 What elements appear in architectural descriptions? Inside an activity system there is both structure (components) and behaviour (processes). Behavioural view Structural view External view Internal view Processes Components This principle underpins most architecture frameworks.

8 What elements appear in architectural descriptions? Inside an activity system there is both structure (components) and behaviour (processes). From the outside, the principle of encapsulation means the external view is an abstraction from internal components and processes. Behavioural view Structural view External view External view of processes External view of components Internal view Processes Components These principles underpin most architecture frameworks.

9 A system is encapsulated in an environment Environment External view Behavioural view System Events/ Services Structural view Interfaces Internal view Processes Components

10 5 kinds of system description element Environment Object Event/ Service Process System Interface Component External Internal Passive Structure Behavior Active Structure

11 5 system description entities as defines them Service: the external view of the process that responds to a singular event or service request Interface: a place or façade where clients can access services External Object: an item or structure that is used, moved or made by processes Object Event/ Service Process System Interface Component Internal Passive Structure Behavior Active Structure Process: a sequence of activities that responds to an event or meets a service request. Component: a subsystem that executes process steps. Copyright Ltd 2013

12 Natural progressions Realisation: the external view is implemented by the internal view. services encapsulate and are realised by behaviour elements (processes) interfaces encapsulate and are realised by active structure elements (components). Realisation Object Event/ Service System Interface Process Component Passive Structure Behavior Active Structure Construction: behaviour is assigned to structure. services are assigned to interfaces. active behaviour (processes) are assigned to active structure (components). Construction

13 The ArchiMate version of this generic meta model Process = behaviour element Component = active structure element System

14 Aside on subject-verb-object grammar ArchiMate s core concepts were inspired not by system theory but by natural language sentences subject = active structure element verb = behavior element object = passive structure. Note that one component can play the role of subject and object in different sentences (and in the same sentence).

15 Aside: further reading For formal yet natural language description of business rules, then try Semantics of Vocabulary and Rules (SBVR) a standard of the Object Management Group (OMG) part of their Model Driven Architecture (MDA). Perhaps also ORM? For an exploration of system theory and how it differs from systems thinking See Systems Theory for Architects at avancier.co.uk

The 5 entities as ArchiMate defines them Service: a unit of functionality that a system exposes to its environment, hides internal operations, provides a value; accessible through interfaces.

16 The 5 entities as ArchiMate defines them Service: a unit of functionality that a system exposes to its environment, hides internal operations, provides a value; accessible through interfaces. Interface: a point of access where services are made available to the environment, provides an external view on the service provider and hides its internal structure. Passive structure element: object on which behavior is performed. System External Internal Behavior element: a unit of activity performed by one or more active structure elements. Active structure element: an entity capable of performing behavior

17 Aside: on ArchiMate s 3rd dimension The ArchiMate Language Primer by Lankhorst et al. defines three dimensions of system description. behaviour --- structure. internal --- external, also individual --- collective. Behaviour Individual External Internal Collective Structure In practice, the individual/collective distinction can be blurred in ArchiMate diagrams.

18 ArchiMate in a Nutshell v11 Conceptual Framework Generic Meta Model / Framework / Meta Model Creative Commons Attribution-No Derivative Works Licence 2.0 Attribution: You may copy, distribute and display this copyrighted work only if you include this note at the start and end. No Derivative Works: You may copy, distribute, display only complete and verbatim copies of this work, not derivative works based upon it. For more information about the licence, see

EA domains EA is about the efficient & effective use of digital information systems by business roles & processes or the effective management & exploitation of information through IT as TOGAF puts it.

19 EA domains EA is about the efficient & effective use of digital information systems by business roles & processes or the effective management & exploitation of information through IT as TOGAF puts it. To facilitate understanding and change impact analysis, EA maintains an abstract description of business roles & processes & the information systems & technologies they use. That abstract description is what TOGAF means by the architecture. Applications Technologies

20 The ArchiMate Framework Maps 3 architecture dimensions to 3 architecture domains/layers

21 Mapping POLDAT entities to the ArchiMate Framework CSC s 6 dimensions of change Location Process Organisation strategy Data Application IT strategy Technology

22 Filling the gaps Just for fun Location Process Organisation Data Object Use Case Application Deployment Artifact Platform Service Technology

23 Mapping BCS entities to the ArchiMate Framework BCS ref. model features concepts typically found in EA frameworks Environment External Activity External Entity Service Function Organisation Process Role Actor Use Case UI Information Systems Data Entity Automated Service Logical Data Model Application Platform Service API Data Store Infrastructure Technology Technology Passive Structure Behaviour Active Structure

24 Mapping TOGAF entities to the ArchiMate Framework TOGAF makes much of separating logical components from physical components. That is, separating vendor-neutral architecture from vendor-specific solution choices. Environment Service Process Function Role Organisation Actor Information Systems Infrastructure Technology Data Entity IS Service Platform Service Logical App Logical Data Component Logical Technology Component Physical App Physical Data Component Physical Technology Component Passive Structure Behaviour Active Structure

Mapping ArchiMate entities to the ArchiMate Framework ArchiMate makes much of separating external from internal. That is, separating services from processes, and interfaces from components.

25 Mapping ArchiMate entities to the ArchiMate Framework ArchiMate makes much of separating external from internal. That is, separating services from processes, and interfaces from components. Environment Service Interface Object Process/Function Role Actor App Service App Interface Information Systems Data Object App Function App Component Infrastruct. Service Infrastruct. Interface Infrastructure Technology Artifact Infrastruct. Function Node Passive Structure Behaviour Active Structure

26 ArchiMate in a Nutshell v11 Conceptual Framework Generic Meta Model / Framework / Meta Model Creative Commons Attribution-No Derivative Works Licence 2.0 Attribution: You may copy, distribute and display this copyrighted work only if you include this note at the start and end. No Derivative Works: You may copy, distribute, display only complete and verbatim copies of this work, not derivative works based upon it. For more information about the licence, see

27 The heart of the ArchiMate v2 meta model - concepts Passive Structure Behavior Active Structure Object Process and Function are different concepts in BA Service Process Function Interface Role Actor Process known to App Architect Data Object App Service App Function App Interface App Component Applications Process unknown to Tech Architect Artifact Infrastructure Service Infrastructure Function Infrastructure Interface Node (inc. Sys Software & Device) Infrastructure Technology

ArchiMate s layer meta model Notice the generic meta model Copyright 2009-2012 The

ArchiMate s Technology (Infrastructure) layer meta model Notice the generic meta model Copyright

31 My reading of interactions and collaborations Interaction a transient cooperation between components or roles a process. Collaboration a persistent cooperation between components or roles or agreement to cooperate an association.

32 Architecture frameworks Methods are useful with all architecture frameworks that share similar domains and entities ArchiMate Language Framework BCS E&SA reference model Methods TOGAF The Open Group CSC s domains of change (POLDAT) IBM s view EA EA as Strategy MIT

33 ArchiMate in a Nutshell v11 Conceptual Framework Generic Meta Model / Framework / Meta Model Creative Commons Attribution-No Derivative Works Licence 2.0 Attribution: You may copy, distribute and display this copyrighted work only if you include this note at the start and end. No Derivative Works: You may copy, distribute, display only complete and verbatim copies of this work, not derivative works based upon it. For more information about the licence, see

Enterprise Architecture Modelling with ArchiMate 3 - Overview

Enterprise Architecture Modelling with ArchiMate 3 - Overview Knut Hinkelmann Reference The ArchiMate 3 specification is available at http://pubs.opengroup.org/architecture/archimate3-doc/ It is referenced