The ability of U.S. military forces to field new weapons systems quickly and to contain their cost growth has declined significantly over the past few decades. There are many causes including increased complexity, funding instability, bureaucracy, and more diverse user demands, but a view that is gaining more acceptance is that better systems engineering (SE) could help shorten development time. To investigate this assertion in more detail, the US Air Force asked the NRC to examine the role that SE can play during the acquisition life cycle to address root causes of program failure especially during pre-milestone A and early program phases. This book presents an assessment of the relationship between SE and program outcome; an examination of the SE workforce; and an analysis of SE functions and guidelines. The latter includes a definition of the minimum set of SE processes that need to be accounted for during project development.Table of Contents


Front Matter
Summary
1 Introduction and Overview
2 Relationship Between Systems Engineering and Program Outcome
3 Systems Engineering Workforce
4 Systems Engineering Functions and Guidelines
Appendixes
Appendix A: Biographical Sketches of Committee Members
Appendix B: Meetings and Speakers
Appendix C: What Is Systems Engineering?