|M.Sc Student||Harel Assaf|
|Subject||Estimating the Number of Faults Remaining in Software Code|
Document Inspected with Iterative Code
|Department||Department of Computer Science||Supervisor||Professor Eliezer Kantorowitz|
Code review is considered an efficient method for detecting faults in a software code document. The number of faults not detected by the review should be small. Current methods for estimating this number assume reviews with several inspectors, but there are many cases where it is practical to employ only two inspectors. In order to compensate for the small number of inspectors, code reviews are repeated several times. Faults that are detected during a review are corrected. The corrected code is reviewed, and so on. The product of the code review process is a nearly “bug free” software code, and a log of all faults that were found during the different code review iterations, along with their description and their severity. This research introduces the name iterative code review (ICR) for this kind of inspection, and a new estimator for the number of undetected faults in an ICR process, so the process may be stopped when a satisfactory result is estimated. This technique employs the Kantorowitz estimator for N-fold inspections, where the N teams are replaced by N reviews. In order to test the performance of the modified estimator, a software industry project was monitored for a period of three years. The experimental results suggest the applicability of the new mathematical model developed in the study, and demonstrate how a decision can be made on when to stop the iterative review process. More experiments are needed in order to fully evaluate the approach.