**The TestPlan folder is intended to capture the written test plan for the susb-systems as well as the fully built top level system. This section should maintain the revisions as they are upgraded**.

Make use of any revision numbering or letter system your program agrees upon. Designate one person as the lead who can make the revisions after the first "release" is made of the test plan. Subsequent revisions should list who made the revision, the date of the revision, and the doc title should indicate it is the latest revision. Example:

System_TestPlan.Project.doc
System_TestPlan.Project_revA.doc
SubSystemA_TestPlan.Project.doc
SubSystemA_TestPlan.Project_revA.doc
SubSystemA_TestPlan.Project_revB.doc

NOTE: Images, diagrams or anything else that will help are encouraged to be included in the test plan. Each phase of a test plan should be clearly delineated and explain the purpose, equipment required in support, and the criteria for pass or fail. Each test should also have a direct and traceable path back to a specification or functional requirement.