The Zachman |
DATA |
FUNCTION |
NETWORK |
PEOPLE |
TIME |
MOTIVATION |
Framework |
What |
HOW |
Where |
Who |
When |
Why |
(Things) |
(Process) |
(Location) |
(People) |
(Time) |
(Motivation) | |
SCOPE |
ustoftmngs impotent to the DU3ln&88 |
ust ot processes me business performe |
Ltótof Loc3tlon8ln wnich me Do8ln*38 operates |
LtetofOrganiz3tk>ns inportant to the Business |
U8t of Event8 Signiflcant to me Business |
List of Business Go3is.'Strategies |
(Ccntextual) Ptanner |
Package ano Class Diagrams Use Case |
Actwity Diagrams Diagrams | ||||
BUSINESS MODEL |
Semanttc Model |
Business Proce88 Model |
Business Logistica System |
Work fiow Model |
Master Schedule |
Business Plan |
(Ccnceptud) Owner |
Class and Composite Structure Diagrams |
Actnńty. State, and Interaction Diagrams | ||||
SYSTEM MODEL |
logical Data Model |
ippllcadon Arcnitecture |
Distributed System Archltecture |
Hum3n intetece Arcnitecture |
Processing Structure |
Business Rule Model |
(Logicd) Designer |
Class. Package: and Component Diagrams |
Actnńty. State. and Interaction Diagrams |
Depioyment Diagram | |||
TECHNOLOGY MODEL (Ptiysical) Bakier |
Pfiy8icai Data Model Class. Package: and Component Diagrams |
System Design Acdvity. State, and Interaction Diagrams |
Technology Archltecture Depioyment Diagram |
Presentatlon Arcnitecture |
Control Structure |
Rule Design |
DETAILED |
Data Deflnitton |
Program |
NetworK Archltecture |
Security Arcnitecture |
Timing Deflnitton |
Rule Specfflcation |
REPRESENTATIONS | ||||||
(Out-of-Ccntext) Sub-Controctor |
Figurę 5. One way UML Diagrams could map to the Zachman Framework.