1. Scope.

This section shall be divided into the following paragraphs.

1.1 Identification.

This paragraph shall contain a full identification of the system and the software to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).

1.2 System overview.

This paragraph shall briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and support agencies; identify current and planned operating sites; and list other relevant documents.

1.3 Document overview.

This paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use.

2. Referenced documents.

This section shall list the number, title, revision, and date of all documents referenced in this report. This section shall also identify the source for all documents not available through normal Government stocking activities.

3. Overview of test results.

This section shall be divided into the following paragraphs to provide an overview of test results.

3.1 Overall assessment of the software tested.

This paragraph shall:

  1. Provide an overall assessment of the software as demonstrated by the test results in this report

  2. Identify any remaining deficiencies, limitations, or constraints that were detected by the testing performed. Problem/change reports may be used to provide deficiency information.

  3. For each remaining deficiency, limitation, or constraint, describe:
    1. Its impact on software and system performance, including identification of requirements not met
    2. The impact on software and system design to correct it
    3. A recommended solution/approach for correcting it

3.2 Impact of test environment.

This paragraph shall provide an assessment of the manner in which the test environment may be different from the operational environment and the effect of this difference on the test results.

3.3 Recommended improvements.

This paragraph shall provide any recommended improvements in the design, operation, or testing of the software tested. A discussion of each recommendation and its impact on the software may be provided. If no recommended improvements are provided, this paragraph shall state "None."

4. Detailed test results.

This section shall be divided into the following paragraphs to describe the detailed results for each test. Note: The word "test" means a related collection of test cases.

4.x (Project-unique identifier of a test).

This paragraph shall identify a test by project-unique identifier and shall be divided into the following subparagraphs to describe the test results.

4.x.1 Summary of test results.

This paragraph shall summarize the results of the test. The summary shall include, possibly in a table, the completion status of each test case associated with the test (for example, "all results as expected," "problems encountered," "deviations required"). When the completion status is not "as expected," this paragraph shall reference the following paragraphs for details.

4.x.2 Problems encountered.

This paragraph shall be divided into subparagraphs that identify each test case in which one or more problems occurred.

4.x.2.y (Project-unique identifier of a test case).

This paragraph shall identify by project-unique identifier a test case in which one or more problems occurred, and shall provide:

  1. A brief description of the problem(s) that occurred

  2. Identification of the test procedure step(s) in which they occurred

  3. Reference(s) to the associated problem/change report(s) and backup data, as applicable

  4. The number of times the procedure or step was repeated in attempting to correct the problem(s) and the outcome of each attempt

  5. Back up points or test steps where tests were resumed for retesting

4.x.3 Deviations from test cases/procedures.

This paragraph shall be divided into subparagraphs that identify each test case in which deviations from test case/test procedures occurred.

4.x.3.y (Project-unique identifier of a test case).

This paragraph shall identify by project-unique identifier a test case in which one or more deviations occurred, and shall provide:

  1. A description of the deviation(s) (for example, test case run in which the deviation occurred and nature of the deviation, such as substitution of required equipment, procedural steps not followed, schedule deviations). (Red-lined test procedures may be used to show the deviations)

  2. The rationale for the deviation(s)

  3. An assessment of the deviations' impact on the validity of the test case

5. Test log.

This section shall present, possibly in a figure or appendix, a chronological record of the test events covered by this report. This test log shall include:

  1. The date(s), time(s), and location(s) of the tests performed

  2. The hardware and software configurations used for each test including, as applicable, part/model/serial number, manufacturer, revision level, and calibration date of all hardware, and version number and name for the software components used

  3. The date and time of each test related activity, the identity of the individual(s) who performed the activity, and the identities of witnesses, as applicable

6. Notes.

This section shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of any terms and definitions needed to understand this document.

A. Appendixes.

Appendixes may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendixes may be bound as separate documents for ease in handling. Appendixes shall be lettered alphabetically (A, B, etc.).