Sample Software Test Report

DATA ITEM DESCRIPTION						Form Approved OMB No. 0704-0188
1. TITLE SOFTWARE TEST REPORT				1. IDENTIFICATION NUMBER DI-MCCR-80017A
3. DESCRIPTION, PURPOSE 3.1 The Software Test Report (STR) is a record of the formal qualification testing performed on a Computer Software Configuration Item (CSCI). 3.2 The STR provides the Government with a permanent record of the formal qualification test performed on a CSCI (continued on page 2)
4. APPROVAL DATE (YYMMDD) 880229	5. OFFICE OF PRIMARY RESPONSIBILITY (OPR) E C		6a. DTIC APPLICABLE		6b. GIDEP APPLICABLE
7. APPLICATION/INTERRELATIONSHIP 7.1 This Data Item Description (DID) contains the format and content preparation instructions for data generated under the work tasks described by paragraph 5.7.3.2 of DOD-STD-2167A. 7.2 The Contract Data Requirements List should specify whether this document is to be prepared and delivered on bound 8-1/2 by 11 inch bond paper or electronic media. If electronic media is selected, the precise format must be specified. (continued on page 2)
8. APPROVAL LIMITATION		9a. APPLICABLE FORMS				9b. AMSC NUMBER N4334
10. PREPARATION INSTRUCTIONS 10.1 Content and format instructions. Production of this document using automated techniques is encouraged. Specific content and format instructions for this document are identified below. a. Response to tailoring instructions. In the event that a paragraph or subparagraph has been tailored out, a statement to that effect shall be added directly following the heading of each such (sub)paragraph. If a paragraph and all of its subparagraphs are tailored out, only the highest level paragraph heading need be included. b. Use of alternate presentation styles. Charts, tables, matrices, or other presentation styles are acceptable when the information required by the paragraphs and subparagraphs of this DID can be made more readable. c. Page numbering. Each page prior to Section 1 shall be numbered in lower-case Roman numerals beginning with page ii for the Table of Contents. Each page starting from Section 1 to the beginning of the appendixes shall be consecutively numbered in Arabic numerals. If the document is divided into volumes, each such volume shall restart the page numbering sequence. (continued on page 2)
11. DISTRIBUTION STATEMENT DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited

3. DESCRIPTION/PURPOSE (continued)

3.3 The STR may be used by the contractor as a basis for retesting of a CSCI.

7. APPLICATION/INTERRELATIONSHIP (continued)

7.3 The STR is used to record the results of one or more formal qualification tests defined in the Software Test Description (STD), DI-MCCR-80025A, for a CSCI.

7.4 The STR summarizes test discrepancies and references their corresponding problem/change reports..

7.5 This DID supersedes DI-MCCR-80017 dated 4 June 1985.

10. PREPARATION INSTRUCTIONS (continued)

d. Document control numbers. For hard copy formats, this document may be printed on one or both sides of each page (single-sided/double-sided). All printed pages shall contain the document control number and the date of the document centered at the top of the page. Document control numbers shall include revision and volume identification as applicable.

e. Multiple (sub)paragraphs. All paragraphs and subparagraphs starting with the phrase "This (sub)paragraph shall..." may be written as multiple subparagraphs to enhance readability. These subparagraphs shall be numbered sequentially.

f. Identifiers. The letter "X" serves as an identifier for a series of descriptions. For example, the subparagraphs describing by 10.1.5.1 shall be structured as follows:

3.1 (Name and identifier of the first qualification test)

3.1.1 (Test name) summary

3.1.2 (Test name) test record

3.2 (Name and identifier of the second qualification test)

3.2.1 (Test name) summary

3.2.2 (Test name) test record

g. Document structure. This document shall consist of the following:

(1) Cover

(2) Title page

(3) Table of contents

(4) Scope

(5) Referenced documents

(6) Test overview

(7) Test results

(8) CSCI evaluation and recommendations

(9) Notes

(10) Appendixes.

10. PREPARATION INSTRUCTIONS (continued)

10.1.1 Title page. The title page shall contain the information identified below in the indicated format:

[Document control number and date: Volume x of y (if multi-volume]

[Rev. indicator: date of Rev.]

SOFTWARE TEST REPORT

FOR THE

[CSCI NAME]

OF

[SYSTEM NAME]

CONTRACT NO. [contract number]

CDRL SEQUENCE NO. [CDRL number]

Prepared for:

[Contracting Agency Name, department code]

Prepared by:

[contractor name and address]

10.1.2 Table of contents. This document shall contain a table of contents listing the title and page number of each titled paragraph and subparagraph. The table of contents shall then list the title and page number of each figure, table, and appendix, in that order.

10.1.3 Scope. This section shall be numbered 1 and shall be divided into the following paragraphs.

10.1.3.1 Identification. This paragraph shall be numbered 1.1 and shall contain the approved identification number, title, and abbreviation, if applicable, of the system and the CSCI to which this STR applies. In addition, this paragraph shall contain the name and number of each formal qualification test for which results are recorded in this report.

10.1.3.2 System overview. This paragraph shall be numbered 1.2 and shall briefly state the purpose of the system and the CSCI to which this STR applies.

10.1.3.3 Document overview. This paragraph shall be numbered 1.3 and shall summarize the purpose and contents of this document.

10.1.4 Referenced documents. This section shall be numbered 2 and shall list by document number and title all documents referenced in this document. This section shall also identify the source for all documents not available through normal Government stocking activities.

10.1.5 Test overview. This section shall be numbered 3 and shall be divided into the following paragraphs and subparagraphs to describe the results of each formal qualification test covered by this report.

10.1.5.1 (Formal qualification test name and project-unique identifier). This paragraph shall be numbered 3.X (beginning with 3.1), shall identify a formal qualification test by name and number, and shall be divided into the following subparagraphs to provide an overview of the test results.

10.1.5.1.1 (Formal qualification test name) summary. This subparagraph shall be numbered 3.X.1 and shall summarize the results of the formal qualification test. The summary shall include the completion status of the test (i.e., success or failure). For failures, the step of the test procedure where the failure occurred and an identification of the resulting problem report shall be included. This information may be provided by reference to a test results summary table similar to Table I.

TABLE I. Example of a test results summary table

TEST A	SUCCESS	FAILURE/ ERRORS*	SOFTWARE PROBLEM REPORTS SUBMITTED	REMARKS
TEST CASE X	" © January 1, 2006 James C. Helm, PhD., P.E.