Editing Zachman Framework (section)

=== Views of rows ===
Each row represents a total view of the solution from a particular perspective. An upper row or perspective does not necessarily have a more comprehensive understanding of the whole than a lower perspective. Each row represents a distinct, unique perspective; however, the deliverables from each perspective must provide sufficient detail to define the solution at the level of perspective and must translate to the next lower row explicitly.<ref name="CIOC99">The Chief Information Officers Council (1999). [http://www.cio.gov/documents/fedarch1.pdf Federal Enterprise Architecture Framework Version 1.1]. September 1999</ref>

Each perspective must take into account the requirements of the other perspectives and the restraint those perspectives impose. The constraints of each perspective are additive. For example, the constraints of higher rows affect the rows below. The constraints of lower rows can, but do not necessarily affect the higher rows. Understanding the requirements and constraints necessitates communication of knowledge and understanding from perspective to perspective. The Framework points the vertical direction for that communication between perspectives.<ref name="CIOC99"/>
[[File:Simplification Zachman Enterprise Framework.jpg|thumb|420px|The Veterans Affairs Zachman Framework with an explanation of its rows.<ref name="VA02Pre">US Department of Veterans Affairs (2002) [http://www.va.gov/oirm/architecture/EA/theory/tutorial.ppt A Tutorial on the Zachman Architecture Framework]. Accessed 06 Dec 2008.</ref><ref>[[Bill Inmon]] called this image "A simple example of The Zachman Framework" in the article 
[http://www.b-eye-network.in/print/1962 John Zachman - One of the Best Architects I Know] Originally published 17 November 2005.</ref>]]
The current version (3) of the Zachman Framework categorizes the rows as follows:
* ''Executive Perspective'' (Scope Contents) – The first architectural sketch is a "[[bubble chart]]" or [[Venn diagram]], which depicts in gross terms the size, shape, partial relationships, and basic purpose of the final structure. It corresponds to an executive summary for a planner or investor who wants an overview or estimate of the scope of the system, what it would cost, and how it would relate to the general environment in which it will operate.
* ''Business Management Perspective'' (Business Concepts) – Next are the architect's drawings that depict the final building from the perspective of the owner, who will have to live with it in the daily routines of business. They correspond to the enterprise (business) models, which constitute the designs of the business and show the business entities and processes and how they relate.
* ''Architect Perspective'' (System Logic) – The architect's plans are the translation of the drawings into detail requirements representations from the designer's perspective. They correspond to the system model designed by a systems analyst who must determine the data elements, logical process flows, and functions that represent business entities and processes.
* ''Engineer Perspective'' (Technology Physics) – The contractor must redraw the architect's plans to represent the builder's perspective, with sufficient detail to understand the constraints of tools, technology, and materials. The builder's plans correspond to the technology models, which must adapt the information systems model to the details of the programming languages, input/output (I/O) devices, or other required supporting technology.
* ''Technician Perspective'' (Tool Components) – Subcontractors work from shop plans that specify the details of parts or subsections. These correspond to the detailed specifications that are given to programmers who code individual modules without being concerned with the overall context or structure of the system. Alternatively, they could represent the detailed requirements for various [[Commercial off-the-shelf|commercial-off-the-shelf (COTS)]], [[Government off-the-shelf|government off-the-shelf (GOTS)]], or components of modular systems software being procured and implemented rather than built.
* ''Enterprise Perspective'' or (Operations Instances)