Department of Defense INSTRUCTION
x9tnk
x9tnk
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
DoDI 5000.02, January 7, 2015<br />
(d) Model 3: Incrementally Deployed S<strong>of</strong>tware Intensive Program. Figure 5 is a<br />
model that has been adopted for many <strong>Defense</strong> Business Systems. It also applies to upgrades to<br />
some command and control systems or weapons systems s<strong>of</strong>tware where deployment <strong>of</strong> the full<br />
capability will occur in multiple increments as new capability is developed and delivered,<br />
nominally in 1- to 2-year cycles. The period <strong>of</strong> each increment should not be arbitrarily<br />
constrained. The length <strong>of</strong> each increment and the number <strong>of</strong> deployable increments should be<br />
tailored and based on the logical progression <strong>of</strong> development and deployment for use in the field<br />
for the specific product being acquired.<br />
Figure 5. Model 3: Incrementally Deployed S<strong>of</strong>tware Intensive Program<br />
Materiel<br />
Development<br />
Decision<br />
CDD<br />
Validation<br />
A<br />
Development<br />
RFP<br />
Release<br />
Decision<br />
B<br />
Limited<br />
Deployment<br />
Decisions<br />
IOC<br />
FDD<br />
FD<br />
Materiel<br />
Solution<br />
Analysis<br />
Risk<br />
Reduction<br />
Build<br />
Build 0<br />
Risk<br />
Reduction<br />
Increment 2<br />
Build 1.1<br />
Build 1.2<br />
. . .<br />
Build 1.n<br />
OT&E<br />
Development &<br />
Deployment<br />
Development RFP<br />
Release Decision<br />
B<br />
Build 2.1<br />
Limited<br />
Deployment<br />
Decisions<br />
Sustainment<br />
Operations &<br />
Support<br />
IOC<br />
FDD<br />
FD<br />
Risk<br />
Reduction<br />
Build 2.2 . . . Build 2.n<br />
OT&E<br />
Development &<br />
Deployment<br />
Sustainment<br />
Operations &<br />
Support<br />
Development RFP<br />
Release Decision<br />
Limited<br />
Deployment<br />
Decisions<br />
IOC<br />
FDD<br />
FD<br />
Legend<br />
Increment n<br />
B<br />
Build n.1<br />
= Milestone Decision<br />
= Decision Point<br />
Risk<br />
Reduction<br />
Build n.2 . . . Build n.n<br />
OT&E<br />
Development &<br />
Deployment<br />
Sustainment Disposal<br />
Operations &<br />
Support<br />
1. This model is distinguished from the previous model by the rapid delivery <strong>of</strong><br />
capability through multiple acquisition increments, each <strong>of</strong> which provides part <strong>of</strong> the overall<br />
required program capability. Each increment may have several limited deployments; each<br />
deployment will result from a specific build and provide the user with a mature and tested subelement<br />
<strong>of</strong> the overall incremental capability. Several builds and deployments will typically be<br />
necessary to satisfy approved requirements for an increment <strong>of</strong> capability. The identification and<br />
development <strong>of</strong> technical solutions necessary for follow-on capability increments have some<br />
Change 2, 02/02/2017 13
Change language