ReeRisk –A Decisional Risk Engineering Framework for Legacy System Rejuvenation through Reengineering

  • Anand Rajavat
  • Vrinda Tokekar
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 142)


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.


Domain Perspective Risk cluster ReeRisk 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Brodie, M.L., Stonebraker, M.: Migrating Legacy Systems: Gateways, Interfaces, & the Incremental Approach. Morgan Kaufmann Publishers, Inc., San Francisco (1995)Google Scholar
  2. 2.
    Sommerville, I.: Software Engineering, 7th edn. Pearson Education, London (2006)zbMATHGoogle Scholar
  3. 3.
    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.0414Google Scholar
  4. 4.
    Sneed, H.M.: Risks Involved in Reengineering Projects. In: WCRE: Proceedings of the 6th IEEE Conference on Reverse Engineering, p. 204 (1999)Google Scholar
  5. 5.
    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/CSMRGoogle Scholar
  6. 6.
    Boehm, B.W.: Software Risk Management: Principles and Practices. IEEE Software 8(1), 32–41 (1991)CrossRefGoogle Scholar
  7. 7.
    Kulik, P.: What is Software Risk Management, 1st edn. white paper KLCI, Inc. (1996)Google Scholar
  8. 8.
    Briden, P.: Software Re-engineering process. Tessella Support Services PLC Technical report, Issue V2.R1.M1 (2000)Google Scholar
  9. 9.
    Feiler, P.H.: Reengineering: An Engineering Problem. Technical Report Software Engineering Institute Carnegie Mellon university Pittsburgh Pennsylvania 15213, CMU/SEI-93-SR-5 (1993)Google Scholar
  10. 10.
    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.877874Google Scholar
  11. 11.
    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.38Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Anand Rajavat
    • 1
  • Vrinda Tokekar
    • 2
  1. 1.Computer Science & EngineeringShri Vaishnav Institute of Technology and ScienceIndoreIndia
  2. 2.Information TechnologyInstitute of Engineering and Technology(DAVV)IndoreIndia

Personalised recommendations