Policy

The following DoD policy relates to defense acquisition, systems engineering, software engineering and system assurance.

• Department of Defense Directive 5000.1, Defense Acquisition Systems (May 12, 2003)
• Department of Defense Instruction 5000.2, Operation of the Defense Acqusition System (May 12, 2003)
• Department of Defense Directive 5200.1, DoD Information Security Program (December 13, 1996)
• Department of Defense Directive 5200.39, Security Intelligence, and Counterintelligence Support to Acquisition Program Protection (September 10, 1997)

Related SE Policy

A strong technical foundation focused on systems engineering leadership, planning, and execution is crucial to achieving technical excellence in defense acquisition. The Department of Defense systems engineering policies listed below focus on the following essentials:

• All programs shall develop a Systems Engineering Plan (SEP).
• Each PEO shall have a lead or chief systems engineer who monitors SE implementation within program portfolio.
• Every program shall institute event-driven technical reviews with entry criteria and independent subject matter expert participation
• OSD shall review program SEPs for major acquisition programs (ACAT ID and IAM).

• OUSD(AT&L) Memorandum, Policy for Systems Engineering in DoD [PDF, 718KB]
  February 20, 2004
• OUSD(AT&L) Memorandum, Implementing Systems Engineering Plans in DoD Programs–Interim Guidance [PDF, 126KB]
  March 30, 2004
• OUSD(AT&L) Memorandum, Policy Addendum for Systems Engineering [PDF, 74KB]
  October 22, 2004
• OUSD(AT&L) Memorandum, Delegation of Approval Authority for Systems Engineering Plans [PDF, 16KB]
  November 21, 2007