Reconstruction of Legacy Systems for Evolutionary Change
Blum (1996) states in his book regarding the future issues of software development that, in the future, software development will have a different character. He states that: There already is enormous investment in software, and there is little likelihood that the software can ever be replaced. It would be too costly to reprogram, and few understand exactly what the current systems do. Thus, despite their imperfections, we must learn to reuse key portions of the available (legacy) systems.
Unable to display preview. Download preview PDF.
- Burd, E.L., Munro, M. and Wezeman, C. (1996a). Analysing large COBOL programs: the extraction of reusable modules. In Proceedings of the International Conference on Software Maintenance, California. IEEE Press.Google Scholar
- Burd, E.L., Munro, M. and Wezeman, C. (1996b). Extracting reusable modules from legacy code: considering issues of module granularity. In Proceedings of the 3rd Working Conference on Reverse Engineering, California. IEEE Press.Google Scholar
- Cimitile, A., De Lucia, A., Di Lucca, G.A. and Fasolino, A.R. (1997). Identifying objects in legacy systems. In International Workshop on Program Comprehension. IEEE Press.Google Scholar
- Cramer, J., Hünnekens, H., Schäfer, W. and Wolf, S. (1991). The MERLIN approach to the re-use of software components. In Dusink, E. and Hall, P.A.V. (eds), Software Re-use Utrecht 89, Ch. 6. Springer-Verlag.Google Scholar
- Girard, J.-F. and Koschke, R. (1997). Finding components in a hierarchy of modules: a step towards architectural understanding. In International Conference on Software Maintenance. IEEE Press.Google Scholar
- Lenz, M., Schmid, H.A and Wolf, P. (1987). Software reuse through building blocks IEEE Software, July.Google Scholar