TDT4252 Modelling of Information Systems Advanced Course

1. TDT4252Modelling of Information SystemsAdvanced Course Sobah Abbas Petersen Adjunct Associate Professor sap@idi.ntnu.no 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. • Additional reading: • The Open Group Architecture Framework (TOGAF) – The continuing Story, Chris Greenslade, 2002. (http://www.enterprise-architecture.info/Images/Documents/Togaf%20seminar.pdf) Lecture 15 – Enterprise Architecture

3. What is Enterprise Architecture – recap Lecture 15 – Enterprise Architecture

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

5. Alignment Common understanding! Lecture 14 - Introduction to Enterprise Architecture

6. Zachman’s EA Framework - recap Aspects View Viewpoints Lecture 14 - Introduction to Enterprise Architecture

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 1995. • Current version is 9. 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 Lecture 15 – Enterprise Architecture

10. The Position of IT Architects 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. Greenslade, 2000-2002 Lecture 15 – Enterprise Architecture

12. TOGAF 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. Lecture 15 – Enterprise Architecture

14. TOGAF’s Enterprise Architecture Describestheprocessesthe business uses to meetits goals. Describeshowspecificapplicationsaredesigned and howtheyinteractwitheachother. Describes how the enterprise datastores are organised and accessed. Describes the hardware and software infrastructure that supports applications and their interactions. Lecture 15 – Enterprise Architecture

15. TOGAF Enterprise Continuum (1) • 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. Lecture 15 – Enterprise Architecture

16. TOGAF Enterprise Continuum (2) Lecture 15 – Enterprise Architecture

17. TOGAF Enterprise Continuum and ADM Generic • 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. Specific Lecture 15 – Enterprise Architecture

18. TOGAF – Components of Foundation Architecture 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. Lecture 15 – Enterprise Architecture

20. TRM – Technical Reference Model • Any TRM has two main components: • A taxonomy, which defines terminology, and provides a coherent description of the components and conceptual structure of an information system. • 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. Lecture 15 – Enterprise Architecture

21. TRM – High level view • 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. Lecture 15 – Enterprise Architecture

22. Architecture Development Cycle - ADM Lecture 15 – Enterprise Architecture

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

24. A Architecture Vision ADM - Architecture Vision • Define the scope of the architecture project • Define high level business requirements Lecture 15 – Enterprise Architecture

25. B Business Architecture ADM – Business Architecture 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. • Select viewpoints • Describe TO-BE • Describe AS-IS • Analysegaps between TO-BE and AS-IS Lecture 15 – Enterprise Architecture

26. Applications Architecture ADM: Informations Systems Architecture - Data 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. • Select viewpoints • Describe TO-BE • Describe AS-IS • Analyze gaps between TO-BE and AS-IS Data Architecture C Information System Architecture Management Lecture 15 – Enterprise Architecture

27. Data Architecture Applications Architecture ADM: Informations Systems Architecture - Applications 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. • Select viewpoints • Describe TO-BE • Describe AS-IS • Analyse gaps between TO-BE and AS-IS C Information System Architecture Management Applications Architecture Lecture 15 – Enterprise Architecture

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

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

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

31. GImplementation Governance ADM: Implementation Governance • Architectural contract. • Ensure compliance with the defined architecture. • Implementation specifications – acceptance criteria. Management Lecture 15 – Enterprise Architecture

32. H Architecture Change Management ADM: Architectural Change Management • Handle architecture change requests • Suggest new architecture projects Management Lecture 15 – Enterprise Architecture

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

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 howto generate enterprise architecture, not necessarily how to generate a good one! Lecture 15 – Enterprise Architecture

35. Architecture Strategy Implementation Gartner • 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 Lecture 15 – Enterprise Architecture

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

37. From Strategy to Implementation • 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 Lecture 15 – 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. Lecture 15 – Enterprise Architecture

39. Gartner Business Owners Business Owners • 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! Common understanding Business Owners Lecture 15 – Enterprise Architecture

40. Gartner x • 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. x Lecture 15 – Enterprise Architecture

41. Environmental Trends Business Strategy Organize Architecture Effort Architecting DevelopRequirements DevelopPrinciples DevelopModels Future State Architecture Closing the Gap Governing & Managing Current State Architecture Documenting Gartner Enterprise Architecture Method The two major facets of the Gartner EA method are: • Gartner Enterprise Architecture Process Model • Gartner Enterprise Architecture Framework Lecture 15 – Enterprise Architecture

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

43. Gartner’s 4 Architectural Viewpoints 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 Lecture 15 – Enterprise Architecture

44. Gartner Enterprise Architecture Process Model Environmental Trends Business Strategy Organize Architecture Effort Architecting DevelopRequirements DevelopPrinciples DevelopModels Future State Architecture Closing the Gap Governing & Managing Current State Architecture Documenting Lecture 15 – Enterprise Architecture

45. Principles • 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. Lecture 15 – Enterprise Architecture

46. From Forces to Enterprise Architecture ExternalForces Business Architecture InformationArchitecture Business requirements BusinessStrategy TechnicalArchitecture Solution Architecture InternalForces Lecture 15 – Enterprise Architecture

47. Organise Architecture Effort Environmental Trends Business Strategy Organize Architecture Effort Architecting DevelopRequirements DevelopPrinciples DevelopModels Future State Architecture Closing the Gap Governing & Managing Current State Architecture Documenting Lecture 15 – Enterprise Architecture

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

49. Develop Requirements Environmental Trends Business Strategy Organize Architecture Effort Architecting DevelopRequirements DevelopPrinciples DevelopModels Future State Architecture Closing the Gap Governing & Managing Current State Architecture Documenting Lecture 15 – Enterprise Architecture

50. CRV - from strategy to business requirements CRV = Common Requirements Vision Lecture 15 – Enterprise Architecture