Estimating software fault content before coding
ICSE '92 Proceedings of the 14th international conference on Software engineering
A Unified Framework for Coupling Measurement in Object-Oriented Systems
IEEE Transactions on Software Engineering
Proceedings of the Conference on The Future of Software Engineering
A Comprehensive Evaluation of Capture-Recapture Models for Estimating Software Defect Content
IEEE Transactions on Software Engineering
An Empirical Study of Experience-Based Software Defect Content Estimation Methods
ISSRE '99 Proceedings of the 10th International Symposium on Software Reliability Engineering
The Application of Capture-Recapture Log-Linear Models To Software Inspections Data
ISESE '03 Proceedings of the 2003 International Symposium on Empirical Software Engineering
A Simulation Study of the Model Evaluation Criterion MMRE
IEEE Transactions on Software Engineering
Team-Based Fault Content Estimation in the Software Inspection Process
Proceedings of the 26th International Conference on Software Engineering
A Defect Estimation Approach for Sequential Inspection Using a Modified Capture-Recapture Model
COMPSAC '05 Proceedings of the 29th Annual International Computer Software and Applications Conference - Volume 01
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2
Ranking bias in deep web size estimation using capture recapture method
Data & Knowledge Engineering
| Hi-index | 0.00 |
Quantitative failure estimates for software systems are traditionally made at end of testing using software reliability growth modeling. A persistent problem with most kinds of failure estimation methods and models is the dependency on historical data. This paper presents a method for estimating the total amount of failures possible to provoke from a unit, without historical data dependency. The method combines the results from having several developers testing the same unit with capture-recapture models to create an estimate of 'remaining' number of failures. The evaluation of the approach consists of two steps: first a pre-study where the tools and methods are tested in a large open source project, followed by an add-on to a project at a medium sized software company. The evaluation was a success. An estimate was created, and it can be used both as a quality gatekeeper for units and input to functional and system testing.