Editing Zachman Framework (section)

== History ==
In the 1980s, [[John Zachman]] contributed to IBM's development of [[Business systems planning|Business System Planning]] (BSP), a method for analyzing, defining, and designing organizational [[Information architecture|information architectures]]. By 1982, Zachman<ref name="Zach82">[http://www.research.ibm.com/journal/sj/211/ibmsj2101D.pdf "Business Systems Planning and Business Information Control Study: A comparisment]. In:  ''IBM Systems Journal'', vol 21, no 3, 1982. p. 31-53.</ref> recognized that such analyses extended beyond automating [[systems design]] and data management, impacting strategic business planning and management science broadly. The approach could also apply to emerging fields like [[enterprise architecture]], data-driven system design, and data classification methodologies.<ref name="Zach82" />

=== "Information Systems Architecture" framework ===
[[File:ZFArticlePages.jpg|thumb|210px|The original 1987 "Information Systems Architecture Framework".]] 
[[File:Zachman Framework Detailed.jpg|thumb|320px|Simple example of the 1992 Framework.]]
In the 1987 article "A Framework for Information Systems Architecture"<ref name="Zach87">{{cite journal |first=John A. |last=Zachman |authorlink=John Zachman |date=1987 |url=http://www.research.ibm.com/journal/50th/applications/zachman.html |title=A Framework for Information Systems Architecture |journal=IBM Systems Journal |volume=26 |issue=3 |id=IBM Publication G321-5298}}</ref> Zachman noted that the term "architecture" was used loosely by information systems professionals, and meant different things to planners, designers, programmers, communication specialists, and others.<ref name="Jac92">{{cite journal |first=Durward P. |last=Jackson |date=1992 |title=Process-Based Planning in Information Resource Management |journal=Emerging Information Technologies for Competitive Advantage and Economic Development: Proceedings of 1992 Information Resources Management Association International Conference |editor-first=Mehdi |editor-last=Khosrowpour |isbn=1-878289-17-9}}</ref> In searching for an objective, independent basis upon which to develop a framework for information systems architecture, Zachman looked at the field of classical [[architecture]], and a variety of complex engineering projects in industry. He saw a similar approach and concluded that architectures exist on many levels and involve at least three perspectives: raw material or [[data]], function or processes, and location or networks.<ref name="Jac92"/>

Zachman's Information Systems Architecture is designed to be a classification schema for organizing architecture models. It provides a synoptic view of the models needed for enterprise architecture. Information Systems Architecture does not define in detail what the models should contain, it does not enforce the modeling language used for each model, and it does not propose a method for creating these models.<ref>[[Alain Wegmann]] et al. (2008). [http://infoscience.epfl.ch/record/129325/files/Wegmann_et_al-SEAM_%26_Zachman-EDOC2008.pdf "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.</ref>

=== Extension and formalization ===
In the 1992 article "Extending and Formalizing the Framework for Information Systems Architecture" [[John F. Sowa]] and John Zachman present the framework and its recent extensions and show how it can be formalized in the notation of conceptual graphs.<ref name="SoZa92">{{cite journal |first1=John F. |last1=Sowa |authorlink1=John F. Sowa |first2=John A. |last2=Zachman |authorlink2=John Zachman |date=1992 |url=http://www.research.ibm.com/journal/sj/313/sowa.pdf |title=Extending and Formalizing the Framework for Information Systems Architecture |journal=IBM Systems Journal |volume=31 |issue=3 |pages=590–616|doi=10.1147/sj.313.0590 }}</ref> Also in 1992:

{{Blockquote|John Zachman's co-author John Sowa proposed the additions of the Scope perspective of the ‘planner’ (bounding lists common to the enterprise and its environment) and the Detailed Representation perspective of the ‘sub-contractor’ (being the out-of-context vendor solution components). The Who, When and Why columns were brought into public view, the notion of the four levels of metaframeworks and a depiction of integration associations across the perspectives were all outlined in the paper. Keri Anderson Healey assisted by creating a model of the models (the framework metamodel) which was also included in the article.|Stan Locke|''Enterprise Convergence in Our Lifetime, from The Enterprise Newsletter''<ref name="Locke08">{{cite journal |first=Stan |last=Locke |url=http://www.ies.aust.com/ten/TEN42.htm#Enterprise_Convergence |title=Enterprise Convergence in Our Lifetime |journal=The Enterprise Newsletter |issue=TEN42 |date=September 16, 2008}}</ref>
}}

Later during the 1990s,<ref name="Locke08"/> methodologists like [[Clive Finkelstein]] refocused on the top two framework rows which he labeled [[Enterprise Engineering]] and has one of the most successful methods for converging the business needs with information technology engineering implementation, and determining a logical build sequence of the pieces.
=== Framework for enterprise architecture ===
In the 1997 paper "Concepts of the Framework for Enterprise Architecture", Zachman said that the framework should be referred to as a "Framework for Enterprise Architecture", and should have been from the beginning. In the early 1980s however, according to Zachman, there was "little interest in the idea of Enterprise Reengineering or [[Enterprise Modeling]] and the use of formalisms and models was generally limited to some aspects of application development within the Information Systems community".<ref name="Zach97">{{cite book |first=John A. |last=Zachman |authorlink=John Zachman |date=1997 |url=http://www.ies.aust.com/PDF-papers/zachman3.pdf |title=Concepts of the Framework for Enterprise Architecture: Background, Description and Utility |publisher=Zachman International |accessdate=19 January 2009}}</ref>

In 2008, Zachman Enterprise introduced the ''Zachman Framework: The Official Concise Definition'' as a new Zachman Framework standard.

=== Extended and modified frameworks ===
Since the 1990s several extended frameworks have been proposed, such as:
* Matthew & McGee (1990)<ref>R. W. Matthews. &. W. C. McGee (1990). [http://www.research.ibm.com/journal/sj/292/ibmsj2902F.pdf "Data Modeling for Software Development"]. in: ''IBM Systems Journal'' 29(2). pp. 228–234</ref> extended the three initial perspectives "what", "how" and "where", to event (the "when"), reason (the "why") and organization (the "who").<ref name="Jac92"/>
* Schoch & Laplante (1995) published in the ''IBM Systems Journal'' (vol. 34, no.1, January 1995, pp.22-38) "A Framework for Real-Time Systems Architecture," an extension of the original Zachman Framework that applies to real-time systems.
* Evernden (1996) presented an alternative [[Information FrameWork]].
* The [[Integrated Architecture Framework]] developed by [[Capgemini]] since 1996.<ref>[[Jaap Schekkerman]] (2003). ''How to Survive in the Jungle of Enterprise Architecture Frameworks''. page 139-144.</ref>
* Vladan Jovanovic et al. (2006) presents a Zachman Cube, an extended of the Zachman Framework into a multidimensional Zachman's Cube.<ref>Vladan Jovanovic, Stevan Mrdalj & Adrian Gardiner (2006). [http://www.iacis.org/iis/2006_iis/PDFs/Jovanovic_Mrdalj_Gardiner.pdf A Zachman Cube]. In: ''Issues in Information Systems''. Vol VII, No. 2, 2006 p. 257-262.</ref>