Guidelines for Documents
Guidelines for Requirement Document and Test Plan [submit softcopy in pdf to your project web site]
- Requirement Document
- at least teamSize * 2 pages (single-spaced, 12-pt font, 1-in margins) [for example, at least 6 pages for a team with 3 members]
- required features/behaviors
- for each required feature/behavior, state sample input and output
of correct (and incorrect) behavior
- Test Plan
- at least teamSize * 1 page (single-spaced, 12-pt font, 1-in margins) [for example, at least 3 pages for a team with 3 members]
- for each required feature/behavior
in the Requirement Document, discuss test cases to verify the feature/behavior.
- Generally, test cases are designed to find bugs. Hence, besides the
"usual" input values, "ununsal" input values should be consdiered as well.
Guidelines for Design Document [submit softcopy in pdf to your project web site]
- at least teamSize * 2 pages (single-spaced, 12-pt font, 1-in margins)
- system architecture diagram (e.g. UML diagram)
- for each module, discuss its functionality and interface among modules
Philip Chan
Last modified: Sat Sep 6 18:07:44 EDT 2008