All complaints are not created equal: text analysis of open source software defect reports

Raja, Uzma

doi:10.1007/s10664-012-9197-9

Cited by 12 publications

(2 citation statements)

References 38 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Defect resolution time is a time taken for actual time spent to correct a defect and the wait time [15],. In many cases, the time needed to correct a defect is short, but the resolution time is longer due to the long waiting time to find a resource and the urgency of the defect to be fixed.…”

Section: B Usability Defect Resolutionmentioning

confidence: 99%

How Usability Defects Defer from Non-Usability Defects? : A Case Study on Open Source Projects

Yusop¹,

Grundy²,

Schneider³

et al. 2020

Int. J. Adv. Sci. Eng. Inf. Technol.

View full text Add to dashboard Cite

Usability is one of the software qualities attributes that is subjective and often considered as a less critical defect to be fixed. One of the reasons was due to the vague defect descriptions that could not convince developers about the validity of usability issues. Producing a comprehensive usability defect description can be a challenging task, especially in reporting relevant and important information. Prior research in improving defect report comprehension has often focused on defects in general or studied various aspects of software quality improvement such as triaging defect reports, metrics and predictions, automatic defect detection and fixing. In this paper, we studied 2241 usability and non-usability defects from three open-source projects-Mozilla Thunderbird, Firefox for Android, and Eclipse Platform. We examined the presence of eight defect attributes-steps to reproduce, impact, software context, expected output, actual output, assume cause, solution proposal, and supplementary information, and used various statistical tests to answer the research questions. In general, we found that usability defects are resolved slower than non-usability defects, even for non-usability defect reports that have less information. In terms of defect report content, usability defects often contain output details and software context while non-usability defects are preferably explained using supplementary information, such as stack traces and error logs. Our research findings extend the body of knowledge of software defect reporting, especially in understanding the characteristics of usability defects. The promising results also may be valuable to improve software development practitioners' practice.

show abstract

Section: B Usability Defect Resolutionmentioning

confidence: 99%

How Usability Defects Defer from Non-Usability Defects? : A Case Study on Open Source Projects

Yusop¹,

Grundy²,

Schneider³

et al. 2020

Int. J. Adv. Sci. Eng. Inf. Technol.

View full text Add to dashboard Cite

show abstract

“…Then, the time spent to fix the similar CRs can be used to predict the fixing time for the new one. The approaches have used TF‐IDF and LSI for text representation and the cosine similarity function for the reasoning with algebra.…”

Section: Challenges: Improving the Management Of Change Requestmentioning

confidence: 99%

Challenges and opportunities for software change request repositories: a systematic mapping study

Cavalcanti

Neto

Machado

et al. 2013

J Software Evolu Process

View full text Add to dashboard Cite

Software maintenance starts as soon as the first artifacts are delivered and is essential for the success of the software. However, keeping maintenance activities and their related artifacts on track comes at a high cost. In this respect, change request (CR) repositories are fundamental in software maintenance. They facilitate the management of CRs and are also the central point to coordinate activities and communication among stakeholders. However, the benefits of CR repositories do not come without issues, and commonly occurring ones should be dealt with, such as the following: duplicate CRs, the large number of CRs to assign, or poorly described CRs. Such issues have led researchers to an increased interest in investigating CR repositories, by considering different aspects of software development and CR management. In this paper, we performed a systematic mapping study to characterize this research field. We analyzed 142 studies, which we classified in two ways. First, we classified the studies into different topics and grouped them into two dimensions: challenges and opportunities. Second, the challenge topics were classified in accordance with an existing taxonomy for information retrieval models. In addition, we investigated tools and services for CR management, to understand whether and how they addressed the topics identified.

show abstract

Changes, Evolution, and Bugs

Borg

Runeson

2013

Recommendation Systems in Software Engineering

View full text Add to dashboard Cite

All complaints are not created equal: text analysis of open source software defect reports

Cited by 12 publications

References 38 publications

How Usability Defects Defer from Non-Usability Defects? : A Case Study on Open Source Projects

How Usability Defects Defer from Non-Usability Defects? : A Case Study on Open Source Projects

Challenges and opportunities for software change request repositories: a systematic mapping study

Changes, Evolution, and Bugs

Contact Info

Product

Resources

About