Difference between revisions of "Software System (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>Hybrid between a system defined by an abstract description in some form of language or model and one in which program code is generated by a translator program that when integrated with and executed by a computer creates an emergent behavior. (Lawson 2010)</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).  
+
Lawson, H. W. 2010. ''A Journey through the Systems Landscape''. London, UK: College Publications, Kings College.
  
 
===Discussion===
 
===Discussion===

Revision as of 15:58, 18 May 2011

Hybrid between a system defined by an abstract description in some form of language or model and one in which program code is generated by a translator program that when integrated with and executed by a computer creates an emergent behavior. (Lawson 2010)

Source

Lawson, H. W. 2010. A Journey through the Systems Landscape. London, UK: College Publications, Kings College.

Discussion

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