ea - lecture 2snu-dhpm.ac.kr/pds/files/061101 lecture 02_zachman... · 2006. 12. 13. ·...

공학기술개론 1

EA - Lecture 2

ZachmanZachman Framework Framework

2005. 9. 9최영환


CSF of BusinessAgility

For value creationCustomer satisfaction & excitement

Cost ReductionOutsourcing (ITO, BPO) for risk reduction

Main Frame

1980s : ISP

• Logical relationship between application systems

Distributed System

1990s : ITA

• Logical relationship between application and infrastructure

• ITA = DA + AA + TA

Virtual System

2000s : EA

• Business driven ITA for virtual enterprises

• EA = BA + ITA


ContentsConcepts & Rules of Zachman FrameworkRows of Zachman FrameworkColumns of Zachman Framework

1st Col : Data (What)2nd Col : Process (HOW)3rd Col : Network (Where)Extended Columns

Zachman Framework & MDARemarks on Zachman Framework


Concepts & Rules


Jone Zachman

"A Framework for Information Systems Architecture",

IBM Systems Journal, 1987

“Organizations and systems must be designed for change.”

Father of Enterprise Architecture


Concepts of Zachman건축건물의설계는하나이상의청사진의조합이다

(기초, 방의배치, 전기시스템, 수도관 ···)

조직조직내그룹마다계획의내용이다르다

새로운전략과목표하에서변화제시

업무프로세스정의

새로운 software application 디자인의도대로조직이활동하는지보장하기위해그요소들이어떻게서로조화되는지정의한다.

관리자가조직에대해총괄적으로생각하도록돕는도구의필요


Concepts of ZachmanArchitecture

Logical frameworkDefine and control the interface and the integration of all of the components of the systemFor decentralization


Rules of Framework

Columns have no order. Each column has a simple, basic model.Basic model of each column is unique.Each row represents a distinct view.Each cell is unique.Combining the cells in one row forms a complete description from that perspective.

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

Basic Model = Entities and Relationships

RelationshipEntityEntity


Rules of FrameworkThe Logic is Recursive


Rules of FrameworkOMG Metadata Architecture

Customertitle = “Dr”name = “Joe”

Customertitle = “Mr”name = “Mark”

Ordernumber = “2604”name = “PO”

Customertitle : Stringname : String

Ordernumber : Stringname : String

<<instanceOf>> <<instanceOf>> <<instanceOf>>

M0 :

M1 :

M2 :

M3 :



M0 :

M1 :

M2 :

M3 :

UML Class

name=“Customer”

UML Class

name = “Order”

UML Attribute

name = “number”

UML Class

name : String

UML Attribute

name : String

<<instanceOf>> <<instanceOf>> <<instanceOf>>



M0 :

M1 :

M2 :

M3 :

MOF Class

name=“UML Class”

MOF Class

name = “UML Attribute”

MOF Class

name : String

<<instanceOf>> <<instanceOf>>


Zachman FrameworkEnterprise Architecture 서술적측면의사실상표준전사적범위의관점과시각

Sliver 개념의도입Engineering 목적인통합성, 정렬, 상호운용성에,Architecting 목적인이식성, 유연성, 적응성등을설명

What Data

How Function

Where Network

Who People

When Time

Why Motivation

Scope (Contextual)

Enterprise Model (Conceptual)

Builder

Planner

Owner

Designer

Sub-contractor

System Model (Logical)

Technology Model (Physical)

Component (Out-of-context)

Views (관점)수평통합

Perspectives(시각) 수직통합

Depth & Detail 범위(범위통합)

Bus

ines

s In

form

atio

n Te

chno

logy

SliverSliver


EA Components in Zachman Framework

데이터

아키텍쳐

비즈니스

아키텍쳐

애플리케이션

아키텍쳐

기술

아키텍쳐조직구조

프로젝트

관리

전략적

계획


Zachman Framework

e.g. DATA

Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEMMODEL(LOGICAL)

TECHNOLOGYMODEL(PHYSICAL)

DETAILEDREPRESEN-

TATIONS(OUT-OF-

CONTEXT)

Sub-Contractor

FUNCTIONINGENTERPRISE

DATA FUNCTION NETWORK

e.g. Data Definition

Ent = FieldReln = Address

e.g. Physical Data Model

Ent = Segment/Table/etc.Reln = Pointer/Key/etc.

e.g. Logical Data Model

Ent = Data EntityReln = Data Relationship

e.g. Semantic Model

Ent = Business EntityReln = Business Relationship

List of Things Importantto the Business

ENTITY = Class ofBusiness Thing

List of Processes theBusiness Performs

Function = Class ofBusiness Process

e.g. Application Architecture

I/O = User ViewsProc .= Application Function

e.g. System Design

I/O = Data Elements/SetsProc.= Computer Function

e.g. Program

I/O = Control BlockProc.= Language Stmt

e.g. FUNCTION

e.g. Business Process Model

Proc. = Business ProcessI/O = Business Resources

List of Locations in whichthe Business Operates

Node = Major BusinessLocation

e.g. Business Logistics System

Node = Business LocationLink = Business Linkage

e.g. Distributed System

Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics

e.g. Technology Arch.

Node = Hardware/SystemSoftware

Link = Line Specifications

e.g. Network Architecture

Node = AddressesLink = Protocols

e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING

MOTIVATIONTIMEPEOPLE

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/Strat

Ends/Means=Major Biz. Goal/Critical Success Factor

List of Events Significant

Time = Major Business Event

e.g. Processing Structure

Cycle = Processing CycleTime = System Event

e.g. Control Structure

Cycle = Component CycleTime = Execute

e.g. Timing Definition

Cycle = Machine CycleTime = Interrupt

e.g. SCHEDULE

e.g. Master Schedule

Time = Business EventCycle = Business Cycle

List of Organizations

People = Major Organizations

e.g. Work Flow Model

People = Organization UnitWork = Work Product

e.g. Human Interface

People = RoleWork = Deliverable

e.g. Presentation Arch.

People = UserWork = Screen Format

e.g. Security Architecture

People = IdentityWork = Job

e.g. ORGANIZATION

Planner

Owner

to the BusinessImportant to the Business

What How Where Who When Why

SCOPE(CONTEXTUAL)

Architecture

e.g. STRATEGY ENTERPRISE

e.g. Business Plan


Rows of ZachmanFramework


Architectural RepresentationsRepresentation Nature / Purpose

Bubble Charts

• Basic concepts for building• Gross sizing, shape, spatial relationships• Architect/owner mutual understanding• Initiate project

Architect’s Drawings

• Final building as seen by the owner• Floor plans, cutaways, pictures• Architect/owner agreement on building• Establish contract

Architect’s Plans

• Final building as seen by the designer• Translation of owner’s view into a product• Detailed drawings – 16 categories• Basis for negotiation with general contractor

Contractor’s Plans

• Final building as seen by the builder• Architect’s plans constrained by laws of nature and available technology• “How to build it” description• Directs construction activities

Shop Plans

• Subcontractor’s design of a part/section• Detailed stand-alone model• Specification of what is to be constructed• Pattern

Building • Physical building


Architectural RepresentationsBubble Chart Architect’s Drawing


Architectural RepresentationsArchitect’s Plan Contractor’s Plan


Architectural RepresentationsA Generic Set of Architectural Representations

Generic Buildings Airplanes Information Systems

Planner’s rep. Bubble charts Concepts Scope/objectives

Owner’s rep. Architect’s drawings Work breakdown structure Business model

Designer’s rep. Architect’s plans Eng. design/BOM System model

Builder’s rep Contractor’s plans Mfg. design/BOM Technology model

Out-of-context rep. Shop plans Assembly drawings Detailed description

Machine language rep. - NC programs Object codes

Product Building Airplane Information System


Different Types of Description

Row Perspective Constraint Model

1 PlannerFinancialExternal

Scope

2 OwnerUsagePolicy

Enterprise Model

3 DesignerStructureOperation

System Model

4 Builder Technology Technology Model

5 Subcontractor Implementation Out-of-context Models


Different Types of Description

Row Perspective Focus

1 ContextualExternal requirements and driversBusiness function modeling

2 ConceptualBusiness process modelsBusiness function allocationElimination of function overlap and ambiguity

3 LogicalLogical modelsProject managementRequirements definition

4 PhysicalPhysical modelsTechnology managementSolution definition and development

5 As-BuiltConfiguration managementDeployment

6 Functioning Enterprise

Operations managementEvaluation


Columns of ZachmanFramework


Different Abstractions of a Thing

Description 1 Description 2 Description 3

Orientation Material Function Location

Focus Structure Transform Flow

Description WHAT the thing is made of HOW the thing works WHERE the flows exists

Example BOM Functional specifications Drawings

Descriptive model Part-relationship-part Input-process-output Site-link-site

IS analogy Data model Process model Network model

IS Descriptive model Entity-relationship-entity Input-process-output Node-line-node


ISA FrameworkFramework for

Information Systems Architecture


Extended Framework


1st Col : Data (What)Entity-Relationship-Entity


1st Column : Data1st Row : Planner’s Perspective (Scope)

A list of things (nouns) as opposed to a list of actions (verbs) : entityStrategy/resource investment decisionSample entities

What How Where Who When WhyPlannerOwner

DesignerBuilder

Out


1st Column : Data2nd Row : Owner’s Perspective (Business Model)

Entities in different modelsEmployee : real being (business entity)Employee : refer to a record on a machine (data entity)

Real-life examples are mixed representationsHard to understand


DesignerBuilder

Out


1st Column : DataWhat How Where Who When Why

PlannerOwner

DesignerBuilder

Out

Sample Entity Relationship Model

Business Entity

Business Rule/Strategy


1st Column : DataWhat How Where Who When Why

PlannerOwner

DesignerBuilder

Out

3rd Row : Designer’s Perspective (System Model)Entity : record of a machineRelationship : data relationship

artificial entity


1st Column : Data4th Row : Builder’s Perspective (Technology Model)

The laws of nature and technology constraints are being applied.For Information Management System

Segment (entity) & Pointer (relationship)For Database System

Row (entity) & Key (relationship)


DesignerBuilder

Out


1st Column : Data5th Row : Out-of-Context (Detailed Description)

Field : entityAddress : relationship


DesignerBuilder

Out


2nd Col : Process (HOW)Input-Process-Output


2nd Column : Process1st Row : Planner’s Perspective (Scope)

Each of the representation in the different cells have differentmeanings associated with input, process, and output.

Scope description Process : business process


DesignerBuilder

Out


2nd Column : Process2nd Row : Owner’s Perspective (Business Model)

Functional flow diagramProcess : business process

not information system processInput, output : business resources

people, cash, material, product, etc.


DesignerBuilder

Out


2nd Column : Process3rd Row : Designer’s Perspective (System Model)

Flow diagramProcess : information system process (application)Input, output : some aggregation data


DesignerBuilder

Out


2nd Column : Process4th Row : Builder’s Perspective (Technology Model)

Process : computer functionInput, output : device format


DesignerBuilder

Out


2nd Column : Process5th Row : Out-of-Context (Detailed Description)

Process : programInput, output : control blocks

(6th Row : Actual system)Object code, machine language representation


DesignerBuilder

Out


3rd Col : Network (Where)Node-Line-Node


3rd Column : NetworkWhat How Where Who When Why

PlannerOwner

DesignerBuilder

Out

ScopeList of location in which the business operateNode : business location

Business ModelNode : business unit

Aggregation business resources at geographical location

Line : logistic connection or flows



PlannerOwner

DesignerBuilder

Out

System ModelConceptual representation, independent of specific technology.Node : IS function

Process storage unit, access point, etc.Line : communication line

Dialup service, mail, etc

Technology ModelPhysical hardware & softwareNode : IBM 3090 processor, PC, communication program, etc.Line : synchronous data link control, 4800 baud, etc.



PlannerOwner

DesignerBuilder

Out

Detailed DescriptionNode : addressLine : protocol


Extended Columns


4th Column : PeoplePeople (Who)

Basic model : People-Work-PeopleWork allocation types

HierarchyMarkets (pool system)


DesignerBuilder

Out

Row Perspective Cell Example Agent Work1 Planner

Owner

Designer

Builder

Subcontractor

Organization list Class of agent2 Organization chart Organization unit Work product

3 Human interface architecture Role Deliverable

4 Human/technology interface User Job

5 Security architecture Identity Transaction

Transaction is simple, well-defined and universally

understood

Transaction is complex, not well-defined, and not

universally understood


5th Column : TimeTime (When)

Basic model : Event-Duration-EventCommitments of enterprise

Length of the durationResources level


DesignerBuilder

Out

Row Perspective Cell Example Event Cycle1 Planner

Owner

Designer

Builder

Subcontractor

List of events Major event Major cycle2 Master schedule Business event Business cycle

3 Processing structure System event Processing cycle

4 Control architecture Execute Component cycle

5 Timing definition Interrupt Machine cycle


6th Column : Motivation Motivation (Why)

Basic model : Ends-Means-EndsEnds : objectives (goals)Means : strategies (methods)


DesignerBuilder

Out

Row Perspective Cell Example Ends Means

1 Planner

Owner

Designer

Builder

Subcontractor

Objectives list Major objectives Major strategies

2 Business plan Business objectives Business strategy

3 Knowledge architecture Criterion Option

4 Knowledge design Condition Action

5 Knowledge definition Subcondition Step


6th Column : Motivation What How Where Who When Why

PlannerOwner

DesignerBuilder

Out

Case of a Video Tape Store


Zachman Framework & MDA


Model Driven Architecture

PIM

Platform Specific Model

CORBA Model

Java/EJB Model

XML/SOAP Model

Other Model

Standard Mapping

CORBA Java/EJB XML/SOAP Other

Platform Indep. Model• Technology-neutral • Vendor-neutral

Platform Specific Data

Generates implementation code

Business Logic

OMG MDA


Model Driven ArchitectureLevels of MDA Models


MDA Models & ZF


UML Diagrams & ZF


MDA Standards & ZF


Remarks on Zachman Framework


RemarksContributions

The use of structured framework for IT management.Standard for information assets of US government.Basis of various EA frameworks such as FEA, DoDAF, TEAF, etc.

LimitationsDid not address any implementation methodologies using the framework.

ea - lecture 2snu-dhpm.ac.kr/pds/files/061101 lecture 02_zachman... · 2006. 12. 13. ·...

Documents