A requirement changes
A fictional library project has an agreed requirement that a member can see the due date for each borrowed item. A stakeholder now asks for reminder messages, and a developer says the request is only a small screen change. Existing records show that notification preferences, contact details and message delivery are handled by separate components. The team has not yet estimated effort or agreed who may approve the change. The analyst must identify related requirements and tests without assuming that a request is automatically accepted or rejected. This teaching scenario does not supply a real privacy law, contract or official approval policy, so those details cannot be asserted.
1. Use traceability for the decision.
Read the worked answer
Relate the new request to the attendance or return need, relevant contact and preference requirements, design components and tests to assess impact.
2. What decision remains?
Read the worked answer
The authorized decision process must weigh value, effort, risk and constraints before approving or declining the change.