The statement describes the concept of iteration within the TOGAF Architecture Development Method (ADM). The ADM is not a rigid, one-time, sequential process. It is designed to be flexible and is almost always applied in an iterative manner. This allows architects to cycle through phases, or groups of phases, in planned cycles to progressively detail the architecture, address specific stakeholder concerns, or manage large, complex projects. The ability to cycle between phases, such as moving back and forth between Business, Information Systems, and Technology Architecture phases (B, C, and D), is a fundamental application of iteration.

A. Requirements management: This is a continuous process that occurs throughout all ADM phases to manage architecture requirements, not the act of cycling between the phases themselves.

C. Implementation governance: This is a specific activity, primarily in Phase G, that ensures implementation projects conform to the defined architecture, rather than the development process of cycling through phases.

D. Enterprise Architecture: This is the overall discipline and the resulting set of artifacts. The statement describes a specific method (iteration) used within the practice of Enterprise Architecture.

1. The TOGAF® Standard

10th Edition

Part II: Architecture Development Method (ADM)

Section 3.3

Applying Iteration to the ADM. This section explicitly states

"The TOGAF ADM is an iterative method... The ADM supports a number of levels of iteration..." It further details different iteration cycles

including "Cycling between phases"

which directly matches the scenario in the question.

2. The TOGAF® Standard

10th Edition

Part II: Architecture Development Method (ADM)

Section 3.3.2

The Iteration Cycles. This section provides diagrams and descriptions of various iteration patterns. Figure 3-2 illustrates "Iteration Between ADM Phases

" showing cycles between Phases B

C

and D

which is a common example of the concept described in the question.

3. The TOGAF® Standard

10th Edition

Part II: Architecture Development Method (ADM)

Chapter 2

ADM Phase: Requirements Management. This chapter describes Requirements Management as a dynamic and continuous process that runs in parallel with the ADM phases

distinguishing it from the iterative cycling of the phases.