(a) Requirement.—The Secretary of Defense shall ensure that the initial acquisition strategy (required under section 2431a of this title) approved by the milestone decision authority and any subsequent revisions include the following:
(1) A comprehensive approach for managing and mitigating risk (including technical, cost, and schedule risk) during each of the following periods or when determined appropriate by the milestone decision authority:
An identification of the major sources of risk in each of the periods listed in paragraph (1) to improve programmatic decisionmaking and appropriately minimize and manage program concurrency.
(b) Approach to Manage and Mitigate Risks.—The comprehensive approach to manage and mitigate risk included in the acquisition strategy for purposes of subsection (a)(1) shall, at a minimum, include consideration of risk mitigation techniques such as the following:
Prototyping (including prototyping at the system, subsystem, or component level and competitive prototyping, where appropriate) and, if prototyping at either the system, subsystem, or component level is not used, an explanation of why it is not appropriate.
Modeling and simulation, the areas that modeling and simulation will assess, and identification of the need for development of any new modeling and simulation tools in order to support the comprehensive strategy.
Technology demonstrations and decision points for disciplined transition of planned technologies into programs or the selection of alternative technologies.
Alternative designs, including any designs that meet requirements but do so with reduced performance.
Phasing of program activities or related technology development efforts in order to address high-risk areas as early as feasible.
(c) Preference for Prototyping.—To the maximum extent practicable and consistent with the economical use of available financial resources, the milestone decision authority for each major defense acquisition program shall ensure that the acquisition strategy for the program provides for—
the production of competitive prototypes at the system or subsystem level before Milestone B approval; or
The term “concurrency” means, with respect to an acquisition strategy, the combination or overlap of program phases or activities.