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.
Code decay analysis of legacy software through successive releases
1999 IEEE Aerospace Conference. Proceedings (Cat. No.99TH8403) ; 5 ; 69-81 vol.5
1999-01-01
1008828 byte
Conference paper
Electronic Resource
English
Code Decay Analysis of Legacy Software through Successive Releases
British Library Conference Proceedings | 1999
|British Library Online Contents | 2005
Implementation of Auto-Code Generation in Legacy Code for Body Control Software Applications
SAE Technical Papers | 2008
|Implementation of Auto-Code Generation in Legacy Code for Body Control Software Applications
British Library Conference Proceedings | 2008
|Software reuse through re-engineering the legacy systems
Tema Archive | 2003
|