Evaluation of Usage-Based Reading - Conclusions after Three Experiments

Empirical Software Engineering

Volumn 9, Issue 1-2, 2004, Pages 77-110

  Thelin, Thomas ^a   Runeson, Per ^a   Wohlin, Claes ^b   Olsson, Thomas ^c   Andersson, Carina ^a  

^a LUND UNIVERSITY   (Sweden)

^b BLEKINGE INSTITUTE OF TECHNOLOGY   (Sweden)

^c FRAUNHOFER IESE   (Germany)

Author keywords

Empirical study; Reading technique; Software inspection; Usage based reading

Indexed keywords

ERROR DETECTION; INSPECTION; KNOWLEDGE BASED SYSTEMS; QUALITY CONTROL; TESTING;

EMPIRICAL STUDIES; READING TECHNIQUES; SOFTWARE INSPECTION; USAGE-BASED READING (UBR);

SOFTWARE ENGINEERING;

EID: 1442332441     PISSN: 13823256     EISSN: None     Source Type: Journal    
DOI: 10.1023/b:emse.0000013515.86806.d4     Document Type: Conference Paper

References (27)

1. Aurum, A., Petersson, H., and Wohlin, C. 2002. State-of-the-art: Software inspections after 25 years. Software Testing, Verification and Reliability 12(3): 133-154.
2. Basili, V. R., Green, S., Laitenberger, O., Lanubile, F., Shull, F., Sørumgård, S., and Zelkowitz, M. V. 1996. The empirical investigation of perspective-based reading. Empirical Software Engineering: An International Journal 1(2): 133-164.
3. Basili, V. R., Shull, F., and Lanubile, F. 1999. Building knowledge through families of experiments. IEEE Transactions on Software Engineering 25(4): 456-473.
4. Cheng, B., and Jeffery, R. 1996. Comparing inspection strategies for software requirement specifications. Proceedings of the 8th Australian Software Engineering Conference, pp. 203-211.
5. Dunsmore, A., Roper, M., and Wood, M. 2002. Further investigations into the development and evaluation of reading techniques for object-oriented code inspection. Proceedings of the 24th International Conference on Software Engineering, pp. 47-57.
6. Fagan, M. E. 1976. Design and code inspections to reduce errors in program development. IBM System Journal 15(3): 182-211.
7. ITU-T Z.100. 1993. Specification and Description Language. SDL, ITU-T Recommendation Z.100.
8. ITU-T Z.120. 1996. Message Sequence Charts. MSC, ITU-T Recommendation Z.120.
9. Jacobson, I., Christerson, M., Jonsson, P., and Övergaard, G. 1992. Object-Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley, USA.
10. Knight, J. C., and Myers, A. E. 1993. An improved inspection technique. Communications of ACM 36(11): 50-69.
11. Laitenberger, O., and DeBaud, J.-M. 2000. An encompassing life cycle centric survey of software inspection. Journal of Systems and Software 50(1): 5-31.
12. Lauesen, S. 2002. Software Requirements - Styles and Techniques. Addison-Wesley, UK.
13. Martin, J., and Tsai, W. T. 1990. N-fold inspection: A requirements analysis technique. Communications of ACM 33(2): 225-232.
14. Musa, J. D. 1998. Software Reliability Engineering: More Reliable Software, Faster Development and Testing. McGraw-Hill, USA.
15. Olofsson, M., and Wennberg, M. 1996. Statistical Usage Inspection. Master's Thesis, Dept. of Communication Systems, Lund University, CODEN: LUTEDX (TETS-5244)/1-81/(1996)&local 9.
16. Petersson, H., Thelin, T., Runeson, P., and Wohlin, C. 2004. Capture-recapture in software inspections after 10 years research - theory, evaluation and application. To appear in Journal of Systems and Software.
17. Porter, A., Votta, L., and Basili, V. R. 1995. Comparing detection methods for software requirements inspection: A replicated experiment. IEEE Transactions on Software Engineering 21(6): 563-575.
18. Runeson, P. 2000. A new software engineering program - structure and initial experiences. Proceedings of the 13th International Conference on Software Engineering Education & Training, pp. 223-232.
19. Saaty, T. L., and Vargas, L. G. 2001. Models, methods, concepts & applications of the analytic hierarchy process. Netherlands: Kluwer Academic Publishers.
20. Siegel, S., and Castellan, N. J. 1988. Nonparametric Statistics for the Behavioral Sciences. Singapore: McGraw-Hill.
21. Thelin, T., Runeson, P., and Regnell, B. 2001. Usage-based reading - an experiment to guide reviewers with use cases. Information and Software Technology 43(15): 925-938.
22. Thelin, T., Runeson, P., and Wohlin, C. 2003a. An experimental comparison of usage-based and checklist-based reading. IEEE Transactions on Software Engineering August, 29(8): 687-704.
23. Thelin, T., Runeson, P., and Wohlin, C. 2003b. Prioritized use cases as a vehicle for software inspections. IEEE Software July/August, 20(4): 30-33.
24. Travassos, G., Shull, F., Fredericks, M., and Basili, V. R. 1999. Detecting defects in object-oriented designs: Using reading techniques to increase software quality. Proc. of the International Conference on Object-Oriented Programming Systems, Languages & Applications.
25. Votta, L. G. 1993. Does every inspection need a meeting? Proceedings of the 1st ACM SIGSOFT Symposium on Foundations of Software Engineering, ACM Software Engineering Notes 18(5): 107-114.
26. Wohlin, C. 1997. Meeting the challenge of large-scale software engineering in a university environment. Proceedings of the 10th Conference on Software Engineering Education & Training, pp. 40-52.
27. Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., and Wesslén, A. 2000. Experimentation in Software Engineering: An Introduction. USA: Kluwer Academic Publisher.