Zachmanフレームワーク
Zachmanフレームワークのトピックス > セルのモデル

The kinds of models or architectural descriptive representations are made explicit at the intersections of the rows and columns. An intersection is referred to as a cell. Because a cell is created by the intersection of a perspective and a focus, each is distinctive and unique. Since each cell is distinctive and unique, the contents of the cell are normalized and explicit per the perspective’s focus.
The cell descriptions in the table itself uses general language for a specific set of targets. Below the focus of each cell in this particular Zachman Framework is explained:
(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
(Why) Rules Diagram – identifies and describes rules that apply constraints to processes and entities without regard to physical or technical implementation
(How) Process Diagram – identifies and describes process transitions expressed as verb-noun phrases without regard to physical or technical implementation
(What) Data Model Diagram – identifies and describes entities and their relationships without regard to physical or technical implementation
(Who) Role Relationship Diagram – identifies and describes roles and their relations to other roles by types of deliverables without regard to physical or technical implementation
(Where) Locations Diagram – identifies and describes locations used to access, manipulate, and transfer entities and processes without regard to physical or technical implementation
(When) Event Diagram – identifies and describes events related to each other in sequence, cycles occur within and between events, without regard to physical or technical implementation
(Why) Rules Specification – expressed in a formal language; consists of rule name and structured logic to specify and test rule state
(How) Process Function Specification – expressed in a technology specific language, hierarchical process elements are related by process calls
(What) Data Entity Specification – expressed in a technology specific format; each entity is defined by name, description, and attributes; shows relationships
(Who) Role Specification – expresses roles performing work and workflow components at the work product detailed specification level
(Where) Location Specification – expresses the physical infrastructure components and their connections
(When) Event Specification – expresses transformations of event states of interest to the enterprise
Eventually the cells with the detailed representation give Rules detail for (Why); Process detail for (How); Data detail for (What); Role detail for (Who); Location detail for (Where); and Event detail for (When).
There is a sixth row in the current Zachman framework, but it is not used for enterprise architecture — while the enterprise is described by rows one to six, enterprise architecture uses only rows one to five, thus only five rows are shown here.
Since the product development (i.e., architectural artifact) in each cell or the problem solution embodied by the cell is the answer to a question from a perspective, typically, the models or descriptions are higher-level depictions or the surface answers of the cell. The refined models or designs supporting that answer are the detailed descriptions within the cell. Decomposition (i.e., drill down to greater levels of detail) takes place within each cell. If a cell is not made explicit (defined), it is implicit (undefined). If it is implicit, the risk of making assumptions about these cells exists. If the assumptions are valid, then time and money are saved. If, however, the assumptions are invalid, it is likely to increase costs and exceed the schedule for implementation.