Zachmanフレームワーク アプリケーションと影響

ウィキペディア

Zachmanフレームワーク

出典: フリー百科事典『ウィキペディア（Wikipedia）』 (2023/08/25 13:40 UTC 版)

アプリケーションと影響

Since the 1990s the Zachman Framework has been widely used as a means of providing structure for Information Engineering-style enterprise modeling. The Zachman Framework can be applied both in commercial companies and in government agencies. Within a government organization the framework can be applied to an entire agency at an abstract level, or it can be applied to various departments, offices, programs, subunits and even to basic operational entities.

カスタマイゼーション

Zachman Framework is applied in customized frameworks such as the TEAF, built around the similar frameworks, the TEAF matrix.

• 

  TEAF Matrix of Views and Perspectives.

• 

  Framework for EA Direction, Description, and Accomplishment Overview.

• 

  TEAF Products.

• 

  TEAF Work Products for EA Direction, Description, and Accomplishment.

Other sources:

• The TEAF matrix is called a customization sample, see here, p. 22

Zachmanフレームワークに基づく標準

Zachman Framework is also used as a framework to describe standards, for example standards for healthcare and healthcare information system. Each cell of the framework contains such a series of standards for healthcare and healthcare information system.

他のフレームワークのマッピング

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.

他のエンタープライズアーキテクチャフレームワークのための基礎

Less obvious are the ways the original Zachman framework has stimulated the development of other enterprise architecture frameworks, such as in the NIST Enterprise Architecture Model, the C4ISR AE, the DOE AE, and the DoDAF:

• 

  NIST Enterprise Architecture Model.

• 

  C4ISR AE, 1997.

• 

  DOE AE, 1998.

• 

  DODAF, 2003.

• The Federal Enterprise Architecture Framework (FEAF) is based on the Zachman Framework but only addresses the first three columns of Zachman, using slightly different names, and focuses in the top of the three rows. (see here)

例: One-VA エンタープライズアーキテクチャ

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. The hard job then followed to de-conflict the data definitions and resolve duplicative implementations of the same business function.

• 

  Integrated Process Flow for VA IT Projects (2001)

• 

  VA Zachman Framework Portal

• 

  VA EA Repository Introduction (2008)

• 

  A Tutorial on the Zachman Architecture Framework

The Department of Veterans Affairs at the beginning of the 21st century planned to implement an enterprise architecture fully based on the Zachman Framework.

• The Zachman Framework was used as a reference model to initiate enterprise architecture planning in 2001.
• Somewhere in between the VA Zachman Framework Portal was constructed.
• This VA Zachman Framework Portal is still in use as a reference model for example in the determination of EA information collected from various business and project source documents.
• Now somewhere in the past this "A Tutorial on the Zachman Architecture Framework".

Eventually an enterprise architecture repository was created at the macro level by the Zachman framework and at a cell level by the meta-model outlined below.

VA EA Meta-Model Cell Details Enlarged.

This diagram has been incorporated within the VA-EA to provide a symbolic representation of the metamodel that VA used, to describe the One-VA Enterprise Architecture and to build an EA Repository without the use of Commercial EA Repository Software. 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:

1. none of the commercial repository tools that were available at that time provided a true Zachman Framework representation of models and relationships; and
2. 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.

1. 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;
2. The diagram emphasizes the importance of the often-neglected Zachman Row-Six (the Integrated, Operational Enterprise View). Representations in Mr. Zuech’s interpretation of Zachman row-six consist, largely, of measurable service improvements and cost savings/avoidance that result from the business process and technology innovations that were developed across rows two through five.

Row-six provides measured Return on Investment for Individual Projects and, potentially, for the entire investment portfolio. Without row-six the Zachman Framework only identifies sunk-cost – the row-six ROI permits the framework to measure benefits and to be used in a continuous improvement process, capturing best practices and applying them back through row-two.