Systems Engineering Plan (SEP) (glossary): Difference between revisions

From SEBoK Draft
Jump to navigation Jump to search
(Created page with '''<blockquote>A comprehensive, integrated plan that identifies the acquisition approach and describes the business, technical, and support strategies that management will follow ...')
 
No edit summary
Line 1: Line 1:
''<blockquote>A comprehensive, integrated plan that identifies the acquisition approach and describes the business, technical, and support strategies that management will follow to manage program risks and meet program objectives. The Acquisition Strategy should define the relationship between the acquisition phases and work efforts, and key program events such as decision points, reviews, contract awards, test activities, production lot/delivery quantities, and operational deployment objectives. (DAU February 19, 2010)</blockquote>''
''<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>''


====Source====
====Source====
DAU. February 19, 2010. ''Defense Acquisition Guidebook (DAG)''. Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/U.S. Department of Defense (DoD).  
None cited.


===Discussion===
===Discussion===

Revision as of 01:08, 20 May 2011

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.

Source

None cited.

Discussion

Discussion as to why this is the "consensus" definition for the SEBoK.

Retrieved from "https://sebokwiki.org/draft/w/index.php?title=Systems_Engineering_Plan_(SEP)_(glossary)&oldid=1590"