Difference between revisions of "Concept of Operations (ConOps) (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 purpose, mission and main objectives of the potential future system (solution). The definition of these elements is the starting point to elicit the set of stakeholders' requirements.  </blockquote>
 +
 
 +
<blockquote>(2) A general way or approach or strategy of operation/utilization. It represents the basic option of how will be used the system in operation.</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:12, 17 May 2011

(1) The purpose, mission and main objectives of the potential future system (solution). The definition of these elements is the starting point to elicit the set of stakeholders' requirements.

(2) A general way or approach or strategy of operation/utilization. It represents the basic option of how will be used the system in operation.

Source

None cited.

Discussion

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