Developing a Simplified and Consistent Defect Taxonomy for Smaller Enterprises

University essay from KTH/Skolan för elektroteknik och datavetenskap (EECS)

Abstract: Developing software that meets the customers’ requirements, expectations, and quality standards is a challenging task for all software organizations. As modern software becomes more and more complex, so do the defects of the software. The aim of this study was to develop a simplified and consistent defect taxonomy that could be executable and usable for smaller enterprises or organizations that want to implement a simplified taxonomy. The aim of this study was also to find characteristic defects that exist in Small- and Medium-sized Enterprises (SMEs) by using the taxonomy. A manual defect classification was done on bug reports collected from three organizations with the same company size as SMEs. An agreement analysis was also conducted in this study to investigate the consistency of the taxonomy. This was done by letting different people classify a subset of the bug reports collected for this study using the proposed taxonomy. Furthermore, in this study, I also investigated how executable and usable the taxonomy would be for smaller enterprises. This was done through four interviews and a survey with seven respondents. The result of the defect classification indicates that Program anomaly (58%), GUI (17%) and Configuration (13%) are three of the most common defect types that exist in SMEs. The result of the defect classification indicates that SMEs have a problem with defects breaking features that worked correctly before, where 19% of all bug reports used in this study were classified as Regression. The survey result indicates that taxonomy is easy to use. However, the result of the different classifications showed that the use of the taxonomy is not consistent between different classifiers. The results of the interviews and the survey indicate that the taxonomy would be executable for smaller enterprises. However, to also be fully usable, the proposed taxonomy needs to be adapted to the particular enterprise, and requires the right competence to propose appropriate measures for the particular enterprise. 

  AT THIS PAGE YOU CAN DOWNLOAD THE WHOLE ESSAY. (follow the link to the next page)