An empirical comparison between pair development and software inspection in Thailand

ISESE'06 - Proceedings of the 5th ACM-IEEE International Symposium on Empirical Software Engineering

Volumn 2006, Issue , 2006, Pages 85-94

  Phongpaibul, Monvorath ^a,b   Boehm, Barry ^c  

^a UNIVERSITY OF SOUTHERN CALIFORNIA   (United States)

^b THAMMASAT UNIVERSITY   (Thailand)

^c University of Southern California   (United States)

Author keywords

Empirical study; Pair programming; Peer review; Software inspection; Software process model; Software verification

Indexed keywords

EMPIRICAL STUDY; PAIR PROGRAMMING; PEER REVIEW; SOFTWARE INSPECTION; SOFTWARE PROCESS MODEL; SOFTWARE VERIFICATION;

COMPUTER PROGRAMMING; OPTIMIZATION; PROJECT MANAGEMENT;

SOFTWARE ENGINEERING;

EID: 34247351635     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/1159733.1159749     Document Type: Conference Paper

References (32)

1. eWorkshop on Software Inspections and Pair Programming Report. December 2003. http://www.cebase.org/www/home/index.htm,
2. Ackerman, A.F., Buchwald, L.S., and Lewski, F.H., Software Inspection: An Effective Verification Process. IEEE Software, Vol. 6, No. 3, May 1989, pp. 31-36.
3. Aunim, A., Petersson, H., and Wohlin, C., State-of-the-Art; Software Inspections after 25 Years. Software Testing, Verification, and Reliability, Vol. 12, 2002, pp. 133-154.
4. Boehm, B., and Turner, R., Balancing Agility and Discipline. Addison-Wesley, 2004
5. Cockburn, A., and Williams, L., The Costs and Benefits of Pair Programming, extreme Programming and Flexible Processes in Software Engineering XP2000.
6. Dion, R., Process Improvement and the Corporate Balance Sheet. IEEE Software, Vol. 10, No. 4, July 1993, pp. 28-35.
7. Fagan, M.E., Advances in Software Inspections. IEEE Trans. Software Eng., Vol. 12, No. 7, July 1986, pp. 744-751.
8. Fagan, M.E., Design and Code Inspections to Reduce Errors in Program Development. IBM Syst. J., Vol. 15, No. 3, 1976, pp. 181-211.
9. Gilb, T. and Graham, D., Software Inspection. Addison-Wesley, Reading, Mass., 1993
10. Kelly, J.C., Sherif, J.S. and Hops, J., An Analysis of Defect Densities Found During Software Inspections. J. of Systems and Software, Vol. 17, No. 2, Feb. 1992, pp. 111-117.
11. Hofstede, G., Culture's Consequences -Comparing Values, Behaviors, Institutions and Organizations Across Nations. Thousand Oaks, CA, Sage, 2001
12. Hofstede, G., Culture and Organizations - Software of the Mind. McGraw-Hill, 1997
13. Jirachierpattana, W., The Impact of Thai Culture on Executive Information Systems Development. Proceeding of the 6th International Conference Theme 1, Globalizaion: Impact on and Coping Strategies in Thai Society, 14-17 October, Chiang Mai, Thailand, pp 97-110, 1996.
14. Lee, K., and Boehm, B., Empirical Results from an Experiment on Value-Based Review (VBR) Processes. Proceeding of ISESE 2005, 17-18 November, 2005.
15. Myers, W., Shuttle Code Achieves Very Low Error Rate. IEEE Software, Vol. 5, No. 5, Sept. 1988, pp. 93-95
16. Phongpaibul, M., Improving Quality Through Software Process Improvement in Thailand: Initial Analysis. Proceeding of 3-WoSQ, ICSE 2005, 17 May, 2005.
17. Russell, G.W., Experience with Inspection in Ultralarge-Scale Development. IEEE Software, Vol. 8, No. 1, Jan. 1991, pp. 25-31.
18. Nagappan, N., Williams, L., Wiebe, E., Miller, C., Balik, S., Ferzli, M., Petlick, M., Pair Learning: With an Eye Toward Future Success. Extreme Programming/Agile Universe 2003.
19. Shull, F., Basili, V., Zelkowitz, M., Boehm, B., Brown, A.W., Port, D., Rus, I., and Tesoreiro, R., What we have Learned about Fighting Defects. Proceeding of International Conference on SW Metrics, June 2002.
20. Siegel, A.F., Statistic and Data Analysis. John Wiley & Sons, Singapore, 1988.
21. Slaughter, S.A., Harter, D.E., and Krishnan M.S., Evaluating the Cost of Software Quality. Communications of ACM, Vol. 41, No. 8, August 1998, pp. 67-73.
22. Succi, G., Marchesi, M., Pedrycz.W., Williams, L., Preliminary Analysis of the Effects of Pair Programming on Job Satisfaction. Fourth International Conference on extreme Programming and Agile Processes in Software Engineering (XP2002).
23. Thanasankit, T., and Corbitt B., Towards Understanding Managing Requirements Engineering - A Case Study of a Thai Software House. Proceedings of Conference on Computers and Information Technology in Asia 99, September, Sarawak, East Malaysia, pp 993-1013, 1999.
24. Thsuiasankit, T., and Corbitt B., Cultural Context and its Impact on Requirements Elicitation in Thailand. The Electronic Journal on Information Systems in Developing Countries, http://www.ejisdc.org, 2000.
25. Weller, E.F., Lessons from Three Years of Inspection Data. IEEE Software, Vol. 10, No. 5, Sept. 1993, pp. 38-45.
26. Wernick, P., and Hall, T., The Impact of Using Pair Programming on System Evolution: a Simulation-Based Study. Proceedings of ICSM' 04, IEEE, 2004.
27. Wheeler, D.A., Brykczynski, B., and Meeson, R.NJr., Peer Review Processes Similar to Inspection. Software Inspection: An Industry Best Practice, IEEE CS Press, Los Alamitos, CA, 1996.
28. Wheeler, D.A., Brykczynski, B., and Meeson, R.N.Jr., Software Inspection: An Industry Best Practice. IEEE CS Press, Los Alamitos, CA, 1996.
29. Wiegers, K.E., Peer Reviews in Software: A Practice Guide. Addison-Wesley, 2002.
30. Williams, L., The Collaborative Software Process. PhD Dissertation, 2000.
31. Williams, L., and Kessler, R.R., Pair Programming Illuminated. Addison-Wesley, 2003.
32. Williams, L., Wiebe, E., Yang, K., Ferzli, M., and Miller, C., In Support of Pair Programming in the Introductory Computer Science Course. Computer Science Education, September 2002.