Multi-factor analysis of pair programming based on PSP methodology

Authors

  • Nabiollah Bayatmoghadam Engineering, Shiraz University
  • Ashkan Sami Engineering, Shiraz University

DOI:

https://doi.org/10.24297/ijct.v15i4.6922

Keywords:

software engineering, XP, pair programming, PSP methodology, multi-factor analysis

Abstract

 In regard with designing software, users play key role. In order to design software, it is necessary to observe standard principles of designation, using templates and using modern methods. Over the decades, using development methods, XP and one of the XP methodologies of paired programming used to design software. These methods have been designed for purpose of enhancing quality of product and rapidresponse to need of market and customer and overcoming weaknesses of traditional methods based on long-term programming and waterfall method. Therefore, every programmer and developer can pass a series of processes for constructing computer software. The processes can be changed daily and efficient processes maynot be effective and useful; although they can be considered as process. The main objective of the present study is multi-factor analysis of pair programming based on PSP methodology. Practical and analytical methodand two PSP methods have been applied for investigations.

Downloads

Download data is not yet available.

References

1. E. Arisholm, H. Gallis, T. Dyba, and D. Sjoberg. 2007. “Evaluating Pair Programming with Respect to System Complexity and Programmer Expertise,” IEEE Trans. on Software Engineering, vol. 33, no. 2, pages: 65-86
2. E. Mendes, L. Al-Fakhri, and A. Luxton-Reilly.2005. “Investigating Pair-Programming in a 2nd-year Software Development and Design Computer Science Course,” Proc. ITiCSE, Monte de Caparica, Portuga, pages: 296- 300
3. J. Nawrocki and A. Wojciechowski.2001. "Experimental Evaluation of Pair Programming,” Proc. European SoftwareControl and Metrics Conf. London, England, (ESCOM)
4. J. Nosek, 1998.“The Case for Collaborative Programming,” Comm.ACM, vol. 41, no. 3, pages: 105-108,.
5. J.C ,Kelly, J.S. Sherif, and Hops, J. “An Analysis of Defect Densities Found During Software Inspections,” Journal, Systems and Software, Vol. 17, No. 2, Feb. 1992, pp.111-117.
6. L. Williams, D. McCrickard, L. Layman, and K. Hussein, “Eleven Guidelines for Implementing Pair Programming in the Classroom,” Agile 2006 Conference, Toronto Canada, pages: 445-459, august 2006.
7. N. Sallehand E. Mendes.2009/ “An Empirical Study of the Effects of Personality in Pair Programming using the Five-Factor Model”, Third International Symposium on Empirical Software Engineering and Measurement, Florida USA, pages: 214-225
8. N. Salleh and E. Mendes.2009. “Investigating the Effect of Pair Programming and Software Size on Software Quality and Programmer Productivity” APSEC, Penang Malaysia, pages: 187- 193
9. R.S.Pressman.2001. Software Engineering: A practitioner’s Approach. McGraw-Hill Science
10. Sison.2008. “Investigating Pair Programming in a Software Engineering Course in an Asian Setting,” Proc. APSEC, Beijing china, pages: 325-331, December
11. W. Humphrey.2000.”The Personal Software Process”, CMU/SEI-2000-TR-022, ESC-TR-2000-022

Downloads

Published

2016-02-23

How to Cite

Bayatmoghadam, N., & Sami, A. (2016). Multi-factor analysis of pair programming based on PSP methodology. INTERNATIONAL JOURNAL OF COMPUTERS &Amp; TECHNOLOGY, 15(4), 6672–6680. https://doi.org/10.24297/ijct.v15i4.6922

Issue

Section

Research Articles