Difference between revisions of "Disruption (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>An interruption in the functionality of a system. Disruptions may be either internal or external. Internal disruptions may be due to human error, software error, or component failure. External disruptions may be caused by hostile attacks or natural phenomena, such as earthquakes, tsunamis, or hurricanes. Disruptions may also result from loss of resources (external) or from “system” errors, that is, failures caused by the interaction of two or more components that performed as designed (internal).</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 14:29, 17 May 2011

An interruption in the functionality of a system. Disruptions may be either internal or external. Internal disruptions may be due to human error, software error, or component failure. External disruptions may be caused by hostile attacks or natural phenomena, such as earthquakes, tsunamis, or hurricanes. Disruptions may also result from loss of resources (external) or from “system” errors, that is, failures caused by the interaction of two or more components that performed as designed (internal).

Source

None cited.

Discussion

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