Skip to main content

Statistical Methods for Testing and Evaluating Defense Systems Interim Report (1995) / Chapter Skim
Currently Skimming:

Appendix A: The Organizational Structure of Defense Acquistion
Pages 49-54

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 49...
... In light of this analysis or assessment, the relevant service, or possibly a unified or specified command, prepares a Mission Needs Statement. This is a conceptual document that is supposed to identify the broadly stated operational need and not a specific solution to counter the perceived threat.
Read the entire page →
From page 50...
... The purpose of this phase 0 in the acquisition process is to determine the most promising solutions to meet the broadly stated mission need. At milestone I, when a concept is approved by the undersecretary, and the Deputy Secretary of Defense agrees that it warrants funding in the DoD programming and budget process, the new acquisition program is formally begun, the relevant service establishes a program office, and a program manager is assigned.
Read the entire page →
From page 51...
... It is prepared by the program office, with input from system testers in both developmental and operational testing, service representatives, and other technical experts. (In the Army, those in charge of requirements assist the program manager in preparing the operational testing portion of the Test and Evaluation Master Plan while in the Air Force and Navy, those in charge of requirements do not formally participate in writing the plan.)
Read the entire page →
From page 52...
... . Moreover, DoD Instruction 5000.2, "Defense Acquisition Management Policies and Procedures," specifies that, "when possible, developmental testing should support and provide data for operational assessment prior to the beginning of formal initial operational test and evaluation by the operational test activity." Ideally, developmental testing is conducted prior to final operational testing, and the system is required to pass an operational test readiness review which is certified by the program executive officer, the program manager's direct supervisor.
Read the entire page →
From page 53...
... In addition, each of the services has its own agency to interpret the test results with input from the program manager. The reports from these organizations are sent to the Defense Acquisition Board for its milestone HI consideration after review by the service acquisition board (e.g., the Army Acquisition Review Board for the Army)
Read the entire page →
From page 54...
... . Thus, test results indicating that a system is in need of further development or fixes before the program proceeds may adversely affect the career of the program manager, even if such results are in no way tied to that individual's performance.
Read the entire page →

Key Terms

  • operational test
  • acquisition program
  • operational requirements
  • master plan
  • defense acquisition

  • requirements document
  • evaluation master
  • acquisition board
  • program baseline
  • acquisition process

  • milestone decision
  • acquisition programs
  • manufacturing development
  • formally begun
  • decision authority

  • initial operational
  • developmental testing
  • validation phase
  • milestone iii
  • relevant service

  • decision authorities
  • critical operational
  • operational testers
  • parameters specified
  • development phase

  • testing community
  • acquisition strategy
  • acquisition decision
  • operational issues
  • initial acquisition


    • 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.