Detail: Prototype and Evaluate User Interface
Iteratively developing prototypes and performing usability testing allows teams to build usable applications. These activities identify potential problems, allowing teams to correct them before launching the website. Use the links below for an overview of these activities. For details about a role, activity, or artifact in the diagram, click on its icon.
More detail: Purpose - How to Staff
Click the icons for definition
      |
|
Purpose
The purpose of this workflow detail is to:
- Create the Artifact: User Interface Prototype
- Plan its evaluation with respect to usability goals
- Evaluate the prototype by conducting usability tests
- Analyze the usability test results and recommend improvements
This process is highly iterative and results from one activity often affect others. For example, the Artifact: Usability Test Report may contain recommendations from the usability testing requiring a revision to Artifact: Site Map and the creation of change requests.
How to Staff
The skills used by the Role: User Interface Prototyper will vary based on the type of prototype to be developed. For example, someone creating a paper-based prototype does not need HTML skills. The person fulfilling the User Interface Prototyper role may change during the project as the prototypes have increasing functionality and higher fidelity.
The Role: Usability Evaluator should not be the same person as the Role: Information Architect or the User Interface Prototyper as it is important for the evaluator to remain objective while analyzing usability test results. The Information Architect or Requirements Analyst may help the Usability Evaluator define appropriate tasks to be used in the usability tests. Fulfilling the Role: End User with actual users is critical for the Activity: Conduct Usability Test. Regardless of how extensive the tests are, without real users the test is considerably less effective. Having real users attempt to complete tasks with the intended user interface is the hallmark of usability testing.
One of the best ways for Information Architects, Graphic Designers, User Interface Prototypers, Requirements Analysts, and Software Designers to understand how users really interact with software is to observe the usability tests. Having stakeholders and Requirements Reviewers observe also gives the team opportunity to learn how their target audiences react to the application or website being developed and the decisions that they have made. Plan to allow people in various roles the opportunity to observe or review videotapes of the usability tests throughout the project.