Transforming a legacy system into components

4Citations
Citations of this article
7Readers
Mendeley users who have this article in their library.
Get full text

Abstract

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. © Springer-Verlag Berlin Heidelberg 2006.

Cite

CITATION STYLE

APA

Kim, H. K., & Chung, Y. K. (2006). Transforming a legacy system into components. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 3982 LNCS, pp. 198–205). Springer Verlag. https://doi.org/10.1007/11751595_22

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free