Sample Test Plan
|
DATA ITEM DESCRIPTION |
Form Approved OMB No. 0704-0188 |
|||||
|
1. TITLE SOFTWARE TEST PLAN |
1. IDENTIFICATION NUMBER DI-MCCR-80014A |
|||||
|
3. DESCRIPTION, PURPOSE 3.1 The Software Test Plan (STP) describes the formal qualification test plans for one or more Computer Software Configuration Items (CSCIs). The STP identifies the software test environment resources required for formal qualification testing (FQT) and provides schedules for FQT activities. In addition, the STP identifies the individual tests that shall be performed during FQT. (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 that data generated under the work tasks described by paragraph 4.3.1 and 5.3.3 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 N4332 |
||||
|
10. PREPARATION INSTRUCTIONS 10.1 Content and format instructions. Production of this plan using automated techniques is encouraged. Specific content and format instructions for this plan 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.2 The STP enables the Government to assess the adequacy of planning for FQT activities.
7. APPLICATION/INTERRELATIONSHIP (continued)
7.3 The STP provides planning for the testing to be performed to validate one or more CSCIs against the requirements of the Software Requirements Specification (SRS), DI-MCCR-80025A, for each CSCI and the Interface Requirements Specification (IRS), DI-MCCR-80026A.
7.4 This DID supersedes DI-MCCR-80014 dated 4 June 1985.
10. PREPARATION INSTRUCTIONS (continued)
d. Document control numbers. For hardcopy 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 letters "X" and "Y" serve as identifies for a series of descriptions. For example, the subparagraphs describing formal qualification tests (see 10.1.6.1) shall be structured as follows:
4.1 (First CSCI name and identifier)
4.1.1 General test requirements
4.1.2 Test classes
4.1.3 Test levels
4.1.4 Test definitions
4.1.4.1 (First test name and identifier)
4.1.4.2 (Second test name and identifier)
4.1.4.3 etc.
4.1.5 Test schedules
4.2 (Second CSCI name and identifier)
4.2.1 etc.
g. Document structure. This plan shall consist of the following:
(1) Cover
(2) Title page
(3) Table of contents
(4) Scope
(5) Referenced documents
(6) Software test environment
(7) Formal qualification test identification
(8) Data recording, reduction, and analysis
(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 PLAN
FOR THE
[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. The software test plan 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 to which this STP applies. It shall also identify the CSCIs to which this plan applies. If the STP applies to all CSCIs in the system, this shall be stated. If it applies to selected CSCIs, the applicable CSCIs shall be named by title, abbreviation, and identifier.
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(s) to which this STP 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.3.4 Relationship to other plans. This paragraph shall be numbered 1.4 and shall describe the relationship, if any, of the STP to related project management plans.
10.1.4 Referenced documents. This
section shall be numbered 2 and shall list by document number and title
all documents referenced in this plan. This section shall also identify
the source for all documents not available through normal Government stocking
activities.
10.1.5 Software test environment. This section shall be numbered 3 and shall be divided into the following paragraphs to identify and describe the plans for implementing and controlling the resources (software, firmware, and hardware) necessary to perform formal qualification testing. To reduce duplication, references may be made in the paragraphs below to the software engineering environment described in the Software Development Plan (SDP) for those resources that are used in both environments.
10.1.5.1 Software items. This paragraph shall be numbered 3.1 and shall identify the software items (e.g., operating systems, compilers, code auditors, dynamic path analyzers, test drivers, preprocessors, test data generators, post-processors) necessary to perform the formal qualification testing activities. This paragraph shall describe the purpose of each item and shall identify any classified processing or security issues associated with the software items.
10.1.5.2 Hardware and firmware items. This paragraph shall be numbered 3.2 and shall identify the computer hardware, interfacing equipment, and firmware items that will be used in the software test environment. This paragraph shall describe the purpose of each item and shall identify any classified processing or security issues associated with the hardware or firmware items.
10.1.5.3 Proprietary nature, and Government rights. This paragraph shall be numbered 3.3 and shall identify the proprietary nature and Government rights associated with each item of the software test environment.
10.1.5.4 Installation, testing, and control. This paragraph shall be numbered 3.4 and shall identify the contractor's plans for installing and testing each item prior to its use. This paragraph shall also describe the contractor's plans for controlling and maintaining each item of the software test environment.
10.1.6 Formal qualification test identification. This section and the following paragraphs and subparagraphs shall be included in Section 4, Volume I, of the Software Test Description to identify each formal qualification test and to describe the formal qualification test requirements for each CSCI to which this STP applies.
10.1.6.1 (CSCI name and project-unique identifier). This paragraph shall be numbered 4.X (beginning with 4.1), shall identify a CSCI by name and project-unique identifier, and shall be divided into the following subparagraphs to describe the total scope of testing for the CSCI.
10.1.6.1.1 General test requirements. This subparagraph shall be numbered 4.X.1 (beginning with 4.1.1) and shall describe requirements that apply to all of the formal qualification tests or to a group of formal qualification tests. For example:
"Each formal qualification tests shall meet the following general test requirements:
a. CSCI size and execution time shall be measured.
b. The CSCI shall be tested using nominal, maximum, and erroneous input values.
c. The CSCI shall be tested for error detection and proper error recovery, including appropriate error messages."
"Formal qualification tests to validate radar tracking requirements shall meet the following test requirements:
a. The CSCI shall be tested using simulated test data for the specified combinations of environmental conditions.
b. The CSCI shall be tested using input data taken from the environment ("live data")."
10.1.6.1.2 Test classes. This paragraph shall be numbered 4.X.2 (beginning with 4.1.2) and shall describe the types or classes of formal qualification tests that shall be executed (e.g., stress tests, timing tests, erroneous input tests, maximum capacity tests).
10.1.6.1.3 Test levels. This paragraph shall be numbered 4.X.3 (beginning with 4.1.3) and shall describe the levels at which formal qualification testing will be performed. For example:
a. CSCI level (CSC or CSU level if necessary) – to evaluate compliance with CSCI requirements.
b. CSCI to CSCI integration level – to evaluate compliance with CSCI external interface requirements.
c. CSCI to HWCI integration level – to evaluate compliance with CSCI external interface requirements.
d. System level – to evaluate compliance with CSCI requirements not evaluated at other levels.
10.1.6.1.4 Test definitions. This paragraph shall be numbered 4.X.4 (beginning with 4.1.4) and shall be divided into the following subparagraphs to identify and describe each formal qualification test to be conducted on the CSCI.
10.1.6.1.4.1 (Test name and project-unique identifier). This subparagraph shall be numbered 4.X.X.Y (beginning with 4.1.4.1) and shall identify a formal qualification test by name and project-unique identifier. This subparagraph shall provide the information specified below for the test. Some or all of this information may be provided graphically.
a. Test objective
b. Any special requirements (e.g., 48 hours of continuous facility time, weapon simulation)
c. Test level
d. Test type or class
e. Qualification method as specified in the Software Requirements Specification
f. Cross reference to the CSCI engineering requirements in the Software Requirements Specification addressed by this test
g. Cross reference to the CSCI interface requirements in the Interface Requirements Specification addressed by this test.
h. Type of data to be recorded
i. Assumptions and constraints.
10.1.6.1.5 Test Schedule. This paragraph shall be numbered 4.X.5 and shall contain or reference the test schedule for conducting the tests identified in paragraph 4.X.4.
10.1.7 Data recording, reduction, and analysis. This section shall be numbered 5 and shall be divided into paragraphs and subparagraphs as appropriate to describe the data reduction and analysis procedures to be used during and following the tests identified in this STP. This section shall document how information resulting from data reduction and analysis will be retained. The results of data recording, reduction, and analysis activities shall be documented in such a way that the resulting information will clearly show whether the test objectives have been met.
10.1.8 Notes. This section shall be numbered 6 and shall contain any general information that aids in understanding this document. This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document.
10.1.9 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 Appendix A, paragraph 10, 10.1, 10.2, 20, 20.1, 20.2, etc.). Pages within each appendix shall be numbered alpha-numerically as follows: Appendix A pages shall be numbered A-1, A-2, A-3, etc. Appendix B pages shall be numbered B-1, B-2, B-3, etc.