Requirements Lifecycle Management Flashcards

In requirements lifecycle management, what does 'impact analysis' assess?

Answer: The effect of a proposed requirements change on other requirements, designs, tests, and the solution

Impact analysis examines the ripple effects of a proposed change on related requirements, downstream work products (designs, tests), and the broader solution to inform change control decisions.

What is the difference between functional and non-functional requirements in lifecycle management?

Answer: Functional requirements describe what the solution must do; non-functional requirements describe how well it must do it

Functional requirements specify the behaviors and capabilities the solution must have, while non-functional requirements (also called quality attributes) specify the performance, security, usability, or reliability standards it must meet.

Why is it important to maintain requirements traceability throughout the solution development lifecycle?

Answer: It enables impact analysis, verification that requirements are implemented, and validation that needs are met

Traceability throughout the lifecycle enables impact analysis of changes, verification that every requirement has been implemented, and validation that the implemented solution actually meets the original business needs.

What does 'requirements approval' formally establish?

Answer: That identified stakeholders have reviewed and accepted the requirements as a basis for solution development

Requirements approval is a formal checkpoint where designated stakeholders review, agree to, and sign off on requirements as the basis for proceeding with solution development.

In managing requirements across multiple project releases, which approach is MOST effective?

Answer: Maintaining a product backlog or requirements repository that evolves across releases

A continuously maintained product backlog or requirements repository ensures continuity across releases, enabling incremental delivery while maintaining a comprehensive view of all requirements.

Which of the following is a sign of POOR requirements lifecycle management?

Answer: Requirements frequently change without formal impact assessment or stakeholder communication

Frequent, uncontrolled changes without impact assessment indicate poor lifecycle management — requirements should evolve through a defined process that evaluates and communicates changes.