. "Summary." Pre-Milestone A and Early-Phase Systems Engineering: A Retrospective Review and Benefits for Future Air Force Acquisition. Washington, DC: The National Academies Press, 2008.
The following HTML text is provided to enhance online
readability. Many aspects of typography translate only awkwardly to HTML.
Please use the page image
as the authoritative form to ensure accuracy.
Pre-Milestone A and Early-Phase Systems Engineering: A Retrospective Review and Benefits for Future Air Force Systems Acquisition
tion life cycle in addressing the root causes of program failure, especially during the pre-Milestone A and early phases of a program. Currently, few formal SE processes are applied to Air Force development programs before the Milestone A review.1
The committee has devoted much time and space in this report to trying to define a minimum set of systems engineering processes. Chapter 4, in particular, is devoted to this effort. The most important of these processes are summarized in the checklist in Box S-1 below in this summary (Box 4-1 in Chapter 4). A few of the things that need to be taken care of before Milestone A and just after it are the following: the consideration of alternative concepts (solutions) up front; the setting of clear, comprehensive key performance parameters (KPPs) and system requirements; and early attention to interfaces and interface complexity, to the concept of operations (CONOPS), and to the system verification approach. It is these early-stage processes that are covered in this report. The importance of
1
This is a result of the elimination in the 1990s of the development planning function that had existed in the Air Force Systems Command.