Difference between revisions of "Hierarchy (glossary)"

From SEBoK
Jump to: navigation, 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>An abstract view of a defined system that is developed to meet some need. The system results from an analysis that decomposes a system into constituent elements at two or more levels.</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 18:01, 17 May 2011

An abstract view of a defined system that is developed to meet some need. The system results from an analysis that decomposes a system into constituent elements at two or more levels.

Source

None cited.

Discussion

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