Test and Evaluation Process Guidelines   (Revised 4/2009)

download AMS

C-5: CONTENT AND FORMAT OF DEVELOPMENT TEST (DT) AND PRODUCTION ACCEPTANCE TEST (PAT) PLANS      

Note: The DT plan format will be tailored to the type of test and/or phase of testing required by contract (production acceptance, site acceptance, factory acceptance, software, system, etc.).

Title Page: The title page contains the name of the program and the type of test plan (software test plan, site acceptance test plan). The title page contains the signatures of the program manager, the test program manager, and the quality assurance manager. The title page is signed by all managers before the test plan is submitted for review.

Executive Summary: The Executive Summary starts on a new page. The Executive Summary contains an overview of the test plan, which includes: the test plan's relationship to the overall test program, the relationship of the test plan to contract requirements, and significant system or program information considered important to completing the tests outlined in the test plan.

Table of Contents: The table of contents contains paragraph titles and page numbers. It lists each test description. Illustrations, tables, and figures are listed separately.

1.0 Introduction: This section is divided into the following paragraphs.

1.1 Purpose: The following statement, in its entirety, will be included in the introduction: "The purpose of this test plan is to validate requirements assigned to this phase of testing required by ________________________ (enter contract system specification number) for the _________________(enter official system title and contract number). This test plan documents _______________(enter contractor's company name) test strategy in order to meet the requirements of the contract."

1.2 Scope: This paragraph provides an overview of the strategy for validating requirements assigned to the phase of testing covered by the test plan. The paragraph generally describes the tests to be accomplished, location of testing, the systematic arrangement of testing, and includes all subcontractor testing, when applicable.

2.0 Reference Documents: This section contains all reference documents used in the development of the test plan, including all requirements documents listed or referenced in the system specification and contract.

3.0 System Description: This section will be divided into the following paragraphs.

3.1 System: This paragraph describes the systems/subsystems to be tested and their major functions. The paragraph also contains a functional block diagram of the system and subsystems.

3.2 Interfaces: This paragraph contains a simplified block diagram with a functional description of each interface. The paragraph includes facility interfaces, remote maintenance monitoring interface, voice communications interface, operator interface, and any interface required to validate the system specification requirements.

4.0 Test Program Management: This section will be divided into the following paragraphs.

4.1 Management: This paragraph describes the contractor's management responsibilities for the testing phase by test plan. This paragraph includes an organizational chart with names of individuals responsible for each department and/or subcontractor participating in the test program.

4.2 Schedule: This paragraph includes a test schedule integrated with program milestones. The schedule identifies all tests to be accomplished.

5.0 Test Configuration Management: This section identifies the specific configuration management process for each unit under test.

6.0 Discrepancy Reporting and Corrective Action. This section describes the Discrepancy Reporting and Corrective Action program that supports the test program. The Discrepancy Reporting and Corrective Action forms and instructions for completing those forms are included in this section.

Test Descriptions: This section contains test descriptions for each test to be conducted under this test plan. The test descriptions are attached as Appendix A of this plan.

The test descriptions contain sufficient information to allow the preparation of the test procedures for the test described. The following outline describes the minimum information to be included in each test description:

a.   Test or Evaluation Title: Specify the title of the test/evaluation and a number designation.

b.   Test or Evaluation Objectives: List the objectives/requirements the test will validate and test success criteria.

c.   Test or Evaluation Approach: State the methods to be used to meet the test objectives.

d.   Execution Time: Estimate the total time it will take to execute the test(s) described, including multiple runs of a test procedure.

e.   Location: Identify the testing location.

f.    Tasks/Activities: List tasks or activities that will occur during the test.

g.   Personnel: Identify number and type of personnel required to accomplish the test.

h.   Test Equipment: Identify all test equipment (hardware and software) required to accomplish the test. Define any analysis tools that will be used to support the test.

i.    Data Reduction/Analysis: Describe the test data reduction method, in relation to the Test Equipment identified in item h that will support the test. Identify any data analysis that will be associated with the test. The contractor describes the data expected, when and how the data will be processed, and how the data supports verification of the requirement.

j.    Special Conditions: Describe any special test conditions, test scenarios, or special operating conditions required to accomplish the test.