Task-directed software inspection

Journal of Systems and Software

Volumn 73, Issue 2, 2004, Pages 361-368

  Kelly, Diane ^a   Shepard, Terry ^a  

^a ROYAL MILITARY COLLEGE OF CANADA   (Canada)

Author keywords

Safety related software; Software process; Structured software inspection technique; Task directed inspection; TDI

Indexed keywords

FUNCTIONS; INSPECTION; PROBLEM SOLVING; PROGRAM DOCUMENTATION; SECURITY SYSTEMS; SOFTWARE ENGINEERING;

SAFETY RELATED SOFTWARE; SOFTWARE PROCESS; STRUCTURED SOFTWARE INSPECTION TECHNIQUE; TASK-DIRECTED INSPECTION (TDI);

COMPUTER SOFTWARE;

EID: 3242665360     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.jss.2003.10.027     Document Type: Article

References (16)

1. Basili V.R., Green S., Laitenberger O., Lanubile F., Shull F., Sorumgard S., Zelkowitz M.V. The empirical investigation of perspective-based reading. Empirical Software Engineering: An International Journal. 2(1):1996;133-164.
2. Boisvert R.F., Tang P.T.P. The Architecture of Scientific Software. 2001;Kluwer Academic Publishers. Available from: http://seg.iit.nrc.ca/ wg25woco8.
3. Canadian Nuclear Safety Commission Regulatory Guide G-149, 2000. Computer Programs Used in Design and Safety Analyses of Nuclear Power Plants and Research Reactors, 2000-11-07.
4. Chernak Y. A statistical approach to the inspection checklist formal synthesis and improvement. IEEE Transactions on Software Engineering. 22(12):1996;866-874.
5. Eisenstadt M. My hairiest bug war stories. Communications of the ACM. 40(4):1997;30-37.
6. Fagan M.E. Design and code inspections to reduce errors in program development. IBM Systems Journal. 15(3):1976;182-211.
7. Humphrey W.S. Managing the Software Process. 1989;Addison-Wesley.
8. Johnson P.M. Reengineering inspection. Communications of the ACM. 41(2):1998;49-52.
9. Kelly, D., Shepard, T., 2000. Task-directed software inspection technique: an experiment and case study. Proceedings IBM CASCON. pp. 122-136.
10. Kelly, D., Shepard, T., 2003. An experiment to investigate interacting versus nominal groups in software inspection. Proceedings IBM CASCON, pp. 122-136.
11. Laitenberger O., DeBaud J.-M. An encompassing life cycle centric survey of software inspection. The Journal of Systems and Software. 50:2000;5-31.
12. Laitenberger, O., Beil, T., Schwinn, T., 2002. An industrial case study to examine a non-traditional inspection implementation for requirements specifications. Proceedings Eighth IEEE Symposium on Software Metrics. pp. 97-106.
13. Laitenberger, O., Atkinson, C., Schlich, M., El-Emam, K., 1999. An Experimental Comparison of Reading Techniques for Defect Detection in UML Design Documents. NRC Report 43614.
14. Lehman, M.M., 2000. Rules and Tools for Software Evolution Planning and Management. Feast 2000 Pre-prints, Imperial College, London.
15. Porter A.A., Siy H.P., Toman C.A., Votta L.G. An experiment to assess the cost-benefits of code inspections in large scale software development. IEEE Transactions on Software Engineering. 23(6):1997;329-346.
16. Votta, L.G., 1993. Does every inspection need a meeting? Proceedings of the 1st ACM SIGSOFT Symposium Software Development Engineering. pp. 107-114.