Enterprise Architecture

Framework
Grace Kwagalakwe
Enterprise Architecture Framework
 An enterprise architecture framework can describe the underlying
infrastructure, thus providing the groundwork for the hardware, software, and
networks to work together.

 An EA framework supports the integration between Business, Systems and

Technology Architectures, and places them in the context of the support for the
enterprise’s strategic direction.

 An Enterprise Architecture Framework (EAF) maps all of the software

development processes within the enterprise and how they relate and interact
to fulfill the enterprise’s mission. It provides organizations with the ability to
understand and analyze weaknesses or inconsistencies to be identified and
addressed.
Purpose of Enterprise Architecture
Frameworks
 EA frameworks provide structured methodologies, processes, and
guidelines for designing, planning, implementing, and managing an
organization's architecture.

 These frameworks enable organizations to make informed

decisions about their IT investments, ensure alignment with
business goals, and minimize risks.
Enterprise Architecture Framework

To support a synchronized, enterprise-wide perspective, numerous EA

frameworks have been created to provide project structures for
developing a comprehensive EA program. These frame works include;

 Zachman Framework

 The Open Group Architecture Framework (TOGAF)

 Federal Enterprise Architecture Framework (FEAF)

 Department of Defense Architecture Framework (DoDAF)

Enterprise Architecture Framework

Zachman Framework

 Created by John A. Zachman in the 1980s

 Often considered the "father" of enterprise architecture frameworks

 Aims to provide a structured and comprehensive representation of an

organization's architecture.

 The framework defines how perspectives are related according to certain

rules or abstractions.

 Focuses on answering key questions about the organization from different

stakeholder perspectives.
 Components of the Zach man framework
 The Zachman Framework is based on a 6x6 matrix, consisting of six columns (What,
How, Where, Who, When, and Why) and six rows (scope, business model, system
model, technology model, components, and working system).

• What (Data): Describes the information the organization requires to operate

• How (Function): Describes the processes and activities needed to transform inputs into
outputs.
• Where (Network): Describes the locations where the organization operates and the
distribution of resources.
• Who (People): Describes the roles and responsibilities of stakeholders involved in the
organization's activities.
• When (Time): Describes the events and timing constraints affecting the organization's
operations.
• Why (Motivation): Describes the strategic goals, objectives, and drivers of the
organization.
Components of the Zach man framework
 Six perspectives (rows) represent different stakeholder viewpoints:
• Executive (Scope): Provides a high-level, abstract view of the organization's
architecture.
• Business Management (Business Model): Describes the organization's
architecture from a functional and process-oriented perspective.
• Architect (System Model): Focuses on the technical aspects of the
organization's architecture.
• Engineer (Technology Model): Specifies the technology components and their
relationships.
• Technician (Components): Describes the implementation details of the
organization's architecture.
• User (Working System): Represents the actual implementation of the
organization's architecture.
 Advantages of using the Zachman
Framework
 Provides a comprehensive, holistic view of the organization's architecture.

 Facilitates communication and understanding among different

stakeholders.

 Allows for the identification and management of dependencies and

relationships across the organization.

 Promotes consistency and standardization in the development and

management of enterprise architecture.

 Enhances the organization's ability to respond to changes in the business

and technology environments.
 Federal Enterprise Architecture
Framework (FEAF)
 Developed by the United States Federal CIO Council in the late 1990s.

 Aims to provide a common approach to enterprise architecture for

U.S. federal agencies.

 Supports the alignment of IT investments with strategic goals and

objectives.

 Facilitates collaboration, information sharing, and the reuse of IT

assets across federal agencies.
Components of FEAF

FEAF is built around five reference models that describe different aspects of an
organization's architecture.

1. Performance Reference Model (PRM): Describes the performance goals and

objectives of the organization, as well as the measures used to evaluate
progress.

2. Business Reference Model (BRM): Provides a functional view of the

organization's processes and activities, organized into Lines of Business and Sub-
functions.

3. Data Reference Model (DRM): Describes the data and information assets of
the organization, focusing on standardization, interoperability, and the sharing of
data across agencies
Components of FEAF

4. Application Reference Model (ARM): Describes the organization's

applications and systems, as well as the relationships between them.

5. Infrastructure Reference Model (IRM): Describes the organization's

technology infrastructure, including hardware, software, networking, and
security components.
Benefits of using FEAF
 Provides a standardized, consistent approach to enterprise architecture for
federal agencies.
 Supports better decision-making, planning, and resource allocation for IT
investments.
 Facilitates communication and collaboration across agencies, promoting the
sharing of best practices and lessons learned.
 Enhances the ability to identify and manage risks and dependencies across the
organization.
 Promotes the reuse of IT assets, reducing development costs and improving
interoperability.
 Aligns IT investments with strategic goals and objectives, improving overall
performance and effectiveness
 Department of Defense Architecture
Framework (DoDAF)
 Developed by the U.S. Department of Defense (DoD) in the 1990s, with
the latest version (DoDAF 2.0) released in 2010.

 Aims to provide a standardized approach to developing and managing

enterprise architectures for defence and national security
organizations.

 Supports decision-making, risk management, and the alignment of IT

investments with strategic objectives.
Components of DoDAF

 DoDAF consists of a set of Views, Products, and Descriptions that describe

different aspects of an organization's architecture.
1. Views: High-level perspectives that help stakeholders understand and analyze
the organization's architecture.
 All View (AV): Describes the overall context, scope, and relationships among
the organization's architectures.
 Capability View (CV): Focuses on the capabilities required to achieve the
organization's strategic objectives.
 Data and Information View (DIV): Describes the data and information assets
of the organization and their relationships.
 Operational View (OV): Describes the organization's missions, activities, and
processes, as well as their relationships and dependencies
Components of DoDAF

 Services View (SvcV): Describes the services and service components

that support the organization's operations.

 Standards View (StdV): Identifies the technical standards and

specifications that govern the organization's architecture.

 Systems View (SV): Describes the organization's systems and their

relationships, as well as the data and information they process
Components of DoDAF

2. Products: Detailed artifacts that represent specific aspects of the

organization's architecture within each View.

3. Descriptions: Textual explanations that provide additional context

and understanding of the Products and Views.
Advantages of using DoDAF.

 Provides a comprehensive, standardized approach to enterprise architecture

for defence and national security organizations.
 Supports better decision-making, planning, and resource allocation for IT
investments.
 Facilitates communication and collaboration among diverse stakeholders,
including military, civilian, and industry partners.
 Enhances the organization's ability to identify, manage, and mitigate risks and
dependencies.
 Aligns IT investments with strategic goals and objectives, improving overall
performance and mission effectiveness.
 Promotes the reuse of architecture assets and the adoption of common
standards, reducing development costs and improving interoperability
Choosing the right framework for your
organization.
 Consider factors such as the organization's size, industry, complexity, and
specific needs.

 Evaluate the strengths and weaknesses of each framework in the context of

your organization's requirements.

 Recognize that a hybrid approach or customization may be necessary to best

meet your organization's needs.

 Continuously evaluate and adapt the chosen framework as the organization

evolves and grows
Hybrid and Customized Frameworks
 While the discussed frameworks provide comprehensive approaches to
enterprise architecture, organizations may find it necessary to adapt,
customize or combine frameworks to better meet their specific needs.
The combined frameworks are called hybrid or customized
frameworks.

 Hybrid frameworks can offer the benefits of multiple approaches while

addressing unique organizational requirements.
Examples of hybrid frameworks.
1. Combining TOGAF's ADM process with Zachman's classification matrix:
This approach can provide a comprehensive, step-by-step process for
developing and managing enterprise architecture while also offering a
holistic representation of the organization's architecture from different
stakeholder perspectives.

2. Integrating FEAF's reference models with DoDAF's Views, Products,

and Descriptions: This approach can offer a standardized method for
aligning IT investments with strategic goals and objectives while also
supporting decision-making and risk management for organizations within
or similar to the U.S. federal government and defence sectors.
 Factors to consider when creating a
hybrid or customized framework.
 Organizational needs: Assess the organization's specific goals,
challenges, and requirements to determine which aspects of each
framework are most relevant and beneficial.

 Flexibility: Ensure the chosen framework is adaptable to changes in the

organization's business and technology environments.

 Scalability: Consider the organization's size and complexity, and select a

framework that can grow and evolve with the organization.
 Factors to consider when creating a
hybrid or customized framework
 Stakeholder engagement: Engage stakeholders from various parts of
the organization to gather input and ensure buy-in for the chosen
framework.

 Continuous improvement: Regularly evaluate the effectiveness of the

chosen framework, making adjustments and refinements as necessary to
better meet the organization's needs.