This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
A Two-Person Inspection Method to Improve Programming Productivity
October 1989 (vol. 15 no. 10)
pp. 1294-1304

[1] M. E. Fagan, "Design and code inspections to reduce errors in program development,"IBM Syst. J., vol. 15, no. 3, pp. 182-211, 1976.
[2] P.J. Fowler, "In-Process Inspections of Products at AT&T,"AT&T Technical J., March/ April 1986, pp. 102-112.
[3] J. Nenz, "Software quality assurance,"Elec. Commun., vol. 59, no, 1/2, pp. 69-73, 1985.
[4] M. E. Fagan, "Advances in software inspections,"IEEE Trans. Software Eng., vol. SE-12, no. 5, pp. 744-751, July 1986.
[5] E. Yourdon,Structured Walkthroughs. Englewood Cliffs, NJ: Prentice-Hall, 1979.
[6] Inspections in Application Development Introduction and Implementation Guidelines, Newslett, GN20-3814, Publ. GC20-2000-0, 1978; available from IBM Corp., 1133 Westchester Ave., White Plains, NY 10604.
[7] M. E. Graden, P. S. Hersley, and T. C. Pingel, "The effects of software inspections on a major telecommunications project,"AT&T Tech. J., vol. 65, no. 3, pp. 32-40, 1986.
[8] F. O. Buck, "Indicators of quality inspections," IBM Syst. Commun. Division, Kingston, NY, Tech. Rep. TR 21.802, 1981.
[9] E. J. Eckel, "Quality in AT&T network systems,"AT&T Tech. J., vol. 65, no. 2, pp. 30-38, 1986.
[10] M. V. Zelkowitz, R. Yeh, R. G. Hamlet, J. D. Gannon, and V. R. Basili, "The software industry: A state of the an survey," Univ. Maryland, College Park, MD, Tech. Rep, UOM 1290, 1983.
[11] E. Soloway and K. Ehrlich, "Empirical studies of programming knowledge,"IEEE Trans. Software Eng., vol. SE-10, no. 5, pp. 595- 609, 1984.
[12] S.D. Conte, H.E. Dunsmore, and V.Y. Shen,Software Engineering: Metrics and Models, Benjamin/Cummings, Menlo Park, Calif., 1986.
[13] M. V. Zelkowitz, R. Yeh, R. G. Hamlet, J. D. Gannon, and V. R. Basili, "Software engineering practices in the U.S. and Japan,"Computer, vol. 17, no. 6, pp. 57-66, 1984.
[14] G. J. Myers, "A controlled experiment in program testing and code walk-throughs/inspections,"Commun. ACM, pp. 760-768, Sept. 1978.
[15] S. Howell, "Inspection and Education." Comput. Sci. Center, Univ. Maryland, College Park, MD, Tcch. Rep. CSC-435, 1984.
[16] R. S. Lemos, "Discussion and correspondence measuring student's attitudes towards structured walk-throughs,"Comput. J., vol. 23, no. 3, pp. 377-380, 1980.
[17] R. S. Lemos, "An implementation of structured walk-throughs in teaching COBOL programming,"Commun. ACM, vol. 22, no. 6, pp. 335- 340, 1979.
[18] R. Lanergan and C. Grasso, "Software engineering with reusable designs and code,"IEEE Trans. Software Eng., vol. SE-10, no. 5, pp. 498-501, 1984.
[19] G. Curry and R. Ayers, "Experience with traits in the Xerox Star workstation,"IEEE Trans. Software Eng., vol. SE-10, no. 5, pp. 519-527, 1984.
[20] H. Schmid and P. Wolf, "Software reuse through building blocks,"IEEE Software, vol. 4, no. 4, pp. 34-42, 1987.
[21] K. H. Kim, "A look at Japan's development of software engineering technology,"Computer, vol. 16, no. 5, pp. 26-37, 1983.
[22] D. Tajima and T. Matsubara, "Inside the Japanese software industry,"Computer, vol. 17, no. 3, pp. 34-43, 1994.
[23] M. Schindler, "Europeans make a CASE for software leadership,"Electron. Design, vol. 34, no. 24, pp. 29-31, 1986.

Index Terms:
detection; inspections; programmer productivity; watkthrough
Citation:
D.B. Bisant, J.R. Lyle, "A Two-Person Inspection Method to Improve Programming Productivity," IEEE Transactions on Software Engineering, vol. 15, no. 10, pp. 1294-1304, Oct. 1989, doi:10.1109/TSE.1989.559782
Usage of this product signifies your acceptance of the Terms of Use.