A Test Readiness Review (TRR) is conducted to determine if the system under review is ready to proceed into formal testing by deciding whether the test procedures are complete and verify their compliance with test plans and descriptions. A TRR is normally conducted before each major test configuration item including hardware and software and provides management with the assurance that a system has undergone a thorough test process and is ready for turnover to the next test phase. The Flight Readiness Review (FRR) is a subset test of the TRR.
The TRR assesses test objectives, test methods and procedures, scope of tests, and safety and confirms that required test resources have been properly identified and coordinated to support planned tests. The TRR verifies the traceability of planned tests to program requirements and user needs. The TRR also assesses the system under review for development maturity, cost/ schedule effectiveness, and risk to determine readiness to proceed to formal testing.
The TRR should answer the following questions:
- Why are we testing?
- What is the purpose of the planned test?
- Does the planned test verify a requirement that is directly traceable back to a system specification or other program requirement?
- What are we testing (subsystem, system, system of systems, other)?
- Is the configuration of the system under test sufficiently mature, defined, and representative to accomplish planned test objectives and or support defined program objectives?
- Are we ready to begin testing?
- Have all planned preliminary, informal, functional, unit level, subsystem, system, and qualification tests been conducted, and are the results satisfactory?
- What is the expected result and how can/do the test evaluation results affect the program?
- Is the planned test properly resourced (people, test article or articles, facilities, data systems, support equipment, logistics, etc.)?
- What are the risks associated with the tests and how are they being mitigated?
- What are the hazards and ESOH risks associated with the specific testing?
- Have the necessary “Safety Releases” from the Program Manager (PM) been provided to developmental and operational testers prior to any test using personnel?
- What is the fall-back plan should a technical issue or potential showstopper arise during testing?
The scope of the TRR is directly related to the risk level associated with performing the planned tests and the importance of the test evaluation results to overall program success. The level of specific risk and associated risk level will vary as a system proceeds from component level, to system level, to systems of systems level testing. Early component level tests may not require the same level of review as the final system level tests. Sound judgment should dictate the scope of a specific test or series of tests.
Typical TRR success criteria including the following:
- Completed and approved test plans for the system under test,
- Completed identification and coordination of required test resources,
- The judgment that previous component, subsystem, and system test results form a satisfactory basis for proceeding into planned tests, and
- Identified risk level acceptable to the program leadership.
The Program Manager (PM) should address the scope of the TRR in the Systems Engineering Plan (SEP). Test and Evaluation (T&E) is an integral part of the Systems Engineering Processes of Verification and Validation.
AcqLinks and References:
- Defense Acquisition Guidebook (DAG)
- DoD TRR Risk Assessment Checklist
- TRR Standards and Guidelines
- Test and Management Guidebook
- NAVAIR Instruction 4355.19D – Systems Engineering Technical Review