Saving legacy with objects
- 1 September 1989
- proceedings article
- Published by Association for Computing Machinery (ACM)
- Vol. 24 (10) , 77-83
- https://doi.org/10.1145/74877.74886
Abstract
Developers of application software must often work with “legacy systems.” These are systems that have evolved over many years and are considered irreplaceable, either because it is thought that duplicating their function would be too expensive, or because they are trusted by users. Because of their age, such systems are likely to have been implemented in a conventional language with limited use of data abstraction or encapsulation. The lack of abstraction complicates adding new applications to such systems and the lack of encapsulation impedes modifying the system because applications depend on system internals. We describe our experience providing and using an object-oriented interface to a legacy system.Keywords
This publication has 4 references indexed in Scilit:
- TGMS: An object‐oriented system for programming geometrySoftware: Practice and Experience, 1989
- The active deallocation of objects in object‐oriented systemsSoftware: Practice and Experience, 1988
- Solid modeling for production designIBM Journal of Research and Development, 1987
- A Geometric Modeling System for Automated Mechanical AssemblyIBM Journal of Research and Development, 1980