%0 Journal Article %1 CavalcantiSQJ2011 %A Cavalcanti, Yguaratã Cerqueira %A da Mota Silveira Neto, Paulo Anselmo %A Lucrédio, Daniel %A Vale, Tassio %A de Almeida, Eduardo Santana %A de Lemos Meira, Silvio Romero %D 2011 %I Springer Netherlands %J Software Quality Journal %K imported myown mypublications %P 1-28 %R 10.1007/s11219-011-9164-5 %T The bug report duplication problem: an exploratory study %U http://dx.doi.org/10.1007/s11219-011-9164-5 %X Duplicate bug report entries in bug trackers have a negative impact on software maintenance and evolution. This is due, among other factors, to the increased time spent on report analysis and validation, which in some cases takes over 20 min. Therefore, a considerable amount of time is lost in duplicate bug report analysis. In order to understand the possible factors that cause bug report duplication and its impact on software development, this paper presents an exploratory study in which bug tracking data from private and open source projects were analyzed. The results show, for example, that all projects we investigated had duplicate bug reports and a considerable amount of time was wasted by this duplication. Furthermore, features such as project lifetime, staff size, and the number of bug reports do not seem to be significant factors for duplication, while others, such as the submitters’ profile and the number of submitters, do seem to influence the bug report duplication.

@article{CavalcantiSQJ2011, abstract = {Duplicate bug report entries in bug trackers have a negative impact on software maintenance and evolution. This is due, among other factors, to the increased time spent on report analysis and validation, which in some cases takes over 20 min. Therefore, a considerable amount of time is lost in duplicate bug report analysis. In order to understand the possible factors that cause bug report duplication and its impact on software development, this paper presents an exploratory study in which bug tracking data from private and open source projects were analyzed. The results show, for example, that all projects we investigated had duplicate bug reports and a considerable amount of time was wasted by this duplication. Furthermore, features such as project lifetime, staff size, and the number of bug reports do not seem to be significant factors for duplication, while others, such as the submitters’ profile and the number of submitters, do seem to influence the bug report duplication.}, added-at = {2012-01-23T13:20:10.000+0100}, author = {Cavalcanti, Yguarat{\~a} Cerqueira and da Mota Silveira Neto, Paulo Anselmo and Lucrédio, Daniel and Vale, Tassio and de Almeida, Eduardo Santana and de Lemos Meira, Silvio Romero}, biburl = {https://www.bibsonomy.org/bibtex/267f62b28743178fbaf9ede91ca5ba11a/yguarata}, doi = {10.1007/s11219-011-9164-5}, interhash = {837e4c0c4cd89578878845e3620f21cc}, intrahash = {67f62b28743178fbaf9ede91ca5ba11a}, issn = {0963-9314}, journal = {Software Quality Journal}, keyword = {Computer Science}, keywords = {imported myown mypublications}, note = {Online first}, pages = {1-28}, publisher = {Springer Netherlands}, timestamp = {2012-01-23T13:41:46.000+0100}, title = {The bug report duplication problem: an exploratory study}, url = {http://dx.doi.org/10.1007/s11219-011-9164-5}, year = 2011 }