CCBA Requirements Lifecycle Management

Question 1

What does 'requirements traceability' enable a business analyst to do?

Accepted Answer

Link requirements to their origins and downstream deliverables to assess impact and ensure completeness

Answer

Track the time spent on each requirement

Answer

Assign requirements to specific developers

Answer

Convert requirements into user stories automatically

Question 2

In requirements lifecycle management, what is the purpose of 'baselining' a set of requirements?

Accepted Answer

To establish an agreed-upon snapshot of requirements at a point in time, enabling change control

Answer

To permanently freeze requirements so no changes can be made

Answer

To archive requirements that are no longer relevant

Answer

To convert requirements into a legal contract

Question 3

Which of the following BEST describes a 'requirements attribute' in requirements lifecycle management?

Accepted Answer

A characteristic or property assigned to a requirement to aid in management and tracking

Answer

A functional behavior that the solution must exhibit

Answer

A measurement of the complexity of the requirement

Answer

A type of business rule governing the requirement

Question 4

What is the recommended approach when a stakeholder requests a change to an approved requirement?

Accepted Answer

Evaluate the impact of the change on scope, schedule, and cost before approving it

Answer

Implement the change immediately to maintain the relationship with the stakeholder

Answer

Reject the change to protect the original scope

Answer

Allow only the project manager to evaluate change requests

Question 5

What is the difference between 'requirements deferral' and 'requirements deletion'?

Accepted Answer

Deferral means the requirement is postponed to a future release; deletion means it is permanently removed from scope

Answer

Deferral requires stakeholder approval; deletion does not

Answer

Deletion is only possible before baselining; deferral can happen at any time

Answer

There is no meaningful difference — both remove the requirement from the current scope

Question 6

In agile business analysis, how does requirements lifecycle management differ from traditional approaches?

Accepted Answer

Requirements are maintained in a living backlog and evolve iteratively rather than being frozen at a baseline

Answer

Requirements are never formally documented in agile

Answer

Change control is eliminated entirely in agile

Answer

Only technical requirements are managed; business requirements are ignored