Investigating the maintenance implications of the replication of code
- 23 November 2002
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 322-329
- https://doi.org/10.1109/icsm.1997.624265
Abstract
This paper describes an investigation into the use of code replication within legacy software systems. Two cases of replication are investigated. These are replication with an individual program and replication of an entire or part of a program across a program suite. For each of the cases an example is given from code used within the commercial sector. The instances of replication are then investigated and the implication of their occurrences within the code on the maintenance process are considered. The reasons why code replication is not a form of software reuse are discussed. Finally this paper investigates whether, with reengineering, areas of high usage of code replication are potential candidates for reuseKeywords
This publication has 5 references indexed in Scilit:
- Extracting reusable modules from legacy code: considering the issues of module granularityPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Program comprehension through the identification of abstract data typesPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Analysing large COBOL programs: the extraction of reusable modulesPublished by Institute of Electrical and Electronics Engineers (IEEE) ,1996
- Software salvaging and the call dominance treeJournal of Systems and Software, 1995
- Program comprehension during software maintenance and evolutionComputer, 1995