Information Technology Reference
In-Depth Information
Zachman Enterprise Architecture Framework
John A. Zachman (siehe [Zac87] und [Zac08]) legte bereits Mitte der 1980er-Jahre den Grund-
stein für sein nach ihm benanntes Framework. In seinen Arbeiten beschrieb Zachman die
Relevanz der ganzheitlichen Betrachtung von Architekturen auf Unternehmensebene. Das
Zachman Enterprise Architecture Framework gilt als eines der bekanntesten Frameworks
und beeinlusste das heutige Verständnis der Unternehmensarchitekturen sowie viele später
entwickelte EA-Frameworks.
John A. Zachman veröfentlichte 1987 die erste Version seines Vorschlags für sein EA-Framework
(siehe [Zac87]). Zusammen mit John F. Sowa (siehe [Sow92]) erweiterte er es 1992, was zu
der heute bekannten Ausprägung des Zachman Enterprise Architecture Frameworks führte
(siehe Abbildung 3.2).
Entwurfsziel des Frameworks war die Bereitstellung von Beschreibungskonzepten, die geeignet
sind, die vielfältigen Schnittstellen von Komponenten eines Informationssystems sowie deren
Integration in die Organisation darzustellen.
Data
What
Function
How
Network
Where
People
Who
Time
When
Motivation
Why
Scope
(Contextual)
Things Important
to the Business
Process Performed
Business Locations
Important Organizations
Events Significant
to the Business
Business Goals
and Strategy
Planner
Entity = Class of
Business Thing
Function = Class of
Business Process
Node = Major
Business Locations
People = Major
Organisations
Time = Major
Business Event
Ends/Means =
Major Business Goals
Enterprise
Model
(Conceptual)
Conceptual Data Model
Business Process Model
Business Logistics Systems
Work Flow Model
Master Schedule
Business Plan
Owner
Ent = Business Entity
Rel = Business Relationship
Proc = Business Process
I/O = Business Ressources
Node = Business Location
Link = Business Linkage
People = Organization Unit
Work = Work Product
Time = Business Event
Cycle = Business Cycle
End = Business Objective
Mears = Action Assertion
System Model
(Logical)
Logical Data Model
Application Architecture
Distributed System
Architecture
Human Interface Architecture
Processing Structure
Business Rule Model
IS 4
IS 1
IS 2
Designer
IS 3
IS 5
Ent = Data Entity
Rel = Data Relationship
Proc = Application Function
I/O = User Views
Node = System Location
Link = Line Characteristics
People = Role
Work = Deliverable
Time = System Event
Cycle = System Cycle
End = Structural Assertion
Mears = Action Assertion
Technology
Model
(Physical)
Physical Data Model
System Design
Technolgy Archtiecture
Presentation Architecture
Control Structure
Rule Design
Builder
Ent = Segment/Table
Rel = Pointer/Key
Proc = Computer Function
I/O = Data Elements/Sets
Node = Hardware/Software
Link = Line Specifications
People = User
Work = Screen Format
Time = Execute
Cycle = Component Cycle
End = Condition
Mears = Action
Detailed
Representations
(Out-Of-Context)
Data Definition
Program
Network Architecture
Security Architecture
Timing Definition
Rule Specification
Sub-Contractor
Programmer
Ent = Field
Rel = Address
Proc = Language Statement
I/O = Control Block
Node = Adresses
Link = Protocols
People = Identity
Work = Job
Time = Interrupt
Cycle = Machine Cycle
End = Sub-Condition
Mears = Step
Usable Data
Working Function
Usable Network
Functioning Organization
Implemented Schedule
Working Strategy
Functioning
Enterprise
User
ABBILDUnG 3.2
Das Zachman Enterprise Architecture Framework (vgl. [Sow92])
Search WWH ::
Custom Search