CCBA Requirements Lifecycle Management 2 — Questions and Answers
Question 1: Which of the following is a key characteristic of a 'requirements repository'?
- It stores only approved requirements, not drafts or deferred requirements
- It is a centralized store for requirements, their attributes, and relationships (Correct answer)
- It automatically generates code from stored requirements
- It is only used in large enterprise projects
Correct answer: It is a centralized store for requirements, their attributes, and relationships
A requirements repository is a centralized system for storing requirements along with their attributes, status, traceability links, and version history, regardless of project size.
A requirements repository (which may be a dedicated requirements management tool, a spreadsheet, or a backlog management system) provides a central location for storing requirements with their associated metadata: attributes, status, traceability links, version history, and change records. It supports lifecycle management by enabling filtering, reporting, impact analysis, and audit trails.
Question 2: What is the purpose of 'requirements prioritization' in lifecycle management?
- To rank requirements in order of technical complexity
- To determine which requirements will deliver the most value relative to cost and risk (Correct answer)
- To allocate requirements to specific developers
- To eliminate low-priority requirements from the project
Correct answer: To determine which requirements will deliver the most value relative to cost and risk
Prioritization determines which requirements deliver the greatest value relative to implementation cost and risk, enabling informed decisions about what to implement first or what to include in scope.
Requirements prioritization uses criteria such as business value, cost of implementation, risk, dependencies, and urgency to rank requirements. Techniques include MoSCoW (Must/Should/Could/Won't), weighted ranking, and Kano model analysis. Prioritization helps ensure that the most valuable requirements are addressed first, especially important in incremental delivery or when scope must be reduced.
Question 3: When should a business analyst re-assess requirements priorities?
- Only at the beginning of the project during initial planning
- Whenever there are significant changes in business context, stakeholder needs, or project constraints (Correct answer)
- Only when the project manager requests it
- Once requirements are baselined, priorities should never change
Correct answer: Whenever there are significant changes in business context, stakeholder needs, or project constraints
Priorities should be re-assessed whenever significant changes occur — in the business environment, stakeholder needs, or project constraints — to ensure the team is working on the highest-value items.
Requirements priorities are not static. As business conditions change, new regulations emerge, technical constraints are discovered, or stakeholder understanding evolves, previously determined priorities may no longer reflect current reality. Business analysts should trigger re-prioritization sessions at key project milestones and whenever significant changes are identified, ensuring the team is always focused on delivering the highest current value.
Question 4: What does 'requirements reuse' mean in lifecycle management?
- Copying requirements from the internet for use in the project
- Applying requirements from previous projects or across multiple projects where they remain relevant (Correct answer)
- Recycling outdated requirements to reduce documentation effort
- Letting developers reuse code from previous projects
Correct answer: Applying requirements from previous projects or across multiple projects where they remain relevant
Requirements reuse involves applying validated requirements from previous projects or initiatives to new projects where those requirements remain applicable, saving elicitation and analysis time.
Requirements reuse means leveraging requirements that have been previously elicited, analyzed, and validated (and potentially implemented) in other projects or contexts. In organizations with mature business analysis practices and requirements repositories, reusable requirements can significantly reduce elicitation and analysis time. Common candidates for reuse include regulatory compliance requirements, security standards, and shared business process requirements.
Question 5: Which of the following BEST describes 'requirements volatility'?
- The degree to which requirements are technically complex
- The rate or frequency at which requirements change during a project (Correct answer)
- The number of stakeholders who have authority to approve requirements
- The risk that requirements may be misunderstood by developers
Correct answer: The rate or frequency at which requirements change during a project
Requirements volatility measures how frequently requirements change during a project, which directly impacts planning, risk management, and the choice of development methodology.
Requirements volatility is a key characteristic to assess during planning because high volatility (frequent changes) increases project risk and may favor adaptive/agile methodologies over predictive/waterfall approaches. Business analysts track volatility as a quality metric and planning input — high volatility may indicate unclear business direction, evolving stakeholder understanding, or inadequate upfront analysis.
Question 6: What is the role of a 'decision log' in requirements lifecycle management?
- Recording technical architecture decisions made by developers
- Documenting key requirements decisions, their rationale, and the parties who made them (Correct answer)
- Tracking the time spent on each requirements activity
- Listing all rejected requirements and the reasons for rejection
Correct answer: Documenting key requirements decisions, their rationale, and the parties who made them
A decision log records important requirements decisions — including the options considered, the rationale for the chosen option, and who made the decision — providing an audit trail and institutional memory.
A decision log documents significant decisions made during requirements elicitation and management, including: what decision was made, when it was made, who made it, what alternatives were considered, and the rationale for the chosen option. This provides an invaluable audit trail for future reference, helps onboard new team members, and prevents re-litigation of previously resolved issues.
CCBA Requirements Lifecycle Management 2
Which of the following is a key characteristic of a 'requirements repository'?