Requirements

Detailed descriptions: affinity diagramming | brainstorming | card sorting | context of use | contextual inquiry | evaluating an existing system |focus groups | interviews | observation of users | scenarios of use |surveys |

Overview

The objective is to ensure that user and usability requirements are well defined and integrated into relevant product requirements specification.

The purposes of usability methods at this stage are to collect information about the user interface, users, tasks and environments, and to agree what aspects should be formalised as requirements.

Information can be collected by

• surveys, interviews, contextual inquiry or observation of users in a field study
• user participation in context of use analysis, focus groups or brainstorming
• evaluating an existing system.

Information can be structured by a combination of

• card sorting or affinity diagramming and producing scenarios of use.

If tasks are not well-understood, they should be clarified by

• task analysis

Requirements can be agreed at a requirements meeting.

From the usability perspective, a complete requirements document will:

• identify entire range of primary and secondary users
• prioritise requirements list according to agreed criteria
• establish measurable usability goals against which future designs will be tested
• include legal requirements, references to relevant standards or recommended demands.