Database design: composing fully normalized tables from a rigorous dependency diagram
Communications of the ACM
Migrating legacy systems: gateways, interfaces & the incremental approach
Migrating legacy systems: gateways, interfaces & the incremental approach
Reverse engineering of legacy systems: a path toward success
Proceedings of the 17th international conference on Software engineering
Integrating legacy systems with modern corporate applications
Communications of the ACM
Legacy object modeling speeds software integration
Communications of the ACM
Human-Computer Interaction
Reverse Engineering and Design Recovery: A Taxonomy
IEEE Software
Planning the Reengineering of Legacy Systems
IEEE Software
Legacy Information Systems: Issues and Directions
IEEE Software
Legacy Integration-Changing Perspectives
IEEE Software
A Methodology for Migration of Legacy Applications to Distributed Object Management
EDOC '97 Proceedings of the 1st International Conference on Enterprise Distributed Object Computing
Encapsulating legacy software for use in client/server systems
WCRE '96 Proceedings of the 3rd Working Conference on Reverse Engineering (WCRE '96)
Risks Involved in Reengineering Projects
WCRE '99 Proceedings of the Sixth Working Conference on Reverse Engineering
Method and Process for Iterative Reengineering of Data in a Legacy System
WCRE '00 Proceedings of the Seventh Working Conference on Reverse Engineering (WCRE'00)
The Butterfly Methodology: A Gateway-free Approach for Migrating Legacy Information Systems
ICECCS '97 Proceedings of the Third IEEE International Conference on Engineering of Complex Computer Systems
IEEE Software
Iterative Reengineering of Legacy Systems
IEEE Transactions on Software Engineering
| Hi-index | 0.00 |
This paper describes a process of gradual reengineering of the procedural components of a legacy system. The process is integrated and completed by the data reengineering process analyzed in a previous paper by the same authors. The proposed method enables the legacy system to be gradually emptied into the reengineered system, without needing to either duplicate the legacy system or freeze it. The process consists of evolving the legacy system components toward firstly a restored system and then toward the reengineered system. Meanwhile, the legacy system can coexist with both the restored and the reengineered parts. By the end of the process, a single system will be in existence: the reengineered one. The method has been applied to reengineer a real system and demonstrated its ability to: support gradual reengineering, maintain the system at work during the process, minimize the need to freeze maintenance requests, renew the operative environment of the reengineered system with respect to the legacy system and, finally, eliminate all the system's aging symptoms.