Reporting usability defects-do reporters report what software developers need?

Yusop, Nor Shahida Mohamad, Grundy, John and Vasa, Rajesh 2016, Reporting usability defects-do reporters report what software developers need?, in EASE 2016 : Proceedings of the 20th Evaluation and Assessment in Software Engineering International Conference, Association for Computer Machinery, New York, N.Y., pp. 271-280, doi: 10.1145/2915970.2915995.

Attached Files
Name Description MIMEType Size Downloads

Title Reporting usability defects-do reporters report what software developers need?
Author(s) Yusop, Nor Shahida Mohamad
Grundy, JohnORCID iD for Grundy, John orcid.org/0000-0003-4928-7076
Vasa, RajeshORCID iD for Vasa, Rajesh orcid.org/0000-0003-4805-1467
Conference name Evaluation and Assessment in Software Engineering. Conference (20th : 2016 : Limerick, Ireland)
Conference location Limerick, Ireland
Conference dates 1-3 Jun. 2016
Title of proceedings EASE 2016 : Proceedings of the 20th Evaluation and Assessment in Software Engineering International Conference
Editor(s) [Unknown]
Publication date 2016
Conference series International Conference of Evaluation and Assessment in Software Engineering
Start page 271
End page 280
Total pages 10
Publisher Association for Computer Machinery
Place of publication New York, N.Y.
Keyword(s) defect repository
software quality
usability defect reporting
Summary Reporting usability defects can be a challenging task, especially in convincing the software developers that the reported defect actually requires attention. Stronger evidence in the form of specific details is often needed. However, research to date in software defect reporting has not investigated the value of capturing different information based on defect type. We surveyed practitioners in both open source communities and industrial software organizations about their usability defect reporting practices to better understand information needs to address usability defect reporting issues. Our analysis of 147 responses show that reporters often provide observed result, expected result and steps to reproduce when describing usability defects, similar to the way other types of defects are reported. However, reporters rarely provide usability-related information. In fact, reporters ranked cause of the problem is the most difficult information to provide followed by usability principle, video recoding, UI event trace and title. Conversely, software developers consider cause of the problem as the most helpful information for them to fix usability defects. Our statistical analysis reveals a substantial gap between what reporters provide and what software developers need when fixing usability defects. We propose some remedies to resolve this gap.
ISBN 9781450336918
Language eng
DOI 10.1145/2915970.2915995
Field of Research 080309 Software Engineering
Socio Economic Objective 890202 Application Tools and System Utilities
HERDC Research category E1 Full written paper - refereed
ERA Research output type E Conference publication
Copyright notice ©2016, ACM
Persistent URL http://hdl.handle.net/10536/DRO/DU:30085229

Document type: Conference Paper
Collections: School of Information Technology
2018 ERA Submission
Connect to link resolver
 
Unless expressly stated otherwise, the copyright for items in DRO is owned by the author, with all rights reserved.

Versions
Version Filter Type
Citation counts: TR Web of Science Citation Count  Cited 0 times in TR Web of Science
Scopus Citation Count Cited 12 times in Scopus
Google Scholar Search Google Scholar
Access Statistics: 222 Abstract Views, 18 File Downloads  -  Detailed Statistics
Created: Wed, 14 Sep 2016, 10:10:31 EST

Every reasonable effort has been made to ensure that permission has been obtained for items included in DRO. If you believe that your rights have been infringed by this repository, please contact drosupport@deakin.edu.au.