Understanding Usability Defect Reporting in Software Defect Repositories

Abstract

Software defect management is a critical component of good software engineering practice. The information reported about a defect is a key element to ensure defects are rectified effectively. However, based on research, reporting usability defects using an existing defect tracking system (DTS) is impractical. This is due to text-centric design and lack of features to support usability attributes. In addition, not all defects can be explained textually; especially defects that involve interface redesign. Another aspect to consider is that the reporters describe usability defects based on their usability knowledge and the information available at the time the defects are found. Defects stored in a DTS in a universal format. Therefore, when reporting usability defects there are some possibilities: the data may not be relevant or irrelevant, useful or not useful, or may even be beyond the reporter's knowledge. This makes it impossible to submit a high quality defect report. To address these issues, I propose a custom defect template that can adjust defect form according to whom, when and how the defect is found. In this way, it will provide flexibility to the reporters to record data based on their expertise and knowledge.