Requirements Lifecycle Management Flashcards

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

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

Requirements traceability links each requirement to its source (business goal, regulation, stakeholder need) and to downstream deliverables (design, test cases, code), enabling impact analysis and completeness verification.

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

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

Baselining establishes an agreed-upon version of requirements at a specific point in time, providing a reference point for change control without permanently preventing change.

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

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

Requirements attributes are properties assigned to requirements (such as priority, source, status, risk, owner) that support management, prioritization, and tracking activities.

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

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

All changes to approved requirements should be evaluated for their impact on scope, schedule, cost, quality, and risk before a decision is made — this is the purpose of formal change control.

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

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

Deferral postpones a requirement to a later release or project phase while keeping it in the backlog, whereas deletion removes the requirement entirely from current and future scope.

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

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

In agile approaches, requirements are maintained as a prioritized, evolving backlog that is continuously refined, rather than being frozen at a baseline and controlled through formal change requests.