Skip to main content

Currently Skimming:

Appendix B: Program Phases and Decision Milestones for SDCI Programs
Pages 116-122

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 116...
... is to validate the need for material development to address the requirement for a new or improved mission capability as a result of a projected deficiency or obsolescence in existing systems that cannot be addressed appropriately through continued evolution of those systems; a technological opportunity; or an opportunity to reduce operating cost. An additional purpose is to gain approval of a draft top-level ("big-R")
From page 117...
... It should also identify major risk factors that could jeopardize success and propose mitigation strategies for each major risk factor. In so doing, it should develop a proposed schedule and budget for the capability increments from the initial capability increment through to the final capability increment and anticipated life-cycle costs, and propose an allocation of the top-level requirements identified in the draft capability description to the capability increments.
From page 118...
... Based on the learning and communication with the end users that result from this concept demonstration prototyping, the planning and analysis efforts should refine the draft capability description and CONOPS, refine the business case, and refine the allocation of the top-level require ments in the draft capability description to the capability increments. It should also establish a vision for the end-state target architecture appro priate to support the full scope of intended capability and appropriate to support the full scale of the intended deployment.
From page 119...
... Based on learning in the previous capability increments and from field experience with the deployed product, all planning and analysis phases after the initial one should focus on incremental refinement of the following: • The top-level capability description and CONOPS, • The business case, • The allocation of top-level requirements from the capability description for the increment to each of the time-boxed iterations, and • Development of the initial proposed small-r requirements for the next capability increment and their initial allocation to the time-boxed iterations within the capability increment. If the capability to be developed in each increment of the IID-based program requires complex deployment processes and/or specific enduser training, the planning activities should also address the intended scope and timeline of deployment across the multiple capability increments of the program.
From page 120...
... MDA Responsibilities: Approve the overall program baseline allocation of big-R requirements across all subsequent increments and the small-r requirements allocated to the next increment. Authorize commencement of the program or next-increment System Development and Demonstration Phase and provide any guidance deemed appropriate for the conduct of that phase.
From page 121...
... If there are subsequent increments, this Milestone C decision should ideally be conducted coincident with the Milestone B decision for the subsequent increment, since many of the factors affecting the deployment decision can also materially affect the composition of the next increment. PM Responsibilities: In conjunction with operational end users, DT&E and OT&E stakeholders, security C&A stakeholders, and interoperability stakeholders that have been responsible for the integrated test and evaluation conducted throughout the increment, the PM shall assess the risk versus benefit in deploying the capability to the intended end users and make a deployment recommendation to the PMT and the MDA.
From page 122...
... This phase is shown with an indeterminate duration in Figure 3.2, since the complexities discussed above in conjunction with the Deployment Phase will, in general, result in multiple versions in use at any given point in time. Even in the simplest case, when end-user "point-and-click" automatic download and installation is the deployment approach, a predetermined interval is typically necessary to allow time for the installed base of end users to update their installations prior to terminating sup port for previously released versions, as is often the case in commercial software applications.


This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.