Difference between revisions of "Agreement (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>Mutual acknowledgement of terms and conditions under which a working relationship is conducted (ISO/IEEE 2008, 1, Section 4.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).  
+
ISO/IEEE. 2008. ''Systems and Software Engineering - Software Life Cycle Processes''. Geneva, Switzerland: International Organization for Standards (ISO)/Institute of Electrical & Electronics Engineers (IEEE) Computer Society, ISO/IEEE 12207:2008(E).  
  
 
===Discussion===
 
===Discussion===

Revision as of 01:01, 17 May 2011

Mutual acknowledgement of terms and conditions under which a working relationship is conducted (ISO/IEEE 2008, 1, Section 4.4)

Source

ISO/IEEE. 2008. Systems and Software Engineering - Software Life Cycle Processes. Geneva, Switzerland: International Organization for Standards (ISO)/Institute of Electrical & Electronics Engineers (IEEE) Computer Society, ISO/IEEE 12207:2008(E).

Discussion

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