Skip to content
Software Architecture Guide

TOGAF Architecture Development Method

Explanation

Section titled “Explanation”

The TOGAF Architecture Development Method (ADM) is a step-by-step way to develop an architecture for a whole organization. For the framework around it, see the article “TOGAF”.

A cycle, not a straight line. The ADM is iterative and cyclic. Finishing one phase feeds directly into the next phases, so the work forms a continuous loop.

Tailoring. An organization does not have to use the ADM exactly as written. It can tailor the method to its own needs and then use it to manage the work.

Moving back and forth. Teams can return to an earlier phase. They can also repeat activities inside one phase to flesh out the architecture content.

Phase C. In Phase C, the data architecture and the application architecture are developed in combination. See “Data Architecture” and “Application Architecture” for what each covers.

Phases G and H. Phase G gives architectural oversight of the implementation. Phase H sets procedures for managing change to the new architecture.

Agile use. The ADM can be tailored for agile practice. TOGAF describes using sprints (short, fixed work periods) to deliver architecture in increments.

Example

Section titled “Example”

A company tailors the ADM to its needs and works in sprints. In one sprint, the team develops data and application architecture together for a new ordering service. A later finding shows that an earlier result was too narrow. The team goes back to that earlier phase, adjusts it, and continues. During implementation, architectural oversight checks the work. Agreed procedures then handle later changes.

Trade-offs

Section titled “Trade-offs”

The facts available describe the freedom the ADM gives: tailoring, going back, repeating work, and using sprints. They do not describe its costs. Each organization has to decide how much to tailor and how often to iterate.

Checks

Section titled “Checks”
  • The document states how the ADM was tailored to the organization’s needs.
  • The document shows that data architecture and application architecture are developed together in Phase C.
  • The document explains whether and how teams return to earlier phases or repeat activities within a phase.
  • If sprints are used, the document says how architecture is delivered incrementally.
  • The document names how implementation is overseen (Phase G) and how change is managed (Phase H).
Section titled “Related”

Sources

Section titled “Sources”