In many requirements specifications we find fuzzy terms: [1],[2],[3]
Mostly
As needed
Might
Make sense
Appropriate
Might make sense
Graceful
At minimum
Major
Slowly
May be of use
Including but not limited to
And/or
Suitable
Various
Clean and stable interface
Several
Requirements Assistant™ looks for many more aspects in the requirements.
If we could only remove these “fuzzies”, and replace them by SMART-requirements, we would gain tremendous benefits in the definition of what we want. We also help the author of the test- and integration-plans, since she knows what to test, and when the test produces acceptable results.
Alternatively, if we cannot replace such fuzzy terms we might add one or more test-cases that cover the vague requirements to the satisfaction of the stakeholders.
[1] Karl Wiegers, article
http://www.processimpact.com/articles/court.html
[2] Dennis Buede
The engineering design of systems
Models and methods (2000), page 138
[3] Joe Kasser
The First Requirements Elucidator Demonstration (FRED) Tool
Systems Engineering Volume 7, number 3, 2004, page 243 - 257
The Journal of The International Council of Systems Engineering
[4] Ellen Gottesdiener
The Software Requirements Memory Jogger
A pocket guide to Help Software and Business Teams Develop and Manage
Requirements. Goal/QPC (2005)