Cite Article

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

Choose citation format

BibTeX

@article{IJASEIT10225,
   author = {Nor Shahida Mohamad Yusop and John Grundy and Jean-Guy Schneider and Rajesh Vasa},
   title = {How Usability Defects Defer from Non-Usability Defects? : A Case Study on Open Source Projects},
   journal = {International Journal on Advanced Science, Engineering and Information Technology},
   volume = {10},
   number = {1},
   year = {2020},
   pages = {98--105},
   keywords = {defect report; open-source; software repository mining; software defect repository; usability defects.},
   abstract = {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.},
   issn = {2088-5334},
   publisher = {INSIGHT - Indonesian Society for Knowledge and Human Development},
   url = {http://ijaseit.insightsociety.org/index.php?option=com_content&view=article&id=9&Itemid=1&article_id=10225},
   doi = {10.18517/ijaseit.10.1.10225}
}

EndNote

%A Mohamad Yusop, Nor Shahida
%A Grundy, John
%A Schneider, Jean-Guy
%A Vasa, Rajesh
%D 2020
%T How Usability Defects Defer from Non-Usability Defects? : A Case Study on Open Source Projects
%B 2020
%9 defect report; open-source; software repository mining; software defect repository; usability defects.
%! How Usability Defects Defer from Non-Usability Defects? : A Case Study on Open Source Projects
%K defect report; open-source; software repository mining; software defect repository; usability defects.
%X 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.
%U http://ijaseit.insightsociety.org/index.php?option=com_content&view=article&id=9&Itemid=1&article_id=10225
%R doi:10.18517/ijaseit.10.1.10225
%J International Journal on Advanced Science, Engineering and Information Technology
%V 10
%N 1
%@ 2088-5334

IEEE

Nor Shahida Mohamad Yusop,John Grundy,Jean-Guy Schneider and Rajesh Vasa,"How Usability Defects Defer from Non-Usability Defects? : A Case Study on Open Source Projects," International Journal on Advanced Science, Engineering and Information Technology, vol. 10, no. 1, pp. 98-105, 2020. [Online]. Available: http://dx.doi.org/10.18517/ijaseit.10.1.10225.

RefMan/ProCite (RIS)

TY  - JOUR
AU  - Mohamad Yusop, Nor Shahida
AU  - Grundy, John
AU  - Schneider, Jean-Guy
AU  - Vasa, Rajesh
PY  - 2020
TI  - How Usability Defects Defer from Non-Usability Defects? : A Case Study on Open Source Projects
JF  - International Journal on Advanced Science, Engineering and Information Technology; Vol. 10 (2020) No. 1
Y2  - 2020
SP  - 98
EP  - 105
SN  - 2088-5334
PB  - INSIGHT - Indonesian Society for Knowledge and Human Development
KW  - defect report; open-source; software repository mining; software defect repository; usability defects.
N2  - 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.
UR  - http://ijaseit.insightsociety.org/index.php?option=com_content&view=article&id=9&Itemid=1&article_id=10225
DO  - 10.18517/ijaseit.10.1.10225

RefWorks

RT Journal Article
ID 10225
A1 Mohamad Yusop, Nor Shahida
A1 Grundy, John
A1 Schneider, Jean-Guy
A1 Vasa, Rajesh
T1 How Usability Defects Defer from Non-Usability Defects? : A Case Study on Open Source Projects
JF International Journal on Advanced Science, Engineering and Information Technology
VO 10
IS 1
YR 2020
SP 98
OP 105
SN 2088-5334
PB INSIGHT - Indonesian Society for Knowledge and Human Development
K1 defect report; open-source; software repository mining; software defect repository; usability defects.
AB 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.
LK http://ijaseit.insightsociety.org/index.php?option=com_content&view=article&id=9&Itemid=1&article_id=10225
DO  - 10.18517/ijaseit.10.1.10225