Skip to main content

Industrial Methods for the Effective Development and Testing of Defense Systems (2012) / Chapter Skim
Currently Skimming:

7 Organizational Structures and Related Issues
Pages 59-64

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 59...
... guidelines and procedures and the role of the program manager in the acquisition process. ENFORCEMENT OF DOD DIRECTIVES AND PROCEDURES Conclusion 10: Many of the critical problems in the U.S.
Read the entire page →
From page 60...
... • Emphasis should be on an event-based strategy, rather than a schedule-based strategy, with meaningful and realistic pass/fail criteria for each stage of development. In particular, systems should not be allowed to proceed to operational testing unless that step is supported by developmental test performance that strongly antici pates that the system will pass; such a determination can be greatly aided through the conduct of a rigorous operational test readiness review.
Read the entire page →
From page 61...
... Input from all divisions -- including sales, marketing, dealers, and manufacturing plants is actively solicited -- but the final decisions are made by the program manager. Other industries, besides automotive, also use a similar concept of having a single person in charge of the entire product realization process.
Read the entire page →
From page 62...
... This approach is in stark contrast with industry, which has more stability and the right incentive structure, which includes being aggressive about finding system defects as early in system development as possible.2 The panel recognizes the challenges associated with program management and does not expect any significant changes to the present system of short-term rotations of military officers as program managers. Nevertheless, we believe that DOD should explore ways to provide more stability, and thereby accountability, to the project management process.
Read the entire page →
From page 63...
... Also, guidelines would have to be developed on how problems from earlier stages of development -- for example, that a sys tem's performance was not comprehensively tested or discovered flaws were left unaddressed -- would affect the assessment of subsequent program managers. Recommendation 5: The Under Secretary of Defense for Acquisi tion, Technology, and Logistics should provide for an independent evaluation of the progress of acquisition category I (ACAT I)
Read the entire page →

Key Terms

  • design flaws
  • realization process
  • defense science
  • dod programs
  • discover design

  • product realization
  • time span
  • entire product
  • besides automotive
  • final designs

  • initial phases
  • final responsibility
  • challenges associated
  • integration development
  • initial state

  • carefully assessed
  • responsibility lies
  • initial development
  • independent evaluation
  • responsibility covers

  • major milestones
  • product feasibility
  • final decisions
  • usually continuity
  • test readiness

  • suitability performance
  • project management
  • testing unless
  • capabilities integration
  • broader context


    • This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
    More information on Chapter Skim is available.