1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

2 This Lecture Enterprise Architectures continued. –TOGAF –Gartner –Based on lecture slides from Spring 2010, by Harald Rønneberg. Based on: –A15: Roger Sessions, A Comparison of the Top Four Enterprise- Architecture Methodologies, White Paper, ObjectWatch Inc. May 2007.A Comparison of the Top Four Enterprise- Architecture Methodologies, White Paper, ObjectWatch Inc. May 2007 Additional reading: –The Open Group Architecture Framework (TOGAF) – The continuing Story, Chris Greenslade, ( architecture.info/Images/Documents/Togaf%20seminar.pdf) TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

3 What is Enterprise Architecture – recap TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

4 EA Bridges Strategy and Implementation The bridge between strategy & implementation Business architecture Information architecture Solution architecture Technology architecture Business Strategy Business drivers Business goals Business policy Trend analysis Implementation Business processes Application systems Tech infrastructure Organizational structure TDT4252, Spring 2011 Lecture 14 - Introduction to Enterprise Architecture

5 Alignment TDT4252, Spring 2011 Lecture 14 - Introduction to Enterprise Architecture Common understanding!

6 Zachman’s EA Framework - recap TDT4252, Spring 2011 Lecture 14 - Introduction to Enterprise Architecture View Aspects Viewpoints

7 TOGAF The Open Group Architecture Framework The Open Group Forums – cooperation between vendors and users, where a variety of common interests are explored, one of which is architecture. Earlier versions of TOGAF available since Current version is 9. TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

8 Enterprise Architecture An architecture –A formal description of a system, or a detailed plan of the system at component level to guide its implementation. –The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time. TOGAF

9 The Position of IT Architects TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

10 The Position of IT Architects TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

11 TOGAF – consists of An Architectural Development Method (ADM) Foundation Architecture –A Technical Reference Model (TRM) –A Standards Information Base (SIB) –Building Blocks Information (BBIB) Resource Base contains advice on: –Architecture views, IT Governance, Business scenarios, Architecture patterns, etc. TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Greenslade,

12 TOGAF TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

13 TOGAF – Framework or Process? TOGAF describes itself as a Framework. But the most important part of it is the Architectural Development Method (ADM): –ADM is a recipe for creating architecture. TOGAF is an architectural process (Roger Sessions). It complements Zachman’s Framework: –Zachman tell you how to categorise artifacts; TOGAF provides a process for creating them. TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

14 TOGAF’s Enterprise Architecture TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Describes the processes the business uses to meet its goals. Describes how specific applications are designed and how they interact with each other. Describes how the enterprise datastores are organised and accessed. Describes the hardware and software infrastructure that supports applications and their interactions.

15 TOGAF Enterprise Continuum (1) TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture TOGAF views the Enterprise Architecture as a continuum of architectures, ranging from the highly generic to the highly specific. It views the process of creating a specific enterprise architecture as moving from the generic to the specific. TOGAF’s ADM provides a process for driving this movement from the generic to the specific.

16 TOGAF Enterprise Continuum (2) TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

17 Foundation Architectures: –Most generic, architectural principles that can be used by any IT organisation. Common System Architectures: –architectural principles that may be found in many types of enterprises. Industry Architectures: –architectural principles that are specific across many enterprises that are in the same domain. Organisational Architectures: –Architectures that are specific to a given enterprise. TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture TOGAF Enterprise Continuum and ADM Generic Specific

18 TOGAF – Components of Foundation Architecture TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

19 TOGAF – Foundation Architecture The TOGAF Foundation Architecture is an architecture of generic services and functions that provides a foundation on which more specific architectures and architectural components can be built. This Foundation Architecture is embodied within the Technical Reference Model (TRM), which provides a model and taxonomy of generic platform services. The TRM is universally applicable and, therefore, can be used to build any system architecture. TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

20 TRM – Technical Reference Model Any TRM has two main components: 1.A taxonomy, which defines terminology, and provides a coherent description of the components and conceptual structure of an information system. 2.An associated TRM graphic, which provides a visual representation of the taxonomy, as an aid to understanding. The objective of the TOGAF TRM is to provide a widely accepted core taxonomy, and an appropriate visual representation of that taxonomy. TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

21 TRM – High level view TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture The high-level TRM seeks to emphasize two major common architectural objectives: Application Portability, via the Application Platform Interface — identifying the set of services that are to be made available in a standard way to applications via the platform. Interoperability, via the Communications Infrastructure Interface — identifying the set of Communications Infrastructure services that are to be leveraged in a standard way by the platform. Both of these goals are essential to enable integration within the enterprise and trusted interoperability on a global scale between enterprises.

22 Architecture Development Cycle - ADM TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

23 ADM - Framework and Principles TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Define architecture principles that drive technological architectures and document those. Choose framework and customise. Framework and Principles

24 ADM - Architecture Vision TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Define the scope of the architecture project Define high level business requirements A Architecture Vision

25 ADM – Business Architecture TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Select viewpoints Describe TO-BE Describe AS-IS Analyse gaps between TO-BE and AS-IS The objective is to define and describe the product and/or service strategy, and the organizational, functional, process, information, and geographic aspects of the business environment. B Business Architecture

26 ADM: Informations Systems Architecture - Data TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Select viewpoints Describe TO-BE Describe AS-IS Analyze gaps between TO-BE and AS-IS C Information System Architecture Applications Architecture Data Architecture Managem ent The objective is to define the major types and source of data necessary to support the business. It is NOT about database design. The goal is to define the data entities relevant to the enterprise.

27 ADM: Informations Systems Architecture - Applications TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture C Information System Architecture Data Architecture Applicati ons Architec ture Managem ent Select viewpoints Describe TO-BE Describe AS-IS Analyse gaps between TO-BE and AS-IS The objective is to define the major kinds of application necessary to process the data and support the business. The goal is to define what kind of applications are relevant to the enterprise, and what they need to do.

28 ADM: Technical Architecture TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture D Technology Architecture Management Select viewpoints Describe TO-BE Describe AS-IS Analyse gaps between TO-BE and AS-IS The objective is to define the technology and technical services that will form the basis of the following implementation work.

29 ADM: Opportunities and Solutions TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture The first phase directly concerned with implementation How to close the gaps? Identify implementation projects E Opportunities and Solutions Management

30 Prioritize between implementation projects i.e. project portfolio management Cost and benefit analysis Risk assessment ADM: Migration Planning TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture F Migration Planning Management

31 ADM: Implementation Governance TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Architectural contract. Ensure compliance with the defined architecture. Implementation specifications – acceptance criteria. G Implementation Governance Management

32 ADM: Architectural Change Management TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Handle architecture change requests Suggest new architecture projects H Architecture Change Management Management

33 ADM: Requirements Management TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Handling new and changing requirements from architecture projects, IT projects, change projects, operations, etc. Requirements Management

34 TOGAF - benefits +TOGAF is flexible about the architecture that is generated – ”architecture agnostic” or vendor neutral. +Comprehensive process, from business requirements to applications to infrastructure. The final architecture may be good, bad or indifferent. ÷TOGAF merely describes how to generate enterprise architecture, not necessarily how to generate a good one! TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

35 Gartner TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture A planning discipline for the enterprise that goes beyond technology choices: –Driven by the strategic intent of the enterprise –Holistic in breadth –Designed to create a future-state “road map” –Provides flexibility and adaptability for changing business, information, and solution needs => change enabler –A bridge between strategy and implementation Architecture ImplementationStrategy

36 EA Bridges Strategy and Implementation The bridge between strategy & implementation Business architecture Information architecture Solution architecture Technology architecture Business Strategy Business drivers Business goals Business policy Trend analysis Implementation Business processes Application systems Tech infrastructure Organizational structure TDT4252, Spring 2011 Lecture 14 - Introduction to Enterprise Architecture

37 From Strategy to Implementation TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Planning and Strategy –Focused on integration of business and IT planning Enterprise Architecture –Goal is to provide the road map for the enterprise Program Management –Primary agent for implementing enterprise transformation Enterprise Planning and Strategy Enterprise Program Management Enterprise Architecture

38 Gartner The Gartner EA methodology is a ”practice” – Sessions. It is an ongoing process of creating, maintaining, and especially, leveraging an enterprise architecture that gives the enterprise its vitality. TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

39 Gartner EA is about creating a common understanding. Bringing together 3 constituents: business owners, information specialists and technology imolementers. If we can unify these behind a common vision that drives the business value  success! TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Business Owners Common understanding

40 Gartner Enterprise Architecture must start where an organisation is going, not where it is  focussed on destination. Recommends that an organisation begins by telling the story of where its strategic direction is heading and what the business drivers are to which it’s responding.  Goal: everybody understands and shares a single vision. As soon as an organisation has a single vision, the implications on the business, technical, information and solution architectures can be considered. TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture x x

41 Gartner Enterprise Architecture Method TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture The two major facets of the Gartner EA method are: Gartner Enterprise Architecture Process Model Environmental Trends Business Strategy Closing the Gap Future State Architecture Current State Architecture Governing & Managing Organize Architecture Effort Architecting Develop Requirements Develop Principles Develop Models Documenting Gartner Enterprise Architecture Framework

42 Gartner’s 4 Architectural Viewpoints TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Three primary viewpoints: –Business Architecture –Information Architecture –Technology Architecture One meta-architecture viewpoint –Solution Architecture Solution Architecture Framework –A framework for creating Solution Architectures

43 Gartner’s 4 Architectural Viewpoints TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Business Architecture –Defines and describes the current- and future- state models of business activities (processes, assets and organization structure) Information Architecture –Defines and describes the current- and future- state models of the information value chain, key information artifacts (concepts), information flows Technology Architecture –Defines and describes the current- and future- state models of the infrastructure and technology platforms required for the solution architecture and which enables rapid engineering, solutions development and technical innovation Solution Architecture –Combining and reconciling (integration) the loosely coupled and often conflicting viewpoints of the primary stakeholders into a unified architecture –Having divided to conquer, we must reunite to rule –SA is a consistent architectural description of a specific enterprise solution –An intersection of viewpoints

44 Gartner Enterprise Architecture Process Model TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Environmental Trends Business Strategy Closing the Gap Future State Architecture Current State Architecture Governing & Managing Organize Architecture Effort Architecting Develop Requirements Develop Principles Develop Models Documenting

45 Principles TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture –Successful organizations establish guiding principles to support consistent decision making, drive consistent behavior and drive cultural changes. –There is no perfect set of principles. –Institutionalisation of principles, the process, is the difficult part. –Principles are an extremely important component of governance and EA.

46 From Forces to Enterprise Architecture TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Information Architecture Technical Architecture Solution Architecture Solution Architecture Business Strategy Internal Forces External Forces Business Architecture Business Architecture

47 Organise Architecture Effort TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Environmental Trends Business Strategy Closing the Gap Future State Architecture Current State Architecture Governing & Managing Organize Architecture Effort Architecting Develop Requirements Develop Principles Develop Models Documenting

48 Organise Architecture Effort - Activities State the goals Scoping Buy-in and commitment Stakeholder analysis Set time box Establish EA team TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

49 Develop Requirements TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Environmental Trends Business Strategy Closing the Gap Future State Architecture Current State Architecture Governing & Managing Organize Architecture Effort Architecting Develop Requirements Develop Principles Develop Models Documenting

50 CRV - from strategy to business requirements TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Environmental Trends Enterprise Business Strategies Business Change Requirements Business Information Requirements Information Technology Requirements Business Solutions Requirements CRV = Common Requirements Vision

51 What is CRV? TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture A process for capturing, discussing and documenting a shared common view of the strategic requirements driving the enterprise:  Position on the impact of environmental trends to the enterprise  Set of enterprise business strategies  Set of common strategic requirements derived from enterprise business strategies The CRV document is an articulation of what will drive the enterprise’s future state Environmental Trends Enterprise Business Strategies Business Change Requirements Business Information Requirements Information Technology Requirements Business Solutions Requirements

52 CRV Best Practices TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Obtain as much business participation as early as possible Remember that wording is very important Provide support with graphics Avoid excessive details Start with a “straw man” document Time-box the development effort

53 CRV process - from trends to business strategy TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Business Strategy Internal Forces External Forces

54 CRV Challenges Business participation Integration with established strategy processes Level of details Wording TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

55 Develop Principles TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Environmental Trends Business Strategy Closing the Gap Future State Architecture Current State Architecture Governing & Managing Organize Architecture Effort Architecting Develop Requirements Develop Principles Develop Models Documenting

56 Principles TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture –Successful organizations establish guiding principles to support consistent decision making, drive consistent behavior and drive cultural changes. –There is no perfect set of principles. –Institutionalisation of principles, the process, is the difficult part. –Principles are an extremely important component of governance and EA.

57 Develop Models TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Environmental Trends Business Strategy Closing the Gap Future State Architecture Current State Architecture Governing & Managing Organize Architecture Effort Architecting Develop Requirements Develop Principles Develop Models Documenting

58 Gartner’s 4 Architectural Viewpoints TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Business Architecture –Defines and describes the current- and future- state models of business activities (processes, assets and organization structure) Information Architecture –Defines and describes the current- and future- state models of the information value chain, key information artifacts (concepts), information flows Technology Architecture –Defines and describes the current- and future- state models of the infrastructure and technology platforms required for the solution architecture and which enables rapid engineering, solutions development and technical innovation Solution Architecture –Combining and reconciling (integration) the loosely coupled and often conflicting viewpoints of the primary stakeholders into a unified architecture –Having divided to conquer, we must reunite to rule –SA is a consistent architectural description of a specific enterprise solution –An intersection of viewpoints

59 Four Levels of Abstraction TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Remember: Just enough models just in time Avoid paralysis by analysis Future state before current state

60 Current state and the gap TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Environmental Trends Business Strategy Closing the Gap Future State Architecture Current State Architecture Governing & Managing Organize Architecture Effort Architecting Develop Requirements Develop Principles Develop Models Documenting

61 Governing and Managing TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture Environmental Trends Business Strategy Closing the Gap Future State Architecture Current State Architecture Governing & Managing Organize Architecture Effort Architecting Develop Requirements Develop Principles Develop Models Documenting

62 Governing and Managing Governing – key words: –Governing EA artifact creation and changes – architecture review board –EA contract –EA compliance or waiver Managing – key words: –Managing the EA program itself –Management of the EA repository and its contents –EA consulting to project team TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

63 Gartner- benefits +Process completeness – the methodology fully guides you through a step-by-step process for creatign EA. +Practical guidance. +Business focus. +Provides a methodology that can support governance. ÷Does not provide a complete taxonomy. ÷Not much information available about it. TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

64 Summary Today, we have looked at the following Enterprise Architecture Methodologies: –TOGAF –Gartner TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture

65 Next Lecture Monday 28 March 2011, 12-13hrs and 15-17hrs. Topic: SOAML, by Babak Farshchian TDT4252, Spring 2011 Lecture 15 – Enterprise Architecture