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: Gartner, FEA

2. This Lecture • Enterprise Architectures continued: Gartner, FEA • Based on lecture slides from Spring 2010, by Harald Rønneberg. • Requiered Reading: • A16: Roger Sessions, A Comparison of the Top Four Enterprise-Architecture Methodologies, White Paper, ObjectWatch Inc. May 2007. • Additional reading: • Federal Enterprise Architecture Framework, Version 1.1, September 1999, (http://www.cio.gov/documents/fedarch1.pdf) • http://en.wikipedia.org/wiki/Federal_Enterprise_Architecture • Cisco Systems, 2009. Federal Enterprise Architecture (FEA) and Network Services, White Paper, pages 1-6. (http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns859/C11-542359-00_FEAnetsol.pdf) Lecture 15 – Enterprise Architecture: Gartner, FEA

3. What is Enterprise Architecture – recap Lecture 15 – Enterprise Architecture: Gartner, FEA

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 15 – Enterprise Architecture: Gartner, FEA

5. Alignment Common understanding! Lecture 15 – Enterprise Architecture: Gartner, FEA

6. Example case: MEM-EA • Internal conflicts between the technical and and the business side. • Business side saw IT as reducing business agility. • IT side saw the business side as making impossible demands. • Crisis! Cath, CEO Irma, CIO Bret, BusinessManager Lecture 15 – Enterprise Architecture: Gartner, FEA

7. Zachman’s EA Framework - recap Aspects View Viewpoints Lecture 15 – Enterprise Architecture: Gartner, FEA

8. 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: Gartner, FEA

9. 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: Gartner, FEA

10. 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: Gartner, FEA

11. Architecture Development Cycle - ADM Lecture 15 – Enterprise Architecture: Gartner, FEA

12. 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: Gartner, FEA

13. 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: Gartner, FEA

14. 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 15 – Enterprise Architecture: Gartner, FEA

15. 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: Gartner, FEA

16. 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: Gartner, FEA

17. Gartner • EA is about creating a common understanding. • Bringing together 3 constituents: business owners, information specialists and technology implementers. • If we can unify these behind a common vision that drives the business value  success! Business Owners Informationspecialist Common understanding TechnologyImplementers Lecture 15 – Enterprise Architecture: Gartner, FEA

18. 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: Gartner, FEA

19. 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: Gartner, FEA

20. 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: Gartner, FEA

21. 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: Gartner, FEA

22. 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: Gartner, FEA

23. 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: Gartner, FEA

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

25. 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: Gartner, FEA

26. CRV - from strategy to business requirements • Greg asks Cath to specify her visions in business (not technical terms). • The visions are prioritised. • Cath decides the highest priority is "MedAMore will reduce its purchasing costs by 10% by consolidating all regional purchasing into a central system". • CRV = Common Requirements Vision Greg, Gartner Consultant Cath, CEO Lecture 15 – Enterprise Architecture: Gartner, FEA

27. What is CRV? • 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 Lecture 15 – Enterprise Architecture: Gartner, FEA

28. Develop Models 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: Gartner, FEA

29. Gartner’s 4 Architectural Viewpoints (1) Business Architecture • Defines and describes the future- state models of business activities (processes, assets and organization structure) Information Architecture • Defines and describes the future- state models of the information value chain, key information artifacts (concepts), information flows Technology Architecture • Defines and describes the future- state models of the infrastructure and technology platforms required for the solution architecture and which enables rapid engineering, solutions development and technical innovation Bret, BusinessManager Greg, Gartner Consultant Greg, Gartner Consultant Irma, CIO Lecture 15 – Enterprise Architecture: Gartner, FEA

30. Gartner’s 4 Architectural Viewpoints (2) 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: Gartner, FEA

31. Current state and the gap 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: Gartner, FEA

32. Governing and Managing 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: Gartner, FEA

33. Gartner- benefits • Process completeness – the methodology fully guides you through a step-by-step process for creating EA. • Practical guidance. • Business focus. • Provides a methodology that can support governance. • Does not provide a complete taxonomy. • Not much information available about it. Lecture 15 – Enterprise Architecture: Gartner, FEA

34. What is FEAF? • FEAF (Federal Enterprise Architecture Framework) provides an organised structure and a collection of common terms by which Federal segments can integrate their respective architectures into the FEA (Federal Enterprise Architecture). • FEA is a strategic information asset base that defines the business, information necessary to operate the business, technology necessary to support the business operations and transitional processes for implementing new technologies in response to the changing needs of the business. Lecture 15 – Enterprise Architecture: Gartner, FEA

35. Why FEAF? Lecture 15 – Enterprise Architecture: Gartner, FEA

36. Value of FEAF Lecture 15 – Enterprise Architecture: Gartner, FEA

37. FEAF Components (1) Refer to all standards (some of which may be mandatory), guidelines and best practices. External stimuli or change agents for the enterprise architecture. Defines the ”as-is” enterprise architecture. Consists of 2 parts: current business and design architectures (i.e. data, applications and technology). Defines the ”to-be” enterprise architecture. Consists of 2 parts: current business and design architectures (i.e. data, applications and technology). Lecture 15 – Enterprise Architecture: Gartner, FEA

38. FEAF Components (2) Consists of focused architecture efforts on major cross-cutting business areas and program areas. Guides the development of the target architecture and consists of a vision, principles, goals and objectives. Defines the business and design models that compromise the segments of the enterprise descriptions. Supports the migration from the current to the target architecture. This includes migration planning, investment planning, engineering change control, etc. Lecture 15 – Enterprise Architecture: Gartner, FEA

39. FEAF - Segments • FEAF allows critical parts of the overall Federal Enterprise, called architectural segments, to be developed individually, while integrating these segments into the larger Enterprise Architecture. Lecture 15 – Enterprise Architecture: Gartner, FEA

40. FEA – Federal Enterprise Architecture • FEA is the latest attempt by the US federal government to unite its agencies and functions in a single common and ubiquitous enterprise architecture. • FEA is the most complete methodology. It has a: • A comprehensive taxonomy, like Zachman’s framework. • An architectural process, like TOGAF. • FEA can be viewed as either a methodology for creating an enterprise architecture or the result of applying that process to a particular enterprise. • FEA includes everything necessary for building an enterprise architecture. Lecture 15 – Enterprise Architecture: Gartner, FEA

41. FEA – Reference Models • The goal of the reference models is to provide standardised terms and definitions for the domain of enterprise architecture and thereby facilitate collaboration and sharing across the federal government. • It’s all about establishing a common language. • Collectively, the reference models comprise a framework for describing important elements of the FEA in a common and consistent way. Lecture 15 – Enterprise Architecture: Gartner, FEA

42. FEA – Reference Models FEA consists of 5 reference models: Lecture 15 – Enterprise Architecture: Gartner, FEA

43. FEA – Reference Models: descriptions • Business Reference Model (BRM): • Gives a business view of the various business functions. • Service Components Reference Model (CRM): • Gives a more IT view of systems that can support business functionality. • Technical Reference Model (TRM): • Defines the various technologies and standards that can be used in building ITsystems. • Data Reference Model (DRM): • Defines standard ways of describing data. • Performance Reference Model (PRM): • Defines standard ways of describing the value delivered by enterprise architecture. Lecture 15 – Enterprise Architecture: Gartner, FEA

44. FEA – Segment architecture approach • FEA perspective on EA: an enterprise is built of segments. • A segment is a major line-of-business functionality, such as human resources. • Although segments function at the political level (the agency), they are defined at the enterprise level (government). • Segments are defined globally to facilitate reuse across the the different enterrpises. Lecture 15 – Enterprise Architecture: Gartner, FEA

45. FEA – Segment Map Segments (vertical columns): spans a single organisation, used by multiple segments. Enterprise Services: have a scope across the entire enterprise. Lecture 15 – Enterprise Architecture: Gartner, FEA

46. FEA Process (1) • FEA Process is primarily focussed on creating a segment architecture for a subset of the overall enterprise. • Segment architecture development process: • Step 1: Architectural analysis. • Step 2: Architectural definition. • Step 3: Investment and funding strategy. • Step 4: Program management plan and execute projects. Lecture 15 – Enterprise Architecture: Gartner, FEA

47. FEA Process, Level I High level Lecture 15 – Enterprise Architecture: Gartner, FEA

48. FEA Process – Level II More detail – the business and design pieces of the architecture and how they are related. Lecture 15 – Enterprise Architecture: Gartner, FEA

49. FEA Process – Level III Expand the design pieces of the framework to show the 3 design architectures: data, application and technology. Lecture 15 – Enterprise Architecture: Gartner, FEA

50. FEA Process – Level IV • Identifies the kinds of models that describe the business architecture and the three design architectures ( data, applications and technology). • It also defines Enterprise Architecture Planning (EAP). • EAP focuses on defining what data, applications and technology architectures are appropriate for and support the overall enterprise. EAP Lecture 15 – Enterprise Architecture: Gartner, FEA