2001CHI '01 extended abstracts on Human factors in computer systems - CHI '01Requires access

Managing usability defects from identification to closure

Paul McInerney, Christian Pantel, Karl Melder

Open publisher page 0 citations

Abstract

Usability engineering programs generate volumes of raw data that are analyzed and synthesized into findings. While quantitative results such as task completion time and satisfaction ratings are straightforward to analyze and report, qualitative findings are less so. Qualitative findings encompass defects or flaws introduced at various stages of development, user suggestions for improving an acceptable design, and more diffuse usability concerns that need further investigation.It is not sufficient for usability engineers to simply identify usability defects. These defects must be communicated, tracked, resolved, and reported on. The effectiveness of a usability engineering process can be measured by its success rate in causing legitimate usability issues to be successfully resolved. This workshop will seek to identify best practices for managing usability defects from the time they are identified to the time they are closed.

About this research paper

What this paper is about

Usability engineering programs generate volumes of raw data that are analyzed and synthesized into findings. While quantitative results such as task completion time and satisfaction ratings are straightforward to analyze and report, qualitative findings are less so. Qualitative findings encompass defects or flaws introduced at various stages of development, user suggestions for improving an acceptable design, and more diffuse usability concerns that need further investigation.It is not sufficient for usability engineers to simply identify usability defects. These defects must be communicated, tracked, resolved, and reported on. The effectiveness of a usability engineering process can be measured by its success rate in causing legitimate usability issues to be successfully resolved. This workshop will seek to identify best practices for managing usability defects from the time they are identified to the time they are closed.

Why it matters

A significance statement is not available in the OpenAlex record.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Usability engineering programs generate volumes of raw data that are analyzed and synthesized into findings. While quantitative results such as task completion time and satisfaction ratings are straightforward to analyze and report, qualitative findings are less so. Qualitative findings encompass defects or flaws introduced at various stages of development, user suggestions for improving an acceptable design, and more diffuse usability concerns that need further investigation.It is not sufficient for usability engineers to simply identify usability defects. These defects must be communicated, tracked, resolved, and reported on. The effectiveness of a usability engineering process can be measured by its success rate in causing legitimate usability issues to be successfully resolved. This workshop will seek to identify best practices for managing usability defects from the time they are identified to the time they are closed.

Key concepts: Usability, Usability engineering, Usability inspection, Cognitive walkthrough, Usability lab, Computer science, Pluralistic walkthrough, Web usability

Related papers

Back to paper searchBrowse research topicsOriginal source
Managing usability defects from identification to closure — Research Paper | ScholarLens