Transforming a Legacy System into Components

  • Haeng-Kon Kim
  • Youn-Ky Chung
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3982)


Most legacy systems are being pressured to continuously respond to changing requirements, but it is impossible almost to cope with these requests effectively. Because many legacy systems have suffered from lack of standardization and openness, difficulty of change, and absence of distributed architecture. Especially, according as legacy system has been deteriorating from an architectural point of view over the years, we must continually maintain these legacy systems at high cost for applying new technologies and extending their business requirements. For the purposes of transforming a legacy system into component system, we need systematic methodologies and concrete guidelines. Through these, we can share information at different levels of abstraction ranging from code to software architecture, and construct the component system with better component-based architecture.

To achieve these goals, we have built upon the L2CBD (Legacy to Component Based Development) methodology providing reengineering process including concrete procedures, product-works, guidelines and considerations. We can transform legacy systems into new component system with improved software architecture by adapting L2CBD.


Legacy System Software Architecture Target System Business Requirement Architectural Information 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Neumann, D.M.: Evolution Process for Legacy System Transformation. In: IEEE Technical Applications Conference, Washington, November 1996, pp. 57–62 (1996)Google Scholar
  2. 2.
    Weiderman, N., Smith, D., Tilley, S.: Approaches to Legacy System Evolution, CMU/SEI-97-TR-014 (1997)Google Scholar
  3. 3.
    Ulrich, W.: Legacy Systems: Transformation Strategies. Prentice Hall, Englewood Cliffs (2002)Google Scholar
  4. 4.
    SEI Reengineering Center Perspectives on Legacy System Reengineering (1995)Google Scholar
  5. 5.
    Kazman, R., Woods, S.G., Carriere, S.J.: Requirements for Integrating Software Architecture and Reengineering Models: CORUM II. In: Fifth Working Conference on Reverse Engineering, Honolulu, Hawaii, October 1998, pp. 154–163 (1998)Google Scholar
  6. 6.
    Abowd, G., Goel, A., Jerding, D.F., McCracken, M., Moore, M., Murdock, J.W., Potts, C., Rugaber, S., Wills, L.: MORALE. Mission ORiented Architectural Legacy Evolution. In: International Conference on Software Maintenance, Bari, Italy, October 1997, pp. 150–159 (1997)Google Scholar
  7. 7.
    Seemann, J., von Gudenberg, J.W.: Pattern-Based Design Recovery of Java Software. Communications of the ACM 38(10), 65–74 (1995)CrossRefGoogle Scholar
  8. 8.
    Cha, J.-E., et al.: Reengineering Process for Componentization of Legacy System. Journal of the Korea Society of System Integration 2(1), 111–122 (2003)Google Scholar
  9. 9.
    Cha, J.-E., et al.: Establishment of Strategies and Processes for Reengineering of Legacy System. In: Proceedings of the 20th KIPS Fall Conference, November 2003, vol. 10(2) (2003)Google Scholar
  10. 10.
    Cha, J.-E., et al.: Definition of Metamodel for Reengineering Methodology of Legacy System. In: Proceedings of the 5th KCSE Conference, February 2003, vol. 5(1) (2003)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Haeng-Kon Kim
    • 1
  • Youn-Ky Chung
    • 2
  1. 1.Department of Computer Information & Communication EngineeringCatholic University of DaeguSouth Korea
  2. 2.Department of Computer EngineeringKyung Il UniversityKyungsan, DaeguKorea

Personalised recommendations