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
This is a result of the elimination in the 1990s of the development planning function that had existed in the Air Force Systems Command.