1

Zachman Framework for

Enterprise Architecture
2
Background
In 1987, John Zachman published the Zachman Framework for Enterprise
Architecture. He wrote "To keep the business from disintegrating, the concept
of information systems architecture is becoming less of an option and more of
a necessity." With this belief, he created the ZIFA. This organization is a
network of information professionals who understand the lue of EA for
organizations participating in today's global economy. The mission of ZIFA is
to promote the exchange of knowledge and experience in the use,
implementation, and ad ncement of the Zachman Framework for Enterprise
Architecture. This framework is used most frequently for business and industry
information systems.
3
Intent
The Zachman Framework is influenced by principles of classical architecture
that establish a common vocabulary and set of perspectives for describing
complex enterprise systems. This influence is reflected in the set of rules that
govern an ordered set of relationships that are balanced and orthogonal. By
designing a system according to these rules, the architect can be assured of a
design that is clean, easy to understand, balanced, and complete in itself.
Zachman's Framework provides the blueprint, or architecture, for an
organization's information infrastructure.
4
Purpose
The purpose of the framework is to provide a basic
structure which supports the organization, access,
integration, interpretation, development, management,
and changing of a set of architectural representations of
the organizations information systems. Such objects or
descriptions of architectural representations are usually
referred to as Artifacts.
5
Scope
The Zachman Framework describes a holistic model of an enterprise's information
infrastructure from six perspectives: planner, owner, designer, builder, subcontractor,
and the working system. There is no guidance on sequence, process, or
implementation of the framework. The focus is on ensuring that all aspects of an
enterprise are well-organized and exhibit clear relationships that will ensure a complete
system regardless of the order in which they are established.
6

7
Structure
The Zachman Framework is a simple concept with
powerful implications. By understanding any particular
aspect of a system at any point in its development,
system designers c onstruct a tool that can be very
useful in making decisions about changes or
extensions. The framework contains 6 rows and 6
columns yielding 36 unique cells or aspects. This can
be seen in the framework diagram.
8
Based on work by
John A. Zachman
VA Enterprise
Architecture
DATA
What
FUNCTI ON
How
NETWORK
Where
PEOPLE
Who
TI ME
When
MOTI VATI ON
Why
DATA
What
FUNCTI ON
How
NETWORK
Where
PEOPLE
Who
TI ME
When
MOTI VATI ON
Why
SCOPE
(CONTEXTUAL)
Planner
ENTERPRI SE
MODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL
(LOGI CAL)
Designer
TECHNOLOGY
MODEL
(PHYSI CAL)
Builder
DETAI LED
REPRESENTATI ONS
(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTI ONI NG
ENTERPRI SE
SCOPE
(CONTEXTUAL)
Planner
ENTERPRI SE
MODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL
(LOGI CAL)
Designer
TECHNOLOGY
MODEL
(PHYSI CAL)
Builder
DETAI LED
REPRESENTATI ONS
(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTI ONI NG
ENTERPRI SE
Things Important
to the Business
Entity = Class of
Business Thing
Processes
Performed
Function = Class of
Business Process
Semantic Model
Ent = Business Entity
Rel = Business Relationship
Business Process
Model
Proc = Business Process
I/O = Business Resources
Business Logistics
System
Node = Business Location
Link = Business Linkage
Work Flow Model
People = Organization Unit
Work = Work Product
Master Schedule
Time = Business Event
Cycle = Business Cycle
Business Plan
End = Business Objectiv e
Means = Business Strategy
Important
Organizations
People = Major
Organizations
Business
locations
Node = Major
Business Locations
Ev ents Significant
to the Business
Time = Major
Business Event
Business Goals
and Strategy
Ends/Means =
Major Business Goals
Logical Data
Model
Ent = Data Entity
Rel = Data Relationship
Application
Architecture
Proc = Application Function
I/O = User Views
Distributed System
Architecture
Node = IS Function
Link = LineCharacteristics
Human Interface
Architecture
People = Role
Work = Deliv erable
Processing
Structure
Time = System Event
Cycle = Processing Cycle
Business Rule
Model
End = Structural Assertion
Means = Action Assertion
Physical Data
Model
Ent = Segment/Table
Rel = Pointer/Key
System
Design
Proc = Computer Function
I/O = Data Elements/Sets
Technology
Architecture
Node = Hardware/Software
Link = Line Specifications
Presentation
Architecture
People = User
Work = Screen Format
Control
Structure
Time = Ex ecute
Cycle = Component Cycle
Rule
Design
End = Condition
Means = Action
Data
Definition
Ent = Field
Rel = Address
Program
Proc = Language Statement
I/O = Control Block
Network
Architecture
Node = Addresses
Link = Protocols
Security
Architecture
People = Identity
Work = Job
Timing
Definition
Time = Interrupt
Cycle = Machine Cycle
Rule
Design
End = Sub-Condition
Means = Step
Data
Ent =
Rel =
Function
Proc =
I/O =
Network
Node =
Link =
Organization
People =
Work =
Schedule
Time =
Cycle =
Strategy
End =
Means =
Based on work by
John A. Zachman
VA Enterprise
Architecture
DATA
What
FUNCTI ON
How
NETWORK
Where
PEOPLE
Who
TI ME
When
MOTI VATI ON
Why
DATA
What
FUNCTI ON
How
NETWORK
Where
PEOPLE
Who
TI ME
When
MOTI VATI ON
Why
SCOPE
(CONTEXTUAL)
Planner
ENTERPRI SE
MODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL
(LOGI CAL)
Designer
TECHNOLOGY
MODEL
(PHYSI CAL)
Builder
DETAI LED
REPRESENTATI ONS
(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTI ONI NG
ENTERPRI SE
SCOPE
(CONTEXTUAL)
Planner
ENTERPRI SE
MODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL
(LOGI CAL)
Designer
TECHNOLOGY
MODEL
(PHYSI CAL)
Builder
DETAI LED
REPRESENTATI ONS
(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTI ONI NG
ENTERPRI SE
Things Important
to the Business
Entity = Class of
Business Thing
Processes
Performed
Function = Class of
Business Process
Semantic Model
Ent = Business Entity
Rel = Business Relationship
Business Process
Model
Proc = Business Process
I/O = Business Resources
Business Logistics
System
Node = Business Location
Link = Business Linkage
Work Flow Model
People = Organization Unit
Work = Work Product
Master Schedule
Time = Business Event
Cycle = Business Cycle
Business Plan
End = Business Objectiv e
Means = Business Strategy
Important
Organizations
People = Major
Organizations
Business
locations
Node = Major
Business Locations
Ev ents Significant
to the Business
Time = Major
Business Event
Business Goals
and Strategy
Ends/Means =
Major Business Goals
Logical Data
Model
Ent = Data Entity
Rel = Data Relationship
Application
Architecture
Proc = Application Function
I/O = User Views
Distributed System
Architecture
Node = IS Function
Link = LineCharacteristics
Human Interface
Architecture
People = Role
Work = Deliv erable
Processing
Structure
Time = System Event
Cycle = Processing Cycle
Business Rule
Model
End = Structural Assertion
Means = Action Assertion
Physical Data
Model
Ent = Segment/Table
Rel = Pointer/Key
System
Design
Proc = Computer Function
I/O = Data Elements/Sets
Technology
Architecture
Node = Hardware/Software
Link = Line Specifications
Presentation
Architecture
People = User
Work = Screen Format
Control
Structure
Time = Ex ecute
Cycle = Component Cycle
Rule
Design
End = Condition
Means = Action
Data
Definition
Ent = Field
Rel = Address
Program
Proc = Language Statement
I/O = Control Block
Network
Architecture
Node = Addresses
Link = Protocols
Security
Architecture
People = Identity
Work = Job
Timing
Definition
Time = Interrupt
Cycle = Machine Cycle
Rule
Design
End = Sub-Condition
Means = Step
Data
Ent =
Rel =
Function
Proc =
I/O =
Network
Node =
Link =
Organization
People =
Work =
Schedule
Time =
Cycle =
Strategy
End =
Means =
Zachman Framework
9

Zachman Framework
Row 1 Scope
External Requirements and Drivers
Business Function Modeling

Row 2 Enterprise Model
Business Process Models
Row 3 System Model
Logical Models
Requirements Definition
Row 4 Technology Model
Physical Models
Solution Definition and Development
Row 5 As Built
As Built
Deployment
Row 6 Functioning Enterprise
Functioning Enterprise
E luation
1
2
3
4
5
6
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
10
Rows
Scope. Corresponds to an executive summary for a planner who wants an
estimate of the size, cost, and functionality of the system.
Business model. Shows all the business entities and processes and how
they interact.
System model. Used by a systems analyst who must determine the data
elements and software functions that represent the business model.
Technology model. Considers the constraints of tools, technology, and
materials.
Components. Represent individual, independent modules that can be
allocated to contractors for implementation.
Working system. Depicts the operational system.

11
Columns
Who. Represents the people relationships within the enterprise. The design of the
enterprise organization has to do with the allocation of work and the structure of
authority and responsibility. The vertical dimension represents delegation of authority,
and the horizontal represents the assignment of responsibility.
When. Represents time, or the event relationships that establish performance criteria
and quantitative levels for enterprise resources. This is useful for designing the master
schedule, the processing architecture, control architecture, and timing devices.
Why. Describes the moti tions of the enterprise. This reveals the enterprise goals and
objectives, business plan, knowledge architecture, and knowledge design.
What. Describes the entities involved in each perspective of the enterprise. Examples
include business objects, system data, relational tables, or field definitions.
How. Shows the functions within each perspective. Examples include business
processes, software application function, computer hardware function, and language
control loop.
Where. Shows locations and interconnections within the enterprise. This includes
major business geographical locations, separate sections within a logistics network,
allocation of system nodes, or even memory addresses within the system.

12
Framework Rules
Rule 1:
Columns have no order
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
Rule 2:
Each column has a simple, basic model
Rule 3:
Basic model of each column is unique
Rule 4:
Each row represents a distinct view
Rule 5:
Each cell is unique
Rule 6:
Combining the cells in one row forms a
complete description from that view
Basic Model = Entities and Relationships
Entity
Relationship
Entity
13
Zachman Framework Row 1
Scope/Planners View
External Requirements
and Drivers
Business Function
Modeling
Moti tion/Why
Business goals, objectives and performance
measures related to each function
Function/How
High-level business functions
Data/What
High-level data classes related to each
function

People/Who
Stakeholders related to each function

Network/Where
locations related to each function

Time/When
Cycles and events related to each
function

1
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
14
Zachman Framework Row 2
Enterprise Model/Designers View
Business Process Models
Business Function
Allocation
Elimination of Function
Overlap and Ambiguity
Moti tion/Why
Policies, procedures and standards for each
process
Function/How
Business processes
Data/What
Business data

People/Who
roles and responsibilities in each
process

Network/Where
locations related to each process

Time/When
Events for each process and sequencing
of integration and process improvements

2
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
15
Zachman Framework Row 3
System Model/Designers View
Logical Models
Project Management
Requirements Definition
Moti tion/Why
policies, standards and procedures
associated with a business rule model
Function/How
Logical representation of information
systems and their relationships
Data/What
Logical data models of data and data
relationships underlying information
People/Who
Logical representation of access privileges
constrained by roles and responsibilities


Network/Where
Logical representation of the distributed
system architecture for locations
Time/When
Logical events and their triggered responses
constrained by business events and their responses
3
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
16
Zachman Framework Row 4
Technology Model/Builders View
Physical Models
Technology Management
Solution Definition and
Development
Moti tion/Why
business rules constrained by information
systems standards
Function/How
Specifications of applications that operate
on particular technology platforms
Data/What
Database management system (DBMS) type
requirements constrained by logical data models

People/Who
Specification of access privileges to
specific platforms and technologies

Network/Where
Specification of network devices and their
relationships within physical boundaries

Time/When
Specification of triggers to respond to system
events on specific platforms and technologies
4
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
17
Zachman Framework Row 5
As Built/Integrators View
As Built
Configuration Management
Deployment
Moti tion/Why
business rules constrained by specific
technology standards
Function/How
Programs coded to operate on specific
technology platforms
Data/What
Data definitions constrained by physical
data models
People/Who
Access privileges coded to control access
to specific platforms and technologies

Network/Where
Network devices configured to conform to
node specifications
Time/When
Timing definitions coded to sequence
activities on specific platforms and technologies
5
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
18
Zachman Framework Row 6
Functioning Enterprise/Users View
Functioning Enterprise
Operations Management
E luation
Moti tion/Why
Operating characteristics of specific
technologies constrained by standards
Function/How
Functioning computer instructions
Data/What
Data lues stored in actual databases

People/Who
personnel and key stakeholders
working within their roles and responsibilities
Network/Where
Sending and receiving messages

Time/When
Timing definitions operating to sequence
activities

6
Contextual
Conceptual
Logical
Physical
Integrated
Functioning
Contextual
Conceptual
Logical
Physical
Integrated
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
19
Zachman
Framework Portal