skip to main content
10.1145/1159733.1159749acmconferencesArticle/Chapter ViewAbstractPublication PagesesemConference Proceedingsconference-collections
Article

An empirical comparison between pair development and software inspection in Thailand

Published: 21 September 2006 Publication History

Abstract

Although pair programming and software inspection have the common aim of minimizing the defects of the software product, each practice has its strengths and weaknesses. We need to understand their costs and benefits under given conditions to be able to select a practice to execute in a development project. The objective of this study is to compare the commonalities and differences between pair development and software inspection as verification techniques in Thailand. One classroom experiment and one industry experiment were conducted. The development effort and effect of quality were investigated with some additional calendar time comparisons. The classroom results showed that average development effort of the pair development group was 24% less than inspection group with the improved product quality. The industry experiment showed pair development to have about 4% more effort but about 40% fewer major defects. In addition, the impacts of cultural differences to the adoption of pair programming or software inspection in Thailand are discussed.

References

[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]
Aurum, 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]
Jirachiefpattana, 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]
Thanasankit, 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.N.Jr., 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.

Cited By

View all
  • (2023)Identifying Agile Practices to Reduce Defects in Medical Device Software DevelopmentSystems, Software and Services Process Improvement10.1007/978-3-031-42310-9_5(61-75)Online publication date: 30-Aug-2023
  • (2016)Teaching mobile application development through lectures, interactive tutorials, and Pair Programming2016 IEEE Frontiers in Education Conference (FIE)10.1109/FIE.2016.7757533(1-9)Online publication date: Oct-2016
  • (2016)Pair ProgrammingEncyclopedia of Software Engineering10.1081/E-ESE-120044181(651-659)Online publication date: 28-Jul-2016
  • Show More Cited By

Recommendations

Comments

Information & Contributors

Information

Published In

cover image ACM Conferences
ISESE '06: Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
September 2006
388 pages
ISBN:1595932186
DOI:10.1145/1159733
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Sponsors

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 21 September 2006

Permissions

Request permissions for this article.

Check for updates

Author Tags

  1. empirical study
  2. pair programming
  3. peer review
  4. software inspection
  5. software process model
  6. software verification

Qualifiers

  • Article

Conference

ISESE06
Sponsor:

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)13
  • Downloads (Last 6 weeks)1
Reflects downloads up to 02 Mar 2025

Other Metrics

Citations

Cited By

View all
  • (2023)Identifying Agile Practices to Reduce Defects in Medical Device Software DevelopmentSystems, Software and Services Process Improvement10.1007/978-3-031-42310-9_5(61-75)Online publication date: 30-Aug-2023
  • (2016)Teaching mobile application development through lectures, interactive tutorials, and Pair Programming2016 IEEE Frontiers in Education Conference (FIE)10.1109/FIE.2016.7757533(1-9)Online publication date: Oct-2016
  • (2016)Pair ProgrammingEncyclopedia of Software Engineering10.1081/E-ESE-120044181(651-659)Online publication date: 28-Jul-2016
  • (2015)Knowledge transfer in pair programming: An in-depth analysisInternational Journal of Human-Computer Studies10.1016/j.ijhcs.2014.09.00173(66-78)Online publication date: Jan-2015
  • (2013)Pair Programming and Software Defects--A Large, Industrial Case StudyIEEE Transactions on Software Engineering10.1109/TSE.2012.6839:7(930-953)Online publication date: 1-Jul-2013
  • (2013)Investigating the Impact of Experience and Solo/Pair Programming on Coding Efficiency: Results and Experiences from Coding ContestsAgile Processes in Software Engineering and Extreme Programming10.1007/978-3-642-38314-4_8(106-120)Online publication date: 2013
  • (2012)Understanding the impact of pair programming on developers attention: a case study on a large industrial experimentationProceedings of the 34th International Conference on Software Engineering10.5555/2337223.2337366(1094-1101)Online publication date: 2-Jun-2012
  • (2012)Understanding the impact of Pair Programming on developers attention: A case study on a large industrial experimentation2012 34th International Conference on Software Engineering (ICSE)10.1109/ICSE.2012.6227110(1094-1101)Online publication date: Jun-2012
  • (2008)Investigating Pair Programming in a Software Engineering Course in an Asian SettingProceedings of the 2008 15th Asia-Pacific Software Engineering Conference10.1109/APSEC.2008.61(325-331)Online publication date: 3-Dec-2008
  • (2007)The economic impact of software process variationsProceedings of the 2007 international conference on Software process10.5555/1763239.1763267(259-271)Online publication date: 19-May-2007
  • Show More Cited By

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Figures

Tables

Media

Share

Share

Share this Publication link

Share on social media