A requirement is good when everyone reads it the same way and a tester can prove it is met. The international standard for requirements (ISO/IEC/IEEE 29148) lists the characteristics; four catch most problems:
- Unambiguous: one meaning. "Recent orders" means different things to different people; "orders from the last 90 days" does not.
- Verifiable: you can write a test that passes or fails. Watch for vague words: fast, user-friendly, easy, flexible, as soon as possible, where appropriate, etc. Each needs a number or a rule.
- Singular: one requirement each. "The system shall email the label and refund the customer" is two; split it, because they may be built, tested and changed separately.
- Feasible and necessary: it can be built within the constraints, and someone needs it.
Write in the active voice with a clear subject: "The system shall..." or "The store manager can...". Keep design out ("a green button") unless it truly is a requirement.
Vague and joined requirements, rewritten.