The Use of Zachman Framework Primitives for Enterprise Modeling

Gundars Osvalds
Senior Principal Member of Technical Staff Litton/TASC gosvalds@tasc.com
26 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

All Rights Reserved 4 .Architecture-centric Process Model Define a Mission System Engineer Identify a Framework Architect Design the System <<include>> <<include>> Implement a System Document Requirements <<include>> Develop an Architecture <<include>> Stakeholder <<include>> <<include>> Developer © Copyright 2000 TASC. Inc.

Inc.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. All Rights Reserved 5 .

* describes 1..* represents 1..* comprise Model 1..* 1 specifies 1...* scopes fulfills 1.* guides Requirement Information System implements Architecture 1. All Rights Reserved 6 .Conceptual Model Enterprise 1 defines It all begins with the framework Architecture Framework Stakeholder 1.* This model documents the architecture-centric concepts associated with enterprise development 1 contains View 1..* © Copyright 2000 TASC..* holds 1...* documents documents guides System Description Architecture Description 1.* Artifacts 1...* Mission 1..* 1.. Inc.

.* comprise Model 1.* View One or more abstractions e. People..g..* Artifacts 1. Time.* 1. and Motivation © Copyright 2000 TASC.Framework Components A logical structure for classifying and organizing the models of an enterprise Architecture Framework A formal definition of an enterprise system represents Architecture Contains the views that are used to describe the architecture documents Architecture Description 1 specifies 1. Function.. Builder. Planner... Designer. Owner. All Rights Reserved 7 . Subcontractor The basic elements describes 1. Inc.* Representations of the Data. Network.

All Rights Reserved 8 . Inc. Popkin) Spewak’s Enterprise Architecture Planning © Copyright 2000 TASC.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.

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 © Copyright 2000 TASC. Inc. All Rights Reserved 9 .

Inc.Conceptual Description of The Zachman Framework DATA (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. All Rights Reserved 10 .

g.g. Master Schedule ENTERPRISE MODEL Owner conceptual Entity = Business Entity Rel. Technical Architecture People = Role Work = Deliverable e.g. Control Structure End = Structural Assertion Means =Action Assertion e.. Zachman.. Network Architecture People = User Work = Screen/Device Format e... Business Plan Time = Major Business Event e. = 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 DATA Implementation FUNCTION Implementation NETWORK Implementation ORGANIZATION Implementation SCHEDULE Implementation STRATEGY Implementation John A. Logistics Network People = Class of People and Major Organizations e.g.. All Rights Reserved .g.g.. Rule Specification DETAILED REPRESENTATIONS Subcontractor out-of-context FUNCTIONING ENTERPRISE Entity = Field Rel.g... Distributed System Architecture People = Organization Unit Work = Work Product e.g.g. = Business Relationship e. Physical Data Model Process. Presentation Architecture Time = System Event Cycle = Processing Cycle e.g.g. Program Node = Hardware/System Software Link = Line Specifications e.= Application Function I/O = User Views e. Business Rule Model SYSTEM MODEL Designer logical Entity = Data Entity Rel.. Semantic Model Function = Class of Business Process e. Inc.. Security Architecture Time = Execute Cycle = Component Cycle e.g. Work Flow Model Ends/Means=Major Business Goal/Critical Success Factor e.g.. Timing Definition End = Condition Means = Action e.. Rel. System Design Node = IS Function Link = Line Characteristics e. Human Interface Architecture Time = Business Event Cycle = Business Cycle e... Zachman International © Copyright 2000 TASC.Zachman Framework for Enterprise Architecture abstractions perspectives DATA What List of Things Important to the Business FUNCTION How List of Processes the Business Performs NETWORK Where List of Locations in which the Business Operates PEOPLE Who List of Organizations Important to the Business TIME When List of Events Significant to the Business MOTIVATION Why List of Business Goals and Strategies SCOPE Planner contextual Entity = Class of Business Thing e. = Key/Pointer/etc.g.. Application Architecture Node = Business Location Link = Business Linkage e. Data Definition Process= Computer Function I/O =Data Elements/Sets e. Rule Design TECHNOLOGY CONSTRAINED MODEL Builder physical Entity = Tables/Segments/etc.g. Business Process Model Node = Major Business Location e.g.g..g.g... e.g.g.g. Processing Structure End = Business Objective Means = Business Strategy e.g. Logical Data Model Process = Business Process I/O = Business Resources e. = Data Relationship e.g.

Relationship of Models to the Zachman Framework  How does Zachman define primitives. Inc. single-variable models?  How are the single-variable models in to describe the perspectives?  How does the Zachman framework define the perspective views? © Copyright 2000 TASC. All Rights Reserved 12 .

g. Rule Specification DETAILED REPRESENTATIONS Subcontractor out-of-context FUNCTIONING ENTERPRISE Entity = Field Rel.. Physical Data Model Process. Inc. Work Flow Model Ends/Means=Major Business Goal/Critical Success Factor e.g. Processing Structure End = Business Objective Means = Business Strategy e.g. Zachman International © Copyright 2000 TASC.g. Logical Data Model Process = Business Process I/O = Business Resources e. Technical Architecture Each cell contains a single variable model People = Role Work = Deliverable Time = System Event Cycle = Processing Cycle e....g...g. Application Architecture Node = Business Location Link = Business Linkage e. Business Plan Time = Major Business Event e.g. Business Rule Model SYSTEM MODEL Designer logical Entity = Data Entity Rel.g. = 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 DATA Implementation FUNCTION Implementation NETWORK Implementation ORGANIZATION Implementation SCHEDULE Implementation STRATEGY Implementation John A. = Data Relationship e. Network Architecture People = User Work = Screen/Device Format e. Logistics Network People = Class of People and Major Organizations e..g..g. Data Definition Process= Computer Function I/O =Data Elements/Sets e. Control Structure e..g. Distributed System Architecture People = Organization Unit Work = Work Product e.g. Program Node = Hardware/System Software Link = Line Specifications e. Zachman. Rel. Semantic Model Function = Class of Business Process e. Human Interface Architecture Time = Business Event Cycle = Business Cycle e. System Design Node = IS Function Link = Line Characteristics e.g.. = Key/Pointer/etc.g.g.g. Business Process Model Node = Major Business Location e. Presentation Architecture e. All Rights Reserved .g.g. Timing Definition End = Condition Means = Action e.Zachman Framework Single Variable Examples abstractions perspectives DATA What List of Things Important to the Business FUNCTION How List of Processes the Business Performs NETWORK Where List of Locations in which the Business Operates PEOPLE Who List of Organizations Important to the Business TIME When List of Events Significant to the Business MOTIVATION Why List of Business Goals and Strategies SCOPE Planner contextual Entity = Class of Business Thing e.. Master Schedule ENTERPRISE MODEL Owner conceptual Entity = Business Entity Rel.. = Business Relationship e. Rule Design End = Structural Assertion Means =Action Assertion TECHNOLOGY CONSTRAINED MODEL Builder physical Entity = Tables/Segments/etc...g.g..g.g...= Application Function I/O = User Views e. Security Architecture Time = Execute Cycle = Component Cycle e.g. e..g.

All Rights Reserved 14 .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.

. Logistics Network The cells contain primitives NETWORK 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 Designer’s View Logical Packages Logical Scenarios Logical Components Logical Interactions © Copyright 2000 TASC. Inc. All Rights Reserved 15 .Primitives to Work Products e.g.

All Rights Reserved 16 .CONTEXTUAL ARTIFACTS Zachman Framework Artifacts DATA 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 PEOPLE PEOPLE Artifact Artifact TIME TIME Artifact Artifact MOTIVATION MOTIVATION Artifact Artifact DATA Artifact MODEL ARTIFACTS MODEL ARTIFACTS FUNCTION 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 data TIME TIME Artifact Artifact TIME TIME MOTIVATION MOTIVATION OUT-OFCONTEXT ARTIFACTS DATA DATA Artifact Artifact FUNCTION FUNCTION Artifact Artifact NETWORK NETWORK Artifact Artifact PEOPLE PEOPLE Artifact Artifact MOTIVATION MOTIVATION Artifact Artifact FUNCTIONING ENTERPRISE DATA Implementation FUNCTION Implementation NETWORK Implementation ORGANIZATION Implementation SCHEDULE Implementation STRATEGY Implementation © Copyright 2000 TASC. Inc.

Create Views and Composite Models CONTEXTUAL 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 artifacts CONCEPTUAL 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 DATA DATA Artifact Artifact FUNCTION FUNCTION Artifact NETWORK NETWORK Artifact Artifact Transformation is the key to bridging the PEOPLE perspectives TIME PEOPLE TIME MOTIVATION MOTIVATION Artifact Artifact Artifact Artifact Artifact Artifact PHYSICAL 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 OUT-OFCONTEXT ARTIFACTS FUNCTIONING ENTERPRISE DATA DATA Artifact Artifact DATA Implementation FUNCTION FUNCTION Artifact Artifact FUNCTION Implementation NETWORK NETWORK Artifact Artifact NETWORK Implementation PEOPLE PEOPLE Artifact Artifact ORGANIZATION Implementation TIME TIME Artifact Artifact SCHEDULE Implementation MOTIVATION MOTIVATION Artifact Artifact STRATEGY Implementation © Copyright 2000 TASC. All Rights Reserved . Inc.

Inc.External Inputs to the Zachman Framework Requirements Requirements Concept of Concept of Operations Operations Business Business Plan Plan CONTEXTUA 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) © Copyright 2000 TASC. All Rights Reserved .

All Rights Reserved .Planner’s View CONTEXTUA 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) Planner’s View Contextual Concepts Contextual Information Contextual Process Contextual Organization Contextual Resources Contextual Risks/Benefits Contextual Goals CONCEPTUA 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) © Copyright 2000 TASC.Bridging the Zachman Framework Bridging the Zachman Framework Perspectives . Inc.Planner’s View Perspectives .

All Rights Reserved .Bridging the Zachman Framework Bridging the Zachman Framework Perspectives .Owner’s View Perspectives . Inc.Owner’s View CONCEPTUA 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) Owner’s View Conceptual Process States Conceptual Resource Interactions Conceptual Process LOGICAL 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) © Copyright 2000 TASC.

Inc.Designer’s View Perspectives .Designer’s View LOGICAL 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) Designer’s View Logical Scenarios Logical Packages Logical Components Logical Interactions PHYSICAL ARTIFACTS DATA Artifact Artifact (What) (What) FUNCTION FUNCTION Artifact Artifact (How) (How) NETWORK NETWORK Artifact (Where) (Where) PEOPLE PEOPLE Artifact Artifact (Who) (Who) TIME TIME Artifact Artifact (When) (When) MOTIVATION MOTIVATION Artifact Artifact (Why) (Why) © Copyright 2000 TASC. All Rights Reserved .Bridging the Zachman Framework Bridging the Zachman Framework Perspectives .

Builder’s View Perspectives . Inc.Builder’s View PHYSICAL 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) Builder’s View Physical Activities Physical Elements Physical Interactions Physical Deployment Physical Behaviors OUT-OFCONTEXT ARTIFACTS FUNCTIONING ENTERPRISE DATA DATA Artifact Artifact (What) (What) DATA Implementation FUNCTION FUNCTION Artifact Artifact (How) (How) FUNCTION Implementation NETWORK NETWORK Artifact Artifact (Where) (Where) NETWORK Implementation PEOPLE PEOPLE Artifact Artifact (Who) ORGANIZATION Implementation TIME TIME Artifact Artifact (When) (When) SCHEDULE Implementation MOTIVATION MOTIVATION Artifact Artifact (Why) (Why) STRATEGY Implementation © Copyright 2000 TASC.Bridging the Zachman Framework Bridging the Zachman Framework Perspectives . All Rights Reserved .

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. All Rights Reserved 23 . Inc.

Defining the Enterprise Architecture Mission 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 <<uses>> Contextual Artifacts <<uses>> Contextual Artifacts <<uses>> Conceptual Artifacts <<uses>> Conceptual Artifacts Define Owner View <<uses>> Logical Artifacts Owner (Stakeholder) builds Frame Architecture Designer (System Engineer) reviews builds Builder reviews <<uses>> Logical Artifacts Define Designer View <<uses>> Physical Artifacts builds Subcontractor reviews Define Builder View <<uses>> Physical Artifacts <<uses>> Out-of-Context Artifacts © Copyright 2000 TASC. Inc. All Rights Reserved 24 .

All Rights Reserved 25 . Inc.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 © Copyright 2000 TASC.

All Rights Reserved 26 .Define Planner View Planner (Architect) This Use Case shows the models used to define the Planner’s View Identify Contextual Risks and Benefits UML Class Identify Contextual Organization Identify Contextual Information UML Class UML Class Identify Contextual Goals UML Class UML Class Identify Contextual Resources UML Model UML Class Owner (Stakeholder) Identify Contextual Concepts Define Contextual Process UML Activity w/Objects © Copyright 2000 TASC. Inc.

Inc.Business Concepts Example Diagram <<entity>> Customer + Description : char <<entity>> Company + Description : char UML Class Diagram Acme Business:Customer Description = <unspecified> TASC:Company Description = <unspecified> persistent persistent Systems Engineering:"Business Unit" Description = <unspecified> <<entity>> Business Unit + Description : char Alpha:Project Name = <unspecified> Organization = <unspecified> Description = <unspecified> Enterprise Architecture:Section Description = <unspecified> Beta:Project Name = <unspecified> Organization = <unspecified> Description = <unspecified> <<entity>> Project + Name : char + Organization : char + Description : char persistent persistent <<entity>> Architectural Description + Description : char <<entity>> Section + Description : char TASC:"Architectural Description" Description = <unspecified> persistent persistent © Copyright 2000 TASC. All Rights Reserved 27 .

Inc. artifacts" important concepts used in the the following Scope Artifacts: Data. Function. "Define interactions between objects" Document the relationships between the business concept objects using information from the Scope Artifacts. Use   Use Case Steps Step Text Preconditions: "Defined Scope Artifacts“ Postconditions: "Defined Enterprise Model Artifacts" © Copyright 2000 TASC. and Motivation. 2. with a few sentences in the description fields.Sample 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] 1. All Rights Reserved 28 . Define the important concepts used in the business. "Create objects from Scope Use a UML Class diagram to represent Description: Build a Conceptual Model. People. Network. Output will fill in the enterprise. Document each concept Enterprise Model Artifact: Data with list of business objects.

* Artifacts comprise 1..* 1.* fulfills 1..* View 1.* CONCEPTUAL ARTIFACTS Model LOGICAL ARTIFACTS DATA Artifact FUNCTION Artifact NETWORK Artifact PEOPLE Artifact TIME Artifact MOTIVATION Artifact Process Procedures 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 Bridge CO 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 ACTS FUNCTIONING ENTERPRISE DATA Artifact DATA Implementation FUNCTION Artifact FUNCTION Implementation NETWORK Artifact NETWORK Implementation PEOPLE Artifact ORGANIZATION Implementation TIME Artifact SCHEDULE Implementation MOTIVATION Artifact STRATEGY Implementation Views Abstractions of the Enterprise that use Models to represent the Architecture Planner’s View Contextual 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 Process Mission Guidelines (Vision) Planner (Architect) guides gathers defines Owner (Stakeholder) reviews Gather Mission Guidelines <<uses>> Contextual Artifacts Define <<uses>> Planner View Contextual Artifacts <<uses>> Conceptual Artifacts <<uses>> Conceptual Artifacts Frame Define Architecture Owner View <<uses>> Logical Artifacts <<uses>> Logical Artifacts Define Designer View <<uses>> Physical Artifacts <<uses>> Physical Artifacts Define Builder View <<uses>> 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) Models Conceptual representations of the Enterprise Acme Corp:Customer Description = <unspecified> Alpha:Project Name = <unspecified> Organization = <unspecified> Description = <unspecified> Model TASC:Company Description = <unspecified> <<entity>> Customer + Description : char persistent Cryptologic Engineering:"Business Unit" Description = <unspecified> <<entity>> Company + Description : persistent <<entity>> Business Unit <<entity>> 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 = <unspecified> Beta:Project Name = <unspecified> Organization = <unspecified> Description = <unspecified> <<entity>> Architectural Description + Description : char TASC:"Architectural Description" Description = <unspecified> persistent <<entity>> Section + Description : persistent © Copyright 2000 TASC..* holds 1..Enterprise Architecture Process Development Enterprise Architecture Process Development Enterprise Organization that uses Information Technology to perform its mission Architecture-Centric Conceptual Model Enterprise Stakeholder Architecture "Blueprint" of the Enterprise that provides guidance to the Systems Engineers 1.. All Rights Reserved ...* describes 1.* Architecture Framework represents implements Information System Architecture Information System guides documents System Description Transformations CONTEXTUAL 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 documents Architecture Description 1 specifies 1. Inc....* Requirement scopes Mission 1 defines 1.* 1..* 1.

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 © Copyright 2000 TASC. Inc. All Rights Reserved 30 .

Sign up to vote on this title
UsefulNot useful