GREEN GREEN Enterprise Enterprise ArchitectureArchitecture

1

ดร.ศศิพร อุษณวศินผอ.หลกัสูตร ป.โท สาขาวศิวกรรมซอฟต์แวร์ (MS.SE)

สถาบันวทิยาการสารสนเทศ (ISIS) มหาวทิยาลยัศรีปทุม

email: sasiporn.us@gmail.com

What is

Enterprise Architecture?2

Simple Answer:

It’s about Strategic Planning� that’s allIt’s about Strategic Planning� that’s all

3

WHAT’S the EA value

proposition?

Answer: A focus on maximizing

investment returns…

4

The most common

misconception?

5

… that it’s a

The most common

misconception?

… that it’s a

function of IT

6

EA is NOT just…

Systems, Information, Service or Solution Architecture

� EAs are stakeholders in their outputs.

7

EA IS about…

$ £ ¥ returns, Objectives & Performance8

Now � with Green IT

Image from: ksc.net 9

What we will gain from GREEN EA (GEA)?

Enterprise

ArchitectureGreen-minded Staffs

+

10

Green IT + ProfitsProfits

=

Now we know what GEA is about

and why we need it�..

That’s easy!!!

The hard part is

HOW TO?11

Let’s think about it as�building a house

Different architectures Different architectures Different architectures Different architectures serves different purposesserves different purposesserves different purposesserves different purposes

Main Purpose: Good Living

What do we mean by “Good”?

General requirements

• Living functionalities

• Security

• Comfortability

Specific requirements

• Location

• Style (Thai, Modern, etc.)• Size

• Money

• Time

Business

Requirements

Business Goal

12

With Green Architecture

Main Purpose: Good Living

What do we mean by “Good”?

General requirements

• Living functionalities

• Security

• Comfortability

Specific requirements

• Location

• Style (Thai, Modern, etc.)• Size

• Money

• Time

Main Purpose: Good Living

What do we mean by “Good”?

General requirements

• Living functionalities

• Security

• Comfortability

• Environmental friendly

Specific requirements

• Location

• Style (Thai, Modern, etc.)• Size

• Money � reduce cost of living

• Time

still have to

maintain business PERFORMANCE!!!13

How to develop GEA?How to develop GEA?First, we need a blueprint!!!

Second, we need to consolidate goals and Second, we need to consolidate goals and value proposition among stakeholders

Third, we need to

re-plan

re-engineering

re-use

re-cycle

replace

remove

reduce

Finally, we need to evaluate the alignment

between Green IT and business performance in order to create/improve GEA

14

we need

EA Framework

15

EA Framework• It’s a disciplines/guidelines for defining and maintaining

the architecture models, governance and transition initiatives needed to effectively co-ordinate disparate groups towards common business and IT goals.

• It also links an enterprise's business strategy to its change programs through the definition of:

• It also links an enterprise's business strategy to its change programs through the definition of:– Architecture models – to capture the intended structures and serve

as a blueprint for technology investment.

– Mechanisms – such as architecture governance and transition planning to help plan and coordinate all parts of the business and ensure that they all pull in the same direction.

16

EA Framework

17

EA Framework

• Many EA frameworks have been published such as:

– Zachman Framework

– TOGAF (The Open Group Architecture Framework)

– FEAF (US Federal Enterprise Architecture Framework)

– DoDAF/MoDAF (US Department of Defense / Ministry of – DoDAF/MoDAF (US Department of Defense / Ministry of

Defense Architecture Framework)

Each FRAMEWORK has its own

Methods, Techniques & Tools

18

Domains in EA Framework

19

Architecture Relationships

The Business Architecture is the result of defining the

• business strategies,

• processes, and

• functional requirements.

The Application Architecture

focused on developing and/or

implementing applications to

fulfill the business

requirements and to achieve requirements and to achieve

the quality thatmeet business goals.

The Information Architecture

describes the data’s physical and

logical aspects and the

management of the data

resources for supporting the

business processes and functions of the enterprise.

The Technical Architecture

identifies and plans the

computing services that form the technical infrastructure for

the enterprise.

The Product Architecture identifies standards and

configurations for the enabling

technologies and products within the Technical

Architecture.

Architecture Level

21

The Zachman FrameworkThe Zachman Framework

22

Zachman Framework

• It is an intersection between two classical schemas:– The first is the fundamentals of communication found in the

primitive interrogatives: What, How, When, Who, Where, and Why. It is the integration of answers to these questions that enables the comprehensive, composite description of complex ideas.

– The second is derived from reification, the transformation of an abstract idea into an instantiation that was initially postulated by ancient Greek philosophers and is labeled in The Zachman Framework™: Identification, Definition, Representation, Specification, Configuration and Instantiation.

http://www.zachmaninternational.com/index.php/home-article/13#maincol

http://en.wikipedia.org/wiki/Five_Ws

23

Zachman Framework

Six Perspectives• Scope (Planner’s Perspective)

– The planner is concerned with positioning the product in the context of its environment, including specifying its scope.

• Enterprise Model (Owner’s Perspective) – The owner is interested in the business deliverable and how it will be

used.

• System Model (Designer’s Perspective) • System Model (Designer’s Perspective) – The designer works with the specifications for the product to ensure that

it will, in fact, fulfill the owner’s expectations.

• Technology Model (Builder’s Perspective) – The builder manages the process of assembling and fabricating the

components in the production of the product.

• Detailed Representations (Subcontractor’s Perspective)– The subcontractor fabricates out-of-context components which meet the

builder’s specifications.

• Functional Representations (Operator’s Perspective)– The operator validates the usability and performance of the product.

Zachman Framework

Six Perspectives• Scope (Planner’s Perspective)

– The planner is concerned with positioning the product in the context of its environment, including specifying its scope.

• Enterprise Model (Owner’s Perspective) – The owner is interested in the business deliverable and how it will be used.

• System Model (Designer’s Perspective) – The designer works with the specifications for the product to ensure that it

Business

Analyst

System

Analyst– The designer works with the specifications for the product to ensure that it

will, in fact, fulfill the owner’s expectations.

• Technology Model (Builder’s Perspective) – The builder manages the process of assembling and fabricating the

components in the production of the product.

• Detailed Representations (Subcontractor’s Perspective)– The subcontractor fabricates out-of-context components which meet the

builder’s specifications.

• Functional Representations (Operator’s Perspective)– The operator validates the usability and performance of the product.

Developers

End users

Technical

Engineer

Zachman Framework

Six Dimensions

• Data (What?) – Each of the rows in this column address the understanding of, and

dealing with, any enterprise’s data.

• Function (How?)– The rows in the function column describe the process of translating the

mission of the enterprise into successively more detailed definitions of its operations.

• Network (Where?)• Network (Where?)– This column is concerned with the geographical distribution of the

enterprise’s activities.

• People (Who?)– The fourth column describes who is involved in the business and in the

introduction of new technology.

• Time (When?) – The fifth column describes the effects of time on the enterprise.

• Motivation (Why?) – This domain is concerned with the translation of business goals and

strategies into specific ends and means.

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

27

Zachman Framework

• Row 1 – ScopeExternal Requirements and Drivers

Business Function Modeling

� Row 2 – Enterprise ModelBusiness Process Models

1

2

3

Contextual

Conceptual

Contextual

Conceptual

WhyWho WhenWhereWhat How

� 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

Evaluation

3

4

5

6

Logical

Physical

As Built

Functioning

Logical

Physical

As Built

Functioning

WhyWho WhenWhereWhat How

28

Framework Rules

• Rule 1:

Columns have no order

Contextual Contextual

WhyWho WhenWhereWhat How

� Rule 2:

Each column has a simple, basic model

Basic Model = Entities and Relationships

EntityRelationshipEntity

Contextual

Conceptual

Logical

Physical

As Built

Functioning

Contextual

Conceptual

Logical

Physical

As Built

Functioning

WhyWho WhenWhereWhat How

� 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

29

Zachman Framework – Row 1

Scope/Planner’s View

• External

Requirements and

Drivers

• Business Function

Modeling

• Motivation/WhyBusiness goals, objectives and performancemeasures related to each function

� Function/HowHigh-level business functions

Modeling� Data/What

High-level data classes related to eachfunction

� People/WhoStakeholders related to each function

� Network/WhereLocations related to each function

� Time/WhenCycles and events related to eachfunction

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 30

Zachman Framework – Row 2

Enterprise Model/Designer’s View

• Business Process Models

• Business Function

Allocation

• Elimination of Function

Overlap and Ambiguity

• Motivation/WhyPolicies, procedures and standards for eachprocess

� Function/HowBusiness processes

Overlap and Ambiguity� Data/What

Business data

� People/WhoRoles and responsibilities in eachprocess

� Network/WhereLocations related to each process

� Time/WhenEvents for each process and sequencingof 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 31

Zachman Framework – Row 3

System Model/Designer’s View

• Logical Models

• Project Management

• Requirements

Definition

• Motivation/WhyPolicies, standards and proceduresassociated with a business rule model

� Function/HowLogical representation of informationsystems and their relationships

Definition � Data/What

Logical data models of data and datarelationships underlying information

� People/WhoLogical representation of access privilegesconstrained by roles and responsibilities

� Network/WhereLogical representation of the distributedsystem architecture for locations

� Time/WhenLogical 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 32

Zachman Framework – Row 4

Technology Model/Builder’s View

• Physical Models

• Technology

Management

• Solution Definition

and Development

• Motivation/WhyBusiness rules constrained by informationsystems standards

� Function/HowSpecifications of applications that operateon particular technology platforms

and Development � Data/What

Database management system (DBMS) typerequirements constrained by logical data models

� People/WhoSpecification of access privileges tospecific platforms and technologies

� Network/WhereSpecification of network devices and theirrelationships within physical boundaries

� Time/WhenSpecification of triggers to respond to systemevents 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 33

Zachman Framework – Row 5

As Built/Integrator’s View

• As Built

• Configuration

Management

• Deployment

• Motivation/WhyBusiness rules constrained by specific technology standards

� Function/HowPrograms coded to operate on specific technology platforms

• Deployment � Data/What

Data definitions constrained by physical data models

� People/WhoAccess privileges coded to control access to specific platforms and technologies

� Network/WhereNetwork devices configured to conform to node specifications

� Time/WhenTiming 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 34

Zachman Framework – Row 6

Functioning Enterprise/User’s View

• Functioning

Enterprise

• Operations

Management

• Evaluation

• Motivation/WhyOperating characteristics of specific technologies constrained by standards

� Function/HowFunctioning computer instructions

• Evaluation � Data/What

Data values stored in actual databases

� People/WhoPersonnel and key stakeholders working within their roles and responsibilities

� Network/WhereSending and receiving messages

� Time/WhenTiming 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 35

Based on work by

John A. Zachman

VA Enterprise

Architectu re

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEXTUAL)

Planner

ENTERPRISE

MODEL

(CONCEPTU AL)

Owner

SYSTEM MODEL

(LOGICAL)

SCOPE

(CONTEXTUAL)

Planner

ENTERPRISE

MODEL

(CONCEPTU AL)

Owner

SYSTEM MODEL

(LOGICAL)

Things Important

to the Bus iness

Entity = C lass of Bus iness Thing

Processes

Performed

Func tion = C lass of Business Process

Semantic Model

Ent = Bus iness Entity

R el = Bus iness Relationship

Business Process

Model

Proc = Bus iness Process

I/O = Bus iness Resources

Business Logis tic s

System

Node = Bus iness Location

Link = Bus iness Linkage

Work F low M odel

People = Organization Unit

Work = Work Product

Mas ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness Plan

End = Bus iness Objec tiv e

Means = Bus iness Strategy

Important

Organizations

People = Major Organizations

Business

locations

N ode = Major Business Locations

Ev ents Significant

to the Business

T ime = MajorBus iness Event

Bus iness Goals

and Strategy

Ends/Means =Major Bus iness Goals

Logical Data

M odel

Application

Architec ture

Dis tributed Sys tem

Architec ture

Human Interface

Architecture

Processing

Struc ture

Bus iness Rule

Model

Based on work by

John A. Zachman

VA Enterprise

Architectu re

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEXTUAL)

Planner

ENTERPRISE

MODEL

(CONCEPTU AL)

Owner

SYSTEM MODEL

(LOGICAL)

SCOPE

(CONTEXTUAL)

Planner

ENTERPRISE

MODEL

(CONCEPTU AL)

Owner

SYSTEM MODEL

(LOGICAL)

Things Important

to the Bus iness

Entity = C lass of Bus iness Thing

Processes

Performed

Func tion = C lass of Business Process

Semantic Model

Ent = Bus iness Entity

R el = Bus iness Relationship

Business Process

Model

Proc = Bus iness Process

I/O = Bus iness Resources

Business Logis tic s

System

Node = Bus iness Location

Link = Bus iness Linkage

Work F low M odel

People = Organization Unit

Work = Work Product

Mas ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness Plan

End = Bus iness Objec tiv e

Means = Bus iness Strategy

Important

Organizations

People = Major Organizations

Business

locations

N ode = Major Business Locations

Ev ents Significant

to the Business

T ime = MajorBus iness Event

Bus iness Goals

and Strategy

Ends/Means =Major Bus iness Goals

Logical Data

M odel

Application

Architec ture

Dis tributed Sys tem

Architec ture

Human Interface

Architecture

Processing

Struc ture

Bus iness Rule

Model

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Designer

TECHNOLOGY

MODEL

(PHYSICAL)

Builder

DETAILED

REPRESENTATIONS

(OUT-OF-CONTEXT)

Sub-Contractor

FUNCTIONING

ENTERPRISE

Designer

TECHNOLOGY

MODEL

(PHYSICAL)

Builder

DETAILED

REPRESENTATIONS

(OUT-OF-CONTEXT)

Sub-Contractor

FUNCTIONING

ENTERPRISE

Ent = Data Entity

R el = Data Relationship

Proc = Application Func tion

I/O = User Views

N ode = IS Func tion

Link = Line Characteris tics

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = Process ing Cycle

End = Struc tural Assertion

Means = Action Assertion

Phys ical Data

M odel

Ent = Segment/Table

R el = Pointer/Key

System

Design

Proc = Computer Func tion

I/O = Data Elements /Sets

Technology

Architec ture

N ode = Hardware/Softw are

Link = Line Spec ifications

Presentation

Architecture

People = User

Work = Screen Format

Control

Struc ture

T ime = Ex ecute

Cyc le = C omponent Cyc le

Rule

Des ign

End = Condition

Means = Action

DataDefinition

Ent = F ield

R el = Address

Program

Proc = Language Statement

I/O = Control Block

N etw orkArchitec ture

N ode = Addresses

Link = Protocols

SecurityArchitecture

People = Identity

Work = Job

T im ing Definition

T ime = Interrupt

Cyc le = Machine Cycle

RuleDes ign

End = Sub-Condition

Means = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organization

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = Means =

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Designer

TECHNOLOGY

MODEL

(PHYSICAL)

Builder

DETAILED

REPRESENTATIONS

(OUT-OF-CONTEXT)

Sub-Contractor

FUNCTIONING

ENTERPRISE

Designer

TECHNOLOGY

MODEL

(PHYSICAL)

Builder

DETAILED

REPRESENTATIONS

(OUT-OF-CONTEXT)

Sub-Contractor

FUNCTIONING

ENTERPRISE

Ent = Data Entity

R el = Data Relationship

Proc = Application Func tion

I/O = User Views

N ode = IS Func tion

Link = Line Characteris tics

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = Process ing Cycle

End = Struc tural Assertion

Means = Action Assertion

Phys ical Data

M odel

Ent = Segment/Table

R el = Pointer/Key

System

Design

Proc = Computer Func tion

I/O = Data Elements /Sets

Technology

Architec ture

N ode = Hardware/Softw are

Link = Line Spec ifications

Presentation

Architecture

People = User

Work = Screen Format

Control

Struc ture

T ime = Ex ecute

Cyc le = C omponent Cyc le

Rule

Des ign

End = Condition

Means = Action

DataDefinition

Ent = F ield

R el = Address

Program

Proc = Language Statement

I/O = Control Block

N etw orkArchitec ture

N ode = Addresses

Link = Protocols

SecurityArchitecture

People = Identity

Work = Job

T im ing Definition

T ime = Interrupt

Cyc le = Machine Cycle

RuleDes ign

End = Sub-Condition

Means = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organization

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = Means =

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

List of

business

process

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

37

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

List of things

(data, material)

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

38

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

List of

geographic

locations

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

39

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

List of

organization

units & roles

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

40

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

List of

events,

triggers

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

41

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

42

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

Process

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

43

Process

model

Process of insurance claim

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

Class-diagram

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

44

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

45

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

46

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

47

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

Mind map

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

48

Mind map

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

49

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

50

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

51

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

52

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

53

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

54

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

55

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

56

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

57

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

58

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

59

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

60

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

61

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

62

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

63

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

64

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

65

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

66

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

67

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Based on wo rk b y

John A. Z achman

VA En terprise

Arch itectu re

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEX TUAL )

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL )

Owner

S YS TEM MODEL

(LOGICAL )

Design er

SCOPE

(CONTEX TUAL)

Planner

ENTERPR IS E

MODEL

(CONCEPTU AL)

Owner

S YS TEM MODEL

(LOGICAL)

Design er

T hings Im portant

to the Bus ines s

Entity = C lass of

Bus iness T hing

Proc esses

Perform ed

F unc tion = C lass of

Bus iness Process

Sem antic M odel

Ent = Bus ines s Entity

R el = Bus ines s R elationship

Bus iness Process

M odel

Proc = Bus iness Process

I/O = Bus iness R esourc es

Bus iness Logis tic s

Sy s tem

N ode = Bus iness Location

Link = Bus iness Link age

Work F low M odel

People = Organization Unit

Work = Work Produc t

M as ter Schedule

T ime = Bus iness Event

Cyc le = Bus iness Cyc le

Bus iness P lan

End = Bus iness Objec tiv e

M eans = Bus iness Strategy

Im portant

Organiz ations

People = Major

Organiz ations

Bus iness

locations

N ode = M ajor

Bus iness Locations

Ev ents Signific ant

to the Bus iness

T ime = M ajor

Bus iness Event

Bus iness Goals

and Stra tegy

Ends/Means =

M ajor Bus iness Goals

Logic al Data

M odel

Ent = Data Entity

Application

Arc h itec ture

Proc = App lic ation Func tion

Dis tributed Sy s tem

Architec ture

N ode = IS F unc tion

Hum an Interface

Arc hitec ture

People = Role

P rocess ing

S truc ture

T ime = Sys tem Event

Bus iness R ule

M odel

End = Struc tural Assertion

Overview of the Zachman Framework

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

DATAWhat

FUNCTIONHow

NETW ORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Design er

TECHNOLOGY

MODEL

(PHYSICAL )

Build er

DETAI LED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Design er

TECHNOLOGY

MODEL

(PHYSICAL)

Bu ilder

DETAILED

REPRES ENTATIONS

(OUT-OF -CONTE XT)

Sub -Con tractor

FUNCTIONING

ENTERPR IS E

Ent = Data Entity

R el = Data Relationship

Proc = App lic ation Func tion

I/O = U ser View s

N ode = IS F unc tion

Link = Line C harac teris tic s

People = Role

Work = Deliv erable

T ime = Sys tem Event

Cyc le = P rocess ing Cycle

End = Struc tural Assertion

M eans = Ac tion As sertion

Phy s ical Data

M odel

Ent = Segm ent/Table

R el = Pointer/Key

Sys tem

Des ign

Proc = C om puter Func tion

I/O = Data Elem ents /Sets

T echnology

Arc hitec ture

N ode = Hardware/Softw are

Link = Line Spec ific ations

P resentation

A rc hitec ture

People = User

Work = Screen F orm at

C ontrol

S truc ture

T ime = Ex ecute

Cyc le = C om ponent Cy c le

R ule

Des ign

End = C ondition

M eans = Ac tion

Data

Defin ition

Ent = F ield

R el = Address

Program

Proc = Language Statem ent

I/O = C ontrol Block

N etw ork

Arc hitec ture

N ode = Addres ses

Link = Protoc ols

Security

A rc hitec ture

People = Identity

Work = Job

T im ing

Defin ition

T ime = Interrupt

Cyc le = M achine Cy cle

R ule

Des ign

End = Sub-C ondition

M eans = Step

Data

Ent = R el =

F unc tion

Proc =I/O =

N etw ork

N ode = Link =

Organiz ation

People = Work =

Schedule

T ime = Cyc le =

Strategy

End = M eans =

68

Applying UML to Zachman Framework

69

Image: http://conferences.embarcadero.com/article/32216

Applying UML to

Zachman Framework

Function (How)

Data (What) People (Who) Data (What)

70

Time (when)

Network (Where)

Image: http://conferences.embarcadero.com/article/32216

Applying UML to

Zachman Framework

71

Image: http://conferences.embarcadero.com/article/32216

Applying UML to

Zachman Framework

72

Image: http://conferences.embarcadero.com/article/32216

Applying UML to

Zachman Framework

73

Image: http://conferences.embarcadero.com/article/32216

Tools• http://www.visual-paradigm.com/

• http://www.sparxsystems.com

74

The Open Architecture Framework

(TOGAF )(TOGAF®)

By the Open Group Standard

75

The Open Group Architecture Framework

(TOGAF®)

• It is a framework for enterprise architecturewhich provides a comprehensive approach fordesigning, planning, implementation, andgovernance of an enterprise informationarchitecture.architecture.

• It provide a high level and holistic approach todesign, which is typically modeled at four levels:– Business,

– Application

– Data

– Technology76

TOGAF: Four Domains of Enterprise Architecture

• The Business Architecture– defines the business strategy, governance, organization, and

key business processes.

• The Data Architecture– describes the structure of an organization's logical and physical

data assets and data management resources.

• The Application Architecture• The Application Architecture– provides a blueprint for the individual applications to be

deployed, their interactions, and their relationships to the core business processes of the organization.

• The Technology Architecture – describes the logical software and hardware capabilities that are

required to support the deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, standards, etc.

77

TOGAF 9 Architecture Framework

78

Entities and Relationships Present within the Core Content Metamodel

79

The TOGAF uses

Architecture Development Method (ADM)

• ADM provides a tested and repeatable process for developing architectures.

– All of these activities are carried out within an iterative cycle of continuous architecture definition and cycle of continuous architecture definition and realization that allows organizations to transform their enterprises in a controlled manner in response to business goals and opportunities.

80

ADM – Basic Principles

An iterative method, over the whole

process, between phases and within

phases

Each iteration = new decisions:Enterprise coverage

Level of detailLevel of detail

Time horizon

Architecture asset re-use:

previous ADM iterations

other frameworks, system

models, industry models,�)

Decisions based on:Competence / resource availability

Value accruing to the enterprise.

81

ADM – Basic Principles

Every phase is validated against and

validates the current requirements of

the business

82

Preliminary Phase: Frameworks & Principles

• This phase prepares the organization for undertaking Enterprise Architecture successfully

– Understand business environment

– Commitment of key stakeholders

– Agreement on scope

– Establish principles

– Establish governance structure

– Agree on methods to be adopted

83

Phase A: Architecture Vision

• Initiates one iteration of the architecture

process

– Sets scope, constraints, expectations

– Required at the start of every

architecture cyclearchitecture cycle

• Validates business context

• Creates Statement of Architecture work

84

Phase B: Business Architecture

• The fundamental organization of

a business, embodied in

– its business processes and people,

– their relationships to each other

and the environment,

– and the principles governing its – and the principles governing its

design and evolution

• Shows how the organization

meets it’s business goals

85

Phase B: Business Architecture - Contents

• Organization structure

• Business goals and objectives

• Business functions

• Business Services

• Business processes

• Business roles• Business roles

• Correlation of organization and functions.

86

Phase B: Business Architecture - Steps

• Confirm context

• Define baseline

• Define target– Views are important

• Validate– Requirements– Requirements

– Concerns

• Perform Gap analysis

• Produce report

87

Phase C: Information Systems Architectures

• The fundamental organization

of an IT system, embodied in

– relationships to each other

and the environment, and the

principles governing its design

and evolutionand evolution

• Shows how the IT systems

meets the business goals of

the enterprise

Continued

88

Phase C: Data or Applications first ?

• It is usually necessary to address

both– Not always the case, depending on project

scope and constraints

• May be developed in either order, or

in parallelin parallel– Theory suggests Data Architecture comes

first

– Practical considerations may mean that

starting with Application Systems may be

more efficient

• There will need to be some iteration

to ensure consistency

89

Phase D: Technology Architecture

• The fundamental organization

of an IT system, embodied in

– its hardware, software and

communications technology

– their relationships to each other – their relationships to each other

and the environment,

– and the principles governing its

design and evolution

90

Phase E: Opportunities and Solutions

• Identify the major implementation projects

• Decide on approach– Make v Buy v Re-Use– Outsource– COTS– COTS– Open Source

• Assess priorities• Identify dependencies

91

Phase F: Migration Planning

• For projects identified in Phase E perform

• Cost/benefit analysis• Risk assessment

• Produce an implementation road-map• Produce an implementation road-map

92

Phase G: Implementation Governance

• Defines architecture constraints

on implementation projects

• Architecture contract

• Monitors implementation work for

conformanceconformance

93

Phase H: Architecture Change Management

• Ensures that changes to the

architecture are managed in a

cohesive and architected way

• Establishes and supports the

Enterprise Architecture to

provide flexibility to evolve provide flexibility to evolve

rapidly in response to changes

in the technology or business

environment

94

ADM – Basic Principles

The steps within the architecture development phases

(Phases B, C, D) are as follows:

• Select reference models, viewpoints, and tools • Develop Baseline Architecture Description

• Develop Target Architecture Description

95

• Develop Target Architecture Description • Perform gap analysis

• Define candidate roadmap components • Resolve impacts across the Architecture Landscape

• Conduct formal stakeholder review • Finalize the Architecture

• Create Architecture Definition Document

Deliverable and Content

Source: http://pubs.opengroup.org/architecture/togaf9-doc/arch/

TOGAF Enterprise Continuum

97

Promoting Reusable Enterprise Artifacts!!!

The relationships between deliverables,

artifacts, and building blocks

A deliverable is a work product that is contractually specified and in turn formally reviewed, agreed,

and signed off by the stakeholders.

An artifact is an architectural work

product that is generally

classified as catalogs

98

A building block represents a (potentially re-usable) component of business, IT, or architectural

capability that can be combined with other building blocks to deliver architectures and solutions.

classified as catalogs

(lists of things), matrices

(showing relationships

between things), and

diagrams (pictures of things).

Example of a deliverable

99

For more information about TOGAF

Website:

100

Website:

http://www.opengroup.org/togaf/

The next question is….The next question is….

101

What about SOA?What about SOA?

Service Orientation

Image: http://www.enterprise-architecture.info

Services Orientation

103

http://www.enterprise-architecture.info

Services Orientation (SO) is an Architectural Style, NOT an Architecture itself.

104

Image: http://www.enterprise-architecture.info

Service Oriented Maturity Model

Services have reached

critical mass and usage

Governance is in place to

measure QoS, SLAs.

105

measure QoS, SLAs.

Services are leveraged

across Business units

Service design are conformed

Industry Standards

Well defined architecture

GREEN EA (GEA) = Green IT + Enterprise Architecture

106

Green IT + EA = GEA

It is an EA that also aims to reduce

carbon footprint.

– The carbon footprint is an estimate of the

amount of CO2e emitted by the use of ICT.amount of CO2e emitted by the use of ICT.

– Computers and telecommunications equipment

contributes about 2% to greenhouse gas

emissions.

107

ICT Energy Consumption

108

Image from: Fujitsu

Energy Consumption

– Operating energy is a measure of the energy used

to operate the ICT equipment.

• This can be measured directly using an energy meter

(electric meter) which measures the electrical energy

used.

• Alternatively, the energy use may be estimated from• Alternatively, the energy use may be estimated from

the power the equipment uses (specified in Watt),

multiplied by the estimated amount of time the

equipment will be used (in Hours) to give the energy

(in Kilowatt hours).

109

Greenhouse Gas Conversion

• Greenhouse gas conversion factors are used to calculate

the amount of greenhouse gas emissions caused by

energy use.

• The conversion factor is used to convert energy

consumed in kWh to kg of equivalent carbon dioxide.

• For example,• For example,

– a computer using 200 W of power for 10 hours per day

uses 2 kWh of energy. Multiplying by a conversion

factor of 0.537 Kg CO2/kWh produces a total of 1.074

Kg CO2 per day.

Example of online calculator:

http://thaicfcalculator.tgo.or.th/110

Reduce Environmental Load by Leveraging IT

111

Image from: Fujitsu

Energy Saving

Data Centers and Client Equipment

• Client equipment (desktop computers and printers) consume more energy and materials than data centers.

• The Natural Edge Project (TNEP) suggest four steps for minimizing energy and materials consumption:

– Assess energy consumption by monitoring client equipment

– Consolidate operating client equipment only when necessary – Consolidate operating client equipment only when necessary

and removing unnecessary equipment

– Innovate by:

• Right-sized client equipment

• Power management strategies

• Low-energy equipment

• Eco-Labels

– Manage and monitor the equipments and activities112

Energy Saving

Data Centers and Client Equipment

The Natural Edge Project (TNEP) suggest seven steps for

minimizing energy and materials consumption of DC:

1. Determine the required services for the client environment.

2. Consolidate and virtualize servers, turning off unused equipment and

reducing the amount of server hardware required.

3. Invest in low-energy IT equipment with power management

technologies, low processors, efficient power supplies and low powertechnologies, low processors, efficient power supplies and low power

storage.

4. Optimize the layout of the data centre equipment to reduce the cooling

load.

5. Optimize airflow around equipment by orienting and spacing equipment

to reduce hotspots.

6. Invest in low-energy cooling technologies, such as direct liquid

cooling.

7. Practice energy conscious management by allocating accountability

for energy consumption and costs, and providing reports. 113

How to cut cost with Green IT?

• Prefer paperless

• If not necessary, no need to travel

• Use virtualization software

• Share the electric bills

• Trade up• Trade up

• Ditch the screen savers

• Take charge of the machines

• Tone down monitors

• Invest in power strips

• Don't forget about the printers

• Move to Cloud and Mobile Computing 114

Conclusion

GEA Value PropositionE

nviro

nm

enta

l Frie

ndly

Enviro

nm

enta

l Frie

ndly

115

Thank YOU!!!

116

Sources

• Colin A. White, The 60 second guide to Enterprise Architecture. www.colinwhite.net

• http://www.zachmaninternational.com

• http://en.wikipedia.org

• http://www.enterprise-architecture.info/EA_Services-Oriented-

Enterprise.htmEnterprise.htm

• http://www.inc.com/magazine/20091201/how-to-cut-costs-with-green-

it.html

• http://www.destinationgreenit.com/fujitsu-group-environmental-policy

117