The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.01 - January/February (2012 vol.14)
pp: 38-43
ABSTRACT
This article defines a legacy system as an aggregate package of software and hardware solutions whose languages, standards, codes, and technologies belong to a prior generation or era of innovation. By this definition, all technology solutions will ultimately become legacy systems. So IT professionals and managers should prepare to manage legacy systems throughout their careers, and software experts and engineers should focus not only on software development but also, after deployment, on the operational phase. Further more, organizations that use software and the vendors that sell and maintain it could benefit from an intentional, formalized, and data-driven approach for making decisions about legacy systems- that is, a systematic approach for evaluating them.
INDEX TERMS
software packages, decision making, personnel, software maintenance, software maintenance, data driven approach, decision making, legacy system sustainability, software package, hardware solution, technology solutions, software development, IT professionals, IT managers, software experts, software engineers, Software engineering, Maintenance engineering, Legacy systems, Microprocessors, Computer architecture, Information technology, Cost benefit analysis, information technology, Keywords: Legacy systems
CITATION
Adenekan Dedeke, "Improving Legacy-System Sustainability: A Systematic Approach", IT Professional, vol.14, no. 1, pp. 38-43, January/February 2012, doi:10.1109/MITP.2012.10
REFERENCES
1. G. Barnett, "The Future of the Mainframe," white paper, Ovum, Oct. 2005.
2. M. Hedge and J. Wall, "Effective Application Modernization with Business Rule Management System—Web Sphere Software," IBM white paper, Oct. 2009; ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/wsw14072usen/WSW14072USEN.PDF.
3. W. Schmitt, "Overcoming the Legacy System Dilemma, Decommission Legacy Systems, for Substantial Cost Savings—Without Incurring Additional Risks," SAP Insider, Information Cycle Management—Special Report, Sept. 2009; www.sdn.sap.com/irj/scn/go/portal/prtroot/ docs/library/uuid50909045-0d6a-2c10-96a2-907a68f600b3?QuickLink=index&overridelayout=true .
4. Software Drain of Business Gain—Assessing Application Value, Relevance and Cost to Your Company, BPM Forum, 2004; http://64.55.148.251/resources/reports/pass software_drain.pdf.
5. A. Sage, Systems Management for Information Technology and Software Engineering, John Wiley & Sons, 1995.
6. T. Saaty, "Fundamentals of Decision Making and Priority Theory With the Analytic Hierarchy Process," (Analytic Hierarchy Process Series), vol. 6, 2000.
7. H. Sneed, "Planning the Reengineering of Legacy Systems," IEEE Software, vol. 12, no. 1, 1995, pp. 24–34.
8. R. Seacord, D. Plakosh, and G. Lewis, Modernizing Legacy Systems: Software Technologies, Engineering Processes, and Business Practices, Addison Wesley, 2003.
9. I. Sommerville, Software Engineering, 9th ed., Addison Wesley, 2010.
10. E. Chikofsky and J. Cross, "Reverse Engineering and Design Recovery: A Taxonomy," IEEE Software, vol. 7, no. 1, 1990, pp. 13–17.
11. W. Adolph, "Cash Cow in the Tar Pit; Re-Engineering a Legacy System," IEEE Software, May 1996, pp. 41–47.
12. R. Arnold, "Common Risks of Re-Engineering," IEEE Computer Society Reverse Engineering Newsletter, Apr. 1992, pp. 1–2.
13. J. Raelin, The Clashes of Cultures: Managers Managing Professionals, Harvard Business School Press, 1991.
27 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool