ACM Home Page
Please provide us with feedback. Feedback
Digital Library logoTake a look at the new version of this page: [ beta version ]. Tell us what you think.
Capture-recapture in software unit testing: a case study
Full text PdfPdf (497 KB)
Source
ESEM archive
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement table of contents
Kaiserslautern, Germany
SESSION: Testing and analysis table of contents
Pages: 32-40  
Year of Publication: 2008
ISBN:978-1-59593-971-5
Authors
Hanna Scott  Blekinge Institute of Technology, SE-37225 Ronneby, Sweden
Claes Wohlin  Blekinge Institute of Technology, SE-37225 Ronneby, Sweden
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 11,   Downloads (12 Months): 116,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1414004.1414012
What is a DOI?

ABSTRACT

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.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Anne Chao, 1998. Capture-Recapture Models, Encyclopaedia of Biostatistics, Editors: Armitage & Colton, Wiley, New York.
 
2
Harlan D. Mills, 1972. On the Statistical Validation of Computer Programs, Technical report FSC-72-6015, IBM Federal Systems Division.
3
 
4
Håkan Petersson, Thomas Thelin, Per Runeson, and Claes Wohlin, 2004, Capture-recapture in software inspections after 10 years research-theory, evaluation and application, Journal of Systems and Software 72,2 (July, 2004), pp. 249--264.
 
5
Catherine Stringfellow, Anneliese Andrews, Claes Wohlin and Håkan Petersson, Estimating the number of components with defects post-release that showed no defects in testing, Software Testing, Verification and Reliability 12,2 (2002) pp. 93--122.
 
6
Mark C. K. Yang and Anne Chao, Reliability-estimation and stopping-rules for software testing, based on repeated appearances of bugs, IEEE Transactions on Reliability 44,2 (1995), pp. 315--321.
 
7
 
8
 
9
 
10
 
11
 
12
 
13
Thomas Thelin and Per Runeson, Confidence intervals for capture-recapture estimations in software inspections, Information and Software Technology 44,12 (Sept. 2002) pp. 683--702.
 
14
15
 
16
Dimitri van Heesch, Doxygen, http://www.stack.nl/~dimitri/doxygen/ 2008-02-29.
 
17
Dokbook, http://www.docbook.org/ 2008-02-29.

Collaborative Colleagues:
Hanna Scott: colleagues
Claes Wohlin: colleagues