Useful EAM-Standards and Best-Practice Frameworks

Transcription

1 Useful EAM-Standards and Best-Practice Frameworks , Prof. Dr. Florian Matthes Software Engineering für betriebliche Informationssysteme (sebis) Fakultät für Informatik Technische Universität München wwwmatthes.in.tum.de

2 Outline 1. Useful EAM-Standards and Best-Practice Frameworks Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 2

3 Enterprise architecture frameworks have a long history. CIMOSA 1984 PERA 1989 GRAI/GIM ARIS 1991 GERAM 1994 GERAM CIMOSA 1999 PERA 2001 Legend: superseeded by influenced by Start of development Intermediate version ARIS Current version No further development JTA JTA TAFIM TAFIM TAFIM TAFIM 2000 DoD EA TRM C4ISR C4ISR DoDAF DoDAF DoDAF TOGAF TOGAF TOGAF TOGAF TISAF TEAF MODAF 2005 MODAF MODAF EAP 1992 EAP 1996 FEAF FEA NIST EA 1989 NC3SAF 2000 NAF NAF Zachmann 1987 Zachmann 1992 Zachmann E2AF 2003 E2AF IAF 1993 IAF IAF IAF v IAF sebis EAMPC 2008 sebis BEAMS 2010 sebis EAMPC Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 3

4 Enterprise architecture frameworks have a long history. Several frameworks for the Enterprise Architecture (EA Frameworks) have been developed over time Their level of detail differs strongly Zachmann - 1 page TOGAF (Version 9 "Enterprise Edition") pages Generalized Enterprise Reference Architecture and Methodology (GERAM) ISO Norm Guidelines for creating frameworks (As of today) no well-accepted reference DoDAF (Department of Defense) and NAF (Nato Architecture Framework) are binding for IT in the military domain ARIS book of 1991 vs. ARIS method manual of the ARIS-Platform of Mainly relevant in DACH Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 4

5 The Zachman Framework for Enterprise Architecture L e v e l o f D e t a i l Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 5

6 Zachmann: Analogy to building construction Building construction Zachman, John A. (1987): A framework for information systems architecture. In: IBM Systems Journal 26 (3), p Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 6

7 Zachman: Different models depending on the stakeholder Bubble charts Basic concepts for building Gross sizing, shape, spatial relationships Architect/owner mutual understanding Initiate project Contractor s plans Final building as seen by the builder Architect s plans constrained by laws of nature and available technology How to build it description Directs construction activities Architect s drawings Final building as seen by the owner Floor plans, cutaways, pictures Architect/owner agreement on building Establish contract Architect s plans Final building as seen by the designer Translation of owner s view into a product Detailed drawings 16 categories Basis for negotiation with general contractor Shop plans Subcontractor s design of a part/section Detailed stand-alone model Specification of what is to be constructed Pattern Building Physical building Zachman, John A. (1987): A framework for information systems architecture. In: IBM Systems Journal 26 (3), p Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 7

8 Zachman: Framework Levels Scope description (ballpark view) Model of the business (owner s view) Model of the information system (designer s view) Technology model (builder s view) Detailed description (out-of-context view) 3 perspectives Data description Process description Network description Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 8

9 Zachman: Framework Zachman Framework started in 1987 as A framework for information systems architecture! with 5 levels and 3 perspectives In 1992 Zachman and Sowa extended the framework with 3 new perspectives Persons (Who?) Time (When?) Motivation (Why?) Added a meta-model for the owner s, designer s und builder s level Defined 7 rules for the concretion of the framework Zachman, J. A. (1987): A framework for information systems architecture. In: IBM Systems Journal 26 (3), p Zachman, J. A. and Sowa, J. F. (1992): Extending and formalizing the framework for information systems architecture. In: IBM Systems Journal 31 (3), p Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 9

10 Quasar Enterprise: Macro-structure of the Integrated Architecture Framework (IAF) (1) The basic structure of CapGemini can be divided into two dimensions Architecture aspects: Different architectures of an enterprise Architecture layers: contextual, conceptual, logical und physical layer of each architecture aspect Contextual Why? Security Architecture Governance Architecture Conceptual What? Logical How? Physical With What? Business Architecture Information Architecture Information Systems Architecture Technology Infrastructure Architecture Macro-structure of the Integrated Architecture Framework (IAF) Engels, G.; Hess, A.; Humm, B.; Juwig, O. (2008): Quasar Enterprise, d-punkt Verlag Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 10

11 Quasar Enterprise: Macro-structure of the Integrated Architecture Framework (IAF) (2) Business architecture Structures the business processes and business services in order to match the business goals and to model the organization of the enterprise Information architecture Structures the information required in the business architecture Information systems architecture Structures the application landscape from a business perspective Technology infrastructure architecture Structures the used technical platforms and system software components Engels, G.; Hess, A.; Humm, B.; Juwig, O. (2008): Quasar Enterprise, d-punkt Verlag Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 11

12 Creation of a regulation framework (1) Creation of a regulating framework for questions, which should be addressed in the context of an enterprise architecture Everything starts with a clear separation between business and IT Business IT Engels, G.; Hess, A.; Humm, B.; Juwig, O. (2008): Quasar Enterprise, d-punkt Verlag Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 12

13 Creation of a regulation framework (2) Afterward it is important to distinguish between requirements and implementation Business IT Require-- ments Business strategy IT strategy Implementation Business architecture (Business process,, Business services, Business objects, organizations, etc.) Architecture of the application landscape Engels, G.; Hess, A.; Humm, B.; Juwig, O. (2008): Quasar Enterprise, d-punkt Verlag Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 13

14 Creation of a regulation framework (3) Business strategy, quality criteria and business architecture are driving the design of the application landscape Business IT Require- ments Business strategy IT strategy Business architecture Implementation (Business processes, Business services, Business objects, Organisation, etc.) Architecture of the application landscape Engels, G.; Hess, A.; Humm, B.; Juwig, O. (2008): Quasar Enterprise, d-punkt Verlag Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 14

15 Map of Quasar Enterprise Creation of an unique view on the business architecture. On the part of the IT, the IAF architecture aspects and -layers are respected Business Information Systems (IS) IT Technical Infrastructure (TI) Contextual (Why?) Conceptual (What?) Logical (How?) Physical (With What?) Business strategy Business architecture Business architecture (business services, business processes, business objects, organisation etc.) Ideal application landscape Domains and (application) services Logical AL components and interfacesphysische Physical AL components and interfacesphysische IT strategy Integration Technical services Logical application and integration platforms Physical application and integration platforms Integration platform As-is To-be IDEAL Evolution Engels, G.; Hess, A.; Humm, B.; Juwig, O. (2008): Quasar Enterprise, d-punkt Verlag Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 15

16 TOGAF 9: Scope & goals Scope TOGAF emphasizes business goals as architecture drivers, and provides a repository of best practices, including: TOGAF Architecture Development Method (ADM) ADM Guidelines & Techniques TOGAF Architecture Content Framework Enterprise Continuum TOGAF Reference Models TOGAF Capability Framework Long-term goals An industry standard, generic enterprise architecture method..usable on its own or in conjunction with frameworks having products relevant/specific to particular sectors. Several frameworks are directly referenced: -Zachman, Spewak, DoD Framework, FEAF, TEAF, Almost complete focus on artefacts, not method TOGAF and. (not TOGAF or.) Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 16

17 TOGAF as abusiness Transformation Framework Business strategy Capability Design options Business model & capabilities Capability Capability Increment Capability Increment Planning, Monitoring, Controlling Project- Portfolio People Dimension Process Dimension Material Dimension Individual Training Collective Training Professional Development Concepts Business Processes Information Management Infrastructure Information Technology Equipment Matthes Useful EAM-Standards and Best-Practice Frameworks TOGAF is a trademark of The Open Group sebis 17 17

18 TOGAF as a Business Transformation Framework The current version 9.1 of TOGAF provides a basis for developing an organizationspecific Business Transformation Framework. Needs of the business shape non-architectural aspects of business operation TOGAF Capability Framework Informs the size, structure and culture of the capability Effective operations of the Architecture Capability ensures realization of the Business Vision Architecture Capability Framework (Part VII) Sets targets, KPIs, plans and budgets for architecture roles Business Capability drives the need for Architecture Capability Maturity The Architecture Capability operates a method Business Vision and Drivers Business need feed into the method, identifying problems to be addressed The method refines understanding of business need Architecture Development Method (Part II) ADM Guidelines and Techniques (Part III) The method delivers new business solutions Business Capabilities The method produces content to be stored in the Repository, classified according to the Enterprise Continuum Architecture Content Framework (Part IV) TOGAF ADM & Content Framework The Enterprise Continuum and Repository inform the business of current state Enterprise Continuum and Tools (Part V) TOGAF Reference Models (Part VI) Operational changes update the Enterprise Continuum and Repository TOGAF Enterprise Continuum Tools Learning from business operation creates new business need Matthes Useful EAM-Standards and Best-Practice Frameworks TOGAF is a trademark of The Open Group sebis 18 18

19 TOGAF core elements of version 9.1 (1) The structure of TOGAF 9.1 is organized along the structure and content of an Enterprise Architecture Capability. Part I: Introduction Introduction of the core concepts of enterprise architecture and in particular the TOGAF approach. Includes definitions and release notes with essential changes to previous TOGAF versions. Part II: Architecture Development Method (ADM) A Architecture Prelim H Vision Framework Architecture B and Principles Change Business Management Architecture G C Implementation Requirements Information System Governance Architectures F D Migration Technology Planning Architectures E Opportunities and Solutions 1 The core of TOGAF describes the TOGAF Architecture Development Method (ADM) a phase-oriented approach for developing an enterprise architecture. Part III: ADM Guidelines and Techniques This collection includes several manuals and methods, supporting the implementation of TOGAF and the TOGAF ADM. Part IV: Architecture Content Framework Architecture Principles, Vision and Requirements Preliminary Architecture Vision Business Principles, Architecture Principles Business Strategy Technology Strategy Architecture Vision Stakeholders Objectives and Drivers Architecture Requirements Requirements Constraints Assumptions Gaps Business Architecture Information Systems Architecture Technology Architecture Motivation Data Application Drivers Goals Objectives Measures Information System Data Entities Platform Services Services Organization Organization Location Actor, Role Logical Data Logical Application Logical Technology Components Components Components Function Business Services, Physical Processes, Events, Physical Data Physical Application Contracts, Service Functions Technology Controls, Products Components Components Qualities Components Architecture Realization Opportunities, Solutions and Migration Planning Implementation Governance Capabilities Work Packages Architecture Contracts Standards Guidelines Specifications This part describes the TOGAF Content Framework. It includes a structured meta-model for architecture artefacts, re-usable architecture building blocks and typical deliverables of enterprise architecting Matthes Useful EAM-Standards and Best-Practice Frameworks TOGAF is a trademark of The Open Group sebis 19 19

20 TOGAF core elements of version 9.1 (2) The structure of TOGAF 9.1 is organized along the structure and content of an Enterprise Architecture Capability. External factors provide context Part V: Enterprise Continuum and Tools Enterprise Repositories (including Requirements Repository, Architecture Repository, Design Stores and CMDB) The Enterprise Continuum provides structure and classification for assets in Enterprise Repositories. Enterprise Repositories provide resources to be classified within the Enterprise Continuum. Enterprise Continuum Architecture Context and Requirements Contextual factors shape architectures Architecture Continuum Generalization for future re-use Generic Specific Architectures Architectures Adaption for use Guides and Guides and Guides and Guides and supports supports supports supports Solutions Continuum Generalization for future re-use Generic Specific Solutions Solutions Adaption for use This part includes necessary taxonomy and tools usable for classifying and storing enterprise architecting results within organizations. Solutions are instantiated within a deployment Deployed solutions become Architecture Context Deployed Solutions Part VI: TOGAF Reference Models Applications Application Platform Communication Infrastructure Diversity Application Platform Interface Communication Infrastructure Interface A selection of reference models, i. a. the TOGAF Technical Reference Model (TRM), and the Integrated Information Infrastructure Reference Model (III-RM). Business Capability for Architecture (Operating at a level of maturity) Part VII: Architecture Capability Framework Governance Bodies Setting priority Measuring success and focus Skilled Resource Pool Training Project/Portfolio Governance Setting priority and focus Improves Improves Roles and Project Business Requires Responsibilities Portfolios Contract Operations Skills Knowledge (both generic and governed specific to a against their contracts Requires particular project) Delivering aligned solutions Possess Possess Assigned Architecture Projects/Portfolios Professionals Re-using building Population the blocks and Repository complying with standards Enterprise Continuum (used to classify inputs to and outputs from the Repository) Participate in Participate in For implementing and operating the architecture function of an enterprise necessary organization, processes, skills, rolls and responsibilities. Architecture Repository TOGAF is a trademark of The Open Group Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 20

21 TOGAF Architecture Development Method (ADM) An iterative method, over the whole process, between phases and within phases Each iteration = new decisions: Enterprise coverage Level of detail Time horizon Architecture asset re-use: previous ADM iterations other frameworks, system models, industry models, Decisions based on: Competence / resource availability Value accruing to the enterprise. Remark: Every phase is validated against and validates the current requirements of the business Iteration is possible Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 21

22 Preliminary Phase This phase prepares the organization for undertaking successful EA projects Understand business environment High level management commitment Agreement on scope Establish principles Establish governance structure Agree on method to be adopted Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 22

23 Phase A Architecture Vision Initiates one iteration of the architecture process Sets scope, constraints, expectations Required at the start of every architecture cycle Creates the Architecture Vision Validates business context Creates Statement of Architecture work Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 23

24 Phase B Business Architecture Describe current business architecture Develop target business architecture Perform gap analysis Define roadmap for transforming the business architecture Select and adapt relevant architecture viewpoints Create architecture definition document Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 24

25 Phase C Information Systems Architecture This phase is detailed in data architecture and application architecture Describe current data/application architecture Develop target data/application architecture Perform gap analysis Define roadmap for transforming the data/application architecture Select and adapt relevant architecture viewpoints Create architecture definition document Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 25

26 Phase D Technology Architectures Describe current technology architecture Develop target technology architecture Perform gap analysis Define roadmap for transforming the technology architecture Select and adapt relevant architecture viewpoints Create architecture definition document Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 26

27 Phase E Opportunities and Solutions Analyze existing culture of the enterprise Consolidate gaps identified in phases B to D Perform initial implementation planning (including dependencies) Identify the major implementation projects Group projects into Transition Architectures Decide on approach Make v Buy v Re-Use Outsource COTS Open Source Assess priorities Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 27

28 Phase F Migration Planning For projects identified in Phase E perform Cost/benefit analysis Risk assessment Develop a detailed Implementation and Migration Plan (roadmap) Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 28

29 Phase G Implementation Governance Provide architectural oversight for the implementation. Defines architecture constraints on implementation projects Architecture contract Monitors implementation work for conformance Realize EA compliance reviews Produce a Business Value Realization Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 29

30 Phase H Architecture Change Management Provide a continual monitoring and a change management process Ensures that changes to the architecture are managed in a cohesive and architected way Establishes and supports the EA to provide flexibility to evolve rapidly in response to changes in the technology or business environment Monitors the business and capacity management. Management of the governance structures (quality gates) Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 30

31 The TOGAF Architecture Content Framework provides an overview of possible information model elements. Architecture Principles, Vision and Requirements Preliminary Architecture Vision Architecture Principles Business Strategy Technology Strategy Business Principles, Objectives and Drivers Architecture Vision Stakeholders Architecture Requirements Requirements Constraints Assumptions Gaps Business Architecture Information Systems Architecture Technology Architecture Motivation Data Application Drivers Goals Organization Objectives Measures Data Entities Information System Services Platform Services Organization Location Function Actor, Role Logical Data Components Logical Application Components Logical Technology Components Business Services, Contracts, Service Qualities Processes, Events, Controls, Products Functions Physical Data Components Physical Application Components Physical Technology Components Architecture Realization Opportunities, Solutions and Migration Planning Capabilities Work Packages Architecture Contracts Implementation Governance Standards Guidelines Specifications Matthes Useful EAM-Standards and Best-Practice Frameworks TOGAF is a trademark of The Open Group sebis 31 31

32 TOGAF bottom line Pro Pervasive in practice Trainings available Certificates available Compliant tools available Internationally accepted Contra Inconsistencies between parts Adaptation necessary Learning TOGAF mastering TOGAF Lack of concrete guidelines for introducing TOGAF Lean EAM countermovement Open development Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 32

33 ArchiMate s historical origin Research project between 2002 and 2004 Funded by 4 million Motivation Increasing need for precise documentation on the enterprise architecture level Communicating about architecture with others Analysis of architectures before their implementation Since 2009, ArchiMate is an Open Group standard and complements TOGAF Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 33

34 ArchiMate s layers and aspects Passive Structure objects Behavior verbs Active Structure subjects Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 34

35 ArchiMate s layers and aspects (in detail) Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 35

36 ArchiMate s generic structure Akin concepts at all layers facilitate learning the language and make its use more consistent: Passive structure Behavior Active structure Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 36

37 ArchiMate s core concepts Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 37 [4]

38 ArchiMate s layered architecture (example) Business Layer Application Layer Technology Layer [5] Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 38

39 ArchiMate s integration with TOGAF [9] Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 39

40 ArchiMate s extensions mapped to TOGAF ArchiMate s core supports these phases: B, C, D Implementation & migration extension: E, F, G Motivation extension H, Preliminary, Requirements Management Passive Structure Behavior Active Structure Business Layer Application Layer Technology Layer Implementation& Migration Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 40

41 ArchiMate s motivation extension Different kinds of relationships: Association relation Realization relation Aggregation relation Specialization relation Contribution relation (+/-) Conflict relation Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 41

42 ArchiMate s migration and implementation extension Different kinds of relationships: Specialization relation Composition relation Aggregation relation Assignment relation Triggering relation Access relation Association relation Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 42

43 Relationship between the ArchiMate core and its extensions [10] Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 43

44 Iteraplan best practice enterprise architecture modeling concepts and their relationships Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 44

45 Recently introduced concepts Marc Lankhorst (2014): Enterprise Portfolio Management, Presentation Insight Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 45

46 Using domain-specific modeling languages Pro Predefined meta-model Specific notation Aligned with other frameworks (e.g. TOGAF) Easier start of modeling due to existing concepts Contra Maybe not prevalent in a specific region (e.g. Germany) Training necessary for every modeler Limited extensibility Terminology mapping required Comprehensive documentation Publicly available Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 46

47 Discussion 1. Which EA frameworks are used in your company? 2. What are expected and realized benefits? Matthes Useful EAM-Standards and Best-Practice Frameworks sebis 47

48 Thank you for your attention. Questions? Florian Matthes Prof.Dr.rer.nat. Technische Universität München Department of Informatics Chair of Software Engineering for Business Information Systems Boltzmannstraße Garching bei München Tel Fax matthes@in.tum.de wwwmatthes.in.tum.de