Identification of green, yellow and red legacy components
- 1 January 1998
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 10636773,p. 6-15
- https://doi.org/10.1109/icsm.1998.738484
Abstract
Software systems are often getting older than expected, and it is a challenge to try to make sure that they grow old gracefully. This implies that methods are needed to ensure that system components are possible to maintain. In this paper, the need to investigate, classify and study software components is emphasized. A classification method is proposed. It is based on classifying the software components into green, yellow and red components. The classification scheme is complemented with a discussion of suitable models to identify problematic components. The scheme and the models are illustrated in a minor case study to highlight the opportunities. The long term objective of the work is to define methods, models and metrics which are suitable to use in order to identify software components which have to be taken care of through either tailored processes (e.g. additional focus on verification and validation) or reengineering. The case study indicates that the long term objective is realistic and worthwhile.Keywords
This publication has 9 references indexed in Scilit:
- Detection of software modules with high debug code churn in a very large legacy systemPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Understanding and predicting the process of software maintenance releasesPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Software agingPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Maintainability measurements on industrial source code maintenance activitiesPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Detection of fault-prone program modules in a very large telecommunications systemPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Predicting fault-prone software modules in telephone switchesIEEE Transactions on Software Engineering, 1996
- Detection of fault-prone software modules during a spiral life cyclePublished by Institute of Electrical and Electronics Engineers (IEEE) ,1996
- The non-homogeneous maintenance periods: a case study of software modificationsPublished by Institute of Electrical and Electronics Engineers (IEEE) ,1996
- A Complexity MeasureIEEE Transactions on Software Engineering, 1976