Table 3: Models Used for the Acquisition of IT Model Description of Model Examples Challenges Used for complex, usually Military unique Can lead to long defense unique software command and waits between programs that are deployed control (C2) deliveries that can MODEL 2 only after several software systems cause product builds have been completed. Significant obsolescence Defense Subsequent software builds upgrades to the Slow delivery can Unique only proceed after successful combat systems cause customer Software completion of program found on major dissatisfaction and Intensive milestones. weapons systems push back Program such as surface combatants and tactical aircraft. Most often referred to as the DBSs Problems in Business Systems” Upgrades to some Increments may be “Defense Model. C2 system software difficult to fix in Used for software Upgrades to other concurrent development programs the weapons systems Increments. deployment of the full software Concurrent capability will occur in multiple Deliveries can be Increments as new capability difficult to manage is developed and delivered, especially in MODEL 3 nominally in 1- to 2-year complex systems. cycles. The program can Incrementally It is distinguished from 2 become Deployed by the rapid delivery of overwhelmed with Software capability through multiple frequent milestone Intensive Increments. or deployment Program Each Increment provides part decision points and of the overall required program associated capability. approval reviews. There is some concurrency of development for each Increment. Can be used for COTS software development with multiple modular capabilities. Used for developing systems Aircraft, ship or Difficult to manage where hardware and software land vehicle the timing for both development is occurring development where HW and SW simultaneously. software is a critical deliveries. The implementation of component of MODEL 5 prototypes determine overall weapon system Hybrid schedule, but software delivery. Program A development and deployment (Hardware must be tightly integrated and Dominant) coordinated with hardware development and delivery. Software builds should lead up to the full capability needed to satisfy program requirements
Table 3: Models Used for the Acquisition of IT Model Description of Model Examples Challenges MODEL 2 Defense Unique Software Intensive Program Used for complex, usually defense unique software programs that are deployed only after several software builds have been completed. Subsequent software builds only proceed after successful completion of program milestones. Military unique command and control (C2) systems Significant upgrades to the combat systems found on major weapons systems such as surface combatants and tactical aircraft. Can lead to long waits between deliveries that can cause product obsolescence Slow delivery can cause customer dissatisfaction and push back MODEL 3 Incrementally Deployed Software Intensive Program Most often referred to as the “Defense Business Systems” Model. Used for software development programs the deployment of the full capability will occur in multiple Increments as new capability is developed and delivered, nominally in 1- to 2-year cycles. It is distinguished from 2 by the rapid delivery of capability through multiple Increments. Each Increment provides part of the overall required program capability. There is some concurrency of development for each Increment. Can be used for COTS software development with multiple modular capabilities. DBSs Upgrades to some C2 system software Upgrades to weapons systems software Problems in Increments may be difficult to fix in other concurrent Increments. Concurrent Deliveries can be difficult to manage especially in complex systems. The program can become overwhelmed with frequent milestone or deployment decision points and associated approval reviews. MODEL 5 Hybrid Program A (Hardware Dominant) Used for developing systems where hardware and software development is occurring simultaneously. The implementation of prototypes determine overall schedule, but software development and deployment must be tightly integrated and coordinated with hardware development and delivery. Software builds should lead up to the full capability needed to satisfy program requirements Aircraft, ship or land vehicle development where software is a critical component of weapon system delivery. Difficult to manage the timing for both HW and SW deliveries.
Chp6_Table%203_v1.docx