Experimentation in software engineering
IEEE Transactions on Software Engineering
NPATH: a measure of execution path complexity and its applications
Communications of the ACM
Design complexity measurement and testing
Communications of the ACM
Methodology for Validating Software Metrics
IEEE Transactions on Software Engineering
The Detection of Fault-Prone Programs
IEEE Transactions on Software Engineering
A Pattern Recognition Approach for Software Engineering Data Analysis
IEEE Transactions on Software Engineering - Special issue on software measurement principles, techniques, and environments
Predictive Modeling Techniques of Software Quality from Software Measures
IEEE Transactions on Software Engineering - Special issue on software measurement principles, techniques, and environments
IEEE Transactions on Software Engineering - Special issue on software reliability
Alternative approaches for the use of metrics to order programs by complexity
Journal of Systems and Software - Special issue of the best papers from the Oregon Workshop on Software Metrics, 1993
Experimental design and analysis in software engineering, part 5: analyzing the data
ACM SIGSOFT Software Engineering Notes
Experimental software engineering: a report on the state of the art
Proceedings of the 17th international conference on Software engineering
A Validation of Object-Oriented Design Metrics as Quality Indicators
IEEE Transactions on Software Engineering
Software metrics for reliability assessment
Handbook of software reliability engineering
Software metrics (2nd ed.): a rigorous and practical approach
Software metrics (2nd ed.): a rigorous and practical approach
Predicting Fault-Prone Software Modules in Telephone Switches
IEEE Transactions on Software Engineering
Experiences with criticality predictions in software development
ESEC '97/FSE-5 Proceedings of the 6th European SOFTWARE ENGINEERING conference held jointly with the 5th ACM SIGSOFT international symposium on Foundations of software engineering
Case-Based Reasoning: Experiences, Lessons and Future Directions
Case-Based Reasoning: Experiences, Lessons and Future Directions
Elements of Software Science (Operating and programming systems series)
Elements of Software Science (Operating and programming systems series)
Classification of Fault-Prone Software Modules: Prior Probabilities,Costs, and Model Evaluation
Empirical Software Engineering
Emerald: Software Metrics and Models on the Desktop
IEEE Software
Return on Investment of Software Quality Predictions
ASSET '98 Proceedings of the 1998 IEEE Workshop on Application - Specific Software Engineering and Technology
Detection of software modules with high debug code churn in a very large legacy system
ISSRE '96 Proceedings of the The Seventh International Symposium on Software Reliability Engineering
Predicting Fault-Prone Modules with Case-Based Reasoning
ISSRE '97 Proceedings of the Eighth International Symposium on Software Reliability Engineering
Predicting the Order of Fault-Prone Modules in Legacy Software
ISSRE '98 Proceedings of the The Ninth International Symposium on Software Reliability Engineering
Evaluating the applicability of reliability prediction models between different software
Proceedings of the International Workshop on Principles of Software Evolution
Classification and evaluation of defects in a project retrospective
Journal of Systems and Software
A defect prediction method for software versioning
Software Quality Control
Evaluating defect prediction approaches: a benchmark and an extensive comparison
Empirical Software Engineering
Hi-index | 0.00 |
Softwarequality models can predict the quality of modules early enoughfor cost-effective prevention of problems. For example, softwareproduct and process metrics can be the basis for predicting reliability.Predicting the exact number of faults is often not necessary;classification models can identify fault-prone modules. However,such models require that ’’fault-prone‘‘ be defined before modeling,usually via a threshold. This may not be practical due to uncertainlimits on the amount of reliability-improvement effort. In suchcases, predicting the rank-order of modules is more useful. A module-order model predicts the rank-orderof modules according to a quantitative quality factor, such asthe number of faults. This paper demonstrates how module-ordermodels can be used for classification, and compares them withstatistical classification models. Two case studies of full-scale industrial software systems comparednonparametric discriminant analysis with module-order models. One case studyexamined a military command, control, and communications system.The other studied a large legacy telecommunications system. Wefound that module-order models give management more flexiblereliability enhancement strategies than classification models,and in these case studies, yielded more accurate results thancorresponding discriminant models.