|
ABSTRACT
This paper describes a software engineering experiment designed to confirm results from an earlier project which measured fault detection rates in user requirements documents (URD). The experiment described in this paper involves the creation of a standardized URD with a known number of injected faults of specific type. Nine independent inspection teams were given this URD with instructions to locate as many faults as possible using the N-fold requirements inspection technique developed by the authors. Results obtained from this experiment confirm earlier conclusions about the low rate of fault detection in requirements documents using formal inspections and the advantages to be gained using the N-fold inspection method. The experiment also provides new results concerning variability in inspection team performance and the relative difficulty of locating different classes of URD faults.
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
|
~AvIzmMs, A. The N-version approach to fault tolerant software. IEEE Trans. Softw. Eng. ~11, 12 (Dec. 1985).
|
| |
2
|
~BO~M, B. Industrial software metrics top ten list IEEE Softw. (Sept 1987).
|
| |
3
|
~COLL~U*ELLO J. S. The software technical review process. Curriculum Module SEI-CM-3-1.5, ~Software Engineering Institute, Carnegie Mellon Univ., Pittsburgh, Pa., 1988.
|
| |
4
|
~FACAN, M.E. Design and code inspections to reduce errors in program developments. IBM ~Syst J., 3 (1976)
|
| |
5
|
~FAmLEY, R. Software Engineering Concepts. McGraw-Hfil, New York, 1985.
|
| |
6
|
|
 |
7
|
|
| |
8
|
~MOILER, T., AND SCHNEIDER, G M. Methodology and experimental research m software ~engineering. Int. J Man-Mach. Stud. 16 (1982).
|
| |
9
|
~RAMAMOOR?HY, R. Application of a methodology for the development and validation of ~process control software. IEEE Trans. Softw. Eng. SE-7, 6 (Nov. 1981).
|
REVIEW
"Paul W. Abrahams : Reviewer"
The authors propose a way to detect faults in a user requirements
document (URD)—a user's description of the functionality and
performance of a software product—by carrying out
N
formal
more...
|