1. PART I--SYSTEM INTRODUCTION
a. Mission Description. Reference the MNS, CRD (if applicable), C4ISP, and ORD. Briefly summarize the mission need described therein. Describe the mission in terms of objectives and general capabilities. Include a description of the operational and logistical environment envisioned for the system.
b. System Description. Briefly describe the system design, to include the following items:
(1) Key features and subsystems, both hardware and software (such as architecture, interfaces, security levels, reserves) for each block/configuration, allowing the system to perform its required operational mission.
(2) Interfaces with existing or planned systems that are required for mission accomplishment. Address relative maturity and integration and modification requirements for non-developmental items. Include interoperability with existing and/or planned systems of other DoD Components or allies. Provide a diagram of the system architecture.
(3) Critical system characteristics or unique support concepts resulting in special test and analysis requirements (e.g., post deployment software support, hardness against nuclear effects; resistance to countermeasures; resistance to reverse engineering/exploitation efforts (Anti-Tamper); development of new threat simulation, simulators, or targets).
c. System Threat Assessment. Reference the System Threat Assessment and briefly summarize the threat environment described therein.
d. Measures of Effectiveness and Suitability . List (see example matrix below) the performance (operational effectiveness and suitability) capabilities identified as required in the ORD. The critical operational effectiveness and suitability parameters and constraints must crosswalk to those used in the Analysis of Alternatives, and include manpower, personnel, training, software, computer resources, transportation (lift), compatibility, interoperability and integration, Information Assurance (IA), Electromagnetic Environmental Effects and Spectrum Supportability, etc. Focus on operational capabilities, not design specifications such as weight, size, etc. Limit the list to critical measures that apply to capabilities essential to mission accomplishment. Include and clearly identify all Key Performance Parameters (KPP). For each listed parameter, provide the threshold and the objective values from the ORD and the ORD reference. If the Operational Test Agency (OTA) or the DOT and E determines that the required capabilities and characteristics contained in the ORD provide insufficient measures for an adequate OT&E, the OTA or DOT&E shall propose additional measures through the IPT process. Upon receipt of such a proposal, the ORD approval authority shall establish the level of required performance characteristics.
Measures of Effectiveness and Suitability
** Key Performance Parameter
e. Critical Technical Parameters
(1) List in a matrix format (see example below) the critical technical parameters of the system (including software maturity and performance measures) that will be evaluated (or reconfirmed if previously evaluated) during the remaining phases of developmental testing. In accordance with section C3.5. of this Regulation, include the maturity criteria and performance exit criteria necessary for operational test readiness certification. Critical technical parameters are measurable critical system characteristics that, when achieved, allow the attainment of operational performance requirements. They are not ORD requirements. Rather, they are technical measures derived from ORD requirements. Failure to achieve a critical technical parameter should be considered a reliable indicator that the system is behind in the planned development schedule or will likely not achieve an operational requirement. Limit the list of critical technical parameters to those that support critical operational issues. The system specification is usually a good reference for the identification of critical technical parameters.
(2) Next to each technical parameter, list a threshold for each stage of development. Developmental test events are opportunities to measure the performance of the system as it matures. For most technical parameters, the listed thresholds should reflect growth as the system progresses toward achieving its ORD requirements. Also, list the decision supported after each event to highlight technical performance required before entering the next acquisition or operational test phase.
(3) Ensure technical parameters are included for technical interoperability.
Critical Technical Parameters
In most cases
TEMP Part III)
reflect level of
May be any decision
entrance into a new
acquisition phase or
may be a
for operational test
Hit, 94 % at
Prod Qual Test
+/- 3 mils
+/- 1 mil
MS C (Low-Rate