This chapter describes the Architecture Development Method (ADM) cycle, adapting the ADM, architecture scope, and architecture integration.
The TOGAF ADM is the result of continuous contributions from a large number of architecture practitioners. It describes a method for developing an enterprise architecture, and forms the core of TOGAF. It integrates elements of TOGAF described in this document as well as other available architectural assets, to meet the business and IT needs of an organization.
Relationship to Other Parts of TOGAF
There are two other main parts to TOGAF, besides the ADM:
- The Enterprise Continuum, described in detail in Part III: Enterprise Continuum. This is a "framework-within-a-framework" that provides context for the leveraging of relevant architecture assets and provides navigational help when discussions move between different levels of abstraction.
The ADM and the Enterprise Continuum
As mentioned above, the Enterprise Continuum provides a framework and context for the leveraging of relevant architecture assets in executing the ADM. These assets may include architecture descriptions, models, and patterns taken from a variety of sources, as explained in Part III: Enterprise Continuum. At relevant places throughout the ADM, there are reminders to consider which architecture assets from the Enterprise Continuum the architect should use, if any. In some cases - for example, in the development of a Technology Architecture - this may be the TOGAF Foundation Architecture (see Part III: Enterprise Continuum). In other cases - for example, in the development of a Business Architecture - it may be a reference model for e-Commerce taken from the industry at large.
The practical implementation of the Enterprise Continuum will often take the form of a repository that includes reference architectures, models, and patterns that have been accepted for use within the enterprise, and actual architectural work done previously within the enterprise. The architect would seek to re-use as much as possible from the Enterprise Continuum that was relevant to the project at hand. (In addition to the collection of architecture source material, the repository would also contain architecture development work-in-progress.)
The criteria for including source materials in an organization's Enterprise Continuum will typically form part of the organization's IT governance process.
The Enterprise Continuum is thus a framework (a "framework-within-a-framework") for categorizing architectural source material - both the contents of the architecture working repository, and the set of relevant, available reference models in the industry.
In executing the ADM, the architect is not only developing the end result of an organization-specific architecture, but is also populating the organization's own Enterprise Continuum, with all the architectural assets identified and leveraged along the way, including, but not limited to, the resultant enterprise-specific architecture.