™

Inventory Process Distribution Responsibility Timing Motivation

Sets Transformations Networks Assignments Cycles Intentions
I n t e g r a t i o n A l i g n m e n t I n t e g r a t i o n
T 0U]LU[VY`0KLU[PÄJH[PVU 7YVJLZZ0KLU[PÄJH[PVU +PZ[YPI\[PVU0KLU[PÄJH[PVU 9LZWVUZPIPSP[`0KLU[PÄJH[PVU ;PTPUN0KLU[PÄJH[PVU 4V[P]H[PVU0KLU[PÄJH[PVU T
r r
Executive a
n Airplanes Acquire Routes Airline Routes Flight Crews Flight Cycle Aircraft
a
n
Scope
Contexts
Airports Schedule Flights Voice/Data Reservations Pass. Trans. Cycle Utilization

s
Perspective s
Gates Sell Bookings Network Aircraft Maint. Maint. Cycle Car/Bus Market
Seats Reserve Seats Parts Distribution Flight Scheduling Phone Wait Cycle Customer

f Passengers
Bookings
Employees
Fly Airplanes

Repair Facilities
Freight
Airport (Runways,
Terminals, etc.)
Airport Ops
Customer Svc
Marketing
Turnaround Cycle
Deicing Cycle
ATC Cycle
Convenience

Growth f
o Routes
Flights
Develop Markets
Maintain Airplanes
Passenger (Mrkts)
Personnel Dist.
Sales
Flight Dispatch
Tarmac Cycle
Bag Handling Cycle
Market Share
3UR¿WDELOLW\ o
(Business Context r Etc. Etc. Etc. Etc. Etc. Etc.
r :JVWL0KLU[PÄJH[PVU
m m
Planners) a a Lists)
t List: Inventory Types List: Process Types List: Distribution Types List: Responsibility Types List: Timing Types List: Motivation Types t
i i
o o
n n
0U]LU[VY`+LÄUP[PVU 7YVJLZZ+LÄUP[PVU +PZ[YPI\[PVU+LÄUP[PVU 9LZWVUZPIPSP[`+LÄUP[PVU ;PTPUN+LÄUP[PVU 4V[P]H[PVU+LÄUP[PVU
Director Business
Perspective Concepts
(Business Concept )\ZPULZZ+LÄUP[PVU
Owners) Business Entity Business Transform Business Location Business Role Business Cycle Business End Models)
Business Relationship Business Input/Output Business Connection Business Work Product Business Moment Business Means

0U]LU[VY`9LWYLZLU[H[PVU 7YVJLZZ9LWYLZLU[H[PVU +PZ[YPI\[PVU9LWYLZLU[H[PVU 9LZWVUZPIPSP[`9LWYLZLU[H[PVU ;PTPUN9LWYLZLU[H[PVU 4V[P]H[PVU9LWYLZLU[H[PVU

Architect System
Perspective Logic
(Business Logic (System
A System Entity System Transform System Location System Role System Cycle System End A
Representation Models)
Designers) l l
i System Relationship System Input /Output System Connection System Work Product System Moment System Means i
g g
n n
m m
e 0U]LU[VY`:WLJPÄJH[PVU 7YVJLZZ:WLJPÄJH[PVU +PZ[YPI\[PVU:WLJPÄJH[PVU 9LZWVUZPIPSP[`:WLJPÄJH[PVU ;PTPUN:WLJPÄJH[PVU 4V[P]H[PVU:WLJPÄJH[PVU e
n n
Engineer t t Technology
Perspective Physics
(Business Physics (Technology
Technology Entity Technology Transform Technology Location Technology Role Technology Cycle Technology End :WLJPÄJH[PVU4VKLSZ
Builders)
Technology Relationship Technology Input /Output Technology Connection Technology Work Product Technology Moment Technology Means

0U]LU[VY`*VUÄN\YH[PVU 7YVJLZZ*VUÄN\YH[PVU +PZ[YPI\[PVU*VUÄN\YH[PVU 9LZWVUZPIPSP[`*VUÄN\YH[PVU ;PTPUN*VUÄN\YH[PVU 4V[P]H[PVU*VUÄN\YH[PVU

Technician Tool
Perspective Components
(Business Component ;VVS*VUÄN\YH[PVU
Implementers) Tool Entity Tool Transform Tool Location Tool Role Tool Cycle Tool End Models)
T Tool Relationship Tool Input /Output Tool Connection Tool Work Product Tool Moment Tool Means T
r r
a a
n n
Business s Inventory Process Distribution Responsibility Timing Motivation s Operations
Perspective
f
o Instantiations Instantiations Instantiations Instantiations Instantiations Instantiations f
o Instances
r r
(Users) m m (Implementations)
a a

The
t
i
Operations Entities Operations Transforms Operations Locations Operations Roles Operations Cycles Operations Ends
t
i The
Enterprise o
n Operations Relationships Operations In/Outputs Operations Connections Operations Work Products Operations Moments Operations Means
o
n Enterprise
I n t e g r a t i o n A l i g n m e n t I n t e g r a t i o n
Ve r s i o n 3 . 0
What How Where Who When Why
(Data) (Function) (Network) (People) (Time) (Motivation)
© 1987-2011 John A. Zachman, all rights reserved. Zachman® and Zachman International® are registered trademarks of John A. Zachman
 Zachman Framework V3.0 for Enterprise Architecture
V1.0 of the Zachman Framework for Enterprise Architecture evolved from
1987. Over this period various people incorporated inconsistent terminology. To
correct this inconsistency, in October 2008 John Zachman released V2.0 of the
framework. In August 2011 he released V3.0, as illustrated in Figure 1.9.

This clears up a number of misconceptions and misunderstandings that have

occurred over the years with the original version of the Framework (Version 1.0). A
full-size graphic is provided online in PDF and Landscape print mode [1].

The column headings are now more consistent with the interrogatives, which
have been moved to the bottom. The top row of each column provides a broad
example. For instance the What column is about Data and Inventory Sets (as a
broad example at the top); the How column is about Function and Process
Transformations at the top; the Where column is about Network and Distribution
Networks at the top; the Who column is about People and Responsibility
Assignments at the top; the When column is about Time and Timing Cycles at the
top; and the Why column is about Motivation and Motivation Intentions at the top.

The Row naming has also now changed to more meaningful terms:

• Row 1 is now the Executive Perspective on the left—for Business Context

Planners and Identification across the columns; with the right axis showing
this addresses Scope Contexts and Scope Identification Lists in an
enterprise. In the book, we will refer to this row as Scope.
• Row 2 is the Director Perspective on the left—for Business Concept
Owners and Definition across the columns; with the right axis showing this
addresses Business Concepts for Business Definition Models. We will refer
to this row as Business.
• Row 3 is now the Architect Perspective on the left—for Business Logic
Designers and Representation across the columns; with the right axis
showing this addresses System Logic for System Representation Models.
We will refer to this row as System.
• Row 4 is now the Engineer Perspective on the left—for Business Physics
Builders and Specification across the columns; with the right axis showing
this addresses Technology Physics for Technology Specification Models.
We will refer to this row as Technology.
• Row 5 is the Technician Perspective on the left—for Business Component
Implementers and Configuration across the columns; with the right axis
showing this addresses Tool Components for Tool Configuration Models.
We will refer to this row as Components.
• Row 6 is the Business Perspective on the left—for Users of the enterprise
and Instantiations across the columns; with the right axis showing this
addresses Operations Instances and Implementations. We will call this the
Enterprise.

1
The Zachman Framework V3.0 graphic is at http://www.ies.aust.com/EA_Book/ZachmanV3.pdf.
Figure 1.1: Zachman Framework V3.0 for Enterprise Architecture

Notice that there are horizontal lines across the columns to represent integration
and alignment, with double headed arrows down each column between the cells to
signify transformation. We discuss alignment in Chapter 4 and Chapter 8. The
examples in each cell have changed to be more illustrative, with more relevant
terms than in the V1.0 Framework. The result now is a more understandable
graphic for Business and for IT users of the Framework.

In V1.0 we referred to each cell by column number and row number, such as
Column 1, Row 2. In V3.0 we can explicitly identify each cell by the name of each
column and the purpose of each row, such as Inventory Definition in Figure 1.9 (for
Col 1, Row 2) or Process Representation (for Col 2, Row 3). In the book we will
use both of these reference methods to refer to individual cells for both versions of
the Zachman Framework.