Zachmanフレームワーク
(Why) Goal List – primary high level organization goals
(How) Process List – list of all known processes
(What) Material List – list of all known organizational entities
(Who) Organizational Unit & Role List – list of all organization units, sub-units, and identified roles
(Where) Geographical Locations List – locations important to organization; can be large and small
(When) Event List – list of triggers and cycles important to organization
(Why) Goal Relationship Model – identifies hierarchy of goals that support primary goals
(How) Process Model – provides process descriptions, input processes, output processes
(What) Entity Relationship Model – identifies and describes the organizational materials and their relationships
(Who) Organizational Unit & Role Relationship Model – identifies enterprise roles and units and the relationships between them
(Where) Locations Model – identifies enterprise locations and the relationships between them
(When) Event Model – identifies and describes events and cycles related by time
He saw a similar approach and concluded that architectures exist on many levels and involves at least three perspectives: raw material or data, function of processes, and location or networks.
The Information Systems Architecture is designed to be a classification schema for organizing architecture models. It provides a synoptic view of the models needed for enterprise architecture. Information Systems Architecture does not define in detail what the models should contain, it does not enforce the modeling language used for each model, and it does not propose a method for creating these models.
For example, the constraints of higher rows affect the rows below. The constraints of lower rows can, but do not necessarily affect the higher rows. Understanding the requirements and constraints necessitates communication of knowledge and understanding from perspective to perspective. The Framework points the vertical direction for that communication between perspectives.
In the 1997 Zachman Framework the rows are described as follows:
Planner's View (Scope) - The first architectural sketch is a "bubble chart" or Venn diagram, which depicts in gross terms the size, shape, partial relationships, and basic purpose of the final structure.
These perspectives are represented in a two-dimensional matrix that defines along the rows the type of stakeholders and with the columns the aspects of the architecture. The framework does not define a methodology for an architecture. Rather, the matrix is a template that must be filled in by the goals/rules, processes, material, roles, locations, and events specifically required by the organization. Further modeling by mapping between columns in the framework identifies gaps in the documented state of the organization.
The framework is a simple and logical structure for classifying and organizing the descriptive representations of an enterprise.