Code decay analysis of legacy software through successive releases
- 1 January 1999
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- Vol. 5, 69-81 vol.5
- https://doi.org/10.1109/aero.1999.790190
Abstract
Prediction of problematic software components is an important activity today for many organizations as they manage their legacy systems and the maintenance problems they cause. This means that there is a need for methods and models to identify troublesome components. We apply a model for classification of software components as green, yellow and red according to the number of times they required corrective maintenance over successive releases. Further, we apply a principal component and box plot analysis to investigate the causes for the code decay and try to characterize the releases. The case study includes eight releases and 130 software components. The outcome indicates a large number of healthy components as well as a small set of troublesome components requiring extensive repair repeatedly. The analysis characterizes the releases and indicates that it is the relationship between components that causes many of the problems.Keywords
This publication has 22 references indexed in Scilit:
- Visualizing software systemsPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Comprehension processes during large scale maintenancePublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Software evolution observations based on product release historyPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Software change through design maintenancePublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Classification of Fault-Prone Software Modules: Prior Probabilities, Costs, and Model EvaluationEmpirical Software Engineering, 1998
- Identification of green, yellow and red legacy componentsPublished by Institute of Electrical and Electronics Engineers (IEEE) ,1998
- The effect of interface complexity on program error densityPublished by Institute of Electrical and Electronics Engineers (IEEE) ,1996
- Visual impact analysisPublished by Institute of Electrical and Electronics Engineers (IEEE) ,1996
- Experience with the accuracy of software maintenance task effort prediction modelsIEEE Transactions on Software Engineering, 1995
- A change analysis process to characterize software maintenance projectsPublished by Institute of Electrical and Electronics Engineers (IEEE) ,1994