Abstract

Pair programming is one of the widely used practices of Extreme Programming (XP). XP is a software development process which intends to enhance quality of software code in order to cater to the ever increasing demands of customers looking for IT solutions. Pair programming promotes team building, raises confidence among individuals and eventually results in richer and a better codebase. As an attempt to compare solo and pair programming, group of post graduate students were assigned the task to implement four out of 23 design patterns (pertaining to real world scenarios) in their lab sessions. In this study, a systematic investigation on pairing by contemplating a pair programming scenario from a design pattern perspective has been presented. Results were obtained using JavaNCSS tool by considering software code metrics which indicated that pair programming can be beneficial in a scholastic framework

Highlights

  • Pair programming is a software development technique in which two individuals collaborate and work at the same workstation as a pair

  • This paper explores the essence of pair programming in a scholastic framework by emphasizing upon quantitative evidence in terms of code metric assessment using a tool called Non Commented Source code Statements (JavaNCSS) and comparing its results with solo programming

  • A sincere attempt was made to establish that pair programming is better than solo programming for certain advanced level lab courses in postgraduate studies

Read more

Summary

Introduction

Pair programming is a software development technique in which two individuals collaborate and work at the same workstation as a pair. In a pair programming scenario, individuals play two crucial roles as that of driver and navigator. They swap their roles quite often and are termed as continuous brainstorming partners. The role essayed by both driver and navigator is pivotal. The idea of proposing a pair programming pedagogy is greatly influenced by the immense popularity it has gained over recent years in a software industry framework. With critical deadlines to meet, customer demands to be fulfilled and a constant desire to outshine their competitors, software professionals adopt pair programming in every possible situation (Lewis, 2011; Dogs and Klimmer, 2004)

Objectives
Methods
Results
Conclusion

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.