This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Restoring a Legacy: Lessons Learned
July/August 1998 (vol. 15 no. 4)
pp. 28-33
ASCII Text
x 
 
Spencer Rugaber, Jim White, "Restoring a Legacy: Lessons Learned," IEEE Software, vol. 15, no. 4, pp. 28-33, July/August, 1998.
 
 
BibTex
x
 
@article{ 10.1109/52.687941,
author = {Spencer Rugaber and Jim White},
title = {Restoring a Legacy: Lessons Learned},
journal ={IEEE Software},
volume = {15},
number = {4},
issn = {0740-7459},
year = {1998},
pages = {28-33},
doi = {http://doi.ieeecomputersociety.org/10.1109/52.687941},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Restoring a Legacy: Lessons Learned
IS - 4
SN - 0740-7459
SP28
EP33
EPD - 28-33
A1 - Spencer Rugaber,
A1 - Jim White,
PY - 1998
VL - 15
JA - IEEE Software
ER -
 
Rebuilding a legacy system has some parallels to the restoration of a work of art. The authors draw upon this comparison to illustrate the challenges they faced in redesigning a telephony system. The restoration involved far more than updating the code?the development team also had to understand the existing architecture, add new functionality, and develop a long-term hardware migration plan. The technical and managerial lessons learned should prove valuable to those involved in similar projects.
Citation:
Spencer Rugaber, Jim White, "Restoring a Legacy: Lessons Learned," IEEE Software, vol. 15, no. 4, pp. 28-33, July-Aug. 1998, doi:10.1109/52.687941
Usage of this product signifies your acceptance of the Terms of Use.