ISSTA '04 Proceedings of the 2004 ACM SIGSOFT international symposium on Software testing and analysis
Predicting the Location and Number of Faults in Large Software Systems
IEEE Transactions on Software Engineering
Looking for bugs in all the right places
Proceedings of the 2006 international symposium on Software testing and analysis
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
Journal of Systems and Software
Using Developer Information as a Factor for Fault Prediction
PROMISE '07 Proceedings of the Third International Workshop on Predictor Models in Software Engineering
Automating algorithms for the identification of fault-prone files
Proceedings of the 2007 international symposium on Software testing and analysis
Software engineering research: from cradle to grave
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Improving fault detection in modified code: a study from the telecommunication industry
Journal of Computer Science and Technology
Comparing negative binomial and recursive partitioning models for fault prediction
Proceedings of the 4th international workshop on Predictor models in software engineering
Empirical Software Engineering
Information and Software Technology
Comparing the effectiveness of several modeling methods for fault prediction
Empirical Software Engineering
What can fault prediction do for you?
TAP'08 Proceedings of the 2nd international conference on Tests and proofs
Hi-index | 0.00 |
This work is based on the idea of analyzing thebehavior all over the life-cycle of the source files having ahigh number of faults at their first release. In terms ofpredictability, our study helps to understand if files thatare faulty in their first release tend to remain faulty inlater releases, and investigates the ways to assure ahigher reliability to the most faulty programs, testingthem carefully or lowering the complexity of theirstructure. The purpose of this paper is to verifyempirically our hypothesis, through an experimentalanalysis on two different projects, and to find causesobserving the structure of the faulty files.As a conclusion, we can say that the number of faultsat the first release of source files is an early andsignificant index of its expected defect rate and reliability.