© Copyright 2000 TASC, Inc. All Rights Reserved

The Use of Zachman Framework Primitives for Enterprise

Modeling

The Use of Zachman Framework Primitives for Enterprise

Modeling

Gundars OsvaldsSenior Principal Member of Technical Staff

Litton/TASC

gosvalds@tasc.com

26 October 2000

2© Copyright 2000 TASC, Inc. All Rights Reserved

ContentsContents

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)

3© Copyright 2000 TASC, Inc. All Rights Reserved

Purpose of an Enterprise ArchitecturePurpose 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

4© Copyright 2000 TASC, Inc. All Rights Reserved

Architecture-centric Process ModelArchitecture-centric Process Model

Stakeholder

DocumentRequirements

Define a Mission

<<include>>

<<include>>

Design theSystem

System Engineer

<<include>>

Identify a Framework

Architect

Develop an Architecture

<<include>>

<<include>>

Developer

<<include>>

Implement a System

5© Copyright 2000 TASC, Inc. All Rights Reserved

What Is an Architecture Framework?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

6© Copyright 2000 TASC, Inc. All Rights Reserved

Conceptual ModelConceptual Model

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

Architecture Framework

Enterprise

Stakeholder

Mission

1

1..*

defines

Requirement

scopes

1..*

1..*

1..*

holds

Architecture Description

Information System

1..*

1..*

fulfills

guides Architecture

represents

documents

implements

Model

View

11

1..*

specifies

1..*

1..*

describes

System Description

documents

guides

1 1..*

Artifacts

1..* 1..*

comprise

contains

1..*

1..*

It all begins with the framework

7© Copyright 2000 TASC, Inc. All Rights Reserved

Framework ComponentsFramework Components

Architecture Framework

Architecture Description

Architecture

represents

documents

Model

View

11

1..*

specifies

1..*

1..*

describes

Artifacts

1..* 1..*

comprise

A logical structure for classifying and organizing the models of an enterprise

One or more abstractions e.g., Planner, Owner,

Designer, Builder, Subcontractor

The basic elements

Representations of the Data, Function, Network, People,

Time, and Motivation

Contains the views that are used to describe the

architecture

A formal definition of an enterprise system

8© Copyright 2000 TASC, Inc. All Rights Reserved

Why Select Zachman Framework as BenchmarkWhy 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)– Spewak’s Enterprise Architecture Planning

9© Copyright 2000 TASC, Inc. All Rights Reserved

What is The Zachman FrameworkWhat 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

10© Copyright 2000 TASC, Inc. All Rights Reserved

MOTIVATION(Why)

TIME(When)

PEOPLE(Who)

NETWORK(Where)

FUNCTION(How)

DATA(What)

Abstractions

Designer

BuilderPer

spec

tives

Objective/Scope

(Contextual)

EnterpriseModel

(Conceptual)

SystemModel

(Logical)

TechnologyModel

(Physical)

DetailedModel (Out of

Context)Subcontractor

Conceptual Description of The Zachman FrameworkConceptual Description of The Zachman Framework

Functioning Enterprise

Owner

Planner

Zachman Framework for Enterprise ArchitectureZachman Framework for Enterprise Architecture

John A. Zachman, Zachman International

DATA Implementation

DATAWhat

FUNCTIONHow

NETWORKWhere

e.g. Data Definition

Entity = FieldRel. = Address

e.g., Physical Data Model

Entity = Tables/Segments/etc.Rel. = Key/Pointer/etc.

e.g., Logical Data Model

Entity = Data EntityRel. = Data Relationship

e.g., Semantic Model

Entity = Business EntityRel. = Business Relationship

List of Things - Important to the Business

Entity = Class ofBusiness Thing

List of Processes -the Business Performs

Function = Class ofBusiness Process

e.g., Application Architecture

Process.= Application FunctionI/O = User Views

e.g., System Design

Process= Computer FunctionI/O =Data Elements/Sets

e.g. Program

Process= Language StatementI/O = Control Block

FUNCTIONImplementation

e.g., Business Process Model

Process = Business ProcessI/O = Business Resources

List of Locations -in which the Business Operates

Node = Major BusinessLocation

e.g., Logistics Network

Node = Business Location Link = Business Linkage

e.g., Distributed System Architecture

Node = IS FunctionLink = Line Characteristics

e.g., Technical Architecture

Node = Hardware/System SoftwareLink = Line Specifications

e.g. Network Architecture

Node = AddressesLink = Protocols

NETWORKImplementation

MOTIVATIONWhy

TIMEWhen

PEOPLEWho

e.g. Rule Specification

End = Sub-conditionMeans = Step

e.g., Rule Design

End = ConditionMeans = Action

e.g., Business Rule Model

End = Structural AssertionMeans =Action Assertion

End = Business ObjectiveMeans = Business Strategy

List of Business Goals and Strategies

Ends/Means=Major BusinessGoal/Critical Success Factor

List of Events -Significant to the Business

Time = Major Business Event

e.g., Processing Structure

Time = System EventCycle = Processing Cycle

e.g., Control Structure

Time = ExecuteCycle = Component Cycle

e.g. Timing Definition

Time = InterruptCycle = Machine Cycle

SCHEDULEImplementation

e.g., Master Schedule

Time = Business EventCycle = Business Cycle

List of Organizations -Important to the Business

People = Class of People andMajor Organizations

e.g., Work Flow Model

People = Organization UnitWork = Work Product

e.g., Human Interface Architecture

People = RoleWork = Deliverable

e.g., Presentation Architecture

People = UserWork = Screen/Device Format

e.g. Security Architecture

People = IdentityWork = Job

ORGANIZATIONImplementation

STRATEGYImplementation

e.g., Business Plan

SCOPEPlanner

SYSTEM MODELDesigner

TECHNOLOGYCONSTRAINED

MODELBuilder

DETAILEDREPRESEN-

TATIONSSubcontractor

ENTERPRISE MODEL

Owner

contextual

conceptual

logical

physical

out-of-context

FUNCTIONINGENTERPRISE

perspectives

abstractions

© Copyright 2000 TASC, Inc. All Rights Reserved

12© Copyright 2000 TASC, Inc. All Rights Reserved

Relationship of Models to the Zachman FrameworkRelationship 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?

Zachman Framework Single Variable ExamplesZachman Framework Single Variable Examples

John A. Zachman, Zachman International

DATA Implementation

DATAWhat

FUNCTIONHow

NETWORKWhere

e.g. Data Definition

Entity = FieldRel. = Address

e.g., Physical Data Model

Entity = Tables/Segments/etc.Rel. = Key/Pointer/etc.

e.g., Logical Data Model

Entity = Data EntityRel. = Data Relationship

e.g., Semantic Model

Entity = Business EntityRel. = Business Relationship

List of Things - Important to the Business

Entity = Class ofBusiness Thing

List of Processes -the Business Performs

Function = Class ofBusiness Process

e.g., Application Architecture

Process.= Application FunctionI/O = User Views

e.g., System Design

Process= Computer FunctionI/O =Data Elements/Sets

e.g. Program

Process= Language StatementI/O = Control Block

FUNCTIONImplementation

e.g., Business Process Model

Process = Business ProcessI/O = Business Resources

List of Locations -in which the Business Operates

Node = Major BusinessLocation

e.g., Logistics Network

Node = Business Location Link = Business Linkage

e.g., Distributed System Architecture

Node = IS FunctionLink = Line Characteristics

e.g., Technical Architecture

Node = Hardware/System SoftwareLink = Line Specifications

e.g. Network Architecture

Node = AddressesLink = Protocols

NETWORKImplementation

MOTIVATIONWhy

TIMEWhen

PEOPLEWho

e.g. Rule Specification

End = Sub-conditionMeans = Step

e.g., Rule Design

End = ConditionMeans = Action

e.g., Business Rule Model

End = Structural AssertionMeans =Action Assertion

End = Business ObjectiveMeans = Business Strategy

List of Business Goals and Strategies

Ends/Means=Major BusinessGoal/Critical Success Factor

List of Events -Significant to the Business

Time = Major Business Event

e.g., Processing Structure

Time = System EventCycle = Processing Cycle

e.g., Control Structure

Time = ExecuteCycle = Component Cycle

e.g. Timing Definition

Time = InterruptCycle = Machine Cycle

SCHEDULEImplementation

e.g., Master Schedule

Time = Business EventCycle = Business Cycle

List of Organizations -Important to the Business

People = Class of People andMajor Organizations

e.g., Work Flow Model

People = Organization UnitWork = Work Product

e.g., Human Interface Architecture

People = RoleWork = Deliverable

e.g., Presentation Architecture

People = UserWork = Screen/Device Format

e.g. Security Architecture

People = IdentityWork = Job

ORGANIZATIONImplementation

STRATEGYImplementation

e.g., Business Plan

SCOPEPlanner

SYSTEM MODELDesigner

TECHNOLOGYCONSTRAINED

MODELBuilder

DETAILEDREPRESEN-

TATIONSSubcontractor

ENTERPRISE MODEL

Owner

contextual

conceptual

logical

physical

out-of-context

FUNCTIONINGENTERPRISE

perspectives

abstractions

Each cell contains a single variable model

© Copyright 2000 TASC, Inc. All Rights Reserved

14© Copyright 2000 TASC, Inc. All Rights Reserved

Work Product GenerationWork Product Generation

The Zachman Framework defines primitive elements– Each cell then presents an example

of a single-variable modelWe define composite models to

use several primitives in the same model– The composite model creates work

products

15© Copyright 2000 TASC, Inc. All Rights Reserved

Designer’s View

Primitives to Work ProductsPrimitives to Work Products

Described as Single-variable

Model

The cells contain primitives

Node = Business Location Link = Business Linkage

e.g., Logistics Network

LOGICAL

ARTIFACTS

DATA

Artifact

DATA

ArtifactFUNCTION

Artifact

FUNCTION

ArtifactNETWORK

Artifact

NETWORK

Artifact

PEOPLE

Artifact

PEOPLE

ArtifactTIME

Artifact

TIME

ArtifactMOTIVATION

Artifact

MOTIVATION

Artifact

(How)(How)(What)(What) (Where)(Where) (Who)(Who) (When)(When) (Why)(Why)

Artifacts containmodel data

NETWORK

Artifact

(Where)

NETWORK

Artifact

(Where)

Logical Components

LogicalPackages Logical

Interactions

LogicalScenarios

Composite Models are the

Work Products

16© Copyright 2000 TASC, Inc. All Rights Reserved

Zachman Framework ArtifactsZachman Framework Artifacts

DATA Implementation

FUNCTIONImplementation

NETWORKImplementation

SCHEDULEImplementation

ORGANIZATIONImplementation

STRATEGYImplementation

FUNCTIONINGENTERPRISE

DATA

Artifact

DATA

Artifact

NETWORK

Artifact

NETWORK

Artifact ArtifactArtifact ArtifactArtifact ArtifactArtifact

FUNCTION

Artifact

FUNCTION

Artifact

DATA

Artifact

DATA

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

NETWORK

Artifact

NETWORK

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

DATA

Artifact

DATA

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

NETWORK

Artifact

NETWORK

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

DATA

Artifact

FUNCTION

Artifact

NETWORK

Artifact

PEOPLE

Artifact

TIME

Artifact

DATA

Artifact

DATA

Artifact

NETWORK

Artifact

NETWORK

Artifact

PEOPLE PEOPLE TIME TIME FUNCTION

Artifact

FUNCTION

Artifact

MOTIVATION MOTIVATION

MOTIVATION

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

PEOPLE PEOPLE TIME TIME MOTIVATION MOTIVATION

ArtifactArtifact ArtifactArtifact ArtifactArtifact

CONTEXTUAL

ARTIFACTS

CONCEPTUAL

ARTIFACTS

PHYSICALARTIFACTS

OUT-OF-CONTEXTARTIFACTS

LOGICAL

ARTIFACTS

MODEL ARTIFACTSMODEL ARTIFACTS

Artifacts contains model data

Create Views and Composite ModelsCreate Views and Composite Models

© Copyright 2000 TASC, Inc. All Rights Reserved

Create View with Models using transformations between abstraction artifactsCreate View with Models using transformations between abstraction artifacts

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

MOTIVATION

Artifact

OUT-OF-CONTEXTARTIFACTS

FUNCTIONINGENTERPRISE

CONTEXTUAL

ARTIFACTS

CONCEPTUALARTIFACTS

LOGICALARTIFACTS

PHYSICALARTIFACTS

DATA Implementation

FUNCTIONImplementation

SCHEDULEImplementation

ORGANIZATIONImplementation

STRATEGYImplementation

DATA ArtifactDATA Artifact PEOPLE

Artifact

PEOPLE

ArtifactTIME ArtifactTIME Artifact MOTIVATION

Artifact

MOTIVATION

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

DATA

Artifact

DATA

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

DATA

Artifact

DATA

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

DATA

Artifact

DATA

ArtifactFUNCTION

Artifact

FUNCTION

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

DATA

Artifact

DATA

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

NETWORKImplementation

NETWORK

Artifact

NETWORK

Artifact

NETWORK

Artifact

NETWORK

Artifact

NETWORK

Artifact

NETWORK

Artifact

NETWORK

Artifact

NETWORK

Artifact

NETWORK

Artifact

NETWORK

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

ArtifactMOTIVATION

Artifact

MOTIVATION

ArtifactTransformation is the key to bridging the perspectives

Transformation is the key to bridging the perspectives

External Inputs to the Zachman FrameworkExternal Inputs to the Zachman Framework

Concept of Operations

Concept of OperationsRequirementsRequirements Business

Plan

BusinessPlan

© Copyright 2000 TASC, Inc. All Rights Reserved

CONTEXTUAL

ARTIFACTS

DATA

Artifact

DATA

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

(How)(How)(What)(What) (Where)(Where) (Who)(Who) (When)(When) (Why)(Why)

NETWORK

Artifact

NETWORK

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

Bridging the Zachman Framework Perspectives - Planner’s ViewBridging the Zachman Framework Perspectives - Planner’s View

© Copyright 2000 TASC, Inc. All Rights Reserved

CONTEXTUAL

ARTIFACTS

DATA

Artifact

DATA

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

(How)(How)(What)(What) (Where)(Where) (Who)(Who) (When)(When) (Why)(Why)

NETWORK

Artifact

NETWORK

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

CONCEPTUAL

ARTIFACTS

DATA

Artifact

DATA

Artifact

NETWORK

Artifact

NETWORK

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

(How)(How)(What)(What) (Where)(Where) (Who)(Who) (When)(When) (Why)(Why)

Planner’s View

ContextualResources

ContextualProcess

Contextual Information

Contextual Risks/Benefits

ContextualOrganization

ContextualConcepts

Contextual Goals

Bridging the Zachman Framework Perspectives - Owner’s ViewBridging the Zachman Framework Perspectives - Owner’s View

CONCEPTUAL

ARTIFACTS

DATA

Artifact

DATA

Artifact

NETWORK

Artifact

NETWORK

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

(How)(How)(What)(What) (Where)(Where) (Who)(Who) (When)(When) (Why)(Why)

Owner’s View

ConceptualProcess

ConceptualResource

Interactions

ConceptualProcess States

© Copyright 2000 TASC, Inc. All Rights Reserved

LOGICAL

ARTIFACTS

DATA

Artifact

DATA

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

NETWORK

Artifact

NETWORK

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

(How)(How)(What)(What) (Where)(Where) (Who)(Who) (When)(When) (Why)(Why)

Bridging the Zachman Framework Perspectives - Designer’s ViewBridging the Zachman Framework Perspectives - Designer’s View

© Copyright 2000 TASC, Inc. All Rights Reserved

LOGICAL

ARTIFACTS

DATA

Artifact

DATA

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

NETWORK

Artifact

NETWORK

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

(How)(How)(What)(What) (Where)(Where) (Who)(Who) (When)(When) (Why)(Why)

PHYSICAL

ARTIFACTS

DATA

Artifact

DATA

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

NETWORK

Artifact

NETWORK

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

(How)(How)(What)(What) (Where)(Where) (Who)(Who) (When)(When) (Why)(Why)

Logical Components

LogicalPackages

LogicalInteractions

LogicalScenarios

Designer’s View

Bridging the Zachman Framework Perspectives - Builder’s ViewBridging the Zachman Framework Perspectives - Builder’s View

Builder’s View

© Copyright 2000 TASC, Inc. All Rights Reserved

PHYSICAL

ARTIFACTS

(How)(How)(What)(What) (Where)(Where) (Who)(Who) (When)(When) (Why)(Why)

DATA

Artifact

DATA

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

NETWORK

Artifact

NETWORK

Artifact

PEOPLE

Artifact

PEOPLE

Artifact

TIME

Artifact

TIME

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

FUNCTIONINGENTERPRISE

DATA Implementation

FUNCTIONImplementation

NETWORKImplementation

SCHEDULEImplementation

ORGANIZATIONImplementation

STRATEGYImplementation

DATA ArtifactDATA Artifact NETWORK

Artifact

NETWORK

Artifact

PEOPLE

Artifact

PEOPLE

ArtifactTIME ArtifactTIME Artifact MOTIVATION

Artifact

MOTIVATION

Artifact

FUNCTION

Artifact

FUNCTION

Artifact

(How)(How)(What)(What) (Where)(Where) (Who)(Who) (When)(When) (Why)(Why)

OUT-OF-

CONTEXT

ARTIFACTS

Physical Behaviors

PhysicalActivities

Physical Elements

PhysicalInteractions

Physical Deployment

23© Copyright 2000 TASC, Inc. All Rights Reserved

Process DocumentationProcess 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

24© Copyright 2000 TASC, Inc. All Rights Reserved

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

Defining the Enterprise ArchitectureDefining the Enterprise Architecture

DefineDesigner View

DefinePlanner View

GatherMission

Guidelines

DefineBuilder View

DefineOwner View

FrameArchitecture

Owner(Stakeholder)

Mission Guidelines(Vision)

Planner(Architect)

Designer(System Engineer)

Builder

Subcontractor

Note: Line colorindicates whouses the artifact

<<uses>>Out-of-Context Artifacts

<<uses>>Logical Artifacts

<<uses>>Conceptual Artifacts

<<uses>>Contextual Artifacts

guides

<<uses>>Contextual Artifacts

reviews

reviews

reviews

reviews

<<uses>>Physical Artifacts

<<uses>>Physical Artifacts

<<uses>>Logical Artifacts

<<uses>>Conceptual Artifacts

builds

builds

builds

defines

gathers

25© Copyright 2000 TASC, Inc. All Rights Reserved

Document the Framework ProcessDocument 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

26© Copyright 2000 TASC, Inc. All Rights Reserved

Define Planner ViewDefine Planner View

This Use Case shows the models used to define the Planner’s View

IdentifyContextual

Risks andBenefits

IdentifyContextual

Organization

IdentifyContextualResources

DefineContextual

Process

IdentifyContextual

Information

IdentifyContextualConcepts

IdentifyContextual

Goals

Planner(Architect)

UML Model

Owner(Stakeholder)

UML Class

UML Activityw/Objects

UML Class

UML Class

UML Class

UML Class

UML Class

27© Copyright 2000 TASC, Inc. All Rights Reserved

Business Concepts Example DiagramBusiness Concepts Example Diagram

Beta:ProjectName = <unspecified>Organization = <unspecified>Description = <unspecified>

Alpha:ProjectName = <unspecified>Organization = <unspecified>Description = <unspecified>

Systems Engineering:"Business Unit"Description = <unspecified>

TASC:"Architectural Description"Description = <unspecified>

Enterprise Architecture:SectionDescription = <unspecified>

Acme Business:CustomerDescription = <unspecified>

TASC:CompanyDescription = <unspecified>

<<entity>>

<<entity>>Project

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

persistent

<<entity>>Architectural Description

+ Description : char

persistent

<<entity>>Customer

+ Description : char

persistent

<<entity>>Business Unit

+ Description : char

persistent

Company

+ Description : char

persistent

<<entity>>Section

+ Description : char

persistent

UML Class Diagram

28© Copyright 2000 TASC, Inc. All Rights Reserved

Sample Use Case Step DocumentationSample Use Case Step Documentation

Use Case: Identify Business Concepts Communicates 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]

Description: Build a Conceptual Model. Define the important concepts used in the business. Use the following Scope Artifacts: Data, Function, Network, People, and Motivation. Output will fill in the Enterprise Model Artifact: Data with list of business objects. 

  Use Case Steps Step Text

1. "Create objects from Scope artifacts"

Use a UML Class diagram to represent important concepts used in the enterprise. Document each concept 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.

  Preconditions: "Defined Scope Artifacts“

Postconditions: "Defined Enterprise Model Artifacts"

ProcessProcess

DefineDesigner View

DefinePlanner View

GatherMission

Guidelines

DefineBuilder View

DefineOwner View

FrameArchitecture

Owner(Stakeholder)

Mission Guidelines(Vision)

Planner(Architect)

Designer(System Engineer)

Builder

Subcontractor <<uses>>Out-of-Context Artifacts

<<uses>>Logical Artifacts

<<uses>>Conceptual Artifacts

<<uses>>Contextual Artifacts

guides

<<uses>>Contextual Artifacts

reviews

reviews

reviews

reviews

<<uses>>Physical Artifacts

<<uses>>Physical Artifacts

<<uses>>Logical Artifacts

<<uses>>Conceptual Artifacts

builds

builds

builds

defines

gathers

Enterprise Architecture Process DevelopmentEnterprise Architecture Process DevelopmentEnterprise Architecture Process DevelopmentEnterprise Architecture Process DevelopmentEnterprise Enterprise Organization that uses Information Technology to perform its mission

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

ProcessProcess

Procedures that are used by the Architect to develop the Architecture

Views Views Abstractions of the Enterprise that use Models to represent the Architecture

ModelsModels

Conceptual representations of the Enterprise <<entity>>

Project

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

persistent

<<entity>>Architectural Description

+ Description : char

persistent

<<entity>> Customer

+ Description : char

persistent

<<entity>>Business Unit

+ Description :

persistent

<<entity>>Company

+ Description :

persistent

<<entity>>Section

+ Description :

persistent

Beta:ProjectName = <unspecified>Organization = <unspecified>Description = <unspecified>

Alpha:ProjectName = <unspecified>Organization = <unspecified>Description = <unspecified>

Cryptologic Engineering:"Business Unit"Description = <unspecified>

TASC:"Architectural Description"Description = <unspecified>

Enterprise Architecture:SectionDescription = <unspecified>

Acme Corp:CustomerDescription = <unspecified>

TASC:CompanyDescription = <unspecified>

ModelModel

© Copyright 2000 TASC, Inc. All Rights Reserved

Architecture-CentricArchitecture-CentricConceptual ModelConceptual Model

`

Architecture Framework

Enterprise

1

scopes

1..*Information System

1..*

1..*

guides

Information System Architecture

represents

implements

Model

View

11

1..*

1..*

1..*

1..*describes

System Descriptiondocuments

1

1..*

Artifacts

1..* 1..*

comprise

Architecture Description

defines

MissionStakeholder

holds

1..*

Requirement

fulfills

documents documents

specifies

1..*

TransformationsTransformations

OUT-OF-CONTEXT

ARTIFACTS

FUNCTIONINGENTERPRISE

NETWORK

Artifact

PEOPLE

Artifact

MOTIVATION

Artifact

FUNCTION

Artifact

CONTEXTUAL

ARTIFACTS

DATA

Artifact

FUNCTION

Artifact

NETWORK

Artifact

PEOPLE

Artifact

TIME

Artifact

CONCEPTUALARTIFACTS

DATA

Artifact

FUNCTION

Artifact

NETWORK

Artifact

PEOPLE

Artifact

TIME

Artifact

LOGICALARTIFACTS

DATA

ArtifactFUNCTION

Artifact

NETWORK

Artifact

PEOPLE

Artifact

TIME

Artifact

PHYICALARTIFACTS

DATA

Artifact

NETWORK

Artifact

PEOPLE

Artifact

TIME

Artifact

FUNCTION

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

MOTIVATION

Artifact

Create View with Models using transformations between abstraction artifacts

TIME

Artifact

DATA

Artifact

DATA Implementation

FUNCTIONImplementation

NETWORKImplementation

SCHEDULEImplementation

ORGANIZATIONImplementation

STRATEGYImplementation

`

Model BridgeModel Bridge

(How)(What) (Where) (Who) (When) (Why)

CONCEPTUAL

ARTIFACTS

DATA

Artifact

FUNCTION

Artifact

NETWORK

Artifact

PEOPLE

Artifact

TIME

Artifact

MOTIVATION

Artifact

ContextualBusiness Concepts

ContextualBusiness ConceptsContextual

Process ContextualProcess

Contextual Information

Contextual Information

ContextualResources

ContextualResources

ContextualRisks/BenefitsContextual

Risks/Benefits

ContextualGoals

ContextualGoals

ContextualOrganization

ContextualOrganization

CONTEXTUAL

ARTIFACTS

DATA

Artifact

FUNCTION

Artifact

NETWORK

Artifact

PEOPLE

Artifact

TIME

Artifact

MOTIVATION

Artifact(How)(What) (Where) (Who) (When) (Why)

Planner’s View

30© Copyright 2000 TASC, Inc. All Rights Reserved

SummarySummary

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