Zachman Framework

The Use of Zachman Framework Primitives for Enterprise Modeling

Gundars OsvaldsSenior Principal Member of Technical Staff Litton/TASC [email protected] October 2000 Copyright 2000 TASC, Inc. All Rights Reserved

Contents Enterprise Architecture purpose and

definition Architecture perspectives Architecture components The Zachman Framework Modeling of a framework Architecture definition process description

Uses the Unified Modeling language (UML) Copyright 2000 TASC, Inc. All Rights Reserved

2

Purpose of an Enterprise Architecture A building plan for a system or

set of systems Set of high-level design decisions made by senior architects Addresses important system-wide issues Documents decisions that affect the subsequent elaboration of a system

Copyright 2000 TASC, Inc. All Rights Reserved

3

Architecture-centric Process ModelDefine a Mission System Engineer Identify a Framework Architect Design the System Implement a System Document Requirements Develop an Architecture

Stakeholder

Developer


4

What Is an Architecture Framework? What is an Architecture? A definition of the information system via models What Is an Architecture Framework? A representation of the information system via views of models How does this relate to an information

system implementation?

The architecture model guides the implementation Copyright 2000 TASC, Inc. All Rights Reserved

5

Conceptual ModelEnterprise 1defines

It all begins with the frameworkArchitecture Framework

Stakeholder1..* holds 1..* scopes fulfills

1..*

Mission1..*

represents

1..* guides

Requirement

Information System

implements

Architecture

1..* documents documents guides

System Description

Architecture Description 1..* 1specifies 1..*

This model documents the architecture-centric concepts associated with enterprise development

1

contains

View1..* describes 1..* 1..*

Artifacts 1..*

comprise

Model 1..*


6

Framework ComponentsA logical structure for classifying and organizing the models of an enterpriseArchitecture Framework

A formal definition of an enterprise system

represents

Architecture

Contains the views that are used to describe the architecture

documents

Architecture Description 1specifies 1..*

View

One or more abstractions e.g., Planner, Owner, Designer, Builder, Subcontractor

The basic elementsdescribes

1..*

1..*

Artifacts 1..*

comprise

Model 1..*

Representations of the Data, Function, Network, People, Time, and Motivation


7

Why Select Zachman Framework as Benchmark Performed industry survey on frameworks Determined that the Zachman Framework describes architecture elements Can be used describe any other framework using elements Since being developed 13 years ago it has consistently proven itself

Used in whole/part by: Federal Architecture Framework C4ISR Architecture Framework (in All Views) Tool Vendors (Ptech, Popkin) Spewaks Enterprise Architecture Planning


8

What is The Zachman Framework The Zachman Framework is a total

set of descriptive representations to fully describe a complex object John Zachman The Zachman Framework is a framework of elements

Defines various Abstractions and

Perspectives


9

Conceptual Description of The Zachman FrameworkDATA (What) Objective/ Scope (Contextual) FUNCTION (How) NETWORK (Where) PEOPLE (Who) TIME (When) MOTIVATION (Why)

Planner

Abstractions

Perspectives

Enterprise Model (Conceptual) System Model (Logical) Technology Model (Physical) Detailed Model (Out of Context)

Owner Designer Builder Subcontractor Functioning Enterprise Copyright 2000 TASC, Inc. All Rights Reserved

10

Zachman Framework for Enterprise Architectureabstractions perspectives

DATAWhatList of Things Important to the Business

FUNCTIONHowList of Processes the Business Performs

NETWORKWhereList of Locations in which the Business Operates

PEOPLEWhoList of Organizations Important to the Business

TIMEWhenList of Events Significant to the Business

MOTIVATIONWhyList of Business Goals and Strategies

SCOPEPlanner contextualEntity = Class of Business Thing e.g., Semantic Model Function = Class of Business Process e.g., Business Process Model Node = Major Business Location e.g., Logistics Network People = Class of People and Major Organizations e.g., Work Flow Model Ends/Means=Major Business Goal/Critical Success Factor e.g., Business Plan

Time = Major Business Event e.g., Master Schedule

ENTERPRISE MODELOwner conceptualEntity = Business Entity Rel. = Business Relationship e.g., Logical Data Model Process = Business Process I/O = Business Resources e.g., Application Architecture Node = Business Location Link = Business Linkage e.g., Distributed System Architecture People = Organization Unit Work = Work Product e.g., Human Interface Architecture Time = Business Event Cycle = Business Cycle e.g., Processing Structure End = Business Objective Means = Business Strategy e.g., Business Rule Model

SYSTEM MODELDesigner logicalEntity = Data Entity Rel. = Data Relationship e.g., Physical Data Model Process.= Application Function I/O = User Views e.g., System Design Node = IS Function Link = Line Characteristics e.g., Technical Architecture People = Role Work = Deliverable e.g., Presentation Architecture Time = System Event Cycle = Processing Cycle e.g., Control Structure End = Structural Assertion Means =Action Assertion e.g., Rule Design

TECHNOLOGY CONSTRAINED MODELBuilder physicalEntity = Tables/Segments/etc. Rel. = Key/Pointer/etc. e.g. Data Definition Process= Computer Function I/O =Data Elements/Sets e.g. Program Node = Hardware/System Software Link = Line Specifications e.g. Network Architecture People = User Work = Screen/Device Format e.g. Security Architecture Time = Execute Cycle = Component Cycle e.g. Timing Definition End = Condition Means = Action e.g. Rule Specification

DETAILED REPRESENTATIONSSubcontractor out-of-context FUNCTIONING ENTERPRISEEntity = Field Rel. = Address Process= Language Statement I/O = Control Block Node = Addresses Link = Protocols People = Identity Work = Job Time = Interrupt Cycle = Machine Cycle End = Sub-condition Means = Step

DATAImplementation

FUNCTIONImplementation

NETWORKImplementation

ORGANIZATIONImplementation

SCHEDULEImplementation

STRATEGYImplementation

John A. Zachman, Zachman International Copyright 2000 TASC, Inc. All Rights Reserved

Relationship of Models to the Zachman Framework How does Zachman define primitives,

single-variable models? How are the single-variable models in to describe the perspectives? How does the Zachman framework define the perspective views?


12

Zachman Framework Single Variable Examplesabstractions perspectives

DATAWhatList of Things Important to the Business

FUNCTIONHowList of Processes the Business Performs

NETWORKWhereList of Locations in which the Business Operates

PEOPLEWhoList of Organizations Important to the Business

TIMEWhenList of Events Significant to the Business

MOTIVATIONWhyList of Business Goals and Strategies

SCOPEPlanner contextualEntity = Class of Business Thing e.g., Semantic Model Function = Class of Business Process e.g., Business Process Model Node = Major Business Location e.g., Logistics Network People = Class of People and Major Organizations e.g., Work Flow Model Ends/Means=Major Business Goal/Critical Success Factor e.g., Business Plan

Time = Major Business Event e.g., Master Schedule

ENTERPRISE MODELOwner conceptualEntity = Business Entity Rel. = Business Relationship e.g., Logical Data Model Process = Business Process I/O = Business Resources e.g., Application Architecture Node = Business Location Link = Business Linkage e.g., Distributed System Architecture People = Organization Unit Work = Work Product e.g., Human Interface Architecture Time = Business Event Cycle = Business Cycle e.g., Processing Structure End = Business Objective Means = Business Strategy e.g., Business Rule Model

SYSTEM MODELDesigner logicalEntity = Data Entity Rel. = Data Relationship e.g., Physical Data Model Process.= Application Function I/O = User Views e.g., System Design Node = IS Function Link = Line Characteristics e.g., Technical Architecture

Each cell contains a single variable modelPeople = Role Work = Deliverable Time = System Event Cycle = Processing Cycle e.g., Presentation Architecture e.g., Control Structure e.g., Rule Design

End = Structural Assertion Means =Action Assertion

TECHNOLOGY CONSTRAINED MODELBuilder physicalEntity = Tables/Segments/etc. Rel. = Key/Pointer/etc. e.g. Data Definition Process= Computer Function I/O =Data Elements/Sets e.g. Program Node = Hardware/System Software Link = Line Specifications e.g. Network Architecture People = User Work = Screen/Device Format e.g. Security Architecture Time = Execute Cycle = Component Cycle e.g. Timing Definition End = Condition Means = Action e.g. Rule Specification

DETAILED REPRESENTATIONSSubcontractor out-of-context FUNCTIONING ENTERPRISEEntity = Field Rel. = Address Process= Language Statement I/O = Control Block Node = Addresses Link = Protocols People = Identity Work = Job Time = Interrupt Cycle = Machine Cycle End = Sub-condition Means = Step

DATAImplementation






John A. Zachman, Zachman International Copyright 2000 TASC, Inc. All Rights Reserved

Work Product Generation The Zachman Framework defines

primitive elements

Each cell then presents an example of a single-variable model

We define composite models to

use several primitives in the same model The composite model creates work products Copyright 2000 TASC, Inc. All Rights Reserved

14

Primitives to Work Productse.g., Logistics Network

The cells contain primitivesNETWORK NETWORK Artifact Artifact

Node = Business Location Link = Business Linkage

Described as Single-variable Model

Artifacts contain model data

(Where) (Where)

LOGICAL ARTIFACT S

DATA DATA Artifact Artifact (What) (What)

FUNCTION FUNCTION Artifact Artifact (How) (How)

NETWORK NETWORK Artifact Artifact (Where) (Where)

PEOPLE PEOPLE Artifact Artifact (Who) (Who)

TIME TIME Artifact Artifact (When) (When)

MOTIVATION MOTIVATION Artifact Artifact (Why) (Why)

Composite Models are the Work Products

Designers ViewLogical Packages

Logical Scenarios

Logical Components

Logical Interactions


15

CONTEXTUAL ARTIFACTS

Zachman Framework ArtifactsDATA DATA FUNCTION FUNCTION Artifact Artifact NETWORK NETWORK Artifact Artifact Artifact Artifact DATA DATA Artifact Artifact FUNCTION FUNCTION Artifact Artifact NETWORK NETWORK Artifact Artifact

PEOPLE PEOPLE Artifact Artifact

TIME TIME Artifact Artifact

MOTIVATION MOTIVATION Artifact Artifact

CONCEPTU AL ARTIFACTS LOGICAL ARTIFACTS




DATA Artifact

MODEL ARTIFACTS MODEL ARTIFACTSFUNCTION Artifact NETWORK Artifact PEOPLE Artifact FUNCTION FUNCTION Artifact Artifact NETWORK NETWORK Artifact PEOPLE PEOPLE Artifact Artifact

TIME Artifact

MOTIVATION Artifact

PHYSICAL ARTIFACTS

DATA DATA Artifact Artifact

Artifacts contains Artifact Artifact Artifact Artifact model dataTIME TIME Artifact Artifact

TIME TIME

MOTIVATION MOTIVATION

OUT-OFCONTEXT ARTIFACTS


FUNCTION FUNCTION Artifact Artifact

NETWORK NETWORK Artifact Artifact



FUNCTIONING ENTERPRISE

DATAImplementation







16

Create Views and Composite ModelsCONTEXTUAL ARTIFACTS DATA DATA Artifact Artifact FUNCTION FUNCTION Artifact Artifact NETWORK NETWORK Artifact Artifact PEOPLE PEOPLE Artifact Artifact TIME TIME Artifact Artifact MOTIVATION MOTIVATION Artifact Artifact

Create View with Models using transformations between abstraction artifactsCONCEPTUAL ARTIFACTS DATA DATA Artifact Artifact FUNCTION FUNCTION Artifact Artifact NETWORK NETWORK Artifact Artifact PEOPLE PEOPLE Artifact Artifact TIME TIME Artifact Artifact MOTIVATION MOTIVATION Artifact Artifact

LOGICAL ARTIFACTS


FUNCTION FUNCTION Artifact


Transformation is the key to bridging the PEOPLE perspectives TIME PEOPLE TIME MOTIVATION MOTIVATIONArtifact Artifact Artifact Artifact Artifact Artifact

PHYSICAL ARTIFACTS


FUNCTION FUNCTION Artifact Artifact





OUT-OFCONTEXT ARTIFACTSFUNCTIONING ENTERPRISE

DATA DATA Artifact ArtifactDATAImplementation

FUNCTION FUNCTION Artifact ArtifactFUNCTIONImplementation

NETWORK NETWORK Artifact ArtifactNETWORKImplementation

PEOPLE PEOPLE Artifact ArtifactORGANIZATIONImplementation

TIME TIME Artifact ArtifactSCHEDULEImplementation

MOTIVATION MOTIVATION Artifact ArtifactSTRATEGYImplementation


External Inputs to the Zachman FrameworkRequirements Requirements Concept of Concept of Operations Operations Business Business Plan Plan

CONTEXTUA L ARTIFACTS








Bridging the Zachman Framework Bridging the Zachman Framework Perspectives - Planners View Perspectives - Planners ViewCONTEXTUA L ARTIFACTS DATA Artifact Artifact (What) (What) FUNCTION FUNCTION Artifact Artifact (How) (How) NETWORK NETWORK Artifact (Where) (Where) PEOPLE PEOPLE Artifact Artifact (Who) TIME TIME Artifact Artifact (When) (When) MOTIVATION MOTIVATION Artifact Artifact (Why) (Why)

Planners ViewContextual Concepts Contextual Information Contextual Process Contextual Organization Contextual Resources Contextual Risks/Benefits Contextual Goals

CONCEPTUA L ARTIFACTS

DATA Artifact Artifact (What) (What)


NETWORK NETWORK Artifact (Where) (Where)

PEOPLE PEOPLE Artifact Artifact (Who)




Bridging the Zachman Framework Bridging the Zachman Framework Perspectives - Owners View Perspectives - Owners ViewCONCEPTUA L ARTIFACTS DATA DATA Artifact Artifact (What) (What) FUNCTION FUNCTION Artifact Artifact (How) (How) NETWORK NETWORK Artifact Artifact (Where) (Where) PEOPLE PEOPLE Artifact Artifact (Who) (Who) TIME TIME Artifact Artifact (When) (When) MOTIVATION MOTIVATION Artifact Artifact (Why) (Why)

Owners ViewConceptual Process States Conceptual Resource Interactions Conceptual Process

LOGICAL ARTIFACTS








Bridging the Zachman Framework Bridging the Zachman Framework Perspectives - Designers View Perspectives - Designers ViewLOGICAL ARTIFACTS DATA DATA Artifact Artifact (What) (What) FUNCTION FUNCTION Artifact Artifact (How) (How) NETWORK NETWORK Artifact Artifact (Where) (Where) PEOPLE PEOPLE Artifact Artifact (Who) (Who) TIME TIME Artifact Artifact (When) (When) MOTIVATION MOTIVATION Artifact Artifact (Why) (Why)

Designers ViewLogical Scenarios Logical Packages

Logical Components

Logical Interactions

PHYSICAL ARTIFACTS

DATA Artifact Artifact (What) (What)


NETWORK NETWORK Artifact (Where) (Where)





Bridging the Zachman Framework Bridging the Zachman Framework Perspectives - Builders View Perspectives - Builders ViewPHYSICAL ARTIFACTS DATA DATA Artifact Artifact (What) (What) FUNCTION FUNCTION Artifact Artifact (How) (How) NETWORK NETWORK Artifact Artifact (Where) (Where) PEOPLE PEOPLE Artifact Artifact (Who) (Who) TIME TIME Artifact Artifact (When) (When) MOTIVATION MOTIVATION Artifact Artifact (Why) (Why)

Builders ViewPhysical Activities Physical Elements Physical Interactions Physical Deployment

Physical Behaviors

OUT-OFCONTEXT ARTIFACTSFUNCTIONING ENTERPRISE

DATA DATA Artifact Artifact (What) (What)DATAImplementation

FUNCTION FUNCTION Artifact Artifact (How) (How)FUNCTIONImplementation

NETWORK NETWORK Artifact Artifact (Where) (Where)NETWORKImplementation

PEOPLE PEOPLE Artifact Artifact (Who)ORGANIZATIONImplementation

TIME TIME Artifact Artifact (When) (When)SCHEDULEImplementation

MOTIVATION MOTIVATION Artifact Artifact (Why) (Why)STRATEGYImplementation


Process Documentation The process develops the models

that represent the architectural views Developed a method for documenting work product models Used UML Use Case diagrams to document the process Used Use Case descriptions to document the recommended steps Copyright 2000 TASC, Inc. All Rights Reserved

23

Defining the Enterprise ArchitectureMission Guidelines (Vision) Planner (Architect) guides gathers

This Use Case shows the high-level representation of the process that produces the artifacts associated with defining the enterprise architecture

Gather Mission Guidelines

Note: Line color indicates who uses the artifact

defines Define Planner View reviews

Contextual Artifacts Contextual Artifacts Conceptual Artifacts Conceptual Artifacts Define Owner View Logical Artifacts

Owner (Stakeholder)

builds

Frame Architecture

Designer (System Engineer) reviews

builds Builder reviews

Logical Artifacts Define Designer View Physical Artifacts

builds Subcontractor reviews Define Builder View

Physical Artifacts

Out-of-Context Artifacts


24

Document the Framework Process Developed top-level description using UML

Use Case diagrams Defined the identified objects (models) using UML diagrams Goal is to use simple UML diagrams so that the process can be easily communicated

Added icons to the UML Activity Model to

incorporate objects previously defined Entered descriptions of each step of the architecture modeling process


25

Define Planner ViewPlanner (Architect)

This Use Case shows the models used to define the Planners View

Identify Contextual Risks and Benefits

UML ClassIdentify Contextual Organization Identify Contextual Information

UML Class UML Class

Identify Contextual Goals

UML Class

UML ClassIdentify Contextual Resources UML Model

UML ClassOwner (Stakeholder) Identify Contextual Concepts Define Contextual Process

UML Activity w/Objects


26

Business Concepts Example Diagram Customer + Description : char Company + Description : char

UML Class DiagramAcme Business:Customer Description =

TASC:Company Description =

persistent

persistent

Systems Engineering:"Business Unit" Description =

Business Unit + Description : char Alpha:Project Name = Organization = Description = Enterprise Architecture:Section Description = Beta:Project Name = Organization = Description =

Project + Name : char + Organization : char + Description : char

persistent

persistent

Architectural Description + Description : char

Section + Description : char TASC:"Architectural Description" Description =

persistent

persistent


27

Sample Use Case Step DocumentationUse Case: Identify Business ConceptsCommunicates With Case Worker: Owner (Stakeholder) Communicates With Actor: UML Models Communicates With Case Worker: Planner (Architect) Child Diagram(s): Example: Identify Business Concepts [UML Class]1. artifacts" important concepts used in the the following Scope Artifacts: Data, Function, Network, People, and Motivation. Output will fill in the enterprise. Document each concept Enterprise Model Artifact: Data with list of business objects. with a few sentences in the description fields. 2. "Define interactions between objects" Document the relationships between the business concept objects using information from the Scope Artifacts. "Create objects from Scope Use a UML Class diagram to represent Description: Build a Conceptual Model. Define the important concepts used in the business. Use Use Case Steps Step Text

Preconditions: "Defined Scope Artifacts Postconditions: "Defined Enterprise ModelArtifacts" Copyright 2000 TASC, Inc. All Rights Reserved

28

Enterprise Architecture Process Development Enterprise Architecture Process DevelopmentEnterpriseOrganization that uses Information Technology to perform its mission

Architecture-Centric Conceptual ModelEnterprise Stakeholder

Architecture"Blueprint" of the Enterprise that provides guidance to the Systems Engineers

1..* holds 1..*Requirement

scopes

Mission

1 defines 1..* 1..* fulfills 1..*

Architecture Framework

represents implementsInformation System Architecture

Information System

guides documentsSystem Description

TransformationsCONTEXTUAL ARTIFACTS DATA Artifact FUNCTION Artifact NETWORK Artifact PEOPLE Artifact TIME Artifact MOTIVATION Artifact Create View with Models using transformations between abstraction artifacts DATA Artifact FUNCTION Artifact NETWORK Artifact PEOPLE Artifact TIME Artifact MOTIVATION Artifact

`1

documents documentsArchitecture Description

1 specifies 1..*View

1..*Artifacts

comprise 1..* 1..*

1..* describes 1..*

CONCEPTUAL ARTIFACTS

Model LOGICAL ARTIFACTS DATA Artifact FUNCTION Artifact NETWORK Artifact PEOPLE Artifact TIME Artifact MOTIVATION Artifact

ProcessProcedures that are used by the Architect to develop the Architecture

PHYICAL ARTIFACTS

DATA Artifact

FUNCTION Artifact

NETWORK Artifact

PEOPLE Artifact

TIME Artifact

MOTIVATION Artifact

Model BridgeCO NTEXTUA L ARTI F ACTS DATA Artifact (What) FUNCTION Artifact (How) NETWORK Artifact (Where) PEOPLE Artifact (Who) TIME Artifact (When) MOTIVATION Artifact (Why)

OU T-OF CON TEXT ARTIF ACTSFUNCTIONING ENTERPRISE

DATA ArtifactDATA Implementation

FUNCTION ArtifactFUNCTION Implementation

NETWORK ArtifactNETWORK Implementation

PEOPLE ArtifactORGANIZATION Implementation

TIME ArtifactSCHEDULE Implementation

MOTIVATION ArtifactSTRATEGY Implementation

ViewsAbstractions of the Enterprise that use Models to represent the Architecture

Planners ViewContextual Contextual Information Information Contextual Contextual Process Process

Contextual Contextual Business Concepts Business Concepts

Contextual Contextual Goals Goals Contextual Contextual Risks/Benefits Risks/Benefits

`Contextual Contextual Resources Resources

Contextual Contextual Organization Organization

ProcessMission Guidelines (Vision) Planner (Architect) guides gathers defines Owner (Stakeholder) reviews Gather Mission Guidelines Contextual Artifacts Define Planner View Contextual Artifacts Conceptual Artifacts Conceptual Artifacts Frame Define Architecture Owner View Logical Artifacts Logical Artifacts Define Designer View Physical Artifacts Physical Artifacts Define Builder View Out-of-Context Artifacts

CON CEPTU A L ARTIF ACTS

DATA Artifact (What)

FUNCTION Artifact (How)

NETWORK Artifact (Where)

PEOPLE Artifact (Who)

TIME Artifact (When)

MOTIVATION Artifact (Why)

ModelsConceptual representations of the EnterpriseAcme Corp:Customer Description = Alpha:Project Name = Organization = Description =

ModelTASC:Company Description = Customer + Description : char persistent Cryptologic Engineering:"Business Unit" Description = Company + Description : persistent Business Unit Project + Name : char + Organization : char + Description : char persistent + Description : persistent

builds Designer (System Engineer) reviews builds Builder reviews builds Subcontractor reviews

Enterprise Architecture:Section Description = Beta:Project Name = Organization = Description =

Architectural Description + Description : char TASC:"Architectural Description" Description = persistent

Section + Description : persistent


Summary Used the Zachman Framework to define the

basic artifacts that the modeling process uses Documented the transformation bridge that provides traceability from the Zachman Framework to the models representing the system implementation

Identified the basic models (OO) needed to

model an Enterprise Architecture Documented the Enterprise Architecture views in a repeatable framework process


30