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

2. This Lecture Enterprise Architectures continued. Based on:
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, ( architecture.info/Images/Documents/Togaf%20seminar.pdf)
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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

4. EA Bridges Strategy and Implementation
Harald Rønneberg
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
Fra ambisjon til handing!
Her ser vi også hva Gartner legger i begrepet business strategy.
Og vi ser at det ikke bare er fokus på implementasjon av IT!!!
Lecture 14 - Introduction to Enterprise Architecture
TDT4252, Spring 2011

5. Alignment Common understanding!
Harald Rønneberg
Alignment
Common understanding!
Slik jeg ser det er dette et godt bilde på alignment. Alle kjenner sin bit og vet hvordan det hele henger sammen.
Det handler om felles forståelse!
Lecture 14 - Introduction to Enterprise Architecture
TDT4252, Spring 2011

6. Zachman’s EA Framework - recap
Harald Rønneberg
Zachman’s EA Framework - recap
Aspects
View
Viewpoints
Radene viser detaljeringen
Kolonnene viser fokusområdene
Du kan selvsagt velge andre fokusområder og detaljering/nedbryting, men det var denne Zachman endte opp med.
Zachman er et kjent EA rammeverk med fokus på alt fra abstrakte og overordnede modeller og beskrivelser
til detaljerte og fysiske modeller og beskrivelser
Skal dette rammeverket følges 100%, får du mange detaljerte modeller og beskrivelser!
Hva er utfordringene med modeller og beskrivelser??? OPPDATERING!!
Lecture 14 - Introduction to Enterprise Architecture
TDT4252, Spring 2011

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
TDT4252, Spring 2011

8. Enterprise Architecture
Harald Rønneberg
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.
Byggverk brukes ofte som eksempel på arkitektur, men det er ofte et mindre godt eksempel, spesielt i IT verden. Grunnen er at byggverk bare har struktur, dynamikk mangler. Levende vesener er bedre eksempler på arkitektur.
TOGAF

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

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

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,
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

12. TOGAF
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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
TDT4252, Spring 2011

14. TOGAF’s 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.
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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
TDT4252, Spring 2011

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

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
TDT4252, Spring 2011

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

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
TDT4252, Spring 2011

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
TDT4252, Spring 2011

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.
But semantic integration is not solved by TRM and the Communications Infrastructure Interface. Semantic integration must be solved by the Information architecture.
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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

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

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

25. ADM – Business Architecture
B 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
Analyse gaps between TO-BE and AS-IS
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

26. ADM: Informations Systems Architecture - Data
C Information System Architecture
Applications Architecture
Data Architecture
Management
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
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

27. ADM: Informations Systems Architecture - Applications
C Information System Architecture
Data Architecture
Applications Architecture
Management
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
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

28. ADM: Technical Architecture
D Technology Architecture
Management
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
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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

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

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

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

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

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!
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

35. 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
Architecture
Implementation
Strategy
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

36. EA Bridges Strategy and Implementation
Harald Rønneberg
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
Fra ambisjon til handing!
Her ser vi også hva Gartner legger i begrepet business strategy.
Og vi ser at det ikke bare er fokus på implementasjon av IT!!!
Lecture 14 - Introduction to Enterprise Architecture
TDT4252, Spring 2011

37. From Strategy to Implementation
Enterprise
Planning
and Strategy
Program
Management
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
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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
TDT4252, Spring 2011

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!
Business Owners
Common understanding
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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.
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

41. Gartner Enterprise Architecture Method
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
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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
TDT4252, Spring 2011

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
TDT4252, Spring 2011

44. 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
Principles are guiding statements of position that communicate fundamental elements, truths, rules or qualities that must be exhibited by an enterprise to realize its goals.
Principles are used to guide consistent decision making.
Principles tend to be fairly timeless and static.
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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.
Principles are guiding statements of position that communicate fundamental elements, truths, rules or qualities that must be exhibited by an enterprise to realize its goals.
Principles are used to guide consistent decision making.
Principles tend to be fairly timeless and static.
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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

47. Organise Architecture Effort
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
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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
TDT4252, Spring 2011

49. Develop Requirements Architecting Closing the Gap Governing & Managing
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
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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

51. 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
A CRV consists of various requirement types, including:
Business change requirements describe what is necessary to change about the business operations (processes, relationships, organization, structure, business model, etc.) to achieve business strategies
Business information requirements describe what the enterprise must do to leverage information to achieve business strategies
Information technology requirements describe what capabilities technology must provide to achieve business strategies
Business solution requirements describe the solutions required to satisfy the business, information, and technology requirements as integrated solutions to achieve business strategies
The CRV document is an articulation of what will drive the enterprise’s future state
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

52. CRV Best Practices
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
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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

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

55. Develop Principles Architecting Closing the Gap Governing & Managing
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
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

56. 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.
Principles are guiding statements of position that communicate fundamental elements, truths, rules or qualities that must be exhibited by an enterprise to realize its goals.
Principles are used to guide consistent decision making.
Principles tend to be fairly timeless and static.
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

57. Develop Models Architecting Closing the Gap Governing & Managing
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
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

58. 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
TDT4252, Spring 2011

59. Four Levels of Abstraction
EBA
EIA
ETA
ESA
Conceptual
Logical
Implementation
Business context
Remember:
Just enough models just in time
Avoid paralysis by analysis
Future state before current state
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

60. Current state and the gap
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
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

61. Governing and Managing
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
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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.
Lecture 15 – Enterprise Architecture
TDT4252, Spring 2011

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

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