june 3, 2015 a tutorial on the zachman enterprise architecture framework 1 a tutorial on the zachman...
Post on 19-Dec-2015
224 views
TRANSCRIPT
April 18, 2023 A Tutorial on the Zachman Enterprise Architecture Framework 1
A Tutorial on the
Zachman Framework for
Enterprise Architecture
April 18, 2023 A Tutorial on the Zachman Enterprise Architecture Framework 2
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL
(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
Things Important to the Business
Entity = Class of Business Thing
Processes Performed
Function = Class of Business Process
Semantic Model
Ent = Business Entity Rel = Business Relationship
Business Process Model
Proc = Business Process I/O = Business Resources
Business LogisticsSystem
Node = Business Location Link = Business Linkage
Work Flow Model
People = Organization Unit Work = Work Product
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objectiv e Means = Business Strategy
ImportantOrganizations
People = Major Organizations
Business locations
Node = Major Business Locations
Ev ents Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends/Means =Major Business Goals
Logical DataModel
Ent = Data Entity Rel = Data Relationship
Application Architecture
Proc = Application Function I/O = User Views
Distributed SystemArchitecture
Node = IS Function Link = Line Characteristics
Human InterfaceArchitecture
People = Role Work = Deliv erable
ProcessingStructure
Time = System Event Cycle = Processing Cycle
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer Function I/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Softw are Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = Ex ecute Cycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language Statement I/O = Control Block
Netw orkArchitecture
Node = Addresses Link = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub-Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Netw ork
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL
(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
Things Important to the Business
Entity = Class of Business Thing
Processes Performed
Function = Class of Business Process
Semantic Model
Ent = Business Entity Rel = Business Relationship
Business Process Model
Proc = Business Process I/O = Business Resources
Business LogisticsSystem
Node = Business Location Link = Business Linkage
Work Flow Model
People = Organization Unit Work = Work Product
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objectiv e Means = Business Strategy
ImportantOrganizations
People = Major Organizations
Business locations
Node = Major Business Locations
Ev ents Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends/Means =Major Business Goals
Logical DataModel
Ent = Data Entity Rel = Data Relationship
Application Architecture
Proc = Application Function I/O = User Views
Distributed SystemArchitecture
Node = IS Function Link = Line Characteristics
Human InterfaceArchitecture
People = Role Work = Deliv erable
ProcessingStructure
Time = System Event Cycle = Processing Cycle
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer Function I/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Softw are Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = Ex ecute Cycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language Statement I/O = Control Block
Netw orkArchitecture
Node = Addresses Link = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub-Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Netw ork
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
Zachman Framework
April 18, 2023 A Tutorial on the Zachman Enterprise Architecture Framework 3
Zachman Framework
Row 1 – ScopeExternal Requirements and DriversBusiness Function Modeling
Row 2 – Enterprise ModelBusiness Process Models
Row 3 – System ModelLogical ModelsRequirements Definition
Row 4 – Technology ModelPhysical ModelsSolution Definition and Development
Row 5 – As BuiltAs BuiltDeployment
Row 6 – Functioning EnterpriseFunctioning EnterpriseEvaluation
1
2
3
4
5
6
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
April 18, 2023 A Tutorial on the Zachman Enterprise Architecture Framework 4
Framework Rules
Rule 1: Columns have no order
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
Rule 2:
Each column has a simple, basic model
Rule 3:
Basic model of each column is unique
Rule 4:
Each row represents a distinct view Rule 5:
Each cell is unique
Rule 6:
Combining the cells in one row forms a complete description from that view
Basic Model = Entities and Relationships
EntityRelationshipEntity
April 18, 2023 A Tutorial on the Zachman Enterprise Architecture Framework 5
Zachman Framework – Row 1Scope/Planner’s View
External Requirements and Drivers
Business Function Modeling
Motivation/WhyBusiness goals, objectives and performancemeasures related to each function
Function/HowHigh-level business functions
Data/WhatHigh-level data classes related to eachfunction
People/WhoStakeholders related to each function
Network/WhereVA locations related to each function
Time/WhenCycles and events related to eachfunction
1 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
April 18, 2023 A Tutorial on the Zachman Enterprise Architecture Framework 6
Zachman Framework – Row 2Enterprise Model/Designer’s View
Business Process Models Business Function Allocation Elimination of Function
Overlap and Ambiguity
Motivation/WhyPolicies, procedures and standards for eachprocess
Function/HowBusiness processes
Data/WhatBusiness data
People/WhoVA roles and responsibilities in eachprocess
Network/WhereVA locations related to each process
Time/WhenEvents for each process and sequencingof integration and process improvements
2
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
April 18, 2023 A Tutorial on the Zachman Enterprise Architecture Framework 7
Zachman Framework – Row 3System Model/Designer’s View
Logical Models Project Management Requirements Definition
Motivation/WhyVA policies, standards and proceduresassociated with a business rule model
Function/HowLogical representation of informationsystems and their relationships
Data/WhatLogical data models of data and datarelationships underlying VA information
People/WhoLogical representation of access privilegesconstrained by roles and responsibilities
Network/WhereLogical representation of the distributedsystem architecture for VA locations
Time/WhenLogical events and their triggered responses constrained by business events and their responses
3
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
April 18, 2023 A Tutorial on the Zachman Enterprise Architecture Framework 8
Zachman Framework – Row 4Technology Model/Builder’s View
Physical Models Technology Management Solution Definition and
Development
Motivation/WhyVA business rules constrained by informationsystems standards
Function/HowSpecifications of applications that operateon particular technology platforms
Data/WhatDatabase management system (DBMS) typerequirements constrained by logical data models
People/WhoSpecification of access privileges tospecific platforms and technologies
Network/WhereSpecification of network devices and theirrelationships within physical boundaries
Time/WhenSpecification of triggers to respond to systemevents on specific platforms and technologies
4
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
April 18, 2023 A Tutorial on the Zachman Enterprise Architecture Framework 9
Zachman Framework – Row 5As Built/Integrator’s View
As Built Configuration Management Deployment
Motivation/WhyVA business rules constrained by specific technology standards
Function/HowPrograms coded to operate on specific technology platforms
Data/WhatData definitions constrained by physical data models
People/WhoAccess privileges coded to control access to specific platforms and technologies
Network/WhereNetwork devices configured to conform to node specifications
Time/WhenTiming definitions coded to sequence activities on specific platforms and technologies
5
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
April 18, 2023 A Tutorial on the Zachman Enterprise Architecture Framework 10
Zachman Framework – Row 6Functioning Enterprise/User’s View
Functioning Enterprise Operations Management Evaluation
Motivation/WhyOperating characteristics of specific technologies constrained by standards
Function/HowFunctioning computer instructions
Data/WhatData values stored in actual databases
People/WhoVA personnel and key stakeholders working within their roles and responsibilities
Network/WhereSending and receiving messages
Time/WhenTiming definitions operating to sequence activities
6
Contextual
Conceptual
Logical
Physical
Integrated
Functioning
Contextual
Conceptual
Logical
Physical
Integrated
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
April 18, 2023 A Tutorial on the Zachman Enterprise Architecture Framework 11
VA Zachman Framework Portal