Authors:
Chauncey Wilson, Kara Coyne
Most development organizations track software bugs and their severity in a corporate database, which is shared with product development and tech support teams. We find, however, that these same organizations seldom have a standard method, if any, of tracking usability issues. Usability practitioners communicate usability problems through reports, highlight tapes, and formal briefings, but are these methods adequate for tracking usability problems through successive cycles of product development? We diverge in our specific approaches to tracking. Chauncey believes that it is essential to track usability issues in the official corporate bug database. Bugs that don't get into the bug…
You must be a member of SIGCHI, a subscriber to ACM's Digital Library, or an interactions subscriber to read the full text of this article.
GET ACCESS
Join ACM SIGCHIIn addition to all of the professional benefits of being a SIGCHI member, members get full access to interactions online content and receive the print version of the magazine bimonthly.
Subscribe to the ACM Digital Library
Get access to all interactions content online and the entire archive of ACM publications dating back to 1954. (Please check with your institution to see if it already has a subscription.)
Subscribe to interactions
Get full access to interactions online content and receive the print version of the magazine bimonthly.
Post Comment
No Comments Found