Zachmanフレームワーク
本記事のタイトルである"Zachmanフレームワーク"は、2021年時点でThe Zachman Framework for Enterprise Architectureの最新版であるバージョン3.0のことを指している。Zachmanフレームワークは、30年間におよぶ歴史の中で以下のように発展してきた。
最初期のフレームワーク。"A Framework for Information Systems Architecture"という名前で、1987年にJohn ZachmanがIBM Systems journalで発表したもの。
1987年の版を、1990年代に拡張してThe Zachman Framework for Enterprise Architectureと改称したもの。
その後のZachmanフレームワークで、Zachman Internationalから業界標準として提示されているもの。
In other sources the Zachman Framework is introduced as a framework, originated by and named after John Zachman, represented in numerous ways, see image. This framework is explained as, for example:
(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
The Zachman Framework methodology has for example been used by the United States Department of Veterans Affairs (VA) to develop and maintain its One-VA Enterprise Architecture in 2001. This methodology required them to define all aspects of the VA enterprise from a business process, data, technical, location, personnel, and requirements perspective. The next step in implementing the Zachman methodology has been to define all functions related to each business process and identify associated data elements. Once identified, duplication of function and inconsistency in data definition can be identified.
Another application of the Zachman Framework is as reference model for other enterprise architectures, see for example these four:
EAP mapped to the Zachman Framework, 1999
Mapping the C4ISR, 1999
DoD Products Map to the Zachman Framework Cells, 2003.
Mapping a part of the DoDAF, 2007.
Other examples:
Analysis of the Rational Unified Process as a Process,
How the Model-driven architecture (MDA) models used in software development map to the Zachman Framework.
Mapping the IEC 62264 models onto the Zachman framework for analysing products information traceability.
Mapping the TOGAF Architecture Development Method (e.g. the methodology) to the Zachman Framework.
a framework to organize and analyze data,
a framework for enterprise architecture.
a classification system, or classification scheme
a matrix, often in a 6x6 matrix format
a two-dimensional model or an analytic model.
a two-dimensional schema, used to organize the detailed representations of the enterprise.
Beside the frameworks developed by John Zachman numerous extensions and or applications have been developed, which are also sometimes called Zachman Frameworks.
The Zachman Framework summarizes a collection of perspectives involved in enterprise architecture.
The One-VA EA repository was developed using an object oriented database within the Caliber-RM Software Product. Caliber-RM is intended to be used as a software configuration management tool; not as an EA repository.
However this tool permitted defining entities and relationships and for defining properties upon both entities and relationships, which made it sufficient for building an EA repository, considering the technology that was available in early 2003. The personal motivation in selecting this tool was two-fold:
none of the commercial repository tools that were available at that time provided a true Zachman Framework representation of models and relationships; and