Introduction to

Enterprise
Architecture
By
Jim S. Jamero, MIT
Sessions
• Session 1: Introduction to Enterprise Architecture
• Session 2: Exploring various EA Frameworks
• Session 3: IndEA Framework
• Session 4: EA Case Study – Land Hub Andhra Pradesh
• Session 4: EA Case Study – University EA Framework
• Session 5: Interactive session involving question and Answers about
Enterprise Architecture and associated
Agenda: Session 1
• Understanding the nexus of Enterprise Architecture
• History & Evolution of Enterprise Architecture
• Components of Enterprise Architecture
• Lifecycle of Enterprise Architecture
• Implementation of EA
• Enterprise Architecture Frameworks
• Zachman Framework
• ToGAF
• IndEA
 Evolution of Government Observed
In the early days... The next steps... Running business needs applications
to be integrated

Moving from departmental stovepipes to citizen

centric approach in service delivery
Transforming and integrating the back office
Collaborative working and information sharing
Product and service innovation
Citizen engagement and inclusion
Automation of manual tasks Application packages (Siloed
Networked form of organization model adding
Apps)
to the complexity
e.g. Payroll, In-House
Enhancing the economic infrastructure and
Development e.g. HR, Financial administration
government Performance
4
Evolution of Government Observed
In the early days... Now …..

5
How are we going to survive this Jungle?
Incompatibilities Problems
 Data between applications Business KPIs are not aligned with Business Vision/ Mission
 User interfaces Organization structure, functions and technology do not align to meet
 Terminologies the business goals
 Workflows Accurate or complete operational data is unavailable when required
 Hardware and software Applications implemented do not integrate / communicate properly
 platforms Business processes are ad-hoc and manual and managing them is time
 Business and IT ! consuming
Technology investments are ad-hoc and not cost effective.
Decision making takes longer time
Data is scattered across departments and information is redundant

6
Enterprise
Architecture

Transformation
Coherence Alignment

Agility
Interoperability

Robustness Scalability

Ability to migrate

7
 Defining Enterprise
Enterprise is a collection of organizations that has a
common set of goals. An enterprise could be a
Government agency, a corporation a single department
or a chain of geographically distant organizations linked
by a common ownership. Enterprises

An extended enterprise frequently includes partners,

suppliers, and customers. If the goal is to integrate an
extended enterprise, then the enterprise comprises the
partners, suppliers, and customers, as well as internal
business units.
A Government consists of multiple ministries,
departments and agencies. All government
organizations, are unified under the common goal to
achieve Digital India vision. Hence, a Government may
be considered as an “Enterprise of Enterprise”.
Enterprise of Enterprises

Source:: TOGAF

8
Defining Enterprise

A collection of
An enterprise has a An evolving and
departments or
shared vision and a transforming business
organizations which
common set of goals entity having a
may be geographically
common ownership
dispersed

It delivers stakeholder
It exists to serve its It follows policies,
services using
stakeholders while guidelines, business
business processes
maintaining its bottom rules and legislative
and multiple IT
lines requirements of
systems
operating geographies
 Defining Architecture
Architecture in context of Enterprise Architecture is fundamental organization of system, embodied in its
components, their relationship to each other and the environment and the principles governing its design
and evolution

- ISO/IEC 42010:2007, Systems and Software Engineering – Recommended Practice for Architectural Description of Software-
Intensive Systems

Architecture

The structure of components, their inter-

A formal description of a system, or a
relationships, and the principles and
detailed plan of the system at a component
guidelines governing their design and
level to guide its implementation.
evolution over time.

10
Defining Enterprise Architecture
A set of descriptive representations relevant for describing an enterprise that is intended
to be created and constitutes the baseline for changing the enterprise once it is created -
John Zachman

The organizing logic for a firm’s core business processes and IT capabilities captured in a
set of principles, policies and technical choices to achieve the business standardization and
integration requirements of the firm’s operating model - MIT Center for Information
Systems Research (CISR)

Enterprise architecture (EA) is a discipline for proactively and holistically leading enterprise
responses to disruptive forces by identifying and analyzing the execution of change toward
desired business vision and outcomes. EA delivers value by presenting business and IT
leaders with signature-ready recommendations for adjusting policies and projects to
achieve target business outcomes that capitalize on relevant business disruptions - Gartner

11
Definition Enterprise Architecture (EA)
• An enterprise architecture (EA) is a conceptual blueprint that defines
the structure and operation of an organization.

• The intent of an enterprise architecture is to determine how an

organization can most effectively achieve its current and perceived
future objectives.

12
Architecture transformation

•Which routes to follow?

• How to organize oneself?
•How to communicate?
• What are the main risks and how can they be reduced?

13
 What is Enterprise Architecture ?
What is Not Enterprise Architecture? What is Enterprise Architecture?
A bunch of hardware, software, and  A shared business and IT vision for the
technical documents describing enterprise organization along with performance
IT benchmarks
 An interoperable and cost effective framework
A one-time effort or a Enterprise Architecture which could transcend, be referenced and used
project for inter-organization discovery and digital
collaboration for effective service delivery to
Business Strategy & stakeholders
 It ensures economies of scale by reusing
IT Governance
Business and Application Services, by the use of
consistent vocabulary in Business, Data,
Application and Technology layers by specifying
A set of artefacts, or documents generated by the interoperability requirements in terms of
architects that describes current state and future
state architecture or documents generated as open standards and open data formats
part of an EA framework.  It ensures “Single Source of Truth” thereby
avoiding multiple data entry, data duplicity etc

14
Agenda
• Understanding the nexus of Enterprise Architecture
• History & Evolution of Enterprise Architecture
• Components of Enterprise Architecture
• Lifecycle of Enterprise Architecture
• Implementation of EA
• Enterprise Architecture Frameworks
• Zachman Framework
• ToGAF
• IndEA
 Evolution of Enterprise Architecture

Business systems Early EA – PRISM Modern

Planning BSP and Zachman EA

• Developed by IBM • 1986, PRISM Research service of indexed • TOGAF

systems, first to define Architecture for • FEAF
• BSP information systems plans an enterprise; PRISM EA Framework • DODAF
describe the relationship • 1987, John Zachman of IBM introduced
between organisation, Zachman Framework, who is also
Business processes, Data and considered to be the father of Enterprise
Architecture by many groups.
Information systems

16
Evolution of Enterprise Architecture –
Genesis: Business Systems Planning methodology

17
Evolution of Enterprise Architecture – PRISM
EA Framework

18
Zachman
Framework

19
 Evolution of Enterprise Architecture from
90s
Year 1987 1994 1995 1996 2002 2003 2006 2009 2017
Zachman’s TAFIM TOGAF 1.0 Clinger – FEA replaces TOGAF 8.0 FEA TOGAF 9 IndEA
Enterprise released Enterprise Cohen Bill FEAF Enterprise completed (~) released released
Activity Architecture Edition passed Edition
released released

The development of the above frameworks has paved the way for multiple Nations (Korea, Singapore, UAE, UK and USA) and Industry
(Microsoft and Oracle) to develop their own tailored enterprise architecture frameworks which are being consumed by enterprises.

The Open Group The Federal Enterprise

The Zachman Framework The Gartner Methodology
Architectural Framework Architecture
The Zachman Framework is The Open Group A federal enterprise Gartner Methodology is
an Enterprise Ontology Architecture Framework architecture (FEA) provides based on the amalgamation
which provides a formal and (TOGAF) is a framework for a common approach for the of Gartner framework and
structured way of viewing enterprise architecture integration of strategic, Meta architecture
and defining an enterprise. which provides an approach business and technology development process.
for designing, planning, management as part of
implementing, and organization design and
governing an enterprise performance improvement
information technology
architecture
Source: TOGAF and A comparison of top four EA methodologies, 2007 by Microsoft

20
Agenda
• Understanding the nexus of Enterprise Architecture
• History & Evolution of Enterprise Architecture
• Components of Enterprise Architecture
• Lifecycle of Enterprise Architecture
• Implementation of EA
• Enterprise Architecture Frameworks
• Zachman Framework
• ToGAF
• IndEA
Components of Enterprise Architecture

22
Agenda
• Understanding the nexus of Enterprise Architecture
• History & Evolution of Enterprise Architecture
• Components of Enterprise Architecture
• Lifecycle of Enterprise Architecture
• Implementation of EA
• Enterprise Architecture Frameworks
• Zachman Framework
• ToGAF
• IndEA
 Obtain
Executive
Buy-in and
support
Establish
Maintain the
management
Enterprise
structure and
Architecture
control

Life Cycle of Define

Use the
Enterprise
Architecture Enterprise Architecture
process and
Approach

Architecture
Develop
Develop the
Baseline
sequencing
Enterprise
plan
Architecture
Develop
Target
Enterprise
Architecture
24
Life Cycle of Enterprise Architecture –
Illustration of a government project

25
Agenda
• Understanding the nexus of Enterprise Architecture
• History & Evolution of Enterprise Architecture
• Components of Enterprise Architecture
• Lifecycle of Enterprise Architecture
• Implementation of EA
• Enterprise Architecture Frameworks
• Zachman Framework
• ToGAF
• IndEA
Ecosystem of Enterprise Architecture I

27
Ecosystem of Enterprise Architecture II

28
Enterprise Architecture helps to align the
vision of the project to the implementability

29
30
Business
Layer
Illustrativ
e

31
 EA implementation benefits
Impact Description
Clarity on long term EA focusses on enterprises developing strategic capabilities. It provides a long-term view of
goals the organization’s processes, systems and technologies. This roadmap and blueprint is
enabled through strong Governance and Coordination teams which help the sub-enterprises to
achieve the desired state.
Strategic, responsive EA enables IT investments to be optimized, strategic, responsive, promote alignment,
and optimized IT standardization and re-use of IT assets. This in turn mandates that IT looks at future
investments requirements and capabilities and is designed to maximize reuse and reduce duplication.
Agile EA is viewed as a key enabler by creating, communicating and improving the key
requirements, principles and models that describe an enterprise’s future state and enable its
evolution.

Improve Total Reduced business Faster time-to-

Efficient IT Optimize
Cost of risk associated market for new
Operations procurement
Investment with IT products

Source:: Enterprise Architecture by Open Group and MIT white paper on Enterprise Architecture Landscape in Singapore Government Agencies published on February 2013

32
Increasing the need for Enterprise
Architecture and the roles and responsibilities
of an Enterprise Architect

33
Need for an Enterprise Architecture
Organisational Process Project Portfolio
Organisational Design
and Process Standards Management

Requirement
Project Management System Development
engineering

Include security,
IT Management and integration,
Project Governance
Decision making performance dimension
in the though process

34
Roles and Responsibilities of an EA
The primary role of the Enterprise Architect is to ensure that the respective business, application, data and
technology perspectives are in line with the organisation’s technology and governance strategies, policies and
standards

The Enterprise Architect is responsible for the creation, maintenance and management of IT architecture
models and their lower level components.

Interpret, use and apply information contained within IT architecture to inform a range of business
improvement activities, particularly those involved in the design, development, enhancement and
maintenance of IT support systems

Ensure that the overall ICT architecture is maintained in a coherent manner and that appropriate
considerations are made for its security and quality.

Recommends and participates in activities related to the design, development and maintenance of the Enterprise
Architecture

35
Roles and Responsibilities of an EA
Conducts and/or actively participates in meetings related to the designated project/s, both locally and internationally, with clients
and/or partners

Advises and recommends enterprise architecture strategies, processes and methodologies.

Recommends and participates in the analysis, evaluation and development of enterprise longterm strategic and
operating plans to ensure that the EA objectives are consistent with the enterprise’s long-term business objectives

Shares best practices, lessons learned and constantly updates the technical system architecture requirements based
on changing technologies, and knowledge related to recent, current and upcoming vendor products and solutions

Participates in and manages Architecture Working Groups for the development and maintenance of the EA

Collaborates with all relevant parties in order to review the objectives and constraints of each solution and determine
conformance with the EA. Recommends the most suitable technical architecture and defines the solution at a high level

Recommends and participates in the development of architecture blueprints for related systems
36
Risks associated with Enterprise Architecture
Stringent EA adherence can lead EA creates significant
Extremely cautious about the
to small to significant project dependencies across the entire
defined metrics as they can prove
delays if contingency planning is value chain of the project, may
counter productive
not diligently done lead to bottlenecks

Enterprise Architecture with its Certain solutions might lead to

focus on common solutions increased overall costs of the Often EA is ignored by IT
introduces additional user project due to unseen managers, solution architects
acceptance risks.  parameters like lead to low adoption rates
strategy/technology overhaul

Stakeholders often complain that

Enterprise Architecture is
In practice, enterprise architects
cumbersome. Meetings,
are seldom security experts and
document reviews and training
tend to shy away from security
can distract critical staff from
issues.
their core business
responsibilities

37
Risks associated with Enterprise Architecture
• Inability to rapidly respond to new requirements
• Lack of focus on enterprise requirements
• Lack of common direction and synergies
• Incomplete visibility of the current and future vision
• Inability to predict impacts of future changes
• Increased gaps and architecture conflicts
• Lack of commonality and consistency
• Rigidity, redundancy and lack of scalability and flexibility in the deployed solutions
• Lack of integration, compatibility and interoperability between applications
• Piece-meal and ad hoc software development driven by a tactical and reactive approach

38
 Challenges to EA implementation
Component Description
Awareness and Multiple definitions and EA frameworks are currently existing with their own definitions and
understanding of EA frameworks. EA has evolved from IT hence there is a confusion on whether EA is to solve IT
specific technical problems which enterprises face.
Measuring tangible US Government Accountability Office (US GAO) identifies EA benefits under lower costs,
benefits out of EA enhanced productivity, improved management, and greater interoperability. Benefits of EA
implementation will cut across ministries and departments which leads to difficulty in
establishing the overall benefits. EA implementation and maturity requires significant time to
realize improvements in overall enterprise architecture.

Lack of EA EA implementation requires support of the senior leadership of an enterprise. Typically this
sponsorship would involve direct reporting to CEO (for private entities) and Cabinet Division / Prime Minister
/ President (for nations). Without the support from senior leadership, the mandate for reforms
and transformations through EA is not implementable.
Sustainability Standards and policies associated with EA are linked to the underlying technology and
platforms. With technology refresh, it is important to establish a habit for continuous review
and improvement of the existing EA practices without which the entire process would fail in
three years.

39
Current Challenges in Enterprise Architecture
Rapidly evolving business capabilities,
aggressive implementation deadlines
– Growing projects que, complex
Capabilities development is DRIVEN
project management, limited ability
by resource availability
to extract common requirements for
reusable solutions. Delays in
providing business capabilities

Lack of Architecture governance –

independently evolving architectures
Lack of traceability between business
for Retail and Enterprise development
goals/capabilities/applications
products – competing data and
functionality/information and data
functionality, limited impact and risk
flow/IT infrastructure
analysis, limited emerging
technologies adaptability

40
Agenda
• Understanding the nexus of Enterprise Architecture
• History & Evolution of Enterprise Architecture
• Components of Enterprise Architecture
• Lifecycle of Enterprise Architecture
• Implementation of EA
• Enterprise Architecture Frameworks
• Zachman Framework
• ToGAF
• IndEA
Enterprise Architecture Frameworks

Gartner

IndEA
FEA

42
 Countries who have adopted EA
Standards Oman
Administratio Bhutan White Andhra
Governmen and eGovernmen
Australian NSW Government n on the Net e- Paper on Pradesh
t of Canada Architectures Government t
Document Name Government Enterprise The ABC FedICT e-gov Govern Enterprise Enterprise for Enterprise Architecture State
Architecture Architecture guide of ment Architectur Enterprise
Architectur eGovernmen Architecture Framework
Reference Models Strategy eGovernment Master e e Working t (OeGAF) - A Architecture
in Austria Plan Group (e-Pragati)
Applications Quick Glance
   
New South Wales
Sr. No.   Parameters Australia (Southeastern Austria Belgium Bhutan Canada Denmark Germany New Zealand Oman India
Australian state)

1   Architecture Type Federated Federated Federated Federated NA Federated Federated NA  Federated NA  Federated
2   Methodology FEA TOGAF SOA Paradigm SOA Paradigm TOGAF TOGAF Zachman RM-ODP   TOGAF TOGAF
3 Vision/Mission Y Y Y NA Y Y Y Y Y Y Y
4 Performance Ref Model Y N NA NA N NA NA NA Y N Y
Architecture Ref Models

5 Business Ref Model Y Y NA NA Y Y NA Y Y Y Y

6 Service Ref Model Y N NA NA N NA NA Y N N Y
7 Data Ref Model Y Y NA NA Y Y NA Y Y Y Y
8 Application Ref Model N Y NA NA Y Y NA Y Y Y Y
9 Technology Ref Model Y Y NA NA Y Y NA Y Y Y Y
10 Security Ref Model N N NA NA N NA NA Y Y N Y
11 Governance Ref Model N Y NA NA Y Y NA NA NA NA Y

43
Popular EA Frameworks
 EA Frameworks

TOGAF Focus areas of the four Enterprise

Architecture Frameworks:

Enterprise Architecture • TOGAF – Process Centric

Gartner FEA
Frameworks • FEA – Implementation Centric
• Zachman – Taxonomy/Framework
Centric
Zachman • Gartner – Practice/outcome Centric

Each of the frameworks follow different philosophies as presented in the above table. It is up to the implementing agency to
choose bits and pieces from each of the methodologies, modify and merge them as per their unique set of requirements.

Source:: TOGAF and Gartner Report September 2014

45
 Methods for implementing Enterprise Architecture
In an EA project, Enterprise Architect must select a framework and an implementation methodology. There are
multiple frameworks available, it is important to select one and model it to the organization’s requirements

DODAF ( The
TOGAF ( The
Department Of
Open Group
Defence
Architecture
Architecture
Framework )
Framework )

EAP (Enterprise
Architecture Gartner
Planning )

Zachman Enterprise FEA ( Federal

Enterprise
Framework
Architecture Architecture )

Covered in
this session
46
Zachman Framework
 Zachman Framework
Overview
The Zachman Framework™ is a schema - the intersection between two historical classifications that have
been in use for literally thousands of years. The first is the fundamentals of communication found in the primitive
interrogatives: What, How, When, Who, Where, and Why. It is the integration of answers to these questions
that enables the comprehensive, composite description of complex ideas.

The second is derived from the transformation of an abstract idea into an instantiation that was initially
postulated by ancient Greek philosophers and is labeled in the Zachman Framework™: Identification,
Definition, Representation, Specification, Configuration and Instantiation

The Zachman Framework™ typically is depicted as a bounded 6 x 6 “matrix” with the Communication
Interrogatives as Columns and the levels of abstractions Transformations as Rows. The Framework
classifications are represented by the Cells, that is, the intersection between the Interrogatives and the
Transformations. This matrix would necessarily constitute the total set of descriptive representations that are
relevant for describing something... anything: in particular an enterprise

48
Source:https://www.zachman.com/about-the-zachman-framework
View Points

49
 The Zachman Framework Matrix

Identification, Planner's View

Contextual

Owner’'s View
Definition, Conceptual

Designer’'s
View
Representation,
Logical

Builder'’s View
Specification, physical

Integrator's
Configuration View

Instantiation User's View.

What How Where Who When 50

Why
Source:https://www.zachman.com/about-the-zachman-framework
 The columns do not have any particular order

Each column represents a simple generic model

Although interconnected, the basic model of each column must be unique

Zachman
Framewor Each row defines a unique, distinct perspective

k Rules Each cell is unique and will not contain items from another cell

All cell models in each row constitute a complete model from the perspective of that row

The logic is generic and recursive

51
Source:https://www.zachman.com/about-the-zachman-framework
The Zachman Framework
The Zachman Framework™ is a metamodel and unlike a methodology, does not imply anything about:
• Whether you do Architecture or whether you simply build implementations that is, whether you build Primitive Models,
the ontological, single-variable intersections between the Interrogatives and the Transformations or whether you simply
build ad hoc, multi-variable, composite models made up of components of several Primitive Models
• How you do Architecture: top-down, bottom-up, left to right, right to left, where to start, etc., etc
• The long-term/short-term trade-off relative to instantiating the expression of the components of the object that is, what is
formalized in the short-term for implementation purposes versus what is engineered for long-term reuse
• How much flexibility you want for producing composite models (Enterprise implementations) from your Enterprise
Architecture (primitive models), that is, how constrained (little flexibility) or unconstrained (much flexibility) you make the
horizontal, integrative relationships between the Cell components across the Rows and the vertical, transformational
relationships of the Cell components down the Columns.
• Although these are significant, identifiable, methodological choices, they are not prescriptions of the Framework structure
52
Source:https://www.zachman.com/about-the-zachman-framework
TOGAF Framework
TOGAF- The Open Group Architecture Framework

Overview

The Open Group Architecture Framework (TOGAF) is a

framework for enterprise architecture which provides an
approach for planning, designing, implementing, and
governing an enterprise information technology
architecture

Source:: TOGAF 9.1

54
TOGAF- The Open Group Architecture Framework

9 Components

55
TOGAF- The Open Group Architecture Framework

Architecture Development Method (ADM)

The TOGAF Architecture

Development Method (ADM)
provides a tested and iterative
process for developing EA. It
comprises instituting an
architectural framework,
transitioning, developing
architecture contents, and
governing the comprehension of
architectures.

56
TOGAF-The Open Group Architecture Framework
TOGAF Architecture Domains

Architecture Domains Description

Business Architecture Business Strategy, Governance, Organization and key Business Process
Data Architecture Structure of Organization’s logical and physical data assets and data
management resources
Application Architecture A blueprint of individual application systems to be deployed, their interactions,
and their relationships to the core business processes of the organization
Technology Architecture Software and Hardware capabilities that are required to support the
deployment of business, data and application services. This includes IT
infrastructure, middle ware, networks, communications, processing and
standards

Source:: TOGAF 9.1

57
 TOGAF- The Open Group Architecture Framework

4 Iteration cycles, based on a grouping of phases:

(Architecture Capability )

Architecture governance

(Architecture development)
58
(Transition planning)
TOGAF- The Open Group Architecture Framework

Enterprise Continuum

59
TOGAF- The Open Group Architecture Framework

Architecture Content Framework

60
TOGAF- The Open Group Architecture Framework

Enterprise Repository
Eight Reference Models of IndEA

61
TOGAF- The Open Group Architecture Framework

ADM Guidelines and Techniques

• Guidelines for Adapting the ADM Process
• Ways to apply iteration to the ADM,
• Applying the ADM at different levels of the enterprise,
• Security considerations for the different phases and
• Supporting SOA
• Techniques for Architecture Development
• Architecture Principles,
• Stakeholder Management,
• Architecture Patterns,
• Business Scenarios,
• Gap Analysis,
• Migration Planning Techniques
• Interoperability Requirements,
• Business Transformation Readiness Assessment,
• Risk Management,
• Capability-Based Planning

62
TOGAF-The Open Group Architecture Framework

TOGAF Capability
Framework

Source:: TOGAF 9.1

63
TOGAF-The Open Group Architecture Framework

Source:: TOGAF

64
IndEA Framework
India Enterprise Architecture (IndEA)
IndEA is a framework for developing a holistic architecture treating
the Government as a single enterprise or more realistically, as an
Enterprise of Enterprises, which are functionally inter-related
IndEA is a structured combination of several Reference Models that,
together, enable a boundary-less flow of information across the
length and breadth of the government and facilitate the delivery of
integrated services to the stakeholders
 It is an authoritative reference providing an integrated, consistent
and cohesive view of strategic goals, business services and enabling
technologies across the entire organization

66
IndEA
Whole of Government WoG Level

67
IndEA
Agency Level

68
IndEA
Solution Level

69
IndEA vis-à-vis State Enterprise Architecture
in the National Context

70
Comparison of a few EA frameworks
 Comparison of the frameworks
Preferred
Sr # Criteria Description of Criteria
Framework
Taxonomy
1 How well you can use the methodology to classify the various architectural artifacts? Zachman
Completeness
Process
2 How fully the methodology guides you through a step-by-step process for creating an enterprise architecture? TOGAF
Completeness
Reference-model
3 How useful the methodology is in helping you build a relevant set of reference models.? FEA, TOGAF
Guidance
How much the methodology helps you assimilate the mind-set of enterprise architecture into your organization
4 Practice Guidance Gartner
and develop a culture in which it is valued and used?
How much guidance the methodology gives you in assessing the effectiveness and maturity of different
5 Maturity Model FEA
organizations within your enterprise in using enterprise architecture?
Whether the methodology will focus on using technology to drive business value, in which business value is
6 Business Focus Gartner
specifically defined as either reduced expenses and/or increased income?
Governance How much help the methodology will be in understanding and creating an effective governance model for
7 FEA, Gartner
Guidance enterprise architecture?
Partitioning How well the methodology will guide you into effective autonomous partitions of the enterprise, which is an
8 FEA
Guidance important approach to managing complexity?
Prescriptive How well the methodology guides you in setting up a catalogue of architectural assets that can be reused in
9 FEA
Catalog future activities?
10 Vendor Neutrality How likely you are to get locked-in to a specific consulting organization by adopting this methodology? TOGAF
Information
11 Amount and quality of free or inexpensive information about this methodology. TOGAF
Availability
Length of time you will likely be using this methodology before you start using it to build solutions that deliver
12 Time to Value Gartner
high business value. 72 by Microsoft
Source:: A comparison of top four EA methodologies, 2007
Comparison between EAIM
Concepts : 1.Alignment between Business and IT
Major Aspects of EAIM ( Enterprise Architecture EA concepts are important 2.Importance of Repository
Implementation Methodologies ) for Enterprises 3.Association & Communication among
artefacts
4. EAIM Strategy
Concepts 5. Governance

Modeling : 1.Easy to Use

EA concepts provide basis for 2.Easy to learn
EAIM. Modeling of different 3.Traceability
perspectives of enterprise 4.Consistency
are significant part of 5.Different Views
EAIM modelling 6.Complexity

Process : 1.Requirement
The activities and steps that 2.Step by Step
Modeling Process guide Enterprise Architects 3.Detailed Design
in EA implementation 4.Implementation
5.Guidelines
6.Maintenance

73
Comparison between EAIM

Concept TOGAF DODAF Gartner FEA

Alignment between Business and IT M M M L

Association & Communication among artefacts H M M M
Governance H M M L
Importance of Repository M M M M
EAIM Strategy H H M H
Modeling TOGAF DODAF Gartner FEA
Easy to Use L M M M
Easy to learn L M M M
Traceability H L L M
Legend
Consistency H L L M
L low consideration or high level
Different Views M M L M description
Complexity L L L L
M Medium consideration or little
description
H high consideration or detailed
and clear description

74
Comparison between EAIM

Process : TOGAF DODAF Gartner FEA

1.Requirement H L L L
2.Step by Step M M M M
3.Detailed Design M M M M
4.Implementation M M M M
5.Guidelines H M L H
6.Maintenance M L L M

Legend
L low consideration or high level
description
M Medium consideration or little
description
H high consideration or detailed
and clear description

75
Thank you