Chapter 4

Enterprise
Architecture
Context and
Need for
Architecture
When do we need
an
architecture?
 Context and Need for
Architecture
Do we need an
Architecture?

In s im ple endeavors , for exam ple

construction of a mud hut, a
formal architecture blueprint may
not be needed to ensure
successful construction and
subsequent maintenance
 Context and Need for
Architecture
Do we need an
Architecture?

In simple endeavors, for

example a wood cabin, a
formal architecture blueprint
may not be needed to ensure
successful construction and
subsequent maintenance
 Context and Need for
Architecture
Greater the complexity of
the endeavor, greater is the
necessity of a guiding
blueprint.

Blueprint is als o es s ential to

undertake further development
or make modifications.

For significantly large

endeavors , not only is a
blueprint es s ential, a
phas ed plan/roadmap is a
must.
 Context and Need for
Architecture
Building large, complex, enterprise-
wide information systems without an
enterprise architecture is like trying to
build a city without a city plan.
Can you build a city without a city
plan? Probably Yes.
Would you want to live in such a
city? Probably not.
 Context and Need for
Architecture
Township State Enterprise and Partner Systems

Gated Community Sector ERP, CRM, SCM, …

ERP (FMIS,
Residential Tower Department
HRMS, ….)

Package
Urban House Agency
(HRMS)

Wood Service Module

Cabin Complexity due to Size & Scale
Architecture for Architecture for
Hut Architecture Request Service Delivery Program Information Systems
for Construct ion in State of Enterprise

Dynamics of Change
 Context and Need for
Architecture

Complexity due to Size & Scale

Architecture for Architecture for
Architecture Service Delivery Information Systems
for Construction in State of Enterprise
Enterprise Architecture – A
Recap
Context and Need for
Enterprise
Architecture

Dynamics of Change
Architecture for Architecture for
Architecture Service Delivery Information Systems
for Construction in State of Enterprise
Defining
Enterprise
Architecture
 Defining Enterprise
Architecture
● Enterprise: Any collection of organizations that have common
goals
○ Union Governm ent or S tate Governm ent at broader level
○ Individual M inis try or Department at narrower level

• Enterprise Architecture: Description of

the current and future services, processes
and information systems of the enterprise
aligned with its vis ion.
 W hat is
architecture
• Process of giving structured solution that meets all of the technical and operational requirements
• optimizing common quality attributes such as performance, security, and manageability
W hy Enterprise
Architecture ?
W hy Enterprise
Architecture…
W hy Enterprise
Architecture…
W hy Enterprise
Architecture…
W hy Enterprise
Architecture…
W hy Enterprise
Architecture…
W hy Enterprise
Architecture…
 Do we need enterprise
● Noarchitects?
there are many enterprises that exist without the intervention of a
enterprise architect. However, there are many situations when it is better to
architect an enterprise than to leave the creation and evolution of its
architecture to chance.

● Every enterprise will always have an architecture, its not optional. But we do have
a choice ..whether we manage its evolution or not and how well we manage it.
 Value of Architectural Thinking

• Public transit, schools and parks are • Future-oriented, planned and sustainable
afterthoughts • Common services
• No common services • Principles and standards (fire, safety,
• Inefficient and fragmented master plan)
processes • Higher productivity and effectiveness
• Aesthetically unpleasing • Aesthetically pleasing
• Limited scope for growth
 Enterprise Architecture is Analogous to
City Planning for an Enterprise
Governance Strategy IT Strategy

Aligning Change to Business Need

Enterprise Architecture
Enterprise-wide focus

Governance IS/IT
Architecture Architecture
• Service • Information
• Process • Application Enterprise Architecture: “the city plan”
• People • Technology

Transition Planning
Project focus

IT Solutions
IT Solutions
Government Processes & IT Systems Solution: “the building design”
Thinking Gap

● Bus ines s M ethods are s pecialis ed

(A difference in philos ophy, a dis tinction)
● Technical Contexts are s pecialis ed
(Network Load, Capacity, Growth, Refres h cycles ))
● Business and Technology have
specialists
(Henry Ford and the 1 armed operator, comfortable with the idea of specialisation)
● Com m unication and Language
(The specialists have specialised vocabulary, opaque to those outside, a barrier)
Enterprise Architecture has consistently
failed to deliver to business
(Gartner 2007 75% struggling, 25% in simple environments)

Fram eworks have grown ever m ore

com plex
(Poorly performing teams – Winning the rally race)

Competitive pressure has never been more

(Business is changing daily – the nature of performance changes as well)

So how can Enterprise Architecture

deliver results?
(We will look at being more creative and effective to deal with these problems)

Create, Integrate, Communicate

How to define Enterprise
Architecture
● There is a process of architecting which is prescribed by the discipline of EA.
● It produces outputs that describe the architecture of an enterprise.
● The process of architecting involves, taking stock of the relevant components or building blocks
that make up an enterprise.
● An architect then needs to examine how these components enable or constrain the enterprise
in fulfilling the goals of the enterprise.
● This is done by looking at how the components are organized or configured, how they are used or
how they behave or perform together
How to define Enterprise
Architecture
● Study the enterprise in its current state and how it should be in the future.
● Work out the alternatives for moving from the current state to the future target state.
● Create frameworks to manage the architecture, spell out descriptions of the architecture and
its components and road maps to show the best way to change or improve the architecture.
● Assess the constraints and opportunities, costs, benefits, risks and value in each option to
help decision makers to select the best alternative.
 EA – The Building
Blocks
Strategy & Performance Architecture
Business

Service & Process Architecture

Business Understanding
IT Change Driven by

IT
 Leveraging Enterprise Architecture
Throughout the globe many countries have utilized Enterprise
Architecture approach to successfully undertake transformation journeys

The United States Singapore South Korea Australia

of America

Estonia United Kingdom New Zealand Germany Finland

EA mandated by act
of Parliament

Bangladesh Bhutan Malaysia

EA Leveraged to Plan and Manage
Transformations

Target State

Transition State 2

Transition State 1
 W hy Enterprise
● Robust
Architecture…
This is why We need enterprise Architecture
● Flexible
● Efficient

TO SATISFY MODERN APPLICATION NEEDS

○ Cloud Ready
○ M obile Friendly
 Build, Releas e and Tes t Autom ated
 Quality attributes (Perform ance, S ecurity and Reliability )
○ ROI
■ Reus able as s ets
■ Future proofed ( Device integration, future requirement
etc…)
■ Cos t of Owners hip
 Decisions in Enterprise
● Architecture
Should we use a common set of applications across different programs / services
OR develop independent applications?
● Which systems must we develop / enhance / retire?
● Which data area / elements must we standardize across the enterprise?
● What enterprise-wide interfaces should our systems provide?
● Should we standardize the technology we use?
● What kind and which current or upcoming technologies should we invest in?
 Key Takeaways

• Enterprise architecture:
• is to understand the enterprise on a holistic basis (business, technology and operating environment)
• helps effectively direct the enterprise to deliver strategic goals by aligning business and technology
operations to strategic intent
• We need enterprise architecture to:
• improve service delivery efficiency and scheme implementation effectiveness by improving alignment of business
& technology to strategic intent
• increase agility by making faster changes in response to dynamic business
• increase RoI from technology investments through optimized landscape enabled by common & re- usable
components
</END
 EA
Domains
Enterprise Architecture (EA) encompasses several domains, each focusing on
specific aspects of an organization's structure, processes, and technology. The
commonly recognized domains of Enterprise Architecture include:

 Business Architecture
 Information Architecture
 Technology Architecture
 Application Architecture:
 Security Architecture:
 Integration Architecture:
 1. Business Architecture
● domain
Focuses on understanding and documenting the structure, operations, processes,
and goals of an organization from a business perspective.
● It provides a comprehensive view of what are the business processes,
functions, capabilities, and strategies align with its overall objectives.
● It is all about understanding the “What” part
● Business Architecture domain provides a holistic view of the organization's
business operations, enabling better alignment between business strategy,
processes, technology, and resources.
● It serves as a foundation for driving business transformation, optimizing
operations, and achieving strategic objectives.
 1. Business Architecture
Businessdomain…
Strategy Alignment:
Business Architecture helps ensure that the organization's business strategy is aligned
with its overall objectives, mission, and vision. It identifies the key business drivers and
objectives and ensures that business processes and capabilities are designed to support
them.

Business Processes and Capabilities:

Business Architecture documents the organization's business processes, workflows, and
capabilities. It identifies the sequence of activities required to deliver value to customers
or stakeholders and defines the capabilities needed to execute those processes
effectively.

Organizational Structure: It describes the organization's structure, including its

departments, business units, roles, responsibilities, and reporting relationships.
Understanding the organizational structure is essential for identifying gaps,
redundancies, and areas for improvement.
 1. Business Architecture
domain…
Information Needs and Flows:
Business Architecture defines the information needs of the organization, including the data required to
support business processes and decision-making. It also describes how information flows through the
organization and how it is captured, stored, processed, and distributed.

Stakeholder Analysis:
It identifies and analyzes the various stakeholders involved in or impacted by the organization's
operations. This includes internal stakeholders such as employees and management, as well as external
stakeholders such as customers, partners, suppliers, regulators, and competitors.

Business Performance Measurement:

Business Architecture defines key performance indicators (KPIs) and metrics to measure the
performance of business processes, functions, and capabilities. It enables the organization to monitor
its performance, identify areas for improvement, and make informed decisions.
 2. Information Architecture
● domain
Focuses on managing and organizing data, information, and knowledge within
an organization to support its business objectives and decision-making
processes.
● Information Architecture plays a crucial role in ensuring that information assets
are well-structured, accessible, secure, and aligned with business needs.
● Information Architecture enables organizations to harness the value of their
information assets, improve decision-making, enhance operational efficiency, and
drive innovation.
● It aligns data management practices with business goals and supports
the organization's digital transformation journey.
 2. Information Architecture
Datadomain…
Governance:
Information Architecture establishes policies, standards, and procedures for managing
data assets across the organization. It defines roles and responsibilities for data
stewardship, data quality management, data security, and compliance with regulatory
requirements.

Data Modeling and Management: It involves designing and implementing data models
that represent the structure, relationships, and semantics of data within the organization.
This includes defining entities, attributes, and their interdependencies to support
effective data management and analysis.

Data Integration and Interoperability: Information Architecture ensures that data flows
seamlessly across different systems, applications, and platforms within the organization.
It defines data integration strategies, data exchange formats, and data synchronization
mechanisms to enable interoperability and data consistency.
 2. Information Architecture
domain…
Metadata Management:
It involves managing metadata, which provides context and descriptive information
about data assets, such as their source, format, usage, and meaning. Information
Architecture establishes metadata standards, taxonomies, and classifications to
facilitate data discovery, understanding, and governance.

Master Data Management (MDM):

Information Architecture defines M D M strategies and processes for managing critical
data entities (e.g., customer, product, employee) consistently across the organization.
M D M ensures data quality, accuracy, and integrity by establishing a single source of
truth for master data.

Information Security and Privacy: It addresses security and privacy concerns related to
information assets, including sensitive data protection, access control, encryption, and
compliance with privacy regulations (e.g., GDPR, HIPAA). Information Architecture
establishes security policies and controls to mitigate risks and safeguard confidential
information.
 2. Information Architecture
● domain…
Data Analytics and Business Intelligence: Information Architecture supports data
analytics and business intelligence initiatives by providing a foundation for storing,
accessing, and analyzing data effectively. It defines data warehouses, data lakes,
and analytics platforms to enable data-driven decision-making and insights
generation.
● Information Lifecycle Management (ILM): It involves managing the lifecycle of
information assets from creation to archival or disposal. Information Architecture
defines retention policies, data archival strategies, and data purging procedures
to optimize storage resources and ensure compliance with legal and regulatory
requirements.
 3. Technology Architecture
● domain
Focuses on defining the structure, components, standards, and configurations
of technology systems and infrastructure within an organization.
● It provides a blueprint for the design, implementation, and management of
IT resources to support business operations and achieve strategic
objectives.
● Technology Architecture aligns IT capabilities with business needs, ensures
technology investments deliver value, and enables organizations to adapt to
evolving business requirements and technological trends.
● It supports the organization's digital transformation efforts and drives innovation
and competitive advantage.
 3. Technology Architecture domain
… and Infrastructure
Hardware
Technology Architecture defines the hardware components (e.g., servers, storage devices,
network equipment) and infrastructure elements (e.g., data centers, cloud services)
needed to support IT operations. It includes capacity planning, scalability, and resilience
considerations to ensure reliable and robust infrastructure.

Software Systems and Applications

It involves identifying, evaluating, and selecting software systems and applications that
meet the organization's requirements. This includes enterprise applications (e.g., ERP,
CRM), custom-developed applications, off-the-shelf software, and open-source solutions.

Integration and Middleware

Technology Architecture addresses integration challenges by defining middleware
platforms, APIs, and integration patterns to enable communication and data
exchange between disparate systems and applications. It ensures interoperability
and seamless integration across the IT landscape.
 3. Technology Architecture domain
Data…
Management and Storage
It includes defining data management strategies, databases, data warehouses, and
storage solutions to store, retrieve, and manage data effectively. Technology Architecture
addresses data security, privacy, and compliance requirements while optimizing data
storage and access.

Networking and Communication

Technology Architecture designs network architectures, protocols, and communication
channels to facilitate connectivity and data transfer within the organization and with
external entities. It ensures network security, bandwidth optimization, and quality of
service (QoS) for critical applications and services.

Security and Identity Management

It addresses cybersecurity risks and threats by defining security architectures, access
controls, encryption mechanisms, and identity management solutions. Technology
Architecture establishes security policies, standards, and procedures to protect IT
assets and data from unauthorized access and breaches.
 3. Technology Architecture domain
…
Virtualization and Containerization
It includes virtualization technologies (e.g., server virtualization, desktop virtualization)
and containerization platforms (e.g., Docker, Kubernetes) to optimize resource utilization,
improve scalability, and streamline application deployment and management.

Monitoring and Management Tools: Technology Architecture selects and implements

monitoring, management, and automation tools to monitor the performance, availability,
and health of IT systems and infrastructure. It includes tools for network monitoring,
system management, configuration management, and incident response.

Cloud Computing and Services

It involves adopting cloud computing platforms and services (e.g., Infrastructure as a
Service, Platform as a Service, Software as a Service) to leverage on-demand
resources, flexibility, and s calability while optim izing cos ts and im proving agility.
 4. Security Architecture
● domain
Focuses on designing and implementing security controls, measures, and policies
to protect an organization's information assets, systems, and networks from
cybersecurity threats and vulnerabilities.
● It is a critical component of EA, ensuring that security considerations are
integrated into the overall architecture to safeguard the organization's valuable
resources and support its business objectives
● enabling organizations to mitigate cybersecurity risks, protect their assets,
and maintain trust and confidence among stakeholders.
● It ensures that security considerations are integrated into the design and
implementation of enterprise systems and processes, enabling organizations
to operate securely and resiliently in today's evolving threat landscape.
 4. Security Architecture
domain…
Risk Management
Security Architecture involves identifying, assessing, and prioritizing cybersecurity risks to the
organization's assets, including data, applications, infrastructure, and personnel. It includes risk
analysis methodologies to quantify the likelihood and impact of threats and vulnerabilities, enabling
informed decision-making on risk mitigation strategies.

Security Controls and Measures

It includes defining and implementing security controls and measures to mitigate identified risks
effectively. This may involve technical controls such as firewalls, intrusion detection systems,
encryption, access controls, and identity and access management (IAM) solutions, as well as
administrative and operational controls such as policies, procedures, and employee awareness
training.

Security Governance
Security Architecture establishes security governance frameworks, policies, and procedures to ensure
that security initiatives align with business objectives and regulatory requirements. It defines roles and
responsibilities for security management, incident response, compliance monitoring, and security
awareness training to foster a culture of security throughout the organization.
 4. Security Architecture
Security domain…
Standards and Best Practices
It involves defining security standards, guidelines, and best practices based on industry
standards (e.g., ISO 27001, NIST Cybersecurity Framework) and regulatory requirements
(e.g., GDPR, HIPAA). Security Architecture ensures that security controls are implemented
consistently across the organization and comply with relevant standards and regulations.

Threat Intelligence and Monitoring

Security Architecture includes mechanisms for gathering, analyzing, and responding to
cybersecurity threats and incidents. This may involve threat intelligence feeds, security
information and event management (SIEM) systems, and incident response processes
to detect, mitigate, and recover from security breaches effectively.

Identity and Access Management (IAM)

It addresses identity and access management challenges by defining IAM strategies,
architectures, and solutions to manage user identities, authentication, authorization,
and privileges across the organization. IAM controls ensure that only authorized users
have access to the organization's resources and data.
 4. Security Architecture
domain…
Data Protection and Privacy
Security Architecture includes data protection and privacy measures to safeguard sensitive
information and comply with privacy regulations (e.g., GDPR, CCPA). This may involve data
encryption, data masking, data loss prevention (DLP) solutions, and privacy-by-design
principles to protect personal and confidential data from unauthorized access or
disclosure.

Security Compliance and Auditing

It involves establishing mechanisms for monitoring, assessing, and ensuring
compliance with security policies, regulations, and industry standards. Security
Architecture includes regular security assessments, audits, and compliance reviews to
identify gaps, assess effectiveness, and address non-compliance issues proactively.
 5. Integration Architecture
● domain
Focuses on designing and implementing the strategies, patterns, and technologies
for seamlessly connecting and interoperating disparate systems, applications, data
sources, and services within the organization.
● Integration Architecture plays a crucial role in enabling information exchange,
process automation, and collaboration across the enterprise.
● It supports business agility, innovation, and digital transformation by facilitating
integration between diverse systems, applications, and data sources, both within
the organization and with external partners and ecosystems.
 5. Integration Architecture
domain…
Integration Patterns and Styles
Integration Architecture defines standardized patterns and styles for integrating
systems and applications, such as point-to-point, hub-and-spoke, publish-subscribe,
and service- oriented architecture (SOA). These patterns help guide the selection and
implementation of integration solutions based on the specific requirements and
characteristics of integration scenarios.

Middleware Platforms
It involves selecting and implementing middleware platforms, integration brokers,
enterprise service buses (ESB), and messaging systems to facilitate communication
and data exchange between different applications and systems. Middleware provides
the infrastructure and services for routing, transformation, and orchestration of
messages and events across distributed environments.
 5. Integration Architecture
API domain…
Management
Integration Architecture includes API management strategies and platforms for
exposing, managing, and securing APIs (Application Programming Interfaces) that
enable interoperability and integration between systems, applications, and services. API
management encompasses API design, documentation, versioning, security, monitoring,
and monetization to promote API reuse and adoption.

Data Integration and ETL (Extract, Trans form , Load)

It addresses data integration challenges by defining strategies, architectures, and
technologies for extracting, transforming, and loading data from disparate sources into
target systems, such as data warehouses, data lakes, and operational databases. Data
integration solutions ensure the consistency, accuracy, and timeliness of data across the
organization.
 5. Integration Architecture
domain…
Event-Driven Architecture (EDA)
Integration Architecture incorporates event-driven architecture principles and
technologies for building loosely coupled, asynchronous systems that respond to
events and messages in real-time. EDA enables organizations to detect, analyze, and
respond to business events and changes rapidly, supporting agile and event-based
integration patterns.
Service-Oriented Architecture (SOA)
It promotes the design and development of modular, reusable services that
encapsulate business logic and expose functionality through standardized interfaces.
SOA enables organizations to achieve loose coupling, abstraction, and interoperability
between distributed systems, facilitating integration and agility in application
development and deployment.
Enterprise Application Integration (EAI)
Integration Architecture includes EAI solutions and platforms for integrating enterprise
applications, such as ERP (Enterprise Resource Planning), CRM (Customer Relationship
Management), and S C M (Supply Chain Management) systems. EAI enables seamless
data flow and process automation across heterogeneous applications and platforms.
 5. Integration Architecture
domain…
Inter-Organizational Integration
It addresses integration challenges in inter-organizational contexts, such as business-
to- business (B2B) integration and supply chain integration. Integration Architecture
defines standards, protocols, and security mechanisms for exchanging data and
conducting transactions with external partners, customers, and suppliers.

Integration Governance and Standards

Integration Architecture establishes governance frameworks, standards, and policies to
ensure consistency, compliance, and quality in integration initiatives. It includes
governance processes for managing integration assets, defining integration patterns,
enforcing security and compliance requirements, and resolving integration-related
issues and conflicts.
 6. Application
● Focuses onArchitecture
the design and structure of individual software applications or
systems within an organization.
● It entails the identification, definition, and specification of the components,
interactions, and behaviors of software applications to meet business
requirements effectively
 6. Application
Component Architecture…
Identification
Application Architecture involves identifying the key components of an application,
including user interfaces, business logic, data access layers, integration points, and
external dependencies. Each component serves a specific function within the
application.

Component Interaction
It defines how the components of an application interact with each other to perform
tasks and achieve business objectives. This includes specifying communication
protocols, data exchange formats, and message flows between components.

Design Patterns and Principles

Application Architecture leverages design patterns and architectural principles to
guide the design and implementation of software applications. Common patterns
include MVC (Model-View-Controller), MVVM (Model-View-ViewModel), and
microservices architecture.
 6. Application
Architecture…
Scalability and Performance
It addresses scalability and performance requirements by designing applications to
handle increasing workloads and user demands. This involves optimizing resource
usage, implementing caching mechanisms, and designing for horizontal scalability.

Security and Compliance

Application Architecture incorporates security and compliance requirements into the
design of software applications. This includes implementing authentication,
authorization, encryption, and auditing mechanisms to protect sensitive data and
ensure regulatory compliance.

Integration and Interoperability

It defines how applications interact with other systems and services within the
organization's IT ecosystem. This includes defining APIs, message formats, and
data exchange protocols to enable seamless integration and interoperability.
 6. Application
Deployment Architecture…
and Hosting
Application Architecture considers deployment and hosting options, including on-
premises infrastructure, cloud platforms, and hybrid environments. It defines
deployment architectures and strategies to ensure applications are deployed efficiently
and reliably.

Resilience and Fault Tolerance

It designs applications to be resilient to failures and faults, ensuring continuity of
service and minimizing downtime. This involves implementing redundancy, failover
mechanisms, and graceful degradation strategies.

Lifecycle Management
Application Architecture addresses the entire lifecycle of software applications, from
design and development to deployment, maintenance, and retirement. It includes
defining processes, tools, and best practices for managing application development and
support activities.
User Experience (UX) Design Application Architecture considers the user experience
and usability aspects of software applications. This includes designing intuitive user
interfaces, optimizing performance, and ensuring accessibility for diverse user groups.
Enterprise
Architecture
Frameworks
 EA Framew orks
Overview EA Frameworks typically include:
TOGAF • Processes & methods
• Catalogue of architecture deliverables and artifacts
• Content model and repository structure
Gartner FEA
• Reference models
• Best practices, guidelines & techniques
Zachman • Architecture capability development
• Architecture governance & compliance
 EA Frameworks
1987 Evolution
1994 1996 2002 2003 2006 2009 2017 2018
Zachman’s TAFIM Clinger – FEA TOGAF 8.0 FEA TOGAF 9 IndEA TOGAF 9.2
Enterprise released Cohen Bill replaces Enterprise completed released created released
Activity
Architecture passed FEAF Edition (~)
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 The Open Group A federal enterprise Gartner Methodology is
is an Enterprise Ontology Architecture Framework architecture (FEA) provides a based on the amalgamation
which provides a formal (TOGAF) is a framework common approach for the of Gartner framework and
and structured way of for enterprise architecture integration of strategic, Meta architecture
viewing and defining an which provides an business and technology development process.
enterprise. approach for designing, management as part of
planning, implementing, organization design and
and governing an performance improvement
enterprise’s architecture
 Zachman Framew ork
● (1/2)
Schema - the intersection between two classifications:
○ First: Primitive interrogatives – What, How, When, Who, Where, and
Why.
○ Second: Derived from the transformation of an abstract idea into an
instantiation – Identification, Definition, Representation,
Specification, Configuration and Instantiation
Zachman Framew ork
(2/2)
The Open Group Architecture Framework (TOGAF)
(1/2)

● Detailed m ethod and a s et of s upporting tools for developing an

enterpris e architecture.
● Based on an iterative process model called Architecture Development Method (ADM)
● TOGAF is developed and maintained by members of The Open Group
The Open Group Architecture Framework (TOGAF)
(2/2)
 Federal Enterprise Architecture (FEA)
(1/2)
● Supports planning and decision-making in US Federal Govt. through documentation
and information providing an abstracted view of enterprise at various levels of scope
and detail.
● Core is Consolidated Reference Model (CRM) – set of 5 interrelated reference models
● Also provides Collaborative Planning Methodology – a simple, repeatable process to
aid planning
Federal Enterprise Architecture (FEA)
(2/2)
Consolidated Reference Model Collaborative Planning Methodology
 Gartner M ethodology
● (1/2)
Gartner methodology believes that EA is about bringing together three constituents:
○ Bus ines s owners
○ Information specialists
○ Technology im plem enters
● According to Gartner, EA project must be started with understanding enterprise direction on
business, not with finding its current position.
 Gartner M ethodology
• The
(2/2)
s equence of future-s tate EA
developm ent activities include
• Develop requirements - identification of the
business-driven requirements
• Develop principles - qualities that must be
exhibited by an enterprise to realize its goals
• Develop models - detailed drilling down of
architecture content

• These activities are meant to convey a logical

sequence of development-based on relationships
and dependencies, rather than a rigidly linear
sequence of events.