Hard System (glossary): Difference between revisions

From SEBoK Draft
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 ...')
 
No edit summary
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>System type characterized by the ability to define purpose, goals and missions that can be addressed via engineering methodologies in attempting to optimize a solution. (Checkland 1999)</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).  
Checkland, P. B. 1999.'' Systems Thinking, Systems Practice''. Chichester, UK: John Wiley & Sons Ltd.  


===Discussion===
===Discussion===

Revision as of 17:58, 17 May 2011

System type characterized by the ability to define purpose, goals and missions that can be addressed via engineering methodologies in attempting to optimize a solution. (Checkland 1999)

Source

Checkland, P. B. 1999. Systems Thinking, Systems Practice. Chichester, UK: John Wiley & Sons Ltd.

Discussion

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

Retrieved from "https://sebokwiki.org/draft/w/index.php?title=Hard_System_(glossary)&oldid=1446"