next up previous contents index
Next: General Requirements Up: Software Engineering Methodology: The Previous: Performance

Example Requirement Document

The analysis phase generates the requirement document. A good requirement document is worth its weight in gold. On many occasions project failure can be traced back to the lack of a high quality requirement document or lack of any requirement document. With this in mind, here is an example of a requirement document for the game of poker based on  [Rai92] and  [Hoy92].

The poker requirement document is written as a dialectic. The author's comments are in italics font and not actually part of the requirement document. The author's comments are to guide the reader through the thought process used to establish the requirements.

This section may be skipped if you are only interested in methods and not interested in requirement documents or the game of poker.





Ronald LeRoi Burback
Wed Jul 30 10:49:53 PDT 1997