Certified Business Analysis Professional Requirements Life Cycle Management 2 — Questions and Answers
Question 1: In the BABOK Guide, which of the following is an input to the Trace Requirements task?
- Business objectives and stakeholder concerns
- Requirements and designs (Correct answer)
- Project charter and scope statement
- Risk register and issue log
Correct 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.
Question 2: What does configuration management provide in the context of requirements life cycle management?
- A method for creating visual models of requirements
- A system for controlling changes and maintaining the integrity of requirements documentation (Correct answer)
- A framework for conducting requirements review sessions
- A tool for converting business requirements into technical specifications
Correct 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.
Question 3: When prioritizing requirements, which factor should be weighted most heavily according to BABOK best practices?
- The technical complexity of implementing the requirement
- The chronological order in which requirements were identified
- The business value delivered relative to implementation cost and risk (Correct answer)
- The number of stakeholders who requested the requirement
Correct 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.
Question 4: What is meant by 'requirements reuse' in the context of Requirements Life Cycle Management?
- Copying requirements from a previous project without modification
- Leveraging existing, approved requirements as inputs for new or related initiatives (Correct answer)
- Recycling rejected requirements after stakeholder approval
- Using the same elicitation techniques across multiple projects
Correct 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.
Question 5: Which of the following best describes the relationship between requirements approval and requirements baseline?
- Approval and baselining are the same activity performed simultaneously
- Requirements must be approved by stakeholders before they can be baselined (Correct answer)
- Baselining occurs first to lock requirements, then approval is sought
- Approval is only needed for functional requirements, while baselining applies to all types
Correct 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.
Question 6: Under what circumstances should a business analyst trigger re-prioritization of requirements?
- At the end of every project phase, regardless of changes in the environment
- Only when the project sponsor requests a formal review
- When business goals, stakeholder needs, constraints, or risks change significantly (Correct answer)
- When more than 50% of the original requirements have been delivered
Correct 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.
Question 7: What is the key difference between functional and non-functional requirements in requirements management?
- Functional requirements describe system behaviors; non-functional requirements define quality attributes like performance and security (Correct answer)
- Functional requirements are documented by developers; non-functional requirements are documented by business analysts
- Functional requirements apply only to software projects; non-functional requirements apply to all project types
- Functional requirements are mandatory; non-functional requirements are always optional
Correct 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.
Certified Business Analysis Professional Requirements Life Cycle Management 2
In the BABOK Guide, which of the following is an input to the Trace Requirements task?