Harmonising two conceptual frameworks for EA

Transcription

1 Harmonising two conceptual frameworks for EA Mapping TOGAF to ArchiMate AKA Terminology Torture Including some slides from s training to BCS Enterprise and Solution Architecture Certificates Copyright Ltd, And three diagrams edited from ArchiMate standards, Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. The Open Group s general principle Standards should be based on executable specification. Specify a system by defining the behaviors it is required to perform, and their results. TOGAF applies this principle to the specification of business systems as well as IT systems. Portfolio System AutoXpress s AutoXpress AutoXpress s Fit tyres Check-up and oil change Full annual service Check brakes Repair brakes Check exhaust Replace exhaust Inspect battery Replace battery Align wheels Replace windscreen wipers Fit bulbs Replace shock absorbers Ltd

2 The unit of behavior - a service a required behavior or unit of work defined as a service requester sees it. a logical representation of a repeatable behavior with a specified result. A service contract hides how a system works. may be short (retrieve customer address) or long (deliver a package). The scope depends on what the requester wants and the resources available to the service performer. AutoXpress s Fit tyres Check-up and oil change Full annual service Check brakes Repair brakes Check exhaust Replace exhaust Inspect battery Replace battery Align wheels Replace windscreen wipers Fit bulbs Replace shock absorbers is realised by one or more components performing one or more processes. The unit of structure - a building block (or component) a subsystem or actor of any kind, including human and computer actors. may be coarse-grained or fine-grained. can realise one or more services, either on its own or in collaboration with others can play the client role of service requester and/or server role of service performer. requests a service by sending a message that identifies the service to be performed. (Less commonly, it pushes a service when triggered by a time event or system state change event.) Client Server & Client Server Ltd

3 Recursive architecture description Both building blocks and services are recursively composed System One building block perform many services One service may require many building blocks (be they nested or sequential). Building Block Building Block The general approach in TOGAF Baseline analysis abstracts performed services from building blocks Identify performed s Study Physical SBBs Target design starts from the required services Identify Goals and Objectives Identify Required s Map s to Logical ABBs Map Logical ABBs to Physical SBBs Define s Map s to Functions Map Functions to Units Data Define Data Entities Map Data Entities to Logical Data s Map Logical Data s to Physical ones Apps Define IS s Map s to Logical App s Map Logical App s to Physical ones Define s Map s to Logical s Map Logical Tech s to Physical ones Ltd

4 TOGAF s generic relation TOGAF 7 and 8 Required behaviors <are clustered and assigned to> Logical ABBs <are realised by> Physical SBBs Cap Gemini TOGAF 9 s <are clustered and assigned to> Logical s <are realised by> Physical s / Function catalog s Functions Units Role catalog + Actor/Role matrix Activities Roles Actors Application portfolio catalog IS s Logical Application s Physical Application s portfolio catalog s Logical s Physical s TOGAF 9.2 artifact types including diagram types to follow PRELIMINARY VISION REQUIREMENTS PLANNING Principles Catalog Driver/Goal/Objective Catalog Value Chain Diagram Model Diagram Stakeholder Catalog Solution Concept Diagram Footprint Diagram BUSINESS Requirements Catalog Requirements Traceability Matrix Project Context Diagram Benefits Diagram Capability view People view Process view data view Goal/Objective/ Diagram Contract Measure Catalog Functional Decomposition Diagram /Function Catalog Interaction Matrix Node Connectivity Diagram Decomposition Diagram Function/ Matrix Role Catalog /Role Catalog Actor/Role Matrix Location Catalog Process Catalog Use Case Diagram Process Flow Diagram Event Diagram Product Lifecycle Diagram Conceptual Data Diagram Data Entity/ Function Matrix /Information Dgrrm Capabilities Catalog Strategy/Capability Matrix Capability Map Map Capability/ Matrix Value Stream (Stages) Catalog Value Stream/Capability Matrix Value Stream Map DATA APPLICATIONS TECHNOLOGY IMPLEMENTATION Data Entity/Data Catalog Application/Data Matrix Logical Data Diagram Data Dissemination Diagram Data Security Diagram Data Migration Diagram Data Lifecycle Diagram Application Portfolio Catalog Interface Catalog Application/Func/Org/Role Matriices InformationExchange Matrix Application Communication Diagram Process Application Realization Diagram Application and User Locations Diagram Application Use Case Diagram Application Migration Diagram Portfolio Catalog Standards Catalog Application/ Matrix Environment and Locations Diagram Platform Decomposition Diagram Software Engineering Diagram Software Distribution Diagram Enteprise Manageability Diagram Processing Diagram Networked Computing Hardware Dgrm Communications Engineering Dgrm Ltd

5 A Architecture approach in TOGAF 8 and 9 architecture approach in TOGAF 8 Corresponding artifacts in TOGAF 9 1 Define organization structure and locations Decomposition Diagram, /Actor Catalog 2 Document business goals and objectives for each organizational unit Driver/Goal/Objective Catalog 3 Identify business functions Functional Decomposition Diagram 4 Define the services each enterprise unit performes, internally and externally 5 Define business processes, inc. measures and deliverables 6 Define business roles, inc. skills requirements. Role Catalog Goal/Objective/ Diagram /Function Catalog Interaction Matrix or Diagram Process Catalog Scenario, Process Flow Diagram 7 Define business data model Conceptual Data Diagram 8 Relate business functions to organizational units Function/ Matrix 1 Define organization structure and locations Organisation Decomposition Diagram + /Actor Catalog Ltd

6 2 Document business goals & objectives for each organizational unit Driver Driver/Goal/Objective catalog a cross-organizational reference... a definitive breakdown of drivers, goals, and objectives... to identify synergies across the organization Goal Objective Stimulate Decomposed into Met by Unit BMM Desired Result Mapping the BMM to TOGAF Means and End words in the Motivation Model from the OMG Direction Contents of Direction in TOGAF 9.2 Mission Vision Driver Mission Statement Vision Directive Desired Result Course of action Directive Desired Result Course of Action Goal Strategy Principle! Goal Strategy Policy Objective Tactic Policy! Objective Project Rule Rule! Architecture Requirement Work Package A business strategy document may include the rest of these elements Ltd

7 3 Identify and define business functions Functional Decomposition Diagram (logical organization structure) Strategic management functions Strategy Fiscal and accounting Risk and Compliance Performance Operational functions Products Marketing Sales care Product definition Market development Distribution channels service relations Product engineering Campaigning Sakes execution channel data Investment Assets Investment performance Banking Money Accounts Contracts life cycle s settlement Investment portfolio Asset inventory Cash flow Money market Contract admin. admin. Support functions HR Process Office Facility ITSM 4 Define the services (first identify them) Goal/Objective/ Diagram Ltd

8 4 Define the services each enterprise unit performes, internally and externally Map business services to logical business functions Document business service contracts in the Architecture Requirement Specification Driver Driver/Goal/Objective catalog Goal/Objective/ diagram /Function catalog Functional Decomposition diagram Function/ matrix Decomposition diagram Goal Objective Met by Function Stimulate Delivered by Unit Decomposed into Contract Measure catalog At step 4, diagram types used may include Node Connectivity Diagram (ADM phase B), or Viewpoint in ArchiMate 3 Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Ltd

9 5 Define business processes (first identify them) Use Case Diagram (Some prefer UML) ABC Limited Supplier Goods receipt Goods delivery Supply Report Settle payment Manager BACS Process Co-operation in ArchiMate 2.1 Realization in ArchiMate 3 Driver Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. At step 5, diagram types used may include Process flow diagram (measures might be in a service contract) (Some prefer BPMN) Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Ltd

10 At step 5, diagram types used may include Event diagram (measures might be in a service contract) Relations Handling Finance Submit Process Assess Pay Receive Money (Some prefer UML) Remaining Architecture Definition Steps 6 Define business roles, including skills requirements Roles are assigned to activities/steps in processes 7 Define business data model ArchiMate s data modelling symbology is very thin People draw 1 to many associations as aggregations Which either turns all associations into part of relationships Or stretches the concept of aggregation to vacuity Many prefer a data modelling notation standard 8 Relate business functions to organizational units in a matrix. Ltd

11 A Architecture artifact map for TOGAF 9.1 and 9.2 Driver/Goal/Objective catalog Goal/Objective/ diagram Driver Stimulate Goal Decomposed into Objective BMM Desired Result /Function catalog Functional Decomposition diagram Function/ matrix Decomposition diagram Or Package of Capability Function Unit Met by Delivered by Role Actor /Actor catalog Perform Contract Measure catalog Role catalog Interaction matrix Information Exchange matrix Node Connectivity diagram Actor/Role matrix Process Process catalog Process Flow diagram Event diagram An alternative Architecture approach Driver Goal Stimulate Decomposed into BMM Desired Result Objective Met by Strategy/Capability Map?? Delivered by Capability Map? Capability? Capability/ matrix? Capability? Role Realized by Perform Process Map? Unit Actor Value Stream Capability/ matrix? Value stream / Capability matrix? Value stream catalog Value stream map Ltd

12 Footprint Diagram Pictures the scope of the architecture project from phase B to F An applications architecture artifact map inc. Application Use Case Diagram Application/ Function Matrix Application/ Role Matrix IS Interface Catalog Application Interaction Matrix Application Communications Diagram Application Function Role Logical App Application Portfolio Catalog Application and User Locations Diagram Application Migration Diagram Unit Actor Process Physical App Application/ Matrix Process Application Realisation Diagram Ltd

13 Application Communication Diagram Serves arrows Flow arrows Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Process Application Realisation Diagram Relations Handling Finance Submit Process Assess Pay Receive Money (Some prefer UML) Ltd

14 Applications and User Locations Diagram location Laptop Salesman Drawing App Ordering App Printer PAN WAN LAN HQ location Product Management Order Management Application Use-Case Diagram ABC Limited Goods handling Supplier Record goods receipt Report monthly Manager Record goods delivery Settle payment BACS Driver (Some prefer UML) Ltd

15 Environment and Locations Diagram / Viewpoint in ArchiMate Stores (100+) Depots (5) Shop Floor Back Office Office Warehouse IBM 4680 IBM 4680 Windows XP Windows XP Windows XP Windows XP Handheld Store loop Switch Server Server Switch Server RF Unix Unix Unix Handheld IBM 4690 Cisco Cisco Private network (TCP/IP over ISDN) Cisco Appl. servers Server Switch Switch Some unreadable agency Unix IBM 4690 Windows XP Windows XP Windows XP IBM Mainframe Gateways Suppliers etc. architecture diagram varieties 1. Platform Decomposition Diagram 2. Software Distribution Diagram 3. Enterprise (Application) Manageability Diagram 4. Processing Diagram 5. Networked Computing/Hardware Diagram 6. Network and Communications Diagram Overlapping variations of the same thing (Some prefer UML, or Visio) Ltd

16 Project Context Diagram Could well resemble the Footprint Diagram Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Mapping ArchiMate to TOGAF? Realized by TOGAF Uses IS Realized by Create and use Data Entity Held in Realized by Process Application Logical App Data Logical Data Logical Tech Function Role Perform Maintain Unit Actor Physical App Physical Data Physical Tech ArchiMate App Data Object Function Role Process Application Application Function Data Object Data Object Node Function Actor Actor App Data Object Node Ltd

17 A possible solution design sequence Driver Stimulate Presuming the baseline organisation structure and functional decomposition are a given Driver/Goal/ Objective catalog Goal Decomposed into Objective Met by I/O Flow Produced & Consumed by Goal/Objective/ diagram Delivered by Create & use Data Entity Held in Logical Data Physical Data Process catalog Process Flow diagram Event diagram Process Performed by Enter & Retrieve Application I/O Flow (Message) IS Provided by Logical App Uses Physical App Role catalog Role Assigned to Unit Provided by Logical Tech Physical Tech Actor catalog Decomposition diagram Interaction matrix Read the associated paper for discussion of In TOGAF s and building blocks Architecture building blocks v solution building blocks Recursive architecture description The general approach and the generic relation In ArchiMate v Process Interface v Actor v Role Process v Function Structure v Behavior Data Object v Object Ltd