IUSR Overview

The Problem

When companies or organizations make large purchase decisions for software, they currently have little visibility into the usability of the products they are buying. However, the business case for software usability has been clearly established. Moreover, poor usability is an uncontrolled source of overhead, caused by the need for users to correct errors and continually re-learn complex user interfaces. Software that is measurably usable reduces errors, reduces training costs, reduces maintenance costs, while increasing user productivity and satisfaction.

From the software supplier's perspective, the pressure to bring software to market rapidly has adversely affected qualities such as usability. As dependence on shrink-wrapped software and Web-based applications increases so will the need for consumers to have information about software product usability before making large purchase decisions.

The Goals

In 1996 we recognized the need to specify usability in the procurement process. We hosted three meetings under the title of "Usability Engineering in Government Symposia". These meetings helped us lay the groundwork for the IUSR project and in October of 1997, the U.S. National Institute of Standards and Technology (NIST) initiated an effort to increase the visibility of software usability. Cooperating in this effort are prominent suppliers of software and representatives from large consumer organizations. The goals of the initiative are to:

NIST's Role

The role of NIST in this effort is to:


Next Steps

The Common Industry Format currently focuses on software usability and summative testing. We are looking into expanding the kinds of things that can be captured in the Format. For instance, user testing with novel hardware devices, formative methods,sofware requirements, and accessibility, to name a few.

Additional Information

Maintained by: Brian Stanton
Last modified: September 8, 2006
September 8, 2006