Projecting Software Defects from Analyzing Ada Designs
IEEE Transactions on Software Engineering - Special issue on software measurement principles, techniques, and environments
A Validation of Object-Oriented Design Metrics as Quality Indicators
IEEE Transactions on Software Engineering
Detection of Fault-Prone Software Modules During a Spiral Life Cycle
ICSM '96 Proceedings of the 1996 International Conference on Software Maintenance
The Impact of Costs of Misclassification on Software Quality Modeling
METRICS '97 Proceedings of the 4th International Symposium on Software Metrics
System-level partitioning with uncertainty
CODES '99 Proceedings of the seventh international workshop on Hardware/software codesign
The Confounding Effect of Class Size on the Validity of Object-Oriented Metrics
IEEE Transactions on Software Engineering
Deriving models of software fault-proneness
SEKE '02 Proceedings of the 14th international conference on Software engineering and knowledge engineering
An empirical evaluation of fault-proneness models
Proceedings of the 24th International Conference on Software Engineering
Accuracy of software quality models over multiple releases
Annals of Software Engineering
Classification of Fault-Prone Software Modules: Prior Probabilities,Costs, and Model Evaluation
Empirical Software Engineering
A Comparative Study of Ordering and Classification of Fault-ProneSoftware Modules
Empirical Software Engineering
Balancing Misclassification Rates in Classification-TreeModels of Software Quality
Empirical Software Engineering
Cost-Benefit Analysis of Software Quality Models
Software Quality Control
An Enhanced Neural Network Technique for Software Risk Analysis
IEEE Transactions on Software Engineering
Return on Investment of Software Quality Predictions
ASSET '98 Proceedings of the 1998 IEEE Workshop on Application - Specific Software Engineering and Technology
Using Code Metrics to Predict Maintenance of Legacy Programs: A Case Study
ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
Classification Tree Models of Software Quality Over Multiple Releases
ISSRE '99 Proceedings of the 10th International Symposium on Software Reliability Engineering
Information theoretic evaluation of change prediction models for large-scale software
Proceedings of the 2006 international workshop on Mining software repositories
Comparing the fault-proneness of new and modified code: an industrial case study
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
Exploring the relationship of history characteristics and defect count: an empirical study
DEFECTS '08 Proceedings of the 2008 workshop on Defects in large software systems
Quantitative analysis of faults and failures with multiple releases of softpm
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
Can developer-module networks predict failures?
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
A hybrid heuristic approach to optimize rule-based software quality estimation models
Information and Software Technology
Information and Software Technology
Predicting stability of classes in an object-oriented system
Journal of Computational Methods in Sciences and Engineering - Special Supplement Issue in Section A and B: Selected Papers from the ISCA International Conference on Software Engineering and Data Engineering, 2009
Hi-index | 4.10 |
Mission-critical systems must use reliable software. However, assuring software reliability often entails costly and time-consuming development processes. Software quality models can mitigate these costs by predicting module reliability early on, which lets developers focus improvement efforts on modules that require the most attention. Many software quality models use only product metrics such as lines of code or McCabe cyclomatic complexity. This product focus assumes that all modules have a similar process history. For systems that evolve, this assumption is not valid. Modules with similar product measurements may have different quality because of different development histories. For example, a reused module with many changes is likely to have more faults than a similar module with few changes. The authors have developed a quality model based solely on process-history variables. Their study posits that a module's history prior to integration can help predict the likelihood of fault discovery during integration and test. Such module reliability predictions can be used to focus review, integration, and testing resources on high-risk areas of a system. They report their findings in a case study involving the Joint Surveillance Target Attack Radar System, an embedded, real-time military system developed by Northrop Grumman for the US Air Force in support of the US Army.