DI-MGMT-82377

TEST PLAN

This Data Item Description outlines test plans and performance objectives for systems and equipment, detailing methods, elements, responsible activities, and recording procedures for procuring activities.

Approval DateJanuary 13, 2022

AMSC Number10297

Preparing Activity—

Project NumberMGMT-2021-015

OPRMDA

DTIC ApplicableNo

GIDEP ApplicableNo

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The test plan outlines the plans and performance objectives at every level of testing on systems or equipment. It provides the procuring activity with the test concept and objectives to be satisfied, test methods, elements, responsible activities associated with the testing, measures required and recording procedures. This Data Item Description (DID) is applicable to system, component, and sub-component design evaluation tests, engineering tests, preliminary qualification tests, formal qualification tests, human factors tests, operational tests and acceptance tests. This DID contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

Preparation Instructions

1Reference documents.None.

2General.The test plan shall document in detail the Contractor's plan for conducting tests and analyzing the test results to show how the system/component/sub-component, when fielded, will satisfy the requirements of the applicable design specification. This test plan shall cover all system testing and associated activities to include support to other activities including, but not limited to: real world, operational exercise type events; cyber & Fast-type events; Warfighter Tactics, Techniques and Procedures development events; Targets of Opportunity (TOOs); component tests; Element or other agency integration activities; and external element upgrades and trial periods. For each type of test event, this test plan shall describe planning, test resources/infrastructure/test ranges, readiness reviews, data management, analyses, reporting, and associated activities.

3Format.The plan shall be in Contractor's native format. Deliverable must be compatible/readable with Government IT systems

4Contents.The plan shall contain the following:

4.1Title page.The title page shall include the following:

4.1.1Contractor's name

4.1.2Contract Number

4.1.3Security Classification

4.1.4Distribution Statement

4.2Introduction.This shall include an overview of the objectives of the test plan, including flow diagrams, milestones, personnel participation, locations, schedules, and security measures to be observed. The plan shall include the following: scope of the test program, relationship of the test plan to other element program documents, the test management approach and the organizational test responsibilities.

4.3Flow Diagram and Test Processes.This plan shall include an overall flow diagram of each test type.

4.4Participation.Identifies the Government and Contractor participation roles and responsibilities.

4.5Location.Identifies the facilities where the testing will be performed.

4.6Schedule.Identifies when flight, ground and cyber testing is planned to be performed (referenced to test completion - e.g., Runs for Record or Launch), identifies key interdependencies driving the planned flight, ground and cyber test schedules, and identifies flight, ground and cyber test schedule risk. Identifies the nominal planned and expected completion timeline for each type of ground, cyber and flight test event.

4.7Security.Identify and state briefly any security measures or guidelines to be observed.

4.8Master Test List.Identifies the major types of system flight, ground and cyber tests and support to other activities including, but not limited to: real world/operational exercise type events such as Fast-type events; Warfighter Tactics, Techniques and Procedures (TTPs) development events; TOOs, external element upgrades and trial periods; and component tests. References shall be made to the test requirements and include the following:

4.8.1Test description.Name and brief description of test to be performed.

4.8.2Applicable specification (s).The specifications shall be identified as follows:

4.8.2.1Title and identification number.

4.8.2.2Paragraph number associated with the tests.

4.8.3Parameters.Specify the critical factors to be evaluated for test events; identify the M&S parameters to be collected in test events. Identify the process for determining the required data to be collected in order to evaluate critical factors specified.

4.8.4Test objectives.Describe the objectives of each test performed, including the criteria, baseline, duration, and number of times each test should be performed.

4.8.4.1Success/failure criteria.

4.8.4.2Baseline

4.8.4.3Duration

4.8.4.4Quantity of tests

4.8.5Test Configuration.Identify the hardware/software configurations for element/components under test; describe functionality to be evaluated for "first-time" testing of hardware/software upgrades; and, the configuration/name of the threats(s) for the test event.

4.8.6Test Support Requirements.Identify and describe technical, logistical and personnel support requirements.

4.8.7Special test equipment.List all special test equipment required to be designed or fabricated for use on the program as follows:

4.8.7.1Description.

4.8.7.2Nomenclature

4.8.7.3Date required

4.8.8Approach.Briefly summarize the approach these tests (e.g., ground, cyber, flight etc.) will use to verify a requirement or specification is met.

4.8.9Data Requirements and Instrumentation.Identify the process for determining data required to be collected in order to evaluate test objectives, critical factors, and M&S parameters. For each data requirement, indicate the type of instrumentation to be used to collect the data.

4.8.10Data reduction and analysis.Describe data to be collected and the data reduction and analysis techniques that will be used to interpret the data.

4.8.11Government or Contractor Test Facilities.Identify the specific Government or Contractor facilities used for each test. Identify Government or Contractor provided simulation capabilities needed for each test. Describe planned use of and requirements for range equipment including communication links and computer equipment.

4.8.12Test Documentation:The test plan shall address development and delivery of the following as required: • Test Description Document, Detailed Test Evaluation Plan, Pre-Test Analysis Plan, Post-Test Analysis Board brief for each ground, flight and cyber test event. • Detailed Test Plan, Data Management Plan and Detailed Test Design for each system test event. • System Pre-Mission Test (SPMT) Test Plan, SPMT Report, System Post-Flight Reconstruction (SPFR) Test Plan, SPFR report, System Anomaly Response Plan, and Launch Commit Criteria for each system flight test. • Certification Data Package for each applicable test. • Quick Look Brief for each System flight, ground and cyber test. Quick Look Report for each System flight, ground and cyber test. • Range Safety Data Package for each interceptor or boost vehicle flight test Test Evaluation Report for each System test event.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer