Downloaded from https://www.everyspec.com program reduces duplication in research and development and can provide cost or performance advantages over traditional acquisition programs. The FCT process is dependent on a developed foreign item, user interest, a valid requirement, good procurement potential, and a successful evaluation. Section 2350a, title 10, U.S. Code, authorizes the FCT Program. Guidance can be found in DOD 5000.3–M–2, and the DOD Federal Acquisition Regulation (FAR) supplement, and the Defense Acquisition Guidebook). A Web site with downloadable templates, samples, and the FCT handbook is at http://www.acq.osd.mil/te/programs/fct/.
Chapter 4 Developmental Testing Although DT and OT are discussed in separate chapters in this regulation, as discussed in paragraph 3–1 h , T&E programs will be structured as an efficient, integrated continuum that obtains necessary, validated data from many sources. The efficient, integrated continuum constitutes a process that will be used to provide the maximum benefits from a complete, unified T&E program by efficiently using resources to shorten acquisition time. The process envisions the development of a single integrated test/simulation execution strategy, leading to a single system evalua- tion report. 4–1.
Types of developmental tests Developmental test is a generic term encompassing M&S and engineering type tests that are used to verify that design risks are minimized, that safety of the system is certified, that achievement of system technical performance is substantiated, and that readiness for OT&E is certified. The DT generally requires instrumentation and measurements and is normally accomplished by engineers and technicians. It is repeatable, may be environmentally controlled, and covers the complete spectrum of system capabilities. All types of DT are listed below.
Tests should be selected from this listing with the objective of building an efficient and effective test and simulation strategy that integrates testing according to paragraph 1–4 of this regulation to support a given program. Software intensive systems may undergo specialized testing (that is, a (6), a (9), a (10), b (6), and b (7)) listed below. a. Pre-FRP-Common to materiel and C4I/IT systems: (1) Research effort or test. (2) Technical feasibility test. (3) Engineering development test. (4) Production prove-out test (PPT). (5) PQT. (6) Software qualification test (to be used for grandfathered systems only). (7) Live fire test (part of vulnerability & lethality).
(8) Logistics demonstration. (9) C4I/IT interoperability certification test. (10) Software development test (SDT). b. Post-FRP-Common to materiel and C4I/IT systems: (1) Production verification test (PVT). (2) First article test. (3) Comparison test. (4) Live Fire Test, if required for product improvements of covered systems. (5) Quality conformance (acceptance) inspection. (6) Tests in support of post-deployment software support (PDSS). (7) C4I/IT interoperability recertification test. (8) Surveillance test. (9) Reconditioning test. 4–2. Pre-full-rate production testing—common to materiel and C4I/IT systems a.
Pre-FRP testing ranges from mission needs determination to the FRP decision review (see DOD Financial Management Regulation, Volume 2B, Chapter 5, June 2004, for information on funding categories). The types of DT conducted prior to FRP are: research effort or test, technical feasibility test, engineering development test, PPT, PQT, live-fire test, logistics demonstration, C4I/IT interoperability certification test, and SDT. b. Pre-FRP tests are defined in (1) through (9) below: (1) Research effort or test.
A research effort or test is conducted during pre-systems acquisition to determine early technical characteristics, to support the research of these items, and to provide fundamental knowledge for solutions of identified military problems. (2) Technical feasibility test. A technical feasibility test is a developmental test typically conducted during concept 17 AR 73–1 • 1 August 2006