Editing Zachman Framework (section)

== Applications and influences ==
Since the 1990s the Zachman Framework has been widely used as a means of providing structure for [[information technology engineering]]-style [[enterprise modeling]].<ref>Ian Graham (1995). ''Migrating to Object Technology: the semantic object modelling approach''. Addison-Wesley, {{ISBN|0-201-59389-0}}. p. 322.</ref> 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.<ref>Jay D. White (2007). ''Managing Information in the Public Sector''. p. 254.</ref>

=== Customization ===
Zachman Framework is applied in customized frameworks such as the [[TEAF]], built around the similar frameworks, the [[Treasury Enterprise Architecture Framework#TEAF Matrix of Views and Perspectives|TEAF matrix]].

<gallery class="center">
File:TEAF Matrix of Views and Perspectives.svg|[[TEAF]] Matrix of Views and Perspectives.
File:Framework for EA Direction, Description, and Accomplishment Overview.jpg|Framework for EA Direction, Description, and Accomplishment Overview.
File:TEAF Products.jpg|TEAF Products.
File:TEAF Work Products for EA Direction, Description, and Accomplishment.jpg|TEAF Work Products for EA Direction, Description, and Accomplishment.
</gallery>
*

=== Standards based on the Zachman Framework ===
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.<ref>{{cite web |url=http://apps.adcom.uci.edu/EnterpriseArch/Zachman/Resources/ExampleHealthCareZachman.pdf |title=Zachman ISA Framework for Healthcare Informatics Standards |date=1997}}</ref>

=== Mapping other frameworks ===
Another application of the Zachman Framework is as reference model for other enterprise architectures, see for example these four: 
<gallery class="center">
File:EAP mapped to the Zachman Framework.jpg|EAP mapped to the Zachman Framework, 1999
File:DOD C4ISR Architecture Framework Products Mapped.jpg|Mapping the [[C4ISTAR|C4ISR]], 1999
File:DoD Products Map to the Zachman Framework Cells.jpg|DoD Products Map to the Zachman Framework Cells, 2003. 
File:DoDAF Support to the Builder.jpg|Mapping a part of the [[DoDAF]], 2007. 
</gallery>

Other examples:
* Analysis of the [[Rational Unified Process]] as a Process,<ref>DJ de Villiers (2001). [http://www.ibm.com/developerworks/rational/library/content/RationalEdge/mar01/UsingtheZachmanFrameworktoAssesstheRUPMar01.pdf "Using the Zachman Framework to Assess the Rational Unified Process"], In: ''The Rational Edge'' Rational Software 2001.</ref>
* How the [[Model-driven architecture]] (MDA) models used in software development map to the Zachman Framework.<ref>[[David S. Frankel]], [[Paul Harmon (management author)|Harmon, P.]], Mukerji, J., Odell, J., Owen, M., Rivitt, P., [[Michael Rosen (enterprise architect)|Rosen, M]]... & Soley, R. M. et al. (2003) [http://www.bptrends.com/publicationfiles/09-03%20WP%20Mapping%20MDA%20to%20Zachman%20Framework.pdf ''The Zachman Framework and the OMG's Model Driven Architecture''] White paper. Business Process Trends.</ref>
* Mapping the IEC 62264 models onto the Zachman framework for analysing products information traceability.<ref>Hervé Panetto, Salah Baïna, Gérard Morel (2007). [http://hal.archives-ouvertes.fr/docs/00/11/91/96/PDF/Panetto_et_al_JIM.pdf Mapping the models onto the Zachman framework for analysing products information traceability : A case Study].</ref>
* Mapping the [[The Open Group Architecture Framework|TOGAF]] Architecture Development Method (e.g. the methodology) to the Zachman Framework.<ref name="TOG06"/>

=== Base for other enterprise architecture frameworks ===
Less obvious are the ways the original Zachman framework has stimulated the development of other [[enterprise architecture framework]]s, such as in the [[NIST Enterprise Architecture Model]], the [[C4ISTAR|C4ISR]] AE, the DOE AE, and the [[DoDAF]]:

<gallery class="center">
File:NIST Enterprise Architecture Model.jpg|NIST Enterprise Architecture Model.<ref name="CIOC99"/>
File:LISI Reference Model 1997.jpg|[[C4ISTAR|C4ISR]] AE, 1997.
File:DOE Information Architecture Conceptual Model.jpg|DOE AE, 1998.
File:DoDAF Perspectives and Decomposition Levels.jpg|[[Department of Defense Architecture Framework|DODAF]], 2003.
</gallery>

* 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.<ref>Roland Traunmüller (2004). ''[https://books.google.co.kr/books?id=QjB5c_v-uMwC&pg=PA51&redir_esc=y Electronic Government]'' p. 51</ref>

==== Example: One-VA Enterprise Architecture ====
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 defining all aspects of the VA enterprise from a business process, data, technical, location, personnel, and requirements perspective. The next step in implementing the 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 and resolved.<ref>[http://www.va.gov/oca/testimony/hvac/soi/13mr02it.asp 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.</ref>

<gallery class="center">
File:Integrated Process Flow for VA IT Projects.jpg|Integrated Process Flow for VA IT Projects (2001)
File:VA Zachman Framework Portal.jpg|VA Zachman Framework Portal
File:VA EA Repository Introduction.jpg|VA EA Repository Introduction (2008)
File:A Tutorial on the Zachman Architecture Framework.jpg|A Tutorial on the Zachman Architecture Framework
</gallery>

The Department of Veterans Affairs at the beginning of the 21st century{{when|date=February 2012}} 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.
  
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.<ref>{{cite web |url=http://www.va.gov/oit/ea/4_3/process/modeling/metamodel.html |title=Meta-Model Cell Details |access-date=25 December 2009}}</ref>

[[File:VA EA Meta-Model Cell Details Enlarged.jpg|thumb|600px|center|VA EA Meta-Model Cell Details Enlarged.]]

This diagram{{efn|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 [[Microsoft Visio|Visio]] diagram in numerous stages of its development between 2000 and present. Al Zuech was the Director, Enterprise Architecture Service at the [[United States Department of Veterans Affairs|Department of Veterans Affairs]] from 2001 until 2007.}} has been incorporated within the VA-EA to provide a symbolic representation of the [[Metamodeling|metamodel]] it used, to describe the One-VA Enterprise Architecture and to build an EA Repository without the use of Commercial EA Repository Software. It 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 available in early 2003. The personal motivation in selecting this tool was that none of the commercial repository tools then available provided a true Zachman Framework representation, and were highly proprietary, making it difficult to incorporate components from other vendors or from open source.

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). Representations in 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 Framework only identifies sunk-cost, but the row-six ROI permits it to measure benefits and to be used in a continuous improvement process, capturing best practices and applying them back through row-two.