SIA 1 Module 2: Overview of Enterprise Architecture Frameworks

It is a formal structure of giving you a list of the key elements that key factors we use in enterprise architecture.

Framework

These frameworks are structured approaches to aligning IT systems with business goals. Provides a layered approach to help design, implement, and manage enterprise architecture

Enterprise Architecture

Four Key Characteristics of EA Framework:

-Skeleton/Structure
-Classification of Schema or Ontology
-Thinking Tool
-Management Tool

Acts as the foundational outline that defines
all components and helps identify what is needed within each layer of architecture.

Skeleton/Structure

It is the way of describing the object,
components that makes up and EA and group it together based on its characteristics. Organizes EA components based on shared characteristics, making it easier to understand the elements involved.

Classification of Schema

It is a set of concepts and categories in a subject area or enterprise architecture that shows their properties and the relations between them.

Ontology

Serves as a tool to plan and visualize the EA's
development. Provides flexibility to adapt the EA as the organization evolves, helping decision-makers explore different configurations.

Thinking Tool

Supports organizations in progressing from the current state to a desired target state. Acts as a roadmap, ensuring that the architecture remains aligned with the
organization's strategic needs.

Management Tool

It was developed by John Zachman at IBM in the 1980s. Inspired by the structured methods seen in construction and aviation industries. Known as a "taxonomy," rather than a strict methodology.

The Zachman Framework for Enterprise Architecture

The structure of the Zachman Framework is organized into _______

matrix

It represents different roles

rows (perspective)

It represents key abstractions (or questions)

columns (abstractions)

Roles or perspectives include:

-Planner
-Owner
-Designer
-Builder
-Subcontractor
-Functioning Enterprise

High-level, strategic view of
requirements.

Planner

Focuses on business
requirements and what is needed.

Owner

Provides technical design
perspectives.

Designer

Specifies the components
and materials needed.

Builder

Focuses on detailed
specifications and parts.

Subcontractor

Represents the operational view after implementation.

Functioning Enterprise

Abstractions or questions include:

-What
-How
-Where
-Who
-When
-Why

Defines the material or
data necessary.

What (data)

Outlines processes
and functionality.

How (function)

Determines physical or virtual locations.

Where (network)

Describes roles and responsibilities.

Who (people)

Focuses on timing and schedules.

When (Time)

Examines reasons and objectives.

Why (Motivation)

Advantages of Zachman framework:

-Holistic Enterprise View
-Tool-Independent
-Focus on Decision-Making

Drawback of Zachman framework:

-Complexity
-Unclear relationships
-Lacks Step-by-Step Guidance
-Limited Future Evaluation

Based on the U.S. Department of Defense's
Technical Architecture Framework for
Information Management (TAFIM). Developed and maintained by The Open Group since 1995 and is one of the most popular EA frameworks

The Open Group Architecture Framework (TOGAF)

Core Components of TOGAF:

1. Architecture Capability Framework
2. Architecture Development Method (ADM)
3. Architecture Content Framework
4. Enterprise Continuum & Tools

This part discusses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture practice within an enterprise

Architecture Capability Framework

This is the core of the TOGAF framework. It describes the TOGAF Architecture Development Method (ADM) - a
step-by-step approach to developing an Enterprise Architecture.

Architecture Development Method (ADM)

This part describes the TOGAF content framework, including a structured metamodel for architectural artifacts, the use of re-usable architecture building blocks, and an overview of typical architecture deliverables.

Architecture Content Framework

This part discusses appropriate taxonomies and tools to categorize and store the outputs of architecture activity within an
enterprise

Enterprise Continuum & Tool

Benefits of TOGAF:

1. Standardization and Consistency
2. Alignment with Business Goals
3. Reduces Risk
4. Scalability and Flexibility