Sample Requirements Documents
Here is a collection of Requirements Documents produced in earlier 3302
class taught by Dr. Abowd. These should help you get a feel for what makes
up a good requirements document for this class. And what mistakes to avoid.
And now, for the not so good. At least not on the first pass.
- Socrates
Bad distinction between functional and non-functional
requirements. Too much "how" in the functional requirements.
Scenarios all describe the same thing.
- YCT squared
Storyboards do not related to scenarios. Poor categorization of
functional requirements ("how" problem again). Vague
nonfunctional requirements.