|
| This Article | ||
| | ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
July/August 1998 (vol. 15 no. 4)
pp. 14-17
| ASCII Text | x | ||
| Norman F. Schneidewind, Christof Ebert, "Guest Editors' Introduction: Preserve or Redesign Legacy Systems?," IEEE Software, vol. 15, no. 4, pp. 14-17, July/August, 1998. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.1998.687937, author = {Norman F. Schneidewind and Christof Ebert}, title = {Guest Editors' Introduction: Preserve or Redesign Legacy Systems?}, journal ={IEEE Software}, volume = {15}, number = {4}, issn = {0740-7459}, year = {1998}, pages = {14-17}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.1998.687937}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Guest Editors' Introduction: Preserve or Redesign Legacy Systems? IS - 4 SN - 0740-7459 SP14 EP17 EPD - 14-17 A1 - Norman F. Schneidewind, A1 - Christof Ebert, PY - 1998 VL - 15 JA - IEEE Software ER - | |||
Legacy software systems represent a significant investment but often become difficult to maintain as they age. Not only does technology evolve beyond them, but business needs change and may require adding or modifying functions. This introduction addresses the question of whether to maintain or replace a legacy system, and gives an overview of the alternatives in dealing with our software legacies.
Citation:
Norman F. Schneidewind, Christof Ebert, "Guest Editors' Introduction: Preserve or Redesign Legacy Systems?," IEEE Software, vol. 15, no. 4, pp. 14-17, July-Aug. 1998, doi:10.1109/MS.1998.687937
Usage of this product signifies your acceptance of the Terms of Use.