Referenced Items are not available for this document.
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
- ISSN :
- 1063-6773
- Print ISBN:
- 0-7695-1905-9
- INSPEC Accession Number:
- 7840050
- Digital Object Identifier :
- 10.1109/ICSM.2003.1235456
About IEEE Xplore | Contact | Help | Terms of Use | Nondiscrimination Policy | Site Map | Privacy & Opting Out of Cookies
A not-for-profit organization, IEEE is the world's largest professional association for the advancement of technology.
© Copyright 2013 IEEE - All rights reserved. Use of this web site signifies your agreement to the terms and conditions.
