Using software maintainability models to track code health
- 1 January 1994
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 154-160
- https://doi.org/10.1109/icsm.1994.336779
Abstract
Useful software usually changes over time. As code changes-for what ever reason-maintenance engineers most often attempt to keep the quality of it from degrading. But without means of measuring the quality or maintainability of the code, their efforts are dependent upon their expert knowledge to decide if the code is in "good" shape or if it needs reengineering. This paper describes mechanisms for automated software maintainability assessment and applies those techniques to industrial software systems. The results demonstrate how a metrics driven maintenance process can be used to prevent code degradation.<>Keywords
This publication has 10 references indexed in Scilit:
- Metrics for assessing a software system's maintainabilityPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2003
- Constructing and testing software maintainability assessment modelsPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Insights on improving the maintenance process through software measurementPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Using metrics to evaluate software system maintainabilityComputer, 1994
- Construction and testing of polynomials predicting software maintainabilityJournal of Systems and Software, 1994
- Real-time software metricsJournal of Systems and Software, 1994
- The detection of fault-prone programsIEEE Transactions on Software Engineering, 1992
- Automatic assessment aids for Pascal programsACM SIGPLAN Notices, 1982
- Programs, life cycles, and laws of software evolutionProceedings of the IEEE, 1980
- A model of large program developmentIBM Systems Journal, 1976