Which statement about Requirements Management is most correct?

The TOGAF Architecture Development Method (ADM) graphically depicts Requirements Management at the center of the ADM cycle. This central placement signifies that it is a continuous, dynamic process that underpins and interacts with all phases of architecture development, rather than being a discrete step. Effective stakeholder engagement is fundamental to this process, as stakeholders are the source of requirements and their concerns must be addressed. Therefore, placing both Requirements Management and stakeholder engagement at the core of architecture development accurately reflects the TOGAF framework's approach to ensuring the architecture aligns with business needs and is fit-for-purpose.

A. Processing change requests is only one activity within the broader scope of Requirements Management, not its primary purpose.
B. Requirements are identified, elaborated, and refined throughout the ADM cycle, not just captured once in Phase A.
C. Requirements Management is a continuous, central process that runs in parallel with the ADM phases, not a sequential step within them.

1. The Open Group Standard

TOGAF® Standard

10th Edition. (2022). Part II: Architecture Development Method (ADM)

Chapter 3

The ADM in Detail

Figure 3-1: The ADM Cycle. This figure visually places "Requirements Management" at the center of the ADM phases

illustrating its central and continuous nature.

2. The Open Group Standard

TOGAF® Standard

10th Edition. (2022). Part III: ADM Guidelines and Techniques

Chapter 16

Requirements Management

Section 16.1

Introduction. This section states

"The Requirements Management process is a dynamic process of managing architecture requirements throughout their lifecycle ... The ADM is continuously driven by the Requirements Management process."

3. The Open Group Standard

TOGAF® Standard

10th Edition. (2022). Part III: ADM Guidelines and Techniques

Chapter 24

Stakeholder Management

Section 24.1

Introduction. This section emphasizes that stakeholder concerns are the key drivers for architecture activity and that understanding them is crucial for defining requirements.