Zachmanフレームワーク
the available commercial tools were highly proprietary and made it difficult to incorporate best-of-breed tools and representations from other vendors or form open sources.
This diagram emphasizes several important interpretations of the Zachman Framework and its adaptation to information technology investment management.
Progressing through the rows from top to bottom, one can trace-out the Systems Development Life Cycle (SDLC) which is a de facto standard across the Information Industry;
The diagram emphasizes the importance of the often-neglected Zachman Row-Six (the Integrated, Operational Enterprise View).
(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
Rule 7 The logic is recursive : The logic is relational between two instances of the same entity.
The framework is generic in that it can be used to classify the descriptive representations of any physical object as well as conceptual objects such as enterprises. It is also recursive in that it can be used to analyze the architectural composition of itself. Although the framework will carry the relation from one column to the other, it is still a fundamentally structural representation of the enterprise and not a flow representation.
How :機能記述
Where :ネットワーク記述
Who :人間記述
When :時間記述
Why :動機記述
In Zachman’s opinion, the single factor that makes his framework unique is that each element on either axis of the matrix is explicitly distinguishable from all the other elements on that axis. The representations in each cell of the matrix are not merely successive levels of increasing detail, but actually are different representations — different in context, meaning, motivation, and use. Because each of the elements on either axis is explicitly different from the others, it is possible to define precisely what belongs in each cell.
In the 1980s John Zachman had been involved at IBM in the development of Business System Planning (BSP), a method for analyzing, defining and designing an information architecture of organizations. In 1982 Zachman had already concluded that these analyses could reach far beyond automating systems design and managing data into the realms of strategic business planning and management science in general. It may be employed in the (in that time considered more esoteric) areas of enterprise architecture, data-driven systems design, data classification criteria, and more.