Systems Engineering Plan (SEP) (glossary)

From SEBoK
Jump to: navigation, search
A systems engineering plan (SEP) is a "living" document that captures a program's current and evolving systems engineering strategy and its relationship with the overall program management effort. The SEP purpose is to guide all technical aspects of the program. It should be established early in the Materiel Solution Analysis phase and updated continually. (DAU 2012)

Source

DAU 2012. "Systems Engineering Plan (SEP)." (online). Virginia, USA: ACQuipedia. Your Online Acquisition Encyclopedia. Accessed on 11 September 2012. Available at: https://acc.dau.mil/ILC_SEP.

Discussion

In many contexts, the Systems Engineering Plan (SEP) and Systems Engineering Management Plan (SEMP) are used interchangeably, to refer to the highest level technical plan. However, in the context of the U.S. Department of Defense the context, intent, and content of these documents are quite different:

  • The SEP is a high-level plan that is made before the system acquisition and development begins. It is written by the government customer.
  • The SEMP is the specific development plan written by the developer (or contractor).


SEBoK v. 1.7 released 27 October 2016

SEBoK Discussion

Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.

If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.

blog comments powered by Disqus