Anywhere, Anytime Code Inspections: Using the Web to Remove Inspection Bottlenecks in Large-Scale Software Development.
| dc.contributor.author | Perpich,, James | en_US |
| dc.contributor.author | Perry, Dewayne E. | en_US |
| dc.contributor.author | Porter, Adam A. | en_US |
| dc.contributor.author | Votta, Lawrence G. | en_US |
| dc.contributor.author | Wade, Michael W. | en_US |
| dc.date.accessioned | 2004-05-31T22:44:41Z | |
| dc.date.available | 2004-05-31T22:44:41Z | |
| dc.date.created | 1997-03 | en_US |
| dc.date.issued | 1998-10-15 | en_US |
| dc.description.abstract | The dissemination of critical information and the synchronization of coordinated activities are critical problems in geographically separated, large-scale, software development. While these problems are not insurmountable, their solutions have varying trade-offs in terms of time, cost and effectiveness. Out previous studies have shown that the inspection interval is typically lengthened because of schedule conflicts among inspectors which delay the (usually) required inspection collection meeting. We present and justify a solution using an intranet web that is both timely in its dissemination of information and effective in its coordination of distributed inspectors. First, exploiting a naturally occurring experiment (reported here), we conclude that the asynchronous collection of inspection results is at least as effective as the synchronous collection of those results. Second, exploiting the information dissemination qualities and the on-demand nature of information retrieval of the web, and the platform independence of browsers, e build an inexpensive tool that integrates seamlessly into the current development process. By seamless we man an identical paper flow that results in an almost identical inspection process. The acceptance of the inspection tool has been excellent. The cost savings just from the reduction in paper work and the time savings from the reduction in distribution interval of the inspection package (sometimes involving international mailings) have been substantial. These savings together with the seamless integration into the existing environment are the major factors for this acceptance. From our viewpoint as experimentalists, the acceptance came too readily. Therefor we lost our opportunity to explore this tool using a series of controlled experiments to isolate the underlying factors or its effectiveness. Nevertheless, by using historical data we can show that the new process is less expensive in terms of cost and at least as effective in terms of quality (defect detection effectiveness). (Also cross-referenced as UMIACS-TR-97-17) | en_US |
| dc.format.extent | 847866 bytes | |
| dc.format.mimetype | application/postscript | |
| dc.identifier.uri | http://hdl.handle.net/1903/882 | |
| dc.language.iso | en_US | |
| dc.relation.isAvailableAt | Digital Repository at the University of Maryland | en_US |
| dc.relation.isAvailableAt | University of Maryland (College Park, Md.) | en_US |
| dc.relation.isAvailableAt | Tech Reports in Computer Science and Engineering | en_US |
| dc.relation.isAvailableAt | UMIACS Technical Reports | en_US |
| dc.relation.ispartofseries | UM Computer Science Department; CS-TR-3757 | en_US |
| dc.relation.ispartofseries | UMIACS; UMIACS-TR-97-17 | en_US |
| dc.title | Anywhere, Anytime Code Inspections: Using the Web to Remove Inspection Bottlenecks in Large-Scale Software Development. | en_US |
| dc.type | Technical Report | en_US |