What is the purpose of Requirements Management (REQM) in the lifecycle?

• A. To define the system architecture and interfaces.
• B. To manage and trace requirements throughout the project, incorporating changes and maintaining alignment with stakeholders.
• C. To allocate and verify requirements to components.
• D. To perform coding standards enforcement.

Answer: (B)

Requirements Management focuses on controlling and tracing what the project must deliver throughout its life. It captures stakeholder needs, establishes baselines, manages changes with impact analysis, and keeps links between each requirement and the design, implementation, and verification activities. This ensures that as requirements evolve, everyone stays aligned with stakeholder intent and the project plans.

In practice, when a stakeholder request changes a requirement, this area ensures the change is evaluated, the requirements document is updated, the plan is adjusted, and the traceability to design and tests is preserved.

Defining the system architecture and interfaces is a design activity, not the ongoing management of changing requirements. Allocating and verifying requirements to components belongs to allocation and verification activities, not the overarching management of requirements. Enforcing coding standards is a quality/development practice, not about requirements lifecycle management.