Towards experiencing the pair programming as a practice of the Rational Unified Process (RUP)

• Published in: 2015 SAI Intelligent Systems Conference (IntelliSys) pp. 537 - 542
• Main Authors: Akhunzada, Adnan, Gani, Abdullah, Hussain, Shahid, Khan, Arif Ali, Ashrafullah
• Format: Conference Proceeding
• Language: English
• Published: IEEE 01-11-2015
• Subjects: Agile Development; Extreme Programming (XP); Organizations; Pair Programming; Process control; Productivity; Programming; Rational Unified Process (RUP); Software; Software Process Models; World Wide Web
• DOI: 10.1109/IntelliSys.2015.7361192

The Rational Unified Process (RUP) is a software engineering process model that is significantly used to enhance the software team productivity within a development organization. However, the asynchronize communication among the developers of a software team shows diverse effects over the team effort and productivity factors as main goals of the RUP. Although, the roles, workflow and artifacts are well documented but there is a need to fill the gap that arises due to the asynchronize communication among the developers. In Agile development, pair programming is considered the best practice for developers to work in pairs and synchronize the communication. The authors have proposed a novel framework to experience the pair programming concept among the role's communication in three main areas of the RUP such as activities of workflow, phase integration, and process and control management. We also advocate a way forward to experience the pair programming as a practice of the RUP model. We applied the framework on a team of six final year students, who developed a Management Information System (MIS) comprises on four modules (Library, Finance, Payroll and Exam-department). Subsequently, we compare the efforts and productivity of the team with another team that also comprises six students but with-out using the proposed framework. The efforts and productivity of a software team have been observed after implementation of the proposed framework. The result shows little variation in effort and productivity of both the teams, however; it may be prolific when applied to large-scale development processes.