Reverse Engineering (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>A process of documenting the functions and behaviors of a device or system by analysis and test.</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 15:17, 18 May 2011

A process of documenting the functions and behaviors of a device or system by analysis and test.

Source

None cited.

Discussion

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

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