ZACHMAN'S FRAMEWORK

G R O U P E | C E 4 - 7
WHAT IS ZACHMAN'S FRAMEWORK?
The Zachman framework was the brainchild of
John Zachman in 1987, becoming a widely used
approach for engineering Enterprise Architecture.
It was published in the system journal of IBM
under the name — A framework for information
systems architecture. The Zachman Framework
isn’t exactly a methodology, mainly because it
doesn’t offer specific processes for handling data.
Instead, it’s considered an “ontology” or “schema”
to help organize enterprise architecture artifacts
such as documents, specifications, and models.
The framework considers who is affected by the
artifact, such as the business owner, and weighs
that against the issue or problem being addressed.
 JOHN A. ZACHMAN
The originator of the “Framework for Enterprise
Architecture” which has received broad
acceptance around the world as an integrative
framework, or “periodic table” of descriptive
representations for Enterprises. Mr. Zachman is not
only known for this work on Enterprise Architecture
but is also known for his early contributions to IBM’s
Information Strategy methodology (Business
Systems Planning) as well as to their executive team
planning techniques (Intensive Planning).
 The Zachman Framework uses 36 categories for
describing anything from products, to services, to
hardware and software. Categories are organized in six
rows by six columns, forming a two-dimensional matrix
with 36 cells that helps you visualize the topic, problem or
product.
ZACHMAN The columns of a Zachman Framework template outline
FRAMEWORK the fundamental questions surrounding the architecture
in question (what, how, where, who, when, and why),
TEMPLATE while the rows represent the perspectives of each type of
stakeholder involved in the project. The finished matrix is
then filled in with processes, necessary materials,
important roles, relevant locations and any goals or rules
associated with the project, based on the fundamental
question and perspective represented in each cell.
ZACHMAN FRAMEWORK TEMPLATE
 SIX ROWS OF THE ZACHMAN
FRAMEWORK MATRIX
01
Planner’s view
(scope)
This row is where you
identify the business plan
or strategy and establish
what issue or concern will
be addressed in the matrix.
02 03
Owner’s view Designer’s view
(business concepts) (system logic)
The second row is where The third row identifies
you will identify business how the plan will meet the
needs and the resources business’ needs. This row
the business will need to corresponds to work done
execute the plan. by systems analysts who
handle the data, process
flows and functions of
business processes.
 SIX ROWS OF THE ZACHMAN
FRAMEWORK MATRIX
04
Engineer’s perspective
(technology physics)
The fourth row includes
relevant information about
how to implement the
strategy and what tools,
technology, materials and
constraints the team will be
working with.
05 06
Technician’s perspective User’s view
(component assembly) (operations classes)
This row is where you will The final row includes
include representations of information about the
requirements for products, functioning system and
services or hardware. how it works in the IT or
business environment.
 SIX COLUMNS THAT REPRESENT THE
INTERROGATIVES OR QUESTIONS THAT ARE
ASKED OF THE ENTERPRISE

01 02 03

What How Where

(data) (function) (network)

This is where you establish The “how” or “function” This column includes the
what business data, column identifies how “where,” which includes all
information and processes work and impact system networks and
requirements are the business. relevant locations where
necessary for the project. business operations take
place.
 SIX COLUMNS THAT REPRESENT THE
INTERROGATIVES OR QUESTIONS THAT ARE
ASKED OF THE ENTERPRISE

04 05 06

Who When Why

(people) (time) (motivation)

In column four you will Column five is where you The final column is where
identify the key will identify when and at you will identify why you
stakeholders and what time business chose the final solution and
determine all of the processes are performed in what the motivation is
relevant personnel for the the company. behind the initiative or
project. project.
ZACHMAN
FRAMEWORK The framework is designed to work with both physical
objects and conceptual ideas. To fill in the matrix’s columns
RULES and rows, you will need to input from stakeholders and will
likely include redundancies and duplicate information. The
goal is to reduce these redundancies as much as possible,
finishing with a concise document that delivers a clear
picture into your organization’s enterprise or IT
architecture. So, Zachman established seven guiding rules
or principles for completing the two-dimensional matrix.
 7 RULES OF THE
ZACHMAN FRAMEWORK

01
Columns have no order, but
should be arranged in top-
down order starting with the
most significant category.
This will be specific to your IT
project or concern and might
change when applied to
another product or service.
You should avoid adding or
removing any columns or
rows, as you will need them
all to gain the complete
picture.
02 03
Lorem ipsum dolor sit The basic model of each
amet, consectetur column must be unique and
adipiscing elit, sed do avoid overlapping or replicating
eiusmod tempor incididunt data in any other column.
ut labore et dolore magna
aliqua. Ut enim ad minim
veniam, quis nostrud
exercitation ullamco laboris
nisi ut aliquip
 7 RULES OF THE
ZACHMAN FRAMEWORK

04 05 06
Each row describes a distinct, If you are successful with Avoid altering the names of
unique perspective. You rules 2, 3 and 4, you should your rows or columns. This can
should avoid having any have a matrix where each change the meaning or cause
meta-models or concepts cell is unique. This is confusion if stakeholders use
ascribed to multiple cells. A strongly emphasized and similar terms differently.
key element of this one of the cornerstones of
framework is that it avoids all this framework, resulting in
redundancies in the final uniquely detailed and
two-dimensional matrix. informative view of your
architecture.
 7 RULES OF THE
ZACHMAN FRAMEWORK

07
The logic is recursive and
generic, which means that it
can be used to classify or
analyze anything related to
the enterprise architecture in
question. It is up to the
analyst to establish the
target and boundaries, and
those decisions can make a
significant impact on the final
outcome of the matrix and
the initiative or project.
 The Zachman framework provides a means of
classifying an organization’s architecture. It is a
proactive business tool, which can be used to
HOW AND model an organization’s existing functions,
WHERE IS THE elements, and processes while helping manage
ZACHMAN business change. The framework draws on
FRAMEWORK Zachman’s experience of how change is
managed in complex products. John Zachman
USED?
stresses that the framework can extend to the
entire enterprise architecture, and is not just
restricted to information architecture.
CONCLUSION:

The Zachman Framework remains relevant for modern businesses

today largely because technology environments have grown
increasingly complex, with legacy technology and information
scattered throughout the organization, often lost to employees who
have moved on to other systems and solutions. With the Zachman
Framework’s 36-column matrix, you can catalogue all your
organization’s architecture, which can help your organization stay agile
and flexible in the face of change by giving you detailed insights into
your company’s IT assets.
THANK YOU
AND
GOD BLESS!