Abstract
Maintaining legacy system to meet continual changing user and business needs is difficult. However organization must consider modernizing these legacy systems to remain viable. Variety of solutions is available for legacy system modernization. Reaching a decision about how to evolve a legacy system cannot be made spontaneously; rather it requires understanding the strengths and weaknesses of each modernization technique. Over the past few years reengineering has emerged as a popular modernization technique. Decision about when to evolve a legacy system through reengineering cannot be made spontaneously; rather it should require risk assessment of legacy application from system, managerial and technical point of view. We present a decision driven risk assessment framework ReeRisk that examines system, managerial and technical domain of legacy system in accordance with requirements of target system. The result of ReeRisk framework is used to take decision about when evolution of a legacy system through reengineering is successful.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Brodie, M.L., Stonebraker, M.: Migrating Legacy Systems: Gateways, Interfaces, & the Incremental Approach. Morgan Kaufmann Publishers, Inc., San Francisco (1995)
Sommerville, I.: Software Engineering, 7th edn. Pearson Education, London (2006)
The management of software engineering, Part I: Principles of software engineering. IBM Systems Journal 19(4), 414–420, ISSN: 0018-8670, doi: 10.1147/sj.194.0414
Sneed, H.M.: Risks Involved in Reengineering Projects. In: WCRE: Proceedings of the 6th IEEE Conference on Reverse Engineering, p. 204 (1999)
Ransom, J., Somerville, I., Warren, I.: A Method for Assessing legacy systems for evolution. In: Proceedings of the Second Euromicro Conference on Software Maintenance and Reengineering (1998) ISBN: 0-8186- 8421-6, doi:10.1109/CSMR
Boehm, B.W.: Software Risk Management: Principles and Practices. IEEE Software 8(1), 32–41 (1991)
Kulik, P.: What is Software Risk Management, 1st edn. white paper KLCI, Inc. (1996)
Briden, P.: Software Re-engineering process. Tessella Support Services PLC Technical report, Issue V2.R1.M1 (2000)
Feiler, P.H.: Reengineering: An Engineering Problem. Technical Report Software Engineering Institute Carnegie Mellon university Pittsburgh Pennsylvania 15213, CMU/SEI-93-SR-5 (1993)
Russ, M.L., McGregor, J.D., Korson-McGregor, Clemson, S.C.: A software development process for small projects. IEEE Software, 96–101, ISSN : 0740-7459, doi:10.1109/52.877874
Boehm, B., Chulani, S., Verner, J., Wong, B.: Fifth Workshop on Software Quality. In: 29th International Conference ICSE 2007 Companion on Software Engineering - Companion, pp. 131–132 (2007), ISBN: 0-7695-2892-9, doi:10.1109/ICSECOMPANION.2007.38
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2011 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Rajavat, A., Tokekar, V. (2011). ReeRisk –A Decisional Risk Engineering Framework for Legacy System Rejuvenation through Reengineering. In: Das, V.V., Stephen, J., Chaba, Y. (eds) Computer Networks and Information Technologies. CNC 2011. Communications in Computer and Information Science, vol 142. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-19542-6_24
Download citation
DOI: https://doi.org/10.1007/978-3-642-19542-6_24
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-19541-9
Online ISBN: 978-3-642-19542-6
eBook Packages: Computer ScienceComputer Science (R0)