1. Lecture 5: Enterprise Architecture (Cont…)
Dr. Taysir Hassan A. Soliman
November 9, 2015
INF411
Information Engineering
Information Systems Dept.
Faculty of Computers & Information

2. Outline Zachman framework for Enterprise Architecture
Zachman in Healthcare
Zachman in Education
The Open Group Architecture Framework (TOGAF)
Gatner
Federal Enterprise Architecture (FEA)
Comparison
Definitions

3. TOGAF – Components of Foundation Architecture

4. 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.

5. Architecture Development Cycle - ADM

6. Summary

8. ADM - Framework and Principles
Irma, CIO
Teri, TOGAF Consultant
Bret, Business Manager
Framework and Principles
Define architecture principles that drive technological architectures and document those.
Choose framework and customise.
Request for Architecture Work

9. Preliminary phase defines “where, what, why, who, and how we do architecture” in the enterprise concerned.
The main aspects are as follows:
• Defining the enterprise.
• Identifying key drivers and elements in the organizational context.
• Defining the requirements for architecture work.
• Defining the architecture principles that will inform any architecture work

11. ADM - Architecture Vision
A Architecture Vision
Define the scope of the architecture project
Define high level business requirements
Statement of architecture work/architectural vision, to be approved by Stakeholders
Architecture Vision defines what is in and what is outside the scope of the architecture effort and the constraints
that must be dealt with.
The constraints will normally be informed by the business principles and architecture
principles, developed as part of the Preliminary phase.

13. ADM – Business Architecture
B Business Architecture
Teri, TOGAF Consultant
Bret, Business Manager
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.
Detailed baseline and target business architecture and full analysis of the gaps between them.

14. Business Architecture
The role of the Business Architecture is to define how to achieve the goals and drivers, and the metrics for success.
Activity models (BPMN & Class Models)

15. ADM: Informations Systems Architecture – Data & Applications
C Information System Architecture
Applications Architecture
Data Architecture
Management
Teri, TOGAF Consultant
Irma, CIO
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.
Target information and application architecture.

16. Data Architecture (Class Diagram)

17. Data Architecture (Data Dissemination)

18. Data Architecture (Data Dissemination)
The purpose of the data dissemination diagram is to show the relationship between data entities, business services, and application components.
The diagram shows how the logical entities are to be physically realized by application components. This allows effective sizing to be carried out and the IT footprint to be refined.

19. Data Architecture (Data Security)
The purpose of the data security diagram is to depict which actor (person, organization, or system) can access which enterprise data. 

21. Data Life Cycle Diagram
The Data Lifecycle diagram is an essential part of managing
business data throughout its lifecycle from conception until
disposal within the constraints of the business process.

22. Application Architecture
The goal of Application Architecture is to define what kinds of application systems are relevant to the enterprise, and what those applications need to do in order to manage data and to present information to the human and computer actors in the enterprise.
The applications are not described as computer systems, but as logical groups of capabilities that manage the data objects in the Data Architecture and support the business functions in the Business Architecture.
The applications and their capabilities are defined without reference to particular technologies

26. ADM: Technical Architecture
D Technology Architecture
Management
Teri, TOGAF Consultant
Irma, CIO
The objective is to define the technology and technical services that will form the basis of the following implementation work.
Complete technical architecture: the infrastructure necesary to support the proposed new architecture.

28. ADM: Opportunities and Solutions
E Opportunities and Solutions
Management
The first phase directly concerned with implementation
How to close the gaps?
Identify implementation projects
Focus on projects that will deliver short term payoffs, e.g. the organisational pain points such as difficulties in completing regional /warehouse specialisation and unreliability in data sharing.

29. ADM: Migration Planning
Prioritize between implementation projects
i.e. project portfolio management
Cost and benefit analysis
Risk assessment
Management
F Migration Planning

30. Data Migration
* The purpose of the Data Migration diagram is to show the flow of data from the source to the target applications.

31. ADM: Implementation Governance
G Implementation Governance
Management
Architectural contract.
Ensure compliance with the defined architecture.
Implementation specifications – acceptance criteria.
Architectural specifications for the implementation projects.

32. ADM: Architectural Change Management
H Architecture Change Management
Management
Handle architecture change requests
Suggest new architecture projects

33. ADM: Requirements Management
Handling new and changing requirements from architecture projects, IT projects, change projects, operations, etc.
Ready to start the phase again.
One of the goals of the first cycle should be information transfer so that Teri's consultancy services are required less in the next cycle.

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

36. 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.

37. 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
Information specialist
Common understanding
Technology Implementers

38. x
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.

39. 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

40. 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

41. 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

42. 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.

43. 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

44. Organise Architecture Effort - Activities
State the goals
Scoping
Buy-in and commitment
Stakeholder analysis
Set time box
Establish EA team

45. CRV - from strategy to business requirements
Cath, CEO
Greg, Gartner Consultant
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
TDT4252, Spring 2012
Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA

46. Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
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
Environmental
Trends
Enterprise
Strategies
Business
Requirements
Change
Information
Technology
Solutions
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
TDT4252, Spring 2012
Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA

47. Gartner’s 4 Architectural Viewpoints (1)
Bret, Business Manager
Greg, Gartner Consultant
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
Irma, CIO
Greg, Gartner Consultant
TDT4252, Spring 2012
Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA

48. 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.
TDT4252, Spring 2012
Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA

49. Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
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.
TDT4252, Spring 2012
Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA

50. 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).
TDT4252, Spring 2012

51. What is FEAF? (Cont…)
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.

52. Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Why FEAF?
TDT4252, Spring 2012
Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA

53. Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Value of FEAF
TDT4252, Spring 2012
Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA

54. Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
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).
Reference page 6, FEAF Version 1.1, 1999, CIO.
TDT4252, Spring 2012
Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA

55. Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
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.
Reference page 6, FEAF Version 1.1, 1999, CIO.
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.
TDT4252, Spring 2012
Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA

56. Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
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.
TDT4252, Spring 2012
Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA

57. 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.

58. 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.

59. Discussion and example case
FEA and FEAF were originally designed for the federal US government.
Can FEA be applied to private enterprises?
Cath, CEO
Fred, FEA Consultant
TDT4252, Spring 2012
Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA

60. FEA and MAM-EA Build enthusiasm for MAM-EA.
Fred, FEA Consultant
FEA and MAM-EA
Build enthusiasm for MAM-EA.
Build a governance structure – FEA Project Management Office (PMO).
Create reference models (PRM, BRM, TRM, DRM, SRM) that can be used by all the organisations across MedAMore.
Create a desription of a reference architecture as it applies to MedAMore.
Test drive the segment architecture process.
Analyse and prioritise the segments.
Enterprise Architecture program assessment.
Restart process with a new segment.

61. Comparing EA Approaches

62. How can we choose an EA methodology?
Go through the criteria for comparing and evaluating EA methodologies, that are important for your organisation.
Rate the methodologies.
What you may find out is that you need a blended approach, in which you create your own enterprise architecture, taking parts of different methodologies that provide the highest value for your specific needs.

63. x
Discussions
Several different EA Methodologies, quite different from one another.
Some of the methodologies complement one another, e.g. Zachman framework provides a taxonomy while TOGAF provides a process.
Enterprise architecture is a path, not a destination.
Main goal: to bring alignment to the business side and the technology side.

64. Definitions (1)
Architect—One whose responsibility is the design of an architecture and the creation of an architectural description
Architectural Artifact—A specific document, report, analysis, model, or other tangible that contributes to an architectural description
Architectural Description*—A collection of products (artifacts) to document an architecture

65. Definitions (2)
Architectural framework—A skeletal structure that defines suggested architectural artifacts, describes how those artifacts are related to each other, and provides generic definitions for what those artifacts might look like
Architectural methodology—A generic term that can describe any structured approach to solving some or all of the problems related to architecture

66. Definitions (3)
Architectural Process—A defined series of actions directed to the goal of producing either an architecture or an architectural description
Architecture*—The fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution

67. Definitions (4)
Enterprise Architecture—An architecture in which the system in question is the whole enterprise, especially the business processes, technologies, and information systems of the enterprise
Architectural Taxonomy—A methodology for organizing and categorizing architectural artifacts

68. Definitions (5)
A Taxonomy – The classification of organisms in an ordered system that indicates natural relationships; the science, laws, or principles of classification.

71. Thank You