Showing posts with label requirements. Show all posts
Showing posts with label requirements. Show all posts
Wednesday, January 13, 2016
Make your requirements awesome
Means and Ends
Requirements must be written with concern to the ends, not the means.
If requirements explain steps taken, they should describe the desired end workflow.
Functionality vs. Design
Requirements should describe the desired functionality, rather than describe how to support the desired functionality.
What, when, where who, why, and how?
Requirements should describe the what, when, where, and who.
Requirements documentation can even describe the why.
Requirements cannot describe the how.
Dangerous territory: mockups
A picture is worth a thousand words.
A mockup is worth hundreds of requirements.
If you have to use mockups, don't.
If you still have to use them, the elements of the mockup that are actual requirements must be identified, highlighted, or listed in some fashion. Otherwise, you're going to be taking the long train to annoying-bug-ville.
Subscribe to:
Posts (Atom)