Difference between revisions of "Component (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) an entity with discrete structure, such as an assembly or software module, within a system considered at a particular level of analysis (ISO/IEC 15026:1998 Information technology -- System and software integrity levels, 3.1)</blockquote>
 +
 
 +
<blockquote>(2) one of the parts that make up a system (IEEE 829-2008 IEEE Standard for Software and System Test Documentation, 3.1.6)</blockquote>
 +
 
 +
<blockquote>(3) set of functional services in the software, which, when implemented, represents a well-defined set of functions and is distinguishable by a unique name (ISO/IEC 29881:2008 Information technology--Software and systems engineering--FiSMA 1.1 functional size measurement method, A.4)</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).
+
  
 
===Discussion===
 
===Discussion===

Revision as of 14:10, 17 May 2011

1) an entity with discrete structure, such as an assembly or software module, within a system considered at a particular level of analysis (ISO/IEC 15026:1998 Information technology -- System and software integrity levels, 3.1)

(2) one of the parts that make up a system (IEEE 829-2008 IEEE Standard for Software and System Test Documentation, 3.1.6)

(3) set of functional services in the software, which, when implemented, represents a well-defined set of functions and is distinguishable by a unique name (ISO/IEC 29881:2008 Information technology--Software and systems engineering--FiSMA 1.1 functional size measurement method, A.4)

Source

Discussion

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