IT:AD:Requirements:HowTo:Write Requirements
Summary
Writing valuable requirements is hard!
Process
Requirements
Content Acronym
An well-known acronym used to elicit useful requirements is SMART:
Specific(approximately:Complete,Accurate,Unambiguous)Measurable(approximately:Consistent,Verifiable)Achievable(approximately:Valid,Testable)Relevant(approximately:Valid)Time-bound(although this can go against the requirement for a
It more or less covers most of the key aspects, bar Modifiable, and Ranked.
Format
There is no universal format for writing Requirements.
Consider the following concepts when defining how you want to format valuable requirements:
What about GWT?
I love IT:AD:GWT when developing Acceptance Tests – but it's not appropriate for RFPs.
That said, maybe the elements of GWT can be embedded in the above some how.
At present it seems to be just a specialization of Test.