Requirements Life Cycle Management

Tracing, maintaining, prioritizing, assessing changes to, and approving requirements throughout the project lifecycle.

5 minutes 5 Questions

Requirements Life Cycle Management (RLM) is a comprehensive CBAP framework that encompasses all activities involved in managing requirements from their inception through project completion and beyond. It represents a structured approach to handling requirements throughout their entire existence wit…

Concepts covered
Requirements Traceability MatrixRelationships Between Requirements LevelsRequirements Attributes and MetadataPrioritize RequirementsMoSCoW PrioritizationNegotiation and Consensus for RequirementsImpact Analysis for Requirements ChangesRequirements Approval Authority and GovernanceTrace RequirementsForward and Backward TracingMaintain RequirementsRequirements Baselining and VersioningTimeboxing and Budgeting for PrioritizationAssess Requirements ChangesConfiguration Management and Change ControlApprove RequirementsConflict and Issue Management
Test mode:
Start practice test

CBAP - Requirements Life Cycle Management Example Questions

Test your knowledge of Requirements Life Cycle Management

Question 1

What is the primary purpose of version control in configuration management?

Correct Answer: To track and manage changes to requirements artifacts over time

Version control in configuration management exists specifically to track and manage changes to requirements artifacts over time, ensuring that every modification is recorded, previous versions are preserved, and the evolution of each artifact is documented.

Assigning ownership and authority levels relates to roles and responsibilities governance, not version control. Establishing traceability links between requirements and test cases is a function of traceability management, a separate discipline. Prioritizing and scheduling changes based on stakeholder impact falls under change control and prioritization processes, not version control.

The key concept tested is understanding the distinct purpose of version control within the broader configuration management system.

Question 2

A team discovers that several requirements in their repository have been marked as 'implemented' but the associated features were rolled back in a recent release due to performance issues. The requirements still appear as completed in the traceability matrix. What should the team do to properly maintain these requirements?

Correct Answer: Update the lifecycle status of the affected requirements to reflect their current state and adjust traceability links to align with the rollback

The correct answer is right because requirements lifecycle management demands that the status of each requirement accurately reflects its current state, and when features are rolled back, both the lifecycle status and traceability links must be updated to maintain the integrity and accuracy of the requirements repository.

Archiving requirements as historically completed misrepresents their actual state and unnecessarily duplicates requirements. Removing features from the traceability matrix and reassigning to a future release goes beyond proper maintenance by making scheduling decisions prematurely. Retaining the implemented status is inaccurate since the feature is no longer in production, and notes alone do not correct the misalignment in the traceability matrix.

Key concept tested: requirements lifecycle management and traceability maintenance.

Question 3

A business analyst has documented and validated requirements for a new claims processing system. Several stakeholders with decision-making authority have reviewed the requirements, but they disagree on priority levels. The project sponsor wants to move forward, while two department managers believe certain requirements need further refinement before approval. The BA needs to resolve this and obtain formal approval. What is the best approach for the BA in this situation?

Correct Answer: Facilitate a conflict resolution session among the approvers to reach consensus on the contested requirements before seeking formal sign-off

Facilitating a conflict resolution session among the approvers is the best approach because the BA's role includes helping stakeholders reach consensus on requirements through collaboration, ensuring all perspectives are heard before formal approval is obtained.

Escalating to the sponsor to override others undermines stakeholder engagement and may result in requirements that do not meet actual business needs. Documenting disagreements as assumptions and obtaining conditional approval defers unresolved conflicts, creating risk later in the project. Splitting requirements into separate approval tracks adds unnecessary complexity and does not address the underlying disagreement among stakeholders.

The key concept tested is the BA's responsibility in stakeholder conflict resolution and consensus-building during requirements approval.

More Requirements Life Cycle Management questions
456 questions (total)
Practice 100 questions
One session at a time, always new questions