Difference between revisions of "Legacy 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>A system that has been in operation for a long time, and whose functions are too essential to be disrupted by upgrading or integration with another system. (Software Engineering Institute)</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).  
+
Unidentified SEI source.
  
 
===Discussion===
 
===Discussion===

Revision as of 18:41, 17 May 2011

A system that has been in operation for a long time, and whose functions are too essential to be disrupted by upgrading or integration with another system. (Software Engineering Institute)

Source

Unidentified SEI source.

Discussion

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

Retrieved from "https://sandbox.sebokwiki.org/index.php?title=Legacy_System_(glossary)&oldid=1459"