- Write atomic requirements that stand alone. Use “Shall“ where requirements are being stated, “Will” when representing statements of facts; and “Should” to present a goal that needs to be achieved.
- Make them easy to read and jargon free. Form a complete sentence devoid of loose terms, buzzwords, or acronyms.
- Avoid using let-out clauses or ambiguity such as but, except, if necessary, etc., etc.
- Use a subject (user/system) and a predicate (intended result, action or condition).
- Write what is wanted not how it is done.
- Avoid indefinable terms like user-friendly, versatile, robust, approximately, minimal impact, etc. Select aspects that are measurable.
- Don’t make references to unreachable documents or requirements yet to be defined.
- Avoid conflicting statements.
- Make them achievable.
- Use positive statements “The system shall…”, not “The system shall not…”.
Sunday, 11 September 2016
Here are 10 tips for requirement writing: