Requirements Life Cycle Management Flashcards
7 cards from real Certified Business Analysis Professional practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Requirements Life Cycle Management flashcards as text
In the BABOK Guide, which of the following is an input to the Trace Requirements task?
Answer: Requirements and designs
According to BABOK, the Trace Requirements task takes requirements and designs as its primary inputs to establish and document relationships between them.
What does configuration management provide in the context of requirements life cycle management?
Answer: A system for controlling changes and maintaining the integrity of requirements documentation
Configuration management provides version control and change tracking mechanisms that preserve the integrity and history of requirements documentation throughout the project.
When prioritizing requirements, which factor should be weighted most heavily according to BABOK best practices?
Answer: The business value delivered relative to implementation cost and risk
BABOK emphasizes that prioritization should be driven by business value relative to cost and risk, ensuring the most impactful requirements are addressed first.
What is meant by 'requirements reuse' in the context of Requirements Life Cycle Management?
Answer: Leveraging existing, approved requirements as inputs for new or related initiatives
Requirements reuse involves applying validated requirements from prior initiatives to new projects, improving efficiency and ensuring consistency across related solutions.
Which of the following best describes the relationship between requirements approval and requirements baseline?
Answer: Requirements must be approved by stakeholders before they can be baselined
Stakeholder approval confirms that requirements meet business needs, and this approval is a prerequisite for establishing a requirements baseline that serves as a change-control reference.
Under what circumstances should a business analyst trigger re-prioritization of requirements?
Answer: When business goals, stakeholder needs, constraints, or risks change significantly
Re-prioritization is warranted whenever significant changes occur in business strategy, stakeholder needs, available resources, or project risks that affect relative requirement value.
What is the key difference between functional and non-functional requirements in requirements management?
Answer: Functional requirements describe system behaviors; non-functional requirements define quality attributes like performance and security
Functional requirements describe what a system should do (capabilities and behaviors), while non-functional requirements specify quality characteristics like performance, reliability, and security.