Views
1 year ago

Department of Defense INSTRUCTION

x9tnk

DoDI 5000.02, January 7,

DoDI 5000.02, January 7, 2015 (c) Model 2: Defense Unique Software Intensive Program. Figure 4 is a model of a program that is dominated by the need to develop a complex, usually defense unique, software program that will not be fully deployed until several software builds have been completed. The central feature of this model is the planned software builds – a series of testable, integrated subsets of the overall capability – which together with clearly defined decision criteria, ensure adequate progress is being made before fully committing to subsequent builds. 1. Examples of this type of product include military unique command and control systems and significant upgrades to the combat systems found on major weapons systems such as surface combatants and tactical aircraft. 2. Several software builds are typically necessary to achieve a deployable capability. Each build has allocated requirements, resources, and scheduled testing to align dependencies with subsequent builds and to produce testable functionality to ensure that progress is being achieved. The build sequencing should be logically structured to flow the workforce from effort to effort smoothly and efficiently, while reducing overall cost and schedule risk for the program. Figure 4. Model 2: Defense Unique Software Intensive Program Materiel Development Decision CDD Validation Development RFP Release Decision Full Deployment Decision (FDD) IOC Full Deployment (FD) A B C Materiel Solution Analysis Build 1.1 Risk Build 1.2 Reduction Build 0.1 Build 1.3 Build 1.4 Technology Maturation & Risk Reduction Build 1.5 Engineering & Manufacturing Development Limited Deployment Integration Build 2.1* OT&E Production & Deployment Sustainment Disposal Operations & Support Legend: = Milestone Decision = Decision Point * The actual number and type of builds during the program will depend on system type. Change 2, 02/02/2017 12

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

Joint Pub 6-02 - United States Department of Defense
joint program management handbook - Defense Acquisition University
OVERVIEW W - Office of the Under Secretary of Defense (Comptroller)
Department of Defense (DoD) Information Enterprise Strategic Plan
Quadrennial Defense Review (QDR) - United States Department of ...
Developing Operational Requirements - U.S. Department of ...
department of defense more disciplined use of resources
Department of Defense Nonlethal Weapons and Equipment Review
MITRE-Defense-Agile-Acquisition-Guide
USAF ILA Handbook - ACC Practice Center - Defense Acquisition ...
DEFENSE ACQUISITION GUIDEBOOK - AcqNotes.com
Navy Cyber Power 2020 - Defense Innovation Marketplace
Download PDF - Department of Navy Chief Information Officer - U.S. ...
JP 4-02 Health Service Support - DMRTI - Defense Medical ...
Joint Service Chemical and Biological Defense Program FY00-02 ...
DHS - S&T Chemical and Biological Defense Programs - Sandia ...
department of defense agency financial report fiscal year 2012
department of defense agency financial report fiscal year 2012
COL Mike Zarbo - PEO STRI - U.S. Army
Operating instructions
Volume 5, Number 1 - Space and Missile Defense Command - U.S. ...
JP 3-01 Countering Air and Missile Threats - Defense Innovation ...