Software metrics model for integrating quality control and prediction

A model is developed that is used to validate and apply metrics for quality control and quality prediction, with the objective of using metrics as early indicators of software quality problems. Metrics and quality factor data from the Space Shuttle flight software are used as an example. Our approach is to integrate quality control and prediction in a single model and to validate metrics with respect to a quality factor. Boolean discriminant functions (BDFs) were developed for use in the quality control and quality prediction process. BDFs provide good accuracy for classifying low quality software because they include additional information for discriminating quality: critical values. Critical values are threshold values of metrics that are used to either accept or reject modules when the modules are inspected during the quality control process. A series of nonparametric statistical methods is also used in the method presented. It is important to perform a marginal analysis when making a decision about how many metrics to use in the quality control and prediction process. We found that certain metrics are dominant in their effects on classifying quality and that additional metrics are not needed to accurately classify quality. This effect is called dominance. Related to the property of dominance is the property of concordance, which is the degree to which a set of metrics produces the same result in classifying software quality. A high value of concordance implies that additional metrics will not make a significant contribution to accurately classifying quality; hence, these metrics are redundant.

[1]  George E. Stark,et al.  Measurements for managing software maintenance , 1996, 1996 Proceedings of International Conference on Software Maintenance.

[2]  Taghi M. Khoshgoftaar,et al.  Early Quality Prediction: A Case Study in Telecommunications , 1996, IEEE Softw..

[3]  Norman F. Schneidewind,et al.  Validating metrics for ensuring Space Shuttle flight software quality , 1994, Computer.

[4]  Norman F. Schneidewind,et al.  Methodology For Validating Software Metrics , 1992, IEEE Trans. Software Eng..

[5]  George E. Stark,et al.  Using metrics in management decision making , 1994, Computer.

[6]  W. J. Conover,et al.  Practical Nonparametric Statistics , 1972 .

[7]  P. Oman,et al.  Maintainability measurements on industrial source code maintenance activities , 1995, Proceedings of International Conference on Software Maintenance.

[8]  Christof Ebert,et al.  Evaluation and application of complexity-based criticality models , 1996, Proceedings of the 3rd International Software Metrics Symposium.

[9]  Taghi M. Khoshgoftaar,et al.  Detection of fault-prone software modules during a spiral life cycle , 1996, 1996 Proceedings of International Conference on Software Maintenance.

[10]  Norman F. Schneidewind Software metrics validation: Space Shuttle flight software example , 1995, Ann. Softw. Eng..

[11]  Niclas Ohlsson,et al.  Predicting Fault-Prone Software Modules in Telephone Switches , 1996, IEEE Trans. Software Eng..

[12]  Sallie M. Henry,et al.  Improving software maintenance at Martin Marietta , 1994, IEEE Software.

[13]  Adam A. Porter,et al.  Empirically guided software development using metric-based classification trees , 1990, IEEE Software.

[14]  Thomas M. Pigoski,et al.  Software maintenance metrics: a case study , 1994, Proceedings 1994 International Conference on Software Maintenance.

[15]  Taghi M. Khoshgoftaar,et al.  The impact of software enhancement on software reliability , 1995 .

[16]  John C. Munson,et al.  Measuring software evolution , 1996, Proceedings of the 3rd International Software Metrics Symposium.