National Academies Press: OpenBook
« Previous: 4 Systems Engineering Functions and Guidelines
Suggested Citation:"Appendixes." National Research Council. 2008. Pre-Milestone A and Early-Phase Systems Engineering: A Retrospective Review and Benefits for Future Air Force Systems Acquisition. Washington, DC: The National Academies Press. doi: 10.17226/12065.
×
Page 109
Suggested Citation:"Appendixes." National Research Council. 2008. Pre-Milestone A and Early-Phase Systems Engineering: A Retrospective Review and Benefits for Future Air Force Systems Acquisition. Washington, DC: The National Academies Press. doi: 10.17226/12065.
×
Page 110

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Appendixes

Next: Appendix A: Biographical Sketches of Committee Members »
Pre-Milestone A and Early-Phase Systems Engineering: A Retrospective Review and Benefits for Future Air Force Systems Acquisition Get This Book
×
Buy Paperback | $49.00 Buy Ebook | $39.99
MyNAP members save 10% online.
Login or Register to save!
Download Free PDF

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.

  1. ×

    Welcome to OpenBook!

    You're looking at OpenBook, NAP.edu's online reading room since 1999. Based on feedback from you, our users, we've made some improvements that make it easier than ever to read thousands of publications on our website.

    Do you want to take a quick tour of the OpenBook's features?

    No Thanks Take a Tour »
  2. ×

    Show this book's table of contents, where you can jump to any chapter by name.

    « Back Next »
  3. ×

    ...or use these buttons to go back to the previous chapter or skip to the next one.

    « Back Next »
  4. ×

    Jump up to the previous page or down to the next one. Also, you can type in a page number and press Enter to go directly to that page in the book.

    « Back Next »
  5. ×

    To search the entire text of this book, type in your search term here and press Enter.

    « Back Next »
  6. ×

    Share a link to this book page on your preferred social network or via email.

    « Back Next »
  7. ×

    View our suggested citation for this chapter.

    « Back Next »
  8. ×

    Ready to take your reading offline? Click here to buy this book in print or download it as a free PDF, if available.

    « Back Next »
Stay Connected!