Difference between revisions of "Preliminary Design Review (PDR) (glossary)"

From SEBoK
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 ...')
 
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>Event conducted to verify and validate the set of system requirements, design artefacts, and justification elements; this occurs at the end of the first engineering loop when using a spiral development process.</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 19:51, 17 May 2011

Event conducted to verify and validate the set of system requirements, design artefacts, and justification elements; this occurs at the end of the first engineering loop when using a spiral development process.

Source

None cited.

Discussion

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

Retrieved from "https://sandbox.sebokwiki.org/index.php?title=Preliminary_Design_Review_(PDR)_(glossary)&oldid=1479"