Navigation ... |
|
|
Scientific Writing ... |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Other Writing ... |
|
|
|
|
Reference details
| Author(s) | Year | Title | Reference | View/Download |
|---|---|---|---|---|
Les Hatton | 2005o | Predicting the total number of faults using parallel code inspections | WEB | Inspect2005.pdf |
Synopsis and invited feedback
Peer review is important and acquiring competent reviewers is becoming a major problem for the journals today so I will be very happy to include constructive comment (positive or negative) with acknowledgement. If I am not competent to judge your commentary I will try and find somebody who is.
If you would like to provide feedback just e-mail me here.
| Synopsis | Invited Feedback | Importance (/10, author rated :-) ) |
|---|---|---|
| Shows two interesting things. a) Parallel code inspections can be used to predict the total number of remaining faults in a software system (during which I rediscovered a technique which I now learn is well known in fisheries, Capture-Recapture), and b) Using 22 parallel 2 person inspection teams, it is shown that independence CANNOT be rejected. This latter result is really surprising as it would be expected that checklists would force some kind of obvious dependence. I went on from this to study it in detail on a much larger scale as shown in the links field. The effect is still there:- checklists appear to have no significant effect on defect detection quality. | None yet | 9 |
Related links
| Related papers and links |
|---|
http://www.leshatton.org/checklists_in_code_inspections.html |
Auto-generated: $Revision: 1.63 $, $Date: 2020/01/25 16:18:09 $, Copyright Les Hatton 2001-