Requirements Writing: The Basis of Mutual Understanding
The purpose of requirements writing is to produce clear requirements documents that provide a basis for the mutual understanding between the users and the designers.
The requirement document should include the details of the functionality of the product, the purposed procedures, a list of the features that need to implement, the required time for development, etc.
This document should also specify the performance requirements, which include inputs and output for users, the accuracy of the product, etc.
Requirements writing should produce each requirement stated in a way that the reader can easily get it.
A good requirement states something that is necessary, verifiable, and attainable. Even if it is verifiable and attainable, and eloquently written, if it is not necessary, it is not a good requirement.
If there is a doubt about the necessity of a requirement, then ask: What is the worst thing that could happen if this requirement were not included? If you do not find an answer of any consequence, then you probably do not need the requirement.
To be verifiable, the requirement must state something that can be verified by examination, analysis, test, or demonstration. Statements that are subjective, or that contain subjective words, such as "easy," are not verifiable. If a requirement is not attainable, there is little point in writing it. A good requirement should be clearly stated.
As you write a requirement, determine how you will verify it. Determine the criteria for acceptance. This step will help insure that the requirement is verifiable.
To be attainable, the requirement must be technically feasible and fit within budget, schedule, and other constraints. If you are uncertain about whether a requirement is technically feasible, then you will need to conduct the research or studies to determine its feasibility.
If still uncertain, then you may need to state what you want as a goal, not as a requirement. Even if a requirement is technically feasible, it may not be attainable due to budget, schedule, or other, e.g., weight, constraints. There is no point in writing a requirement for something you cannot afford -- be reasonable.
Want to learn more? Tonex offers Requirements Writing Training Course -- Specification Writing Training, a 2-day course that shows you how to write well-formed, validated requirements and specifications.
This is an excellent course for project stakeholders, SMEs, directors, project sponsors, users and just about anyone involved in the planning and writing of specifications requirements.
For more information, questions, comments, Contact us.