An Empirical Study on the Impact of an IDE Tool Support in the Pair and Solo Programming
The adoption of Agile software development approaches has been widespread. One well-known Agile approach is extreme programming, which encompasses twelve practices of which pair programming is one of them. Although various aspects of pair programming have been studied, we have not found, under a tra...
| Autores: | , , , , , |
|---|---|
| Tipo de recurso: | artículo |
| Estado: | Versión publicada |
| Fecha de publicación: | 2017 |
| País: | México |
| Institución: | Universidad Autónoma de Yucatán |
| Repositorio: | Repositorio Digital Institucional de la Universidad Autónoma de Yucatán |
| Idioma: | inglés |
| OAI Identifier: | oai:redi.uady.mx:123456789/1026 |
| Acceso en línea: | http://redi.uady.mx:8080/handle/123456789/1026 |
| Access Level: | acceso abierto |
| Palabra clave: | info:eu-repo/classification/cti/1 info:eu-repo/classification/cti/7 software prototyping Pair programming Software quality and cost Integrated development environment Controlled experiment Software engineering |
| Sumario: | The adoption of Agile software development approaches has been widespread. One well-known Agile approach is extreme programming, which encompasses twelve practices of which pair programming is one of them. Although various aspects of pair programming have been studied, we have not found, under a traditional setting of pair programming, studies that examine the impact of using a tool support, such as an integrated development environment (IDE) or a simple text editor. In an attempt to obtain a better understanding of the impact of using an IDE in this field, we present the results of a controlled experiment that expose the influence on quality, measured as the number of defects injected per hour, and cost, measured as the time necessary to complete a programming assignment, of pair and solo programming with and without the use of an IDE. For quality, our findings suggest that the use of an IDE results in significantly higher defect injection rates (for both pairs and solos) when the programming assignment is not very complicated. Nevertheless, defect injection rates seem to decrease when pairs work on more complicated programming assignments irrespective of the tool support that they use. For cost, the programming assignment significantly affects the time needed to complete the assignment. In relation to the programming type, pairs and solos performed in a similar way with regards to quality and cost. |
|---|