The Zachman Framework For Enterprise PDF

Zachman Framework 2 TM
ENTERPRISE
Engineering and Manufacturing
John A. Zachman
Zachman International
2222 Foothill Blvd. Suite 337
La Canada, Ca. 91011
www.ZachmanInternational.com
c 2007 John A. Zachman, Zachman International
THE ENTERPRISE
Agenda
I. Why Zachman Framework2 TM Standards ?
II. Introduction to Changes
A. New Framework Graphic
B. Language Support
C. Reestablish the Forgotten (Implementation) Relationships
III. What Hasn't Changed?
A. The Underlying Theory
B. The Classification Concepts
C. The Normalized Structure of Descriptions
D. The Framework Is an Enterprise Ontology
IV. Internet Standards Support (10/31/07)
A. Graphic Navigation
B. Hyperlinks to Historic Materials and Dictionary Definitions
C. Framework Graphic Printing Capability
D. Official Zachman Framework-related Certifications
E. Access to the other three Meta Framework Standards
V. What's Next?
A. Certifiable Elaborations
B. Licensing
C. Certification (Individuals, Methodologies, Tools, Curriculum, etc.)
VI. Conclusions
Why Framework Standards?

A. CLARIFICATION
More precise expression of the Framework Classification concepts.
B. ENTERPRISE ORIENTATION
As opposed to a systems or technology orientation.
C. CONSISTENCY
Semantic consistency in global communications.
Conceptual consistency within the meta structures.
D. DIFFERENTIATION
Unique vocabulary (to the extent possible) for each of the four
Framework meta structures.
E. ELABORATION
Authorized facility for publishing certified elaborations
(customized versions of the Framework graphic that do not
compromise the concepts of the Framework Classification)
F. CERTIFICATION
Authorized facility for publishing education, methodology, tool
and personal certifications (those curricula, methods, tools,
architects, etc.) that have been evaluated and declared Framework
compliant. c 2005 John A. Zachman, Zachman International
Original Framework Graphic
TM
ENTERPRISE ARCHITECTURE - A FRAMEWORK
DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why
SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events/Cycles List of Business
to the Business Business Performs Significant to the Business Goals/Strategies
SCOPE
(CONTEXTUAL) the Business Operates Important to the Business (CONTEXTUAL)
Planner ENTITY = Class of Process = Class of Node = Major Business People = Major Organization Time = Major Business Ends/Means = Major Business
Goal/Strategy
Planner
Business Thing Business Process Location Unit Event/Cycle
e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan
BUSINESS BUSINESS
System
MODEL MODEL
(CONCEPTUAL) (CONCEPTUAL)
Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner
Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy
e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model
SYSTEM
SYSTEM Architecture Architecture
MODEL
MODEL (LOGICAL)
(LOGICAL)
Node = I/S Function

Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion
Designer Reln = Data Relationship
Designer
I/O = User Views Link = Line Characteristics Work = Deliverable Cycle = Processing Cycle Means =Action Assertion
e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY
TECHNOLOGY
MODEL MODEL
(PHYSICAL) (PHYSICAL)
Node = Hardware/Systems
Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Builder
Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action
DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED
REPRESEN- REPRESEN-
TATIONS TATIONS
(OUT-OF- (OUT-OF
CONTEXT) CONTEXT)
Sub-
Contractor Ent = Field Proc.= Language Statement Node = Address People = Identity Time = Interrupt End = Sub-condition Sub-
Reln = Address I/O = Control Block Link = Protocol Work = Job Cycle = Machine Cycle Means = Step Contractor
FUNCTIONING FUNCTIONING
.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY
ENTERPRISE ENTERPRISE
c 1987-2005 John A. Zachman, Zachman International
2 TM
ZACHMAN FRAMEWORK FOR ENTERPRISES
INTERROGATIVE TARGET
PERSPECTIVES WHAT HOW WHERE WHO WHEN WHY CONTRIBUTORS
SCOPE STRATEGISTS
DATA
EXECUTIVE
BUSINESS List of Things Important LEADERS
SCOPE
to the Business
(CONTEXTUAL)
Planner ENTITY = Class of

Business Thing ARCHITECTS
SYSTEM e.g. Semantic Model
BUSINESS
MODEL
(CONCEPTUAL)
Row 6 equal to all other Rows to resolve Confusion

Owner
TECH-
Ent = Business Entity
Reln = Business Relationship between instances and abstractions. ENGINEERS
e.g. Logical Data Model
NOLOGY
SYSTEM
MODEL
(LOGICAL)
Ent = Data Entity

COMPONENT
e.g. Physical Data Model
TECHNICIANS
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
OPERATIONS
DETAILED
REPRESEN-
T h e (R E A L) E n t e r p r i s e
Ent = Segment/Table/etc.
Reln = Pointer/Key/etc.
e.g. Data Definition
WORKERS
TATIONS
(OUT-OF-
CONTEXT)
(instances)
AUDIENCE cMOTIVATION TARGET
Sub-
PERSPECTIVESEnt = INVENTORY PROCESS NETWORK ORGANIZATION TIMING Sub-
DOMAIN
Contractor Field Proc.= Language Statement Node = Address People = Identity Time = Interrupt End = Sub-condition
e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY
ENTERPRISE c 2007 John A. Zachman, Zachman International ENTERPRISE
Characteristics of Framework Rows
INTERROGATIVE
PERSPECTIVE WHAT HOW WHERE WHO WHEN WHY Outcome TARGET
CONTRIBUTORS
SCOPE
Context
STRATEGISTS
BUSINESS EXECUTIVE
Concepts
LEADERS
SYSTEM Logic
ARCHITECTS
TECH-
NOLOGY
Physics
ENGINEERS
COMPONENT
Elements
TECHNICIANS
OPERATIONS
Reality
WORKERS
TARGET
AUDIENCE INVENTORY PROCESS NETWORK ORGANIZATION TIMING MOTIVATION DOMAINS
PERSPECTIVES
TM
to the Business Business Performs Significant to the Business Goals/Stratgies
SCOPE
INTERROGATIVE
PERSPECTIVES WHAT HOW WHERE WHO WHEN WHY
Node = Major Business People = Major Organization Time = Major Business Ends/Means = Major Business
Business Thing Business Process Location Unit Event/Cycle Goal/Strategy
BUSINESS BUSINESS
System
MODEL MODEL
Columns are named by the Classification interrogatives.

Ent = Business Entity
Reln = Business Relationship
Proc. = Business Process
I/O = Business Resources
Node = Business Location
Link = Business Linkage
People = Organization Unit
Work = Work Product
Time = Business Event
Cycle = Business Cycle
End = Business Objective
Means = Business Strategy
Owner
e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model
SYSTEM
Architecture Architecture
MODEL
MODEL (LOGICAL)
(LOGICAL)
Node = I/S Function

Reln = Data Relationship
Designer
e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY
TECHNOLOGY
MODEL MODEL
Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Builder
DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED
REPRESEN- REPRESEN-
TATIONS TATIONS
(OUT-OF- (OUT-OF
CONTEXT) CONTEXT)
Enterprise model names are now at the bottom of the Column.

FUNCTIONING
FUNCTIONING
e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY
(They are the ENTERPRISE manifestation of the Columnar interrogatives.)

INVENTORY PROCESS NETWORK ORGANIZATION TIMING MOTIVATION

INTERROGATIVE
PERSPECTIVE WHAT HOW WHERE WHO Perspective
WHEN WHY TARGET
CONTRIBUTORS
SCOPE
Scope STRATEGISTS
BUSINESS
Business EXECUTIVE
LEADERS
SYSTEM System ARCHITECTS
TECH- ENGINEERS
NOLOGY Technology
COMPONENT
Component TECHNICIANS
OPERATIONS WORKERS
Operations
TARGET
PERSPECTIVES

Contributors
INTERROGATIVE
AUDIENCE
WHAT
PERSPECTIVE HOW WHERE WHO WHEN WHY ITARGET
TARGET
CONTRIBUTORS
Strategists
SCOPE STRATEGISTS
Executive EXECUTIVE
BUSINESS
Leaders LEADERS
Architects
SYSTEM ARCHITECTS
TECH- ENGINEERS
Engineers
NOLOGY
COMPONENT
Technicians TECHNICIANS
Workers
OPERATIONS WORKERS
TARGET
PERSPECTIVES

TM
to the Business Business Performs Significant to the Business Goals/Stratgies
SCOPE
the Business Operates Important to the Business
INTERROGATIVE (CONTEXTUAL) TARGET(CONTEXTUAL)
PERSPECTIVES WHAT HOW WHERE WHO WHEN WHY CONTRIBUTORS
SCOPE Business Thing Business Process Location Unit Event/Cycle
STRATEGISTS
Goal/Strategy
Planner
BUSINESS BUSINESS
System
MODEL MODEL
Owner Ent = Business Entity Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner
EXECUTIVE
BUSINESS Reln = Business Relationship Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy
LEADERS
e.g. Logical Data Model e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model
SYSTEM
SYSTEM Architecture Architecture
MODEL
MODEL (LOGICAL)
(LOGICAL)
Node = I/S Function

Ent = Data Entity (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion
Designer Designer
SYSTEM Reln = Data Relationship Link = Line Characteristics Work = Deliverable Cycle = Processing Cycle ARCHITECTS
Means =Action Assertion
e.g. Physical Data Model e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY
TECHNOLOGY
MODEL MODEL
TECH- Builder Ent = Segment/Table/etc. Software People = User Time = Execute End = Condition Builder
Reln = Pointer/Key/etc. Link = Line Specifications Work = Screen Format Cycle = Component Cycle ENGINEERS
Means = Action
NOLOGY
DETAILED e.g. Data Definition e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED
REPRESEN- REPRESEN-
TATIONS TATIONS
(OUT-OF- (OUT-OF
CONTEXT) CONTEXT)
Sub-
Contractor Ent = Field Node = Address People = Identity Time = Interrupt End = Sub-condition Sub-
COMPONENT Reln = Address Link = Protocol Work = Job Cycle = Machine Cycle Means = Step Contractor
TECHNICIANS
e.g. DATA e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY
OPERATIONS INVENTORY PROCESS NETWORK ORGANIZATION TIMING MOTIVATION WORKERS
2 TM
ZACHMAN FRAMEWORK FOR ENTERPRISES
WHAT HOW WHERE WHO WHEN WHY CONTRIBUTORS
PERSPECTIVES
SCOPE STRATEGISTS
EXECUTIVE
BUSINESS LEADERS
ARCHITECTS
SYSTEM
ENGINEERS
TECH-
NOLOGY
COMPONENT TECHNICIANS
OPERATIONS
THE ENTERPRISE WORKERS
AUDIENCE TIMING MOTIVATION TARGET

PERSPECTIVES
INVENTORY PROCESS NETWORK ORGANIZATION
DOMAINS

TM
to the Business Business Performs Significant to the Business Goals/Strategies
SCOPE
Goal/Strategy
Planner
Business Thing Business Process Location Unit Event/Cycle
e.g. e.g. e.g. e.g. e.g. e.g
BUSINESS BUSINESS
MODEL MODEL
Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner
All of the Cell instance examples (the "e.g.'s") have been removed.
Reln = Business Relationship
e.g.
I/O = Business Resources
e.g.
Link = Business Linkage
e.g.
Work = Work Product
e.g.
Cycle = Business Cycle
e.g.
Means = Business Strategy
e.g.,
SYSTEM
SYSTEM MODEL
Each Cell now has an absolute name based on the Framework schema.
MODEL
(LOGICAL)
(LOGICAL)
Node = I/S Function

Designer
e.g. e.g. e.g. e.g. e.g. e.g. TECHNOLOGY
TECHNOLOGY
MODEL MODEL
Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Builder
DETAILED e.g. e.g e.g. e.g e.g. e.g. DETAILED

REPRESEN- REPRESEN-
TATIONS TATIONS
(OUT-OF- (OUT-OF
CONTEXT) CONTEXT)
Sub-
FUNCTIONING e.g. FUNCTIONING

e.g. e.g. e.g. e.g. e.g.
THE ENTERPRISE
INTERROGATIVE
PERSPECTIVE WHAT HOW Action WHO WHEN WHY TARGET
CONTRIBUTORS
WHERE
SCOPE
Identify STRATEGISTS
BUSINESS
Define EXECUTIVE
LEADERS
SYSTEM Represent ARCHITECTS
ENGINEERS
TECH-
NOLOGY Specify
COMPONENT
TECHNICIANS
Configure
OPERATIONS WORKERS
Instantiate
TARGET
PERSPECTIVES
THE ENTERPRISE
THE ENTERPRISE
THE ENTERPRISE
THE ENTERPRISE

INTERROGATIVE
PERSPECTIVE WHAT HOW Format
WHERE WHO WHEN WHY TARGET
CONTRIBUTORS
SCOPE STRATEGISTS
Lists
BUSINESS
Constructs EXECUTIVE
LEADERS
SYSTEM Models ARCHITECTS
TECH- ENGINEERS
NOLOGY Drawings
COMPONENT
Listings TECHNICIANS
OPERATIONS WORKERS
Activities
TARGET
PERSPECTIVES

PERSPECTIVE Model
WHAT
Type
HOW WHERE WHO WHEN WHY CONTRIBUTORS
SCOPE STRATEGISTS
Boundary
BUSINESS
Semantic EXECUTIVE
LEADERS
SYSTEM Schematic ARCHITECTS
TECH- ENGINEERS
NOLOGY Blueprint
COMPONENT
Instruction TECHNICIANS
OPERATIONS
Execution WORKERS
TARGET
PERSPECTIVES
Helping Words to help Classify by Row

INTERROGATIVE
AUDIENCE INTERROGATIVE
TARGET
WHAT HOW WHERE WHO WHY
Originators Model Type
PERSPECTIVE
Format Action WHEN
Perspectives Outcome CONTRIBUTORS
PERSPECTIVE
SCOPE STRATEGISTS
Strategists' Boundary Lists Identify Scope Context
VISIONARIES
Executive
BUSINESS
Semantic Constructs Define Business Concepts
EXECUTIVE
Leaders' LEADERS
SYSTEM
Architects' Schematic Models Represent System Logic
ARCHITECTS
TECH-
Engineers'
NOLOGY Blueprint Drawings Specify Technology ENGINEERS
Physics
Technicians'
COMPONENT
Instruction Listings Configure Component Elements
IMPLE-
MENTERS
Workers'
OPERATIONS Execution Activities Instantiate Operations WORKERS
Reality
TARGET
PERSPECTIVES

Helping Words to help Classify by Column
INTERROGATIVE
AUDIENCE TARGET
PERSPECTIVE WHAT HOW WHERE WHO WHEN WHY CONTRIBUTORS
SCOPE
STRATEGISTS
Model Normal- Optimi- Trans- Alloca- Coordin- Aspir-
Objective ization zation porta- tion ation ation
BUSINESS
tion EXECUTIVE
LEADERS
Mech-
anism Counting Tuning Provi- Managing Schedul- Measuring
SYSTEM sioning ing ARCHITECTS
Enterprise
Objective Integrity Quality Capacity Account- Stability Credibility
ability
TECH-
NOLOGY ENGINEERS
Critical
Success Control Yield Resil- Perfor- Response Attainment
Factors ience mance
COMPONENT
TECHNICIANS
Enterprise Inventory Process Network Organi- Timing Motivation

OPERATIONS WORKERS
zation
TARGET
PERSPECTIVES
The "e.g.'s" are now only for the graphic notation of the Cells.
The Cells are absolutely named and defined by the schema,
NOT relatively named and defined by the examples.
THE ENTERPRISE
THE ENTERPRISE
The Total Picture

M D Dv
e ta M ev l D Pr
M etho elopm pmn vlpmn ofessi
od ds/ t t on
els too ent E Work Life C Obje
nv c
ls mt Flow ycle tives
.
PROFESSION FRAMEWORK
M Fw Fw Fw
eta
-m k . k. k F
eta Pr Ge . Op Fwk. wk. O
oc era Cyc
Pr M es omet tion
b
les jective
W od ses ry s
En
oc
ess Netw ork Bus Enter els s
tit
Fl ine pr
y
M o
od rk M ow M ss Cy ise Ob
M
"ZACHMAN FRAMEWORK"
od
e ls od ode cle ject

s ive
el
els ls s
s
ENTERPRISE FRAMEWORK
MACHINE TOOL RAIL CAR
VENDOR
ETC., ETC.
Fu Op
Bi
nc Ge erati Tim Pro

lls
t. o n i d
Sp met g Ins ng Di uct Ob
of
M
ec ry tru agr ject

at
c ti
s. ons ams ives
er
CUSTOMER
ia
l
PRODUCT FRAMEWORK TRUCK
FACILITY COMPUTER
PRODUCT
The Knowledge Base of the Enterprise
2 TM
ZACHMAN FRAMEWORK FOR PROFESSIONS
INTERROGATIVE WHO WHY TARGET
WHAT HOW WHERE WHEN CONTRIBUTORS
PERSPECTIVES
COLLECTION METHOD IDENTIFICATION NETWORK* IDENTIFICATION ORGANIZATION TIMING* IDENTIFICATION MOTIVATION IDENTIFICATION
IDENTIFICATION IDENTIFICATION
PRINCIPLES THOUGHT
LEADERS
PRINCIPLES
COLLECTION PRINCIPLES METHODS PRINCIPLES NETWORK* PRINCIPLES ORGANIZATION PRINCIPLES TIMING* PRINCIPLES MOTIVATION
COLLECTION METHOD DEFINITION NETWORK DEFINITION ORGANIZATION DEFINITION TIMING DEFINITION MOTIVATION DEFINITION
DEFINITION
e.g.. e.g.. e.g.. e.g.. e.g.. ARCHITECTS

PRIMITIVES e.g..
PRIMITIVE ENTITY PRIMITIVE TRANSFORM PRIMITIVE LOCATION PRIMITIVE ROLE PRIMITIVE CYCLE PRIMITIVE END
PRIMITIVE RELATIONSHIP PRIMITIVE INPUT PRIMITIVE CONNECTION PRIMITIVE WORK PRIMITIVE MOMENT PRIMITIVE MEANS
ORGANIZATION TIMING* REPRESENTATION MOTIVATION

COLLECTION METHOD REPRESENTATION NETWORK REPRESENTATION
REPRESENTATION REPRESENTATION
REPRESENTATION
METHOD-
STANDARDS
e.g.. e.g.. e.g.. e.g.. e.g.. OLOGISTS
e.g..
STANDARDS ENTITY STANDARDS TRANSFORM STANDARDS LOCATION STANDARD ROLE STANDARDS CYCLE STANDARDS END
STANDARDS RELATIONSHIP STANDARDS INPUT STANDARDS CONNECTION STANDARDS WORK STANDARDS MOMENT STANDARDS MEANS
COLLECTION METHOD SPECIFICATION NETWORK SPECIFICATION ORGANIZATION TIMING* SPECIFICATION MOTIVATION SPECIFICATION
SPECIFICATION SPECIFICATION
TECH-
TEMPLATES e.g.. e.g.. e.g.. e.g.. e.g.. NOLOGISTS
e.g..
TEMPLATE ENTITY TEMPLATE TRANSFORM TEMPLATE LOCATION TEMPLATE ROLE TEMPLATE CYCLE TEMPLATE END
TEMPLATE RELATIONSHIP TEMPLATE INPUT TEMPLATE CONNECTION TEMPLATE WORK TEMPLATE MOMENT TEMPLATE MEANS
COLLECTION METHOD CONFIGURATION NETWORK CONFIGURATION ORGANIZATION TIMING* CONFIGURATION MOTIVATION CONFIGURATION
CONFIGURATION CONFIGURATION
SPECIALISTS
ARTIFACTS
TOOLING ENTITY TOOLING TRANSFORM TOOLING LOCATION TOOLING ROLE TOOLING CYCLE TOOLING END
TOOLING RELATIONSHIP TOOLING INPUT TOOLING CONNECTION TOOLING WORK TOOLING MOMENT TOOLING MEANS
COLLECTION METHOD INSTANTIATION NETWORK INSTANTIATION ORGANIZATION TIMING* INSTANTIATION MOTIVATION INSTANTIATION
INSTANTIATION INSTANTIATION
PRACTICES
PRACTICE ENTITY
THE PRACTICE
PRACTICE TRANSFORM PRACTICE LOCATION PRACTICE ROLE PRACTICE CYCLE PRACTICE END
PROFES-
SIONALS
PRACTICE RELATIONSHIP PRACTICE INPUT PRACTICE CONNECTION PRACTICE WORK PRACTICE MOMENT PRACTICE MEANS
AUDIENCE COLLECTION COMMUNITY TARGET

PERSPECTIVES
METHOD PLACEMENT PHASE RATIONALE
DOMAINS
2 TM
ZACHMAN FRAMEWORK FOR PRODUCTS
PERSPECTIVES
MATERIAL IDENTIFICATION FUNCTIONALITY GEOMETRY IDENTIFICATION USER IDENTIFICATION TIMING IDENTIFICATION PURPOSE IDENTIFICATION
IDENTIFICATION
OPPOR- INVENTORS
TUNITY
OPPORTUNITY MATERIAL OPPORTUNITY FUNCTIONALITY OPPORTUNITY GEOMETRY OPPORTUNITY USERS OPPORTUNITY TIMING* OPPORTUNITY PURPOSE
MATERIAL DEFINITION FUNCTIONALITY DEFINITION GEOMETRY DEFINITION USER DEFINITION TIMING DEFINITION PURPOSE DEFINITION
e.g. e.g. e.g. e.g. e.g. CUSTOMERS

REQUIRE- e.g.
MENTS
REQUIREMENT ENTITY REQUIREMENT TRANSFORM REQUIREMENT LOCATION REQUIREMENT ROLE REQUIREMENT CYCLE REQUIREMENT END
REQUIREMENT RELATIONSHIP REQUIREMENT INPUT REQUIREMENT CONNECTION REQUIREMENT WORK REQUIREMENT MOMENT REQUIREMENT MEANS
FUNCTIONALITY USER TIMING REPRESENTATION PURPOSE

MATERIAL GEOMETRY REPRESENTATION
REPRESENTATION REPRESENTATION REPRESENTATION
REPRESENTATION
DESIGN
e.g. e.g. e.g. e.g. e.g. ENGINEERS
e.g.
DESIGN ENTITY DESIGN TRANSFORM DESIGN LOCATION DESIGN ROLE DESIGN CYCLE DESIGN END
DESIGN RELATIONSHIP DESIGN INPUT DESIGN CONNECTION DESIGN WORK DESIGN MOMENT DESIGN MEANS
MATERIAL FUNCTIONALITY GEOMETRY SPECIFICATION USER TIMING SPECIFICATION PURPOSE SPECIFICATION

SPECIFICATION SPECIFICATION SPECIFICATION
BUILDERS
PLAN e.g. e.g. e.g. e.g. e.g.
e.g.
PLANNED ENTITY PLANNED TRANSFORM PLANNED LOCATION PLANNED ROLE PLANNED CYCLE PLANNED END
PLANNED RELATIONSHIP PLANNED INPUT PLANNED CONNECTION PLANNED WORK PLANNED MOMENT PLANNED MEANS
MATERIAL FUNCTIONALITY GEOMETRY CONFIGURATION USER TIMING CONFIGURATION PURPOSE CONFIGURATION

CONFIGURATION CONFIGURATION CONFIGURATION
CRAFTSMEN
ASSEMBLIES
PART ENTITY PART COMPONENT PART LOCATION PART ROLE PART CYCLE PART END
PART RELATIONSHIP PART OUTCOME PART CONNECTION PART WORK PART MOMENT PART MEANS
MATERIAL FUNCTIONALITY GEOMETRY INSTANTIATION USER INSTANTIATION TIMING INSTANTIATION PURPOSE INSTANTIATION
INSTANTIATION INSTANTIATION
USES
THE FINISHED GOOD
COMPONENT ENTITY COMPONENTTRANSFORM COMPONENT LOCATION COMPONENT ROLE COMPONENT CYCLE COMPONENT END
CONSUMERS
COMPONENT RELATIONSHIP COMPONENT INPUT COMPONENT CONNECTION COMPONENT WORK COMPONENT MOMENT COMPONENT MEANS
AUDIENCE MATERIAL TARGET

PERSPECTIVES
FUNCTIONALITY GEOMETRY USER TIMING* PURPOSE
DOMAINS
2 TM
ZACHMAN FRAMEWORK FOR CLASSIFICATION
PERSPECTIVES
SET IDENTIFICATION TRANSFORMATION PLACE PEOPLE IDENTIFICATION TIMING IDENTIFICATION MOTIVATION IDENTIFICATION
IDENTIFICATION IDENTIFICATION
CONTEXT THEORISTS
CONTEXT SETS CONTEXT TRANSFORMATIONS CONTEXT LOCATIONS* CONTEXT PEOPLE CONTEXT TIMEING CONTEXT MOTIVATIONS
SET* DEFINITION TRANSFORMATION PLACE DEFINITION PEOPLE DEFINITION TIMING DEFINITION MOTIVATION DEFINITION
DEFINITION
e.g. e.g. e.g. e.g. e.g. OWNERS

CONCEPTS e.g.
CONCEPTS ENTITY CONCEPTS TRANSFORMATION CONCEPTS LOCATION CONCEPTS ROLE CONCEPTS CYCLE CONCEPTS END
CONCEPTS RELATIONSHIP CONCEPTS INPUT CONCEPTS CONNECTION CONCEPTS WORK CONCEPTS MOMENT CONCEPTS MEANS
PLACE PEOPLE REPRESENTATION TIMING REPRESENTATION MOTIVATION

SET*REPRESENTATION TRANSFORMATION
REPRESENTATION REPRESENTATION
REPRESENTATION
DESIGNERS
LOGIC
e.g. e.g. e.g. e.g. e.g.
e.g.
LOGIC ENTITY LOGIC TRANSFORMATION LOGIC LOCATION LOGIC ROLE LOGIC CYCLE LOGIC END
LOGIC RELATIONSHIP LOGIC INPUT LOGIC CONNECTION LOGIC WORK LOGIC MOMENT LOGIC MEANS
SET* SPECIFICATION TRANSFORMATION PLACE SPECIFICATION PEOPLE SPECIFICATION TIMING SPECIFICATION MOTIVATION
SPECIFICATION SPECIFICATION
BUILDERS
PHYSICS e.g. e.g. e.g. e.g. e.g.
e.g.
CONSTRUCTS ENTITY CONSTRUCTS TRANSFORM CONSTRUCTS LOCATION CONSTRUCTS ROLE CONSTRUCTS CYCLE CONSTRUCTS END
CONSTRUCTS RELATIONSHIP CONSTRUCTS INPUT CONSTRUCTS CONNECTION CONSTRUCTS WORK CONSTRUCTS MOMENT CONSTRUCTS MEANS
SET* CONFIGURATION TRANSFORMATION PLACE CONFIGURATION PEOPLE CONFIGURATION TIMING CONFIGURATION MOTIVATION
CONFIGURATION CONFIGURATION
IMPLE-
PIECES MENTERS
ELEMENT ENTITY ELEMENT TRANSFORM. ELEMENT LOCATION ELEMENT ROLE ELEMENT CYCLE ELEMENT END
ELEMENT RELATIONSHIP ELEMENT INPUT ELEMENT CONNECTION ELEMENT WORK ELEMENT MOMENT ELEMENT MEANS
SET* INSTANTIATION TRANSFORMATION PLACE INSTANTIATION PEOPLE INSTANTIATION TIMING INSTANTIATION MOTIVATION INSTANTIATION
INSTANTIATION
CLASSES
THE CLASSIFICATION
TARGET ENTITY TARGET PROCESS TARGET LOCATION TARGET ROLE TARGET CYCLE TARGET END
PARTICI-
PANTS
TARGET RELATIONSHIP TARGET OUTCOME TARGET CONNECTION TARGET WORK TARGET MOMENT TARGET MEANS
AUDIENCE TARGET
PERSPECTIVES SET TRANSFORMATION POSITIONING PEOPLE TIMING* REASON
DOMAINS
Concluding Thoughts on Intro to Changes

I. What has Changed?
A. Column Names - Communications Interrogatives and Enterprise Manifestations
B. Row Names - Audience/Contributor Roles
C. Cell Names - Removed e.g.'s. Absolute names based on Schema
D. Row 6 - Provision for Instances and Examples (to differentiate from Cell
abstractions)
E. Meta Model relates every Row to Row 6 for traceability and alignment
F. Meta Entity Names - more precise and more business oriented
G. Cell graphic icons now have e.g.'s
H. Row 1 meta-entities are Mass Nouns (Column Names)
I. Modeling objectives by Row (Identification, Definition, etc.)
J. No adjectives used in the Framework graphic
K. Dictionary definition for every word
L. Helping words to classify by Row.
M. Helping words to classify by Column
N. Every Framework graphic is generated from the Repository metamodel (one
authorized, consistent source for every Framework graphic (no unauthorized
variations) ... however, with provision for "certified" local elaborations.
O. The Framework graphic can be printed in any form (slide, placemat, poster, etc.
from the www.ZachmanInternational.com website.
What has NOT changed
A. The Framework Theory
All descriptive representations can be expressed in terms of Things and
Relationships (i.e. Thing-Relationship-Thing Models).
B. The logic of the Framework
1. A two dimensional classification system - a "schema".
a. Communications Interrogatives (What, How, Where, Who, When and Why)
b. Audience Perspectives (Scope, Business, System, Technologies,
Components and Enterprise)
2. Each intersection (Cell) is a unique, independent variable (Class, Abstraction)
- a "normalized" structure, one (meta) fact in one Cell
3. The Cell context defines the meaning of the Enterprise Models' words.
4. The two-dimensional schema is depicted in matrix form
C. Each "Primitive" Cell Model has two meta (meta, meta) entities a "Thing" and a
"Relationship".
D. Comprehensive and Complete
The classification on both axes is comprehensive and complete - therefore, the
intersections (Cells) have to be comprehensive and complete.
The Framework is a classification theory about the nature of an Enterprise and the kinds
of "Things" (entities) that have existence in an Enterprise. Therefore, the Framework is
an ENTERPRISE ONTOLOGY
Reestablishing the Forgotten

Implementation Relationships
1. Integration Relationships (Horizontal)
"The integration of all Cell models in a Row constitute the complete
Enterprise model from the Row's Perspective" (1992 Systems Journal article)
2. Transformation Relationships (Vertical)
Meta entities are related to the Cell above and the Cell below (for
"alignment") and meta entities of each Row are related to Row 6 (instances)
for "traceability".
3. (For completeness) Meta entities are related to themselves within each Cell.
4. Tight integration between the four meta Frameworks
The Row 2 models of one Framework are the "meta" models of all the Cells of
another Framework.
Three dimensional models are required to visualize the Integration and Transfor-
mation relationships - these are the IMPLEMENTATION COMPOSITES.
A. Hexagon
B. Hexagon Row inside the Row above (Box within a box)
C. Hologram
Integration Relationships
THE ENTERPRISE
Integration Relationships
Two-dimensional
Framework
Integration
Relationships Inventory
Pr
on
oc
ti
va
es
ti
s
Mo
Implementation
Tim
Composites
ing
ork
Architectural
tw
Ne
Primitives
Organization
The Enterprise
(Total aggregate
set of composites)
Transformation Relationships
THE ENTERPRISE
Transformation Relationships
(Vertical Alignment)
ENTERPRISE
Row 4
Row 3
Row 2
Mo
s
tiv
es
ati
oc
on
Pr
Inventory

"Association" Relationships
THE ENTERPRISE
Tight Integration Between 4 Frameworks

M
eta M Deve Dvlp Dv Prof
M etho lopm mnt lpmn ession
od d Wo t Li Obj
els s/too ent E rk fe e
ls nv Flo Cycl ctives
mt w e
PROFESSION . FRAMEWORK
M
eta F
-m wk. Fwk. Fwk Fw F
eta Pr Ge . O k . wk
oc p C .
Pr
M
od ess omet erat ycles Object
oc W E es ry ion ives
En
ess Netw ork Busin nterp els s

tit
M ork Flow ess C rise O

y
"ZACHMAN FRAMEWORK"
M
od
els Mod Mod ycles bjecti
od
els v es
el
els
s
ENTERPRISE FRAMEWORK
MACHINE TOOL RAIL CAR
VENDOR
ETC., ETC.
Fu Op
Bi
e ra
nc G t Ti Pr
lls
t. eom ing I ming oduct

of
Sp e tr nst D O
ruc iagra bject
M
ec y ives
at
CUSTOMER s. tio ms
er
ns
ia
PRODUCT FRAMEWORK
l
TRUCK
FACILITY COMPUTER
PRODUCT
The Knowledge Base of the Enterprise
The Enteprise is like a hologram.
Inventory Eye
Pr
n
ti o
oc
tiva
es
s
Mo
The
Tim Enterprise
ork
i
ng
tw
Ne
Organization
If you only look at the Enterprise through a single
facet, you see everything relative to that facet.
Internet Standards Support (10/31/07)

A. Graphic Navigation (mouse clicks)
1. To any Framework, any Column, Row, Cell, Primitive Component
2. Horizontal ("integration") Relationships between Primitive
Components for implementations
3. Vertical ("transformation") Relationships between Primitive
Components for alignment
B. Hyperlinks to dictionary definitions for every term appearing in the

Framework graphic
C. Hyperlnks to historic material

1. My first-cut Cell Definitions and Framework Standards that appear in
my eBook, "The Zachman Framework: A Primer for Enterprise
Engineering and Manufacturing"
2. Previously published graphic representations of the Framework
D. Framework graphic printing capability (slides, placemats, posters, etc.)

E. Sample Models (no certified models presently in inventory)
Internet Standards Support (10/31/07) cont.
F. Access to ENTERPRISE Framework Standards plus access to
KNOWLEDGE Framework Standards, PROFESSION Framework
Standards and PRODUCT Framework Standards as they become available
(presently in draft form)
G. Official Zachman Framework-related Certifications

1. For individuals
a. Education records (Education provided by Zachman or by
Zachman-authorized Professionals)
b. Presentation materials
c. Work products
2. Commercial Certifications
a. Method Certifications
b. Tool Certifications
c. Curriculum Certifications
d. Text Book Certifications
3. Framework Metamodel Elaboration Certifications
(No certifications presently in inventory)
What's Next
A. Certification of Elaborations to the Framework Standards
1. Allowable modifications to the Framework metamodel
a. Graphic icons (Remembering that there is some elegance to
differentiating the Columns by icon shape, differentiating the
Rows by icon color and retaining some universal
interchangeability.)
b. Synonyms (or, local colloquialisms)
c. Sub-typing of the meta-entities (remembering the
"Thing-Relationship-Thing structuring rules.)
d. Extensions to the metamodel (adding meta entities)
e. Remembering the "dumb-down" rule of elaborations
2. Level of elaboration utilization
a. Unique to local Enterprise
b. Industry usage and acceptance
c. Global Standard (common to all)
3. Any non-certified, unlicensed modification would be a violation of
copyright laws
(Continued on next page) c 2007 John A. Zachman, Zachman International
What's Next (cont)
B. Licensing
1. Personal Use License (some modest maintenance fee)
Provides access to:
a. Enterprise Framework metamodel
b. Enterprise Framework graphic print capability
c. Internet graphic navigation (Frameworks, Columns, Rows, Cells,
Primitive Components)
d. Enterprise Framework Cell definitions
e. Hyperlinked dictionary definitions of all Enterprise Framework
terms
f. Hyperlinks to historical materials
1. First-cut Cell definitions in eBook
2. Previously published Enterprise Framework graphics
g. Certifications for Elaborations
h. Certifications for Individuals
i. Certifications for Methodologies
j. Certifications for Tools
k. Inventory of Sample Models
(Continued on next page) c 2007 John A. Zachman, Zachman International
What's Next (cont)

B. Licensing (continued)
1. Personal Use Licensing (continued)
l. Knowledge Framework Standards (as available)
m. Profession Framework Standards (as available)
n. Product Framework Standards (as available)
2. Student Discount for Personal use License
3. Education Publication License (for textbook or curriculum

employment of the Framework graphic) NO CHARGE
4. Commercial License (for software deployment)

a. Framework graphic as tool interface - $100.00 US per
customer copy
b. Framework metamodel implementation - $1,000.00 US per
customer copy
(Continued on next page)

What's Next (cont)
C. Certifications
1. Education Certifications - attendance at a Zachman-certified

education offering recorded on the ZachmanInternational website
2. All other certifications are billed on a "time and materials" basis

including:
a. Education Curriculum
b. Presentation Materials
c. Elaborations of the Framework Metamodel
d. Work Products
e. Methodologies
f. Tools
g. Articles
h. Books
What's Next (cont)

Note: You can minimize the time and materials costs for Certifications by
utilizing the plethora of supporting resource materials to minimize a
submission's conceptual divergence from the Framework principles
including:
1. My eBook "The Zachman Framework: A Primer for Enterprise

Engineering and manufacturing"
2. The 30 or so Zachman-authored articles
3. The half dozen or so Zachman-authorized articles
4. Zachman-authorized education
5. Framework Standards materials
a. The Cell Definitions
b. The Framework meta-model
6. Certified sample models (as they become available)
7. Etc., etc.

What's Next (cont)
D. Education offerings
In addition to the currently available Zachman-authorized education

offerings including:
Enterprise Architecture Fundamentals - 2 days Zachman
Enterprise Architecture Implementation Strategies - 2 days Locke
Enterprise Architecture Planning Methodology - 3 days
Zachman & Holcman
Enterprise Architecture Integration Methodology - 5 days Finkelstein
There will be a new seminar:

Enterprise Framework Standards and Modeling Workshop - 3 days
Zachman & Locke
E. Tools pending certification:
1. Primitive Model Graphics Tool
2. Framework Model Repository
3. Generalized Enterprise Modeling Language and Primitive Model
Generator
Conclusions
The Zachman Framework itself has not changed. The classifications
on both axes have been employed by humanity for thousands of years.
Within the last five years,

major contributions have been made to the Framework body of knowledge
and
major improvements have been made to the Framework language,
the ENTERPRISE ONTOLOGY.
Proposition: The Zachman Framework Standards including the horizontal, vertical

and meta integrations as depicted in the three dimensional Architectural models
constitute an Enterprise "scale model" and a sufficient, precise definition of
Enterprise Architecture to be foundational for a Scientific Discipline -
ENTERPRISE ENGINEERING AND MANUFACTURING

which, I submit, is
THE ISSUE OF THE CENTURY

The Zachman Framework For Enterprise PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

The Zachman Framework For Enterprise PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Zachman Framework 2 TM

Why Framework Standards?

Node = I/S Function

c 1987-2005 John A. Zachman, Zachman International

Planner ENTITY = Class of

Row 6 equal to all other Rows to resolve Confusion

Ent = Data Entity

c 2007 John A. Zachman, Zachman International

Columns are named by the Classification interrogatives.

Node = I/S Function

Enterprise model names are now at the bottom of the Column.

(They are the ENTERPRISE manifestation of the Columnar interrogatives.)

INVENTORY PROCESS NETWORK ORGANIZATION TIMING MOTIVATION

c 2005 John A. Zachman, Zachman International

SYSTEM System ARCHITECTS

c 2007 John A. Zachman, Zachman International

Characteristics of Framework Rows

c 2007 John A. Zachman, Zachman International

Node = I/S Function

OPERATIONS INVENTORY PROCESS NETWORK ORGANIZATION TIMING MOTIVATION WORKERS

c 2005 John A. Zachman, Zachman International

AUDIENCE TIMING MOTIVATION TARGET

c 2007 John A. Zachman, Zachman International

Node = I/S Function

DETAILED e.g. e.g e.g. e.g e.g. e.g. DETAILED

FUNCTIONING e.g. FUNCTIONING

c 2007 John A. Zachman, Zachman International

SYSTEM Represent ARCHITECTS

c 2007 John A. Zachman, Zachman International

Characteristics of Framework Rows

SYSTEM Models ARCHITECTS

c 2007 John A. Zachman, Zachman International

SYSTEM Schematic ARCHITECTS

c 2007 John A. Zachman, Zachman International

Helping Words to help Classify by Row

c 2007 John A. Zachman, Zachman International

Enterprise Inventory Process Network Organi- Timing Motivation

c 2007 John A. Zachman, Zachman International

The Total Picture

e ls od ode cle ject

MACHINE TOOL RAIL CAR

nc Ge erati Tim Pro

ec ry tru agr ject

PRODUCT FRAMEWORK TRUCK

e.g.. e.g.. e.g.. e.g.. e.g.. ARCHITECTS

ORGANIZATION TIMING* REPRESENTATION MOTIVATION

AUDIENCE COLLECTION COMMUNITY TARGET

e.g. e.g. e.g. e.g. e.g. CUSTOMERS

FUNCTIONALITY USER TIMING REPRESENTATION PURPOSE

MATERIAL FUNCTIONALITY GEOMETRY SPECIFICATION USER TIMING SPECIFICATION PURPOSE SPECIFICATION

MATERIAL FUNCTIONALITY GEOMETRY CONFIGURATION USER TIMING CONFIGURATION PURPOSE CONFIGURATION

AUDIENCE MATERIAL TARGET

e.g. e.g. e.g. e.g. e.g. OWNERS

PLACE PEOPLE REPRESENTATION TIMING REPRESENTATION MOTIVATION

Concluding Thoughts on Intro to Changes

Reestablishing the Forgotten

c 2007 John A. Zachman, Zachman International

Tight Integration Between 4 Frameworks

ess Netw ork Busin nterp els s

M ork Flow ess C rise O

MACHINE TOOL RAIL CAR

t. eom ing I ming oduct

Internet Standards Support (10/31/07)