Difference between revisions of "Systems Engineering Plan (SEP) (glossary)"

From SEBoK
Jump to navigation Jump to search
(20 intermediate revisions by 6 users not shown)
Line 1: Line 1:
''<blockquote>A living document in which periodic updates capture the program’s status and evolving systems engineering implementation and its relationship with the overall program management effort.</blockquote>''
+
''<blockquote>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)</blockquote>
  
====Source====
+
===Source===
This definition was developed for the SEBoK version 0.5. ''Note to reviewers '': If you are aware of a more authoritative definition, please provide this information in your review.  
+
DAU 2012. "Systems Engineering Plan (SEP)." (online). Virginia, USA: ACQuipedia. Your Online Acquisition Encyclopedia. Accessed on 20 October 2019. Available at: https://www.dau.edu/acquipedia/pages/articledetails.aspx#!206.
  
 
===Discussion===
 
===Discussion===
There is currently no discussion for this term. This will be completed for SEBoK version 1.0.
+
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).
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
 +
<center>'''SEBoK v. 2.4, released 19 May 2021'''</center>

Revision as of 02:47, 20 May 2021

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 20 October 2019. Available at: https://www.dau.edu/acquipedia/pages/articledetails.aspx#!206.

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. 2.4, released 19 May 2021