A number of architecture frameworks exist, each of which has its particular advantages and disadvantages, and relevance, for enterprise architecture. Several are discussed in Other Architectures and Frameworks .
However, there is no accepted industry standard method for developing an enterprise architecture. The Open Group goal with TOGAF is to work towards making the TOGAF ADM just such an industry standard method, which can be used for developing the products associated with any recognized enterprise framework that the architect feels is appropriate for a particular architecture. The Open Group vision for TOGAF is as a vehicle and repository for practical, experience-based information on how to go about the process of enterprise architecture, providing a generic method with which specific sets of deliverables, specific reference models, and other relevant architectural assets can be integrated.
To illustrate the concept, this section provides a mapping of the various phases of the TOGAF ADM to the cells of the well-known Zachman Framework.
Das Zachman Framework ist ein 1987 von John Zachman konzipierter domänenneutraler Ordnungsrahmen zur Entwicklung von Informationssystemen.
Es bildet dabei einen Leitfaden, der Vorschläge enthält, welche Aspekte aus welchen Perspektiven Berücksichtigung finden sollten, um die IT-Architektur einer Unternehmung erfolgreich aufzustellen. Mit Hilfe dieser Modellierung kann sowohl die Dokumentation- als auch die Planung eines solchen Projekts unterstützt werden, wenn bspw. nachvollzogen werden soll, welche Entscheidungen welche technischen Umsetzungen nach sich gezogen haben.
The Zachman Framework is a framework for enterprise architecture, which provides a formal and highly structured way of viewing and defining an enterprise.
The Framework in practice is used for organizing enterprise architectural "artifacts" in a way that takes into account both:
who the artifact targets for example, business owner and builder, and
what particular issue for example, data and functionality is being addressed.
These artifacts may include design documents, specifications, and models.[3]
The Framework is in essence a matrix,[4]. It is named after its creator John Zachman, who first developed the concept in the 1980s at IBM. It has been updated several times ever since.[5]