Difference between revisions of "Complexity (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>(1) The degree to which a system's design or code is difficult to understand because of numerous components or relationships among components</blockquote>
 +
 
 +
<blockquote>(2) Pertaining to any of a set of structure-based metrics that measure the attribute in (1); (3) The degree to which a system or component has a design or implementation that is difficult to understand and verify. (ISO/IEC 2009)</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).  
+
(1) and (2) ISO/IEC. 2009. "Systems and Software Engineering Vocabulary (SEVocab)" - ISO/IEC 24765. in International Organization for Standardization (ISO)/International Electronical Commission (IEC) [database online]. Geneva, Switzerland, 2009 [cited December 21 2009]. Available from http://pascal.computer.org/sev_display/index.action.
  
 
===Discussion===
 
===Discussion===

Revision as of 13:54, 17 May 2011

(1) The degree to which a system's design or code is difficult to understand because of numerous components or relationships among components

(2) Pertaining to any of a set of structure-based metrics that measure the attribute in (1); (3) The degree to which a system or component has a design or implementation that is difficult to understand and verify. (ISO/IEC 2009)

Source

(1) and (2) ISO/IEC. 2009. "Systems and Software Engineering Vocabulary (SEVocab)" - ISO/IEC 24765. in International Organization for Standardization (ISO)/International Electronical Commission (IEC) [database online]. Geneva, Switzerland, 2009 [cited December 21 2009]. Available from http://pascal.computer.org/sev_display/index.action.

Discussion

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