Comparing detection methods for software requirements inspections: A replication using professional subjects

Empirical Software Engineering

Volumn 3, Issue 4, 1998, Pages 355-379

  Porter, Adam ^a   Votta, Lawrence ^b  

^a UNIVERSITY OF MARYLAND   (United States)

^b NOKIA RESEARCH CENTER   (United States)

Author keywords

Controlled experiment; Inspection; Replication

Indexed keywords

CHECKLIST METHODS; CONTROLLED EXPERIMENTS; REPLICATION; SOFTWARE REQUIREMENTS SPECIFICATIONS (SRS);

ERROR DETECTION; INSPECTION; POPULATION STATISTICS; PROFESSIONAL ASPECTS; SOCIETIES AND INSTITUTIONS; STATISTICAL METHODS; STUDENTS; COMPUTER SOFTWARE SELECTION AND EVALUATION; SPECIFICATIONS; STATISTICAL TESTS;

SOFTWARE ENGINEERING;

SOFTWARE REQUIREMENTS INSPECTIONS;

EID: 0032320404     PISSN: 13823256     EISSN: None     Source Type: Journal    
DOI: 10.1023/A:1009776104355     Document Type: Article

References (21)

1. Ardis, M. A. 1994. Lessons from using basic LOTOS. Proceedings of the Sixteenth International Conference on Software Engineering. Sorento, Italy, 5-14.
2. Basili, V. R., and Weiss, D. M. 1981. Evaluation of a software requirements document by analysis of change data. Proceedings of the Fith International Conference on Software Engineering. San Diego, CA, 314-323.
3. Boehm, B. W. 1981. Software Engineering Economics. Englewood Cliffs, New Jersey: Prentice Hall Inc.
4. Box, G. E. P., Hunter, W. G., and Hunter, J. S. 1978. Statistics for Experimenters. New York: John Wiley & Sons.
5. Eick, S. G., Loader, C. R., Long, M. D., Vander Wiel, S. A., and Votta, L. G. 1992. Estimating software fault content before coding. Proceedings of the Fourteenth International Conference on Software Engineering. Melborne, Australia, 59-65.
6. Fagan, M. E. 1976. Design and code inspections to reduce errors in program development. IBM Systems Journal 15(2): 182-211.
7. Gerhart, S., Craigen, D., and Ralston, T. 1994. Experience with formal methods in critical systems. IEEE Software 11(1): 21-28.
8. Heiberger, R. M. 1989. Computation for the Analysis of Designed Experiments. New York: John Wiley & Sons.
9. Heninger, K. L. 1980. Specifying software requirements for complex systems: New techniques and their applications. IEEE Transactions on Software Engineering 6: 2-13.
10. Humphery, W. S. 1989. Managing the Software Process. Reading, Massachusetts: Addison-Wesley Publishing Co.
11. IEEE. 1984. IEEE Guide to Software Requirements Specifications. Soft. Eng. Tech. Comm. of the IEEE Computer Society. IEEE Std 830-1984.
12. IEEE. 1989. IEEE Standard for Software Reviews and Audits. Soft. Eng. Tech. Comm. of the IEEE Computer Society. IEEE Std 1028-1988.
13. Judd, C. M., Smith, E. R., and Kidder, L. H. 1991. Research Methods in Social Relations. Fort Worth, Texas: Holt, Rinehart and Winston, Inc.
14. Kirby, J. 1984. Example NRL/SCR software requirements for an automobile cruise control and monitoring system. Wang Institute of Graduate Studies, Bedford, MA, TR-87-07.
15. Parnas, D. L., and Weiss, D. M. 1985. Active design reviews: principles and practices. Proceedings of the Eighth International Conference on Software Engineering. London, UK, 215-222.
16. Porter, A. A., Votta, L. G., and Basili, V. R. 1994. Comparing detection methods for software requirement inspections: A replicated experiment. IEEE Transactions on Software Engineering 21: 563-575.
17. Schneider, G. M., Martin, J., and Tsai, W. T. 1992. An experimental study of fault detection in user requirements. ACM Transactions on Software Engineering and Methodology 1: 188-204.
18. vanSchouwen, J. 1990. The A-7 requirements model: Re-examination for real-time systems and an application to monitoring systems. Queen's University, Kingston, Ontario, Canada, TR-90-276.
19. Votta, L. G. 1993. Does every inspection need a meeting? Proceedings of ACM SIGSOFT '93 Symposium on Foundations of Software Engineering. Los Angeles, California, 107-114.
20. Wheeler, D. J. 1987. Understanding Industrial Experimentation. Knoxville, TN: SPC Press Inc.
21. Wood, W. G. 1989. Temporal logic case study. Software Engineering Institute, Pittsburgh, PA, CMU/SEI-89-TR-24.