Downloaded from https://www.everyspec.com 1. The LFT&E strategy will include a Plans Matrix that will include all tests, test schedules, issues to be addressed, and the planning documents (for example, the EDP and DTP) proposed for submission to DOT&E. The Plans Matrix identifies which plans are provided to DOT&E for approval or for information and review only. The DOT&E approves the LFT&E strategy via the current TEMP approval process. For TEMPs that do not require OSD approval, the LFT&E strategy contained in the TEMP will be extracted and submitted through TEMA for the Army T&E Executive submission to DOT&E for approval (see the Defense Acquisition Guidebook). 2.
The EDPs and DTPs for LFT&E are submitted through TEMA for the Army T&E Executive submission to DOT&E as required by the LFT&E plan matrix in the LFT&E strategy. The EDP must be provided to the Army T&E Executive 180 days prior to initiation of the full-up system level test and be received by the DOT&E at least 30 days before commencement of test. The DTP for the full-up system level Live Fire Test will be submitted to the Army T&E Executive 60 days and to the DOT&E 30 days prior to test. At a minimum, the EDP and DTP for the full up, system level LFT&E are submitted for DOT&E approval.
For EDPs and DTPs not requiring DOT&E approval, documents are approved in accordance with policy contained in chapter 10. (f) A covered system will not proceed to LRIP until LFT&E is completed and the report describing the results of the test is provided to the DOT&E for submission to the congressional defense committees. (g) USATEC chairs the live fire subgroup of the T&E WIPT and schedules meetings to develop and coordinate the necessary T&E activities. USATEC is responsible for developing and coordinating the LFT&E strategy.
(h) The Under Secretary of Defense for Acquisition, Technology, and Logistics (USD(AT&L)), for ACAT ID programs, or the Army T&E Executive, for less than ACAT ID programs, may waive the requirement for full-up system level testing. However, before the system or program enters systems acquisition (that is, MS B), the USD(A- T&L) or Army T&E Executive, must certify to the Congress (through the DOT&E), that full-up system level LFT&E of such system or program would be unreasonably expensive and impractical. Certification to the Congress will include the DOT&E approved alternative LFT&E strategy (that is, how the Army plans to evaluate the vulnerability or lethality of the system).
Such approval only waives the requirement for the full-up system level LFT&E. The requirement for LFT&E planning, coordination, and submittal/approval of documentation still apply, to include the inclusion of a LFT&E strategy in the TEMP. (7) Logistics demonstration. A logistics demonstration (LD) evaluates the achievement of maintainability goals; the adequacy and sustainability of tools, test equipment, selected test programs sets, built-in test equipment, associated support items of equipment, technical publications, and maintenance instructions.
It also evaluates the adequacy of trouble-shooting procedures, personnel skill requirements; the selection and allocation of spare parts, tools, test equipment, and tasks to appropriate maintenance levels; and the adequacy of maintenance time standards. A LD is required for all new acquisition systems or system changes which have an operational impact, including any new or improved support and test equipment intended for support of the system. Within available resources, a dedicated engineering prototype will be provided for the LD.
The LD requires a test plan, to include the data to be recorded and the evaluation procedures, and a final report that documents the results, analysis of findings, and recommendations for corrective actions. The TEMP will contain and schedule the LD. (See AR 700–127.) (8) C4I/IT interoperability certification test. The interoperability certification test is a test that applies to C4I/IT systems having interfaces or interoperability requirements with other systems. This test may consist of demonstrations using message analysis or parsing software with limited interface connectivity, or extend to full-scale scenario-driven exercises with all interfaces connected.
The APTU will coordinate certification testing requirements for joint inter- operability with the DISA. (See the Defense Acquisition Guidebook and Chairman, Joint Chiefs of Staff, Instruction (CJCSI) 6212.01D) (9) Software development test. The software development test (SDT) consists of program or module and cycle or system levels of testing. The software developer conducts the SDT, and the independent quality control element of the software development center also participates in the SDT. The proponent agency also participates and validates that the functional requirements are being met. The unit or module test is the initial testing level.
Testing is executed on local testbed hardware, and benchmark test files are used. This testing provides data to assess the effectiveness of the instruction code and economy of subroutines and object components for efficient processing. It also ensures that input and output formats, data handling procedures, and outputs are produced correctly. The cycle or system test involves testing the combination of linkage of programs or modules into major processes. It is a formal test conducted by the software developer and the proponent agency to ensure that the technical and functional objectives of the system are met.
It requires a formal test plan, test analysis report, and certification that the objectives were met and were satisfactory to all participants. c. Pre-FRP test requirements will be incorporated into the TEMP in support of MS B or C. 4–3. Post-full-rate production testing—common to materiel and C4I/IT systems a. Testing during production and deployment of the system life-cycle includes the testing necessary to verify that requirements specified in technical data packages and production contracts for hardware and software are met. Production testing also provides a baseline for post-production testing during operations and support. DT for C4I/IT systems generally supports PDSS.
If a software baseline change of major proportions (such as, redesign) appears necessary, the development phase of the C4I/IT will be re-entered and testing will follow the same procedures as 19 AR 73–1 • 1 August 2006