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.[30] 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. [31]

カスタマイゼーション

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

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.[32]

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

Another application of the Zachman Framework is as reference model for other enterprise architectures, see for example these four:

Other examples:

  • Analysis of the Rational Unified Process as a Process,[33]
  • How the Model-driven architecture (MDA) models used in software development map to the Zachman Framework.[34]
  • Mapping the IEC 62264 models onto the Zachman framework for analysing products information traceability.[35]
  • Mapping the TOGAF Architecture Development Method (e.g. the methodology) to the Zachman Framework.[5]

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

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:

  • 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.[36] (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.[37]

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.[38]

VA EA Meta-Model Cell Details Enlarged.

This diagram[39] 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.


  1. ^ a b The Concise Definition of The Zachman Framework by: John A. Zachman”. Zachman International, Inc. (2008年). 2021年10月31日閲覧。
  2. ^ Roger Sessions (2007年5月). “A Comparison of the Top Four Enterprise Architecture Methodologies”. Microsoft Developer Network Architecture Center. 2021年10月31日閲覧。
  3. ^ The Zachman Framework Evolution”. Zachman International (2009年4月). 2021年10月31日閲覧。
  4. ^ A framework for information systems architecture”. IBM Systems Journal, Vol. 26. No. 3 (1987年). 2019年1月11日閲覧。
  5. ^ a b The Open Group (1999–2006). "ADM and the Zachman Framework" in: TOGAF 8.1.1 Online. Accessed 25 Jan 2009.
  6. ^ William H. Inmon, John A. Zachman, Jonathan G. Geiger (1997). Data Stores, Data Warehousing, and the Zachman Framework: Managing Enterprise Knowledge. McGraw-Hill, 1997. ISBN 0070314292.
  7. ^ Pete Sawyer, Barbara Paech, Patrick Heymans (2007). Requirements Engineering: Foundation for Software Quality. page 191.
  8. ^ Kathleen B. Hass (2007). The Business Analyst as Strategist: Translating Business Strategies Into Valuable Solutions. page 58.
  9. ^ Harold F. Tipton, Micki Krause (2008). Information Security Management Handbook, Sixth Edition, Volume 2. page 263.
  10. ^ O'Rourke, Fishman, Selkow (2003). Enterprise Architecture Using the Zachman Framework. page 9.
  11. ^ a b James McGovern et al. (2003). A Practical Guide to Enterprise Architecture. p. 127-129.
  12. ^ Marc Lankhorst (2005). Enterprise Architecture at Work. p. 24.
  13. ^ a b "Business Systems Planning and Business Information Control Study: A comparisment. In: IBM Systems Journal, vol 21, no 3, 1982. p. 31-53.
  14. ^ John A. Zachman (1987). " A Framework for Information Systems Architecture". In: IBM Systems Journal, vol 26, no 3. IBM Publication G321-5298.
  15. ^ a b c Durward P. Jackson (1992). "Process-Based Planning in Information Resource Management". In: Emerging Information Technologies for Competitive Advantage and Economic Development. Proceedings of 1992 Information Resources Management Association International Conference. Mehdi Khosrowpour (ed). ISBN 1878289179.
  16. ^ Alain Wegmann et al. (2008). "Augmenting the Zachman Enterprise Architecture Framework with a Systemic Conceptualization". Presented at the 12th IEEE International EDOC Conference (EDOC 2008), München, Germany, September 15–19, 2008.
  17. ^ John F. Sowa and John Zachman (1992). "Extending and Formalizing the Framework for Information Systems Architecture" In: IBM Systems Journal, Vol 31, no.3, 1992. p. 590-616.
  18. ^ a b Stan Locke (2008). "Enterprise Convergence in Our Lifetime" In: THE ENTERPRISE NEWSLETTER, TEN42 September 16, 2008
  19. ^ John A. Zachman (1997). "Concepts of the Framework for Enterprise Architecture: Background, Description and Utility". Zachman International. Accessed 19 Jan 2009.
  20. ^ R.W. Matthews. &. W.C. McGee (1990). "Data Modeling for Software Development". in: IBM Systems Journal" 29(2). pp. 228–234
  21. ^ Jaap Schekkerman (2003). How to Survive in the Jungle of Enterprise Architecture Frameworks. page 139-144.
  22. ^ Vladan Jovanovic, Stevan Mrdalj & Adrian Gardiner (2006). A Zachman Cube. In: Issues in Information Systems. Vol VII, No. 2, 2006 p. 257-262.
  23. ^ a b c VA Enterprise Architecture Innovation Team (2001). Enterprise Architecture: Strategy, Governance, & Implementation report Department of Veterans Affairs, August, 2001.
  24. ^ The government information factory and the Zachman Framework by W. H. Inmon, 2003. p. 4. Accessed July 14, 2009.
  25. ^ a b c d e f g The Chief Information Officers Council (1999). Federal Enterprise Architecture Framework Version 1.1. September 1999
  26. ^ US Department of Veterans Affairs (2002) A Tutorial on the Zachman Architecture Framework. Accessed 06 Dec 2008.
  27. ^ Bill Inmon called this image "A simple example of The Zachman Framework" in the article John Zachman - One of the Best Architects I Know Originally published 17 November 2005.
  28. ^ The Zachman Framework Evolution”. Zachman International (April, 2009). 2009年10月15日閲覧。
  29. ^ Adapted from: Sowa, J.F. & J.A. Zachman, 1992, and Inmon, W.H, J.A. Zachman, & J.G. Geiger, 1997. University of Omaha
  30. ^ Ian Graham (1995). Migrating to Object Technology: the semantic object modelling approach. Addison-Wesley, ISBN 0201593890. p. 322.
  31. ^ Jay D. White (2007). Managing Information in the Public Sector. p. 254.
  32. ^ ZACHMAN ISA FRAMEWORK FOR HEALTHCARE INFORMATICS STANDARDS, 1997.
  33. ^ DJ de Villiers (2001). "Using the Zachman Framework to Assess the Rational Unified Process", In: The Rational Edge Rational Software 2001.
  34. ^ David S. Frankel et al. (2003) The Zachman Framework and the OMG's Model Driven Architecture White paper. Business Process Trends.
  35. ^ Hervé Panetto, Salah Baïna, Gérard Morel (2007). Mapping the models onto the Zachman framework for analysing products information traceability : A case Study.
  36. ^ Roland Traunmüller (2004). Electronic Government p. 51
  37. ^ Statement of Dr. John A. Gauss, Assistant Secretary for Information and Technology, Department of Veterans Affairs, before the Subcommittee on Oversight and Investigations Committee on Veterans' Affairs U.S. House of Representatives. March 13, 2002.
  38. ^ Meta-Model Cell Details Accessed 25 Dec 2009
  39. ^ This diagram is the exclusive work of Albin Martin Zuech of Annapolis Maryland, who placed it in the public domain in 2001. Al Zuech maintains the original visio diagram in numerous stages of its development between 2000 and present. Al Zuech was the Director, Enterprise Architecture Service at the Department of Veterans Affairs from 2001 until 2007.





英和和英テキスト翻訳>> Weblio翻訳
英語⇒日本語日本語⇒英語
  

辞書ショートカット

すべての辞書の索引

「Zachmanフレームワーク」の関連用語

Zachmanフレームワークのお隣キーワード
検索ランキング

   

英語⇒日本語
日本語⇒英語
   



Zachmanフレームワークのページの著作権
Weblio 辞書 情報提供元は 参加元一覧 にて確認できます。

   
ウィキペディアウィキペディア
All text is available under the terms of the GNU Free Documentation License.
この記事は、ウィキペディアのZachmanフレームワーク (改訂履歴)の記事を複製、再配布したものにあたり、GNU Free Documentation Licenseというライセンスの下で提供されています。 Weblio辞書に掲載されているウィキペディアの記事も、全てGNU Free Documentation Licenseの元に提供されております。

©2024 GRAS Group, Inc.RSS