FIGURE 2-4 The B-2 systems engineering graphic showing an assessment of the application of the process. SOURCE: Contributed by committee member John Griffin.

modeling and simulation, affordability analysis, and specialty engineering disciplines (e.g., reliability, maintainability, survivability, system security, and technology maturity management).

  • There is a need to establish and nurture a collaborative user/acquirer/ industry team pre-Milestone A to perform system trade-offs and manage overall system complexity. Today, there are often significant disconnects in the hand-offs between users, acquirers, requirements developers, industry, and others. Some of the “best practices” include structured collaboration among these members.

  • One must clearly establish a complete and stable set of system-level requirements and products at Milestone A. While requirements creep is a real problem that must be addressed, some degree of requirements flexibility is also necessary as lessons involving feasibility and practicality are learned and insights are gained as technology is matured and the development subsequently proceeds. Certainly control is necessary, but not an absolute freeze. Also, planning ahead for most likely change possibilities through architectural choices should be encouraged, but deliberately managed, a concept encouraged herein. A typical program execution team has a program manager (PM)-level SE integration team (SEIT), with



The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement