You are here: | ||
<<< Previous | Home | |
This chapter provides a mapping of the TOGAF Architecture Development Method (ADM) to the Zachman Framework.
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.
The Zachman Framework for Enterprise Architecture, sometimes simply referred to as the "Zachman Framework", has become a de facto standard for classifying the artifacts developed in enterprise architecture. It is a logical structure for classifying and organizing the design artifacts of an enterprise that are significant to its management. It draws on a classification scheme found in the more mature disciplines of architecture/construction and engineering/manufacturing, used for classifying and organizing the design artefacts relating to complex physical products such as a building or an aircraft. Zachman adopts this classification scheme to the design and construction of information systems.
The Zachman Framework comprises a 6x6 matrix.
The columns represent various aspects of the enterprise that can be described or modeled; and the rows represent various viewpoints from which the aspects can be described. Thus each cell formed by the intersection of a column and a row represents an aspect of the enterprise modeled from a particular viewpoint. The architect selects and models the cells that are appropriate to the immediate purpose, with the ultimate objective of modeling all the cells.
The six viewpoints are:
The six aspects - and the interrogatives to which they correspond - are:
Although the Zachman Framework applies to enterprises, the Framework itself is generic. It is a comprehensive, logical structure for the descriptive representations (i.e., models or design artefacts) of any complex object, and it does not prescribe or describe any particular method, representation technique, or automated tool.
The strength of the Framework is that it provides a way of thinking about an enterprise in an organized way, so that it can be described and analyzed. It also enables the individuals involved in producing enterprise information systems to focus on selected aspects of the system without losing sight of the overall enterprise context. In designing and building complex systems, such as enterprise systems, there are simply too many details and relationships to consider simultaneously. At the same time, isolating single variables and making design decisions out of context results in sub-optimization, with all the attendant costs and risks. The challenge is the same whether the system is physical (like an aircraft) or conceptual (like an enterprise system). How do you design and build it, piece by piece, and step by step, such that it achieves its purpose without losing its value and raising its cost by optimizing the pieces and sub-optimizing the overall?
The scope of the four architecture domains of TOGAF align very well with the first four rows of the Zachman Framework, as shown in the following mapping of these domains.
Several domains overlap in the above diagram: the earliest domain to address a cell has precedence in the coloring scheme.
The mappings of the individual phases of the ADM are shown in detail below.
The outputs of this phase are:
ZF: Business/Function (model of the architecture development process)
[R2,C2]
ZF: Scope/Data, Scope/Function, Scope/Network, Scope/People, Scope/Time, Scope/Motivation
[R1,C1; R1,C2; R1,C3; R1,C4; R1,C5; R1,C6]
ZF: Composite of: Scope/Motivation, Business/Motivation
[R1,C6; R2,C6]
The outputs of this phase are:
ZF: Scope/Data, Scope/Function, Scope/Network, Scope/People, Scope/Time
[R1,C1; R1,C2; R1,C3; R1,C4; R1,C5; R1,C6]
ZF: Scope/Data, Scope/Motivation
[R1,C1; R1,C6]
ZF: Scope/Data, Scope/Function, Scope/Network, Scope/People, Scope/Time, Scope/Motivation
[R1,C1; R1,C2; R1,C3; R1,C4; R1,C5; R1,C6]
ZF: Business/Data, Business/Function, Business/Network, Business/People, Business/Time, Business/Motivation
[R2,C2; R2,C2; R2,C3; R2,C4; R2,C5; R2,C6]
ZF: System/Data, System/Function, System/Network, System/People, System/Time, System/Motivation
[R3,C2; R3,C2; R3,C3; R3,C4; R3,C5; R3,C6]
ZF: Business/Data, Business/Function, Business/Network, Business/People, Business/Time, Business/Motivation
[R2,C2; R2,C2; R2,C3; R2,C4; R2,C5; R2,C6]
ZF: System/Data, System/Function, System/Network, System/People, System/Time, System/Motivation
[R3,C2; R3,C2; R3,C3; R3,C4; R3,C5; R3,C6]
The outputs of this phase are:
ZF: Scope/Data, Scope/Function, Scope/Network, Scope/People, Scope/Time
[R1,C1; R1,C2; R1,C3; R1,C4; R1,C5; R1,C6]
ZF: Scope/Network, Scope/People, Business/Network, Business/People
[R1,C3; R1,C4; R2,C3; R2,C4]
ZF: Scope/Network, Scope/Time, Business/Network, Business/Time, Business/Motivation
[R1,C3; R1,C5; R2,C3; R2,C5; R2,C6]
ZF: Scope/Function, Business/Function
[R1,C2; R2,C2]
ZF: Business/Function, System/Function
[R2,C2; R3,C2]
ZF: Business/Function, Business/Time
[R2,C2; R2,C5]
ZF: Scope/People, Business/People
[R1,C4; R2,C4]
ZF: Scope/Function, Scope/Network, Scope/People, Business/Function, Business/Network, Business/People
[R1,C2; R1,C3; R1,C4; R2,C2; R2,C3; R2,C4]
ZF: System/Motivation
[R3,C6]
The outputs of this part of Phase C are:
ZF: Scope/Data, Scope/Network, Scope/People, Scope/Time
[R1,C3; R1,C4; R1,C5]
ZF: Business/Data
[R2,C1]
ZF: System/Data
[R3,C1]
ZF: System/Function, System/People
[R3,C2; R3,C3]
ZF: Composite of Business/People, System/Data, System/Function
[R2,C4; R3,C1; R3,C2]
ZF: Composite of System/Data, System/Function, System/Network, System/People
[R3,C1; R3,C2; R3,C3; R3,C4]
ZF: Composite of System/Data, System/Function, System/Network, System/People
[R3,C1; R3,C2; R3,C3; R3,C4]
ZF: Composite of System/Data, System/Function, System/Time
ZF: Composite of System/Function, System/Data, System/Network, System/People, System/Time
ZF: Composite of Business/Data, System/Data, Business/Time, System/Time
ZF: System/Motivation
The outputs of this part of Phase C are:
ZF: Scope/Function, Scope/Network, Scope/People, Scope/Time
ZF: System/Function
ZF: System/Network
ZF: System/People
ZF: System/Time
ZF: Composite of System/Data, System/Function, System/Network, System/People, System/Time, System/Motivation
ZF: Composite of System/Data, System/Function, System/Network, System/People, System/Time
ZF: Composite of System/Data, System/Function, System/Network, System/Time
ZF: Composite of System/Data, System/Function, System/Network, System/Time
ZF: Composite of System/Network, System/People
ZF: Composite of Business/Data, Business/Function, Business/Network, Business/People, Business/Time
ZF: Composite of Business/Data, Business/People, Business/Time
ZF: System/Motivation
The outputs of Phase D are given below, first by relevant individual step, and then as a composite for the whole phase.
The outputs of this step are:
ZF: Scope/Data, Scope/Function, Scope/Network, Scope/People, Scope/Time, Scope/Motivation
ZF: Technology/Function, Technology/Network
The outputs of this step are:
ZF: System/Network, Technology/Network
ZF: Composite of: System/Network, System/People, Technology/Network, Technology/People
ZF: System/Data, System/Function, System/Network, System/People, System/Time, Technology/Data, Technology/Function, Technology/Network, Technology/People, Technology/Time
ZF: Technology/Motivation
ZF: Technology/Motivation
ZF: System/Motivation
The outputs of this step are:
ZF: Technology/Network, System/Network
ZF: Composite of: Technology/Network, Technology/People, System/Network, System/People
ZF: Technology/Network, Technology/Time, Technology/People, Technology/Data, Technology/Function, System/Network, System/Time, System/People, System/Data, System/Function
ZF: Technology/Motivation
ZF: Technology/Motivation
The outputs of this step are:
ZF: Technology/Network, Technology/Time, Technology/People, Technology/Data, Technology/Function, Technology/Motivation
The outputs of this step are:
ZF: Composite of Technology/Data, Technology/ Function, Technology/Network, Technology/People, Technology/Time, Technology/Motivation
For more detailed information on the Zachman Framework, refer to any of John Zachman's publications, or the Zachman Institute
for Framework Advancement (ZIFA) (www.zifa.com).
return to top of page
The TOGAF document set is designed for use with frames. To navigate around the document:
Downloads of the TOGAF documentation, are available under license from the TOGAF information web site . The license is free to any organization wishing to use TOGAF entirely for internal purposes (for example, to develop an information system architecture for use within that organization). A hardcopy book is also available from The Open Group Bookstore as document G063 .