TOGAF Learning Outcome: Introduction to the ADM

The Candidate must be able to:
1. Briefly describe the ADM cycle, its phases, and the objective of each phase

ADM Cycle

2. Describe a typical set of steps, such as those for Phases B, C, and D

Typical set of steps in Phase B, C, and D are:

  • Select Reference Models, Viewpoints and Tools
  • Develop Baseline Architecture description
  • Develop Target Architecture description
  • Perform Gap analysis
  • Define Candidate Road map components
  • Resolve impacts across architecture landscape
  • Conduct formal stakeholder review
  • Finalize the arcihtecture
  • Create ADD – Architecture definition document.

3. Describe the versioning convention for deliverables used in Phases A to D

  • Version 0.1 – High level outline of the architecture is in place.
  • Version 1.0 – A formally reviewed detailed architecture is in place.

ADM Version Numbering Convention
4. Briefly describe the relationship between the ADM and other parts of TOGAF (Enterprise Continuum, Architecture Repository, Foundation Architecture, Supporting Guidelines and Techniques)

  • Enterprise Continuum provides a framework and context to support the leverage of relevant architecture assets in executing the ADM.
  • The practical implementation of Enterprise Continuum typically takes the form of Architecture Repository that includes reference architectures, models and patterns that have been accepted for use within the enterprise, and actual architectural work done previously in the enterprise
  • ADM helps populate the foundation architecture of an enterprise. Business requirements of an enterprise may be used to identify the necessary definitions and selections in the Foundation Architecture.
  • ‘Supporting Guidelines and techniques’ is a set of resources – guidelines, templates, checklists, and other detailed materials – that support application of the TOGAF ADM.

5. Explain the purpose of the supporting guidelines and techniques, and the difference between guidelines and techniques

  • ‘Supporting Guidelines and techniques’ is a set of resources – guidelines, templates, checklists, and other detailed materials – that support application of the TOGAF ADM.
  • Difference between G & T ???

6. Briefly describe the key points of the ADM cycle

  • For each ADM iteration, a fresh decision must be taken as to:
    • The breadth and coverage of the enterprise to be defined.
    • The level of detail to be defined
    • Extent of time period aimed at, including the number and extent of any intermediate time periods.
    • Architectural assets to be leveraged
      • Assets created in the previous iterations of ADM cycle within the enterprise
      • Assets available elsewhere in the industry
  • ADM is an iterative process
  • ADM is intended to be used by enterprises in a wide variety of geographies and applied in different vertical sectors / industries.


7. List the main reasons why you would need to adapt the ADM

  • Main reasons for adapting the ADM
    • The order of phases in ADM depends on the maturity of architecture discipline within the enterprise.
    • The possible need to integrate TOGAF with another enterprise framework in use at the enterprise.

8. Explain the need for the ADM process to be governed

  • ADM process should be governed as the architecture board should be satisfied that the ADM is being correctly applied across all phases of an architecture development iteration.

9. Describe the major information areas managed by a governance repository

  • Major information areas managed by governance repository:
    • Reference Data
    • Process Status
    • Audit Information


10. Briefly explain the reasons for scoping an architecture activity

  • Reasons for scoping an architecture activity relate to limits in
    • The organization authority of the team producing the architecture
    • Th objectives and stakeholder concerns to be addressed by the architecture
    • The availability of people, finance and other resources

11. List the possible dimensions for limiting the scope

  • Four dimensions are typically used to define and limit the scope of an architecture
    • Breadth
    • Depth
    • Time period
    • Architecture domains

12. Briefly explain the need for an integration framework that sits above individual architectures

  • Architectures that are created to address a subset of issues within an enterprise require a consistent frame of reference so that they can be considered as a group as well as point deliverables
  • Need for effective standards governance to reduce the need for manual co-ordination and conflict resolution.

Leave a Reply

Your email address will not be published. Required fields are marked *

Post Navigation