WHERETO FROM ZACHMAN Architecture Practitioners’ conference April 2004 VISH VISWANATHAN Managing Consultant- CCANDC Solutions Regional Partner- The Open Group (Australia/ New Zealand /ASEAN) Vice Chair-Asia/Pacific, Architecture Forum e.g. DATA ENTERPR I SE ARCH I TECTURE - A FRAMEWORK Builder SCOPE (CONTEXTUAL) MODEL (CONCEPTUAL) ENTERPR I SE Designer SYSTEM MODEL (LOGICAL) TECHNOLOGY MODEL (PHYSI CAL) DETAI LED REPRESEN- TATIONS (OUT-OF- CONTEXT) Sub- Contractor FUNCT I ONI NG ENTERPR I SE DATA FUNCT I ON NETWORK e.g. Data Definition Ent = Field Rel n = Address e.g.Physi calDataModel Ent = Segment/Tabl e/etc. Rel n=Poi nter/Key/etc. e.g. Logi calData Model Ent = Data Entity Rel n = Data Rel at i onshi p e.g. Semant i c Model Ent = Business Entity Rel n = Busi ness Rel at i onshi p List of Things Important to the Busi ness ENTI TY=Cl assof Busi nessThi ng List of Processes the Busi nessPerforms Funct i on = Cl ass of Busi nessProcess e.g. Application Architecture I/O = User Vi ews Proc .= Appl i cat i on Funct i on e.g. System Desi gn I/O = Data El ements/Sets Proc.= Computer Funct i on e.g. Program ll Proc.= Language Stmt e.g. FUNCTION e.g. Busi ness Process Model Proc. = Busi ness Process I/O = Busi ness Resources Li stofLocat i onsi nwhi ch the Busi ness Operates Node = Maj or Busi ness Location e.g. Business Logistics System Node = Busi ness Locat i on Li nk = Busi ness Li nkage e.g.Distributed System Link = Line Characteristics e.g. Technology Architecture Node = Hardware/System Software Li nk = Li ne Speci f i cat i ons e.g. NetworkArchitecture Node = Addresses Link = Protocols e. g. NETWORK Architecture Planner Owner Builder ENTERPR I SE MODEL (CONCEPTUAL) Designer SYSTEM MODEL (LOGICAL) TECHNOLOGY MODEL (PHYSICAL) DETAI LED REPRESEN- TAT I ONS (OUT-OF CONTEXT) Sub- Contractor FUNCT I ONI NG MOT I VAT I ON T I ME PEOPLE e.g. Rule Specification End = Sub-condition Means = Step e.g. Rul e Desi gn End = Condi t i on Means = Act i on e.g., Busi ness Rul e Model Means=Act i onAssert i on End = Busi ness Obj ect i ve Means = Busi ness Strategy Li stofBusi nessGoal s/Strat Ends/Means=Maj or Bus. Goal / Cr i t i calSuccessFactor List of Events Significant Ti me = Maj or Busi ness Event e.g. Processing Structure l i l Ti me = System Event e.g. Control Structure l e = Component Cycl e Ti me = Execute e.g.Timing Definition l i ne Cycl e Ti me = Interupt e.g. SCHEDULE e.g. Master Schedul e Ti me = Busi ness Event Cycl e = Busi ness Cycl e List of Organizations Peopl e = Maj or Organi zat i ons e.g. Work Fl ow Model Peopl e = Organi zat i on Uni t Work = Work Product e.g. Human Interface l l Work = Deliverable e.g.Presentat i onArchi tecture l Work = Screen Format e.g. SecurityArchitecture Peopl e = Ident i ty Work=Job e. g.ORGANI ZATI ON Planner Owner to the Busi ness Important to the Busi ness What How Where Who When Why John A. Zachman, Zachman International (810) 231-0531 SCOPE (CONTEXTUAL) Archi tecture e. g.STRATEGY ENTERPRI SE e.g. Busi ness Pl an TM
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
WHERETO FROM ZACHMANArchitecture Practitioners’ conference
April 2004
VISH VISWANATHAN
Managing Consultant- CCANDC Solutions
Regional Partner- The Open Group (Australia/ New Zealand /ASEAN)
Vice Chair-Asia/Pacific, Architecture Forum
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
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/Sets
Proc.= 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 which the 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 Architecture
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 = Condition
Means = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. 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 Architecture
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
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
CIO champions EAAs the solution
Appoints Enterprise ArchitectRequires EA to be developed ASAP
Enterprise Architect looks for help
ROI Pressures
On CIO
ØConsultants
ØWeb based information
Ø Seminars
CURRENT STATE OF PLAY OF EA IN AUSTRALASIA
Employ first tier consultants(outsource)
Take over implementation(in source)
Investigation Phase Reports Initial Implementation Full Implementation
Get training & hand holding Assistance from specialist consultants
Select Framework, methodology & tools Assistance from specialist consultants
Use in-house resources
QA Review /audit By specialist consultants
TYPICAL EA PROJECT START UP PROCESS
In-house investigation
OR
A WELL KNOWN HIGH LEVEL FRAMEWORK……….
ØZACHMAN FRAMEWORK
• De-facto standard for classifying the Enterprise architectural artifacts
• Logical structure for analysing and presenting artifacts from a management perspective
• Draws parallels from the well understood Engineering or Construction paradigm
• Widely recognised as a management tool for checking architectural completeness and maturity
• No processes for implementation
• Difficult to implement in total
• No ready examples or checklists
• Extent of coverage of the cells unclear
A DISCIPLINED PROCESS……………
ØTOGAF
• Focuses on implementation cycle (ADM) and processes
• Has a foundation architecture as a part of “Enterprise continuum”
• Rich in the technical architecture area
• Resource base provides a lot of reference materials
• Supported by a set of certification processes
• Being positioned as the benchmark for EA best practice
and AN EASY-TO-USE TOOL ………….
Ø SYSTEM ARCHITECT
• Certified formally as TOGAF support tool / Ongoing commitment for future versions
• Comprehensive support for Zachman Framework
• Can be customised and extended to facilitate a hybrid approach
• Has a variety of built-in EA related models and artifacts
• Easy to learn
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
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 which the 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 Architecture
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 Bus. 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 Architecture
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
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
A
G
BC
F
P
Practical Enterprise Architecture implementation using a hybrid approach
ZACHMAN FRAMEWORK
E
DH
TOGAF8
•Step by Step process
•Templates / checklists
•Customised features
•Training & professional services
VALUE ADDS
8
Architectural Development Planning
Business
Application
DataTechnology
Principles Rules Guidelines Models Building Blocks Standards
EA Version 1.0
EA Version 2.0
EA Version 3.0
EA Version 4.0
9
The Enterprise Architecture “Shell”
Business
Application( Systems)
Information (Data)
Technology (Infrastructure)
Principles /Rules/Guidelines
Principles /Rules/Guidelines
Principles /Rules/Guidelines
MODELS
MODELS
MODELS
Building BlocksInformation Base
Standards
Information BaseTRM
Principles /Rules/Guidelines
Governance
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
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 which the 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 Architecture
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-condition
Means = 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 Bus. 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 Architecture
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
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGY ENTERPRISE
e.g. Business Plan
TM
SIMPLIFIED COVERAGE OF ALL FOUR EA LAYERS
Business Application
Data TechnologyPlanning/Vision
11
Migrationplanning
Migrationplanning
Opportunities & solutions
Opportunities & solutions
Implementation& Governance
Implementation& Governance
Information Systems
Architecture
Information Systems
Architecture
ArchitectureChange
maintenance
ArchitectureChange
maintenance
Business Architecture
Business Architecture
Architectural Vision
Architectural Vision
RequirementsManagement
RequirementsManagement
Framework andprinciples
Framework andprinciples
EA services (ADM plus)EA services (ADM plus)
TechnologyArchitecture Technology
Architecture G
E
D
B
CH
F
A
PChecklists/templates
Touch points toExisting PMO processes
EA deliverables Planning
EA Objects
EA workshops
üSENIOR EXECUTIVESüARCHITECTSüPROJECT MANAGERSüEA USERS
Collaborative
Creation
processes
Customised Governanceprocesses
Customised Changeprocesses
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
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 which the 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 Architecture
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 Bus. 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 Architecture
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
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
A
G
BC
F
P
1. TOGAF Phase P plus: Creation of the “EA shell” & initial management agreement
2. Snapshot study of current “architecture” & Concerns analysis to highlight the need for EA
3. Customise ADM / Customise Zachman cell checklists
4. Training of Architects and other key stake holders
5. TOGAF Phase A
6. TOGAF phases B/C/D: Complete Version 1 of Reference Models
7. Identify ,Create and store Building Blocks ( ABB/SBB)
8. Refer to relevant Zachman cells for completeness at the end of each phase
9. TOGAF ADM Phases E/F: Provide touch points to existing processes
10. Complete processes for phases G/H
Steps towards Enterprise Architecture
PRACTICAL EA DEVELOPMENT PROCESS
ZACHMAN FRAMEWORK
ENTERPRISE SPECIFIC ARCHITECTURE
TOGAFRESOURCES-FoundationArchitecture-TRM /SIB-Checklists-Templates
-Case studiesEtc.,
E
DH
SAMPLE EA MODEL
Accountreceivable
System process
Manual process
Business
Data
Application
Technology
Customerinterface
A/c receivable
Customer
contact
Service
request
Service
requestService
deliveryService
fulfillment
Service
pricing
Service
billing
Service Standard
Service
Pricing
Billing
collection
FinanceCustomerhistory
ServiceCustomer
Finance
UIS DMS DIS DTS
ARCHITECTURE BUILDING BLOCKS & SOLUTION BUILDING BLOCKS
ABB1
ABB2
ABB3
SBB1
SBB2
SBB3
VIEW 1
SAMPLE ARCHITECTURE BUILDING BLOCK FORMAT(Technology Architecture domain)
Header
Body
Tail
•Name
•Architecture Domain
•Owner
•SME
Principles /Rules/ Guidelines
•Strategy
•Implementation plan
•Interim
•Retiring (Legacy)
•Current
•V/L
•Date of creation / change
•Change history
•Links to SBB (s) and any other detailed information / modelsLinks
SAMPLE SOLUTION BUILDING BLOCK FORMAT(Technology Architecture domain)
Header
Body
Tail
•Name
•Solution Domain
•Owner
•SME
•Rules/ Guidelines/standards
•Rationale for inclusion
•Implementation plan
•V/L
•Date of creation / change
•Change history
•Links to any other detailed information / technical data Links
q Training :Ø One day TOGAF appreciation course (group / customised)Ø 4/5 days TOGAF practical implementation course (group/
customised)Ø Other Special training / personalised training services
q Architecture ( general):Ø Linking into vertical architecturesØ Linking into ITIL/OMG/Zachman / other architectures and
processes Ø Linking into existing / strategic vendor architectures
q Modeling / tools:Ø Tool (s) selection / Tolls embedding Ø ABB / SBB structures & rulesØ Data modeling Ø BBIB repository systems
q Processes: Ø Process maps for creation/ governance/change
management Ø Process maps to suit outsourcing contracts / SLA’s Ø Processes & content of RFIs / RFPs for selecting tools,
methodologies or service providers
q Resourcing :Ø Short term / permanent resources for implementation
VALUE ADDED SERVICES FROM CCAND C SOLUTIONS…
WHERETO FROM ZACHMANArchitecture Practitioners’ conference
April 2004
Contact:
VISH VISWANATHAN
61 2 94109855 / 61 412293336
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
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/Sets
Proc.= 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 which the 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 Architecture
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 = Condition
Means = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. 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 Architecture
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
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Related Documents
