By Topic

Re-using software architecture in legacy transformation projects

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Terekhov, A.A. ; St. Petersburg State Univ., Russia

Summary form only given, as follows. Software engineers sometimes have to take part in the legacy transformation projects, which are characterized by the complete absence of automated migration tools. In such cases, specialists usually aim at reproducing the original system using the new technologies, without adding any new features. It is common knowledge that it makes sense to keep the functionality as close to the original as possible, because in this case on could use the legacy system as an executable set of requirements. We argue that another, less obvious advantage of "replicating" the old system is re-use of architectural decisions that built in the original legacy system and usually represent an invaluable treasure, because they reflect an implemented understanding of the application domain.

Published in:

Software Maintenance, 2003. ICSM 2003. Proceedings. International Conference on

Date of Conference:

22-26 Sept. 2003