- 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…”.
Understand the art of the possible. My mission is to make executable Model-based Systems Engineering (MBSE) easy with the Object Management Group's Systems Modeling Language™ (SysML®) and UML® to make simple modeling easy to deploy to the masses. This site provides practical experience of tuning IBM® Rational® Rhapsody® - a precision engineering UML/SysML tool. Rhapsody tips and ideas will be posted with links to videos. You can follow by email (if google app is allowed).
Sunday, 11 September 2016
10 Tips for Requirement Writing
Here are 10 tips for requirement writing:
Subscribe to: Post Comments (Atom)
Post a Comment
Note: only a member of this blog may post a comment.