Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment

IEEE Transactions on Software Engineering

Volumn 21, Issue 6, 1995, Pages 563-575

  Porter, Adam A ^a   Basili, Victor R ^a   Votta, Lawrence G ^b  

^a UNIVERSITY OF MARYLAND   (United States)

^b LUCENT TECHNOLOGIES   (United States)

Author keywords

Controlled experiments; inspections; reading techniques; technique and methodology evaluation

Indexed keywords

COMPUTER SOFTWARE SELECTION AND EVALUATION; ENCODING (SYMBOLS); ERROR DETECTION; INTERFACES (COMPUTER); RANDOM PROCESSES; SPECIFICATIONS;

CHECKLIST REVIEWERS; CONTROLLED EXPERIMENTS; FAULT DETECTION RATE; RANDOMIZED EXPERIMENTAL DESIGN; READING TECHNIQUES; SOFTWARE REQUIREMENTS INSPECTIONS; TECHNIQUE AND METHODOLOGY EVALUATION;

SOFTWARE ENGINEERING;

EID: 0029325011     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/32.391380     Document Type: Article

References (20)

1. W.S. Humphery, Managing the Software Process, Reading, Mass.: Addison-Wesley Publishing Co., 1989.
2. IEEE Standard for Software Reviews and Audits, Soft. Eng. Tech. Comm. of the IEEE Computer Society, 1989, IEEE Std. 1028-1988.
3. L.G. Votta, “Does every inspection need a meeting?,” Proc. of ACM SIGSOFT '93 Symp. Foundations of Software Eng. Assoc. for Computing Machinery, Dec. 1993.
4. D.L. Parnas and D.M. Weiss, “Active design reviews: Principles and practices,” Proc. Eighth Int'l Conf. Software Eng, Aug. 1985, pp. 215-222.
5. M.E. Fagan, “Design and code inspections to reduce errors in program development,” IBM Systems J., vol. 15, no. 3, pp. 182-211, 1976.
6. B.W. Boehm, Software Engineering Economics, Englewood Cliffs, N.J.: Prentice Hall, 1981.
7. C.M. Judd, E.R. Smith, and L.H. Kidder, Research Methods in Social Relations, Fort Worth, Tex.: Holt, Rinehart and Winston, Inc., 6th edition, 1991.
8. M.A. Ardis, “Lessons from using basic lottos,” Proc. 16th Int'l Conf. Software Eng., Sorrento, Italy, May 1994, pp. 5-14.
9. S. Gerhart, D. Craigen, and T. Ralston, “Experience with formal methods in critical systems,” IEEE Software, vol. 11, no. 1, pp. 21-28, Jan. 1994.
10. S.G. Eick, C.R. Loader, M.D. Long, S.A. Vander Wiel, and L.G. Votta, “Estimating software fault content before coding,” Proc. 14th Int'l Conf. Software Eng., May 1992, pp. 59-65.
11. G.E.P. Box, W.G. Hunter, and J.S. Hunter, Statistics for Experimenters, New York: John Wiley & Sons, 1978.
12. R.M. Heiberger, Computation for the Analysis of Designed Experiments, New York: Wiley & Sons, 1989.
13. K.L. Heninger, “Specifying software requirements fox complex systems: New techniques and their application,” IEEE Trans. Software Eng., vol. SE-6, no. 1, pp. 2-13, Jan. 1980.
14. W.G. Wood, “Temporal logic case study,” Tech. Report CMU/SEI-89-TR-24, Software Eng. Inst., Pittsburgh, Penn., Aug. 1989.
15. J. van Schouwen, “The A-7 requirements model: Re-examination for real-time systems and an application to monitoring systems,” Tech. Report TR-90-276, Queen's Univ., Kingston, Ont., Canada, May 1990.
16. J. Kirby, “Example NRL/SCR software requirements for an automobile cruise control and monitoring system,” Tech. Report TR-87-07, Wang Inst. of Graduate Studies, July 1984.
17. G.M. Schneider, J. Martin, and W.T. Tsai, “An experimental study of fault detection in user requirements,” ACM Trans. Software Eng. and Methodology, vol. 1, no. 2, pp. 188-204, Apr. 1992.
18. V.R. Basili and D.M. Weiss, “Evaluation of a software requirements document by analysis of change data,” Proc. Fifth Int'l Conf. Software Eng., San Diego, Calif., Mar. 1981, pp. 314-323.
19. IEEE Guide to Software Requirements Specifications, Soft. Eng. Tech. Comm. of the IEEE Computer Society, 1984, IEEE Std. 830-1984.
20. S. Siegel and N.J. Castellan, Jr., Nonparametric Statistics for the Behavioral Sciences, New York: McGraw-Hill Book Co., 2nd ed., 1988.