Not every requirement is about what the system does. The BABOK Guide sorts them into four kinds, and keeping them apart makes each one easier to write and to test.
- Business requirements say why: the goals and objectives of the organization. "Reduce refund handling cost by 30% this year."
- Stakeholder requirements say what a group of stakeholders needs to reach those goals. "Customer service agents need to see a refund's status."
- Solution requirements describe the solution. Functional ones say what it does ("The system shall email the customer when the refund is paid"); non-functional ones say how well it must do it ("Status loads within 2 seconds").
- Transition requirements are needed only to move from today to the new solution, then they disappear: migrating open refunds, training agents, running old and new side by side for a month.
Each kind traces to the one above it. A functional requirement that serves no stakeholder or business requirement is a warning sign: either a need is missing from your list, or the feature is not needed.