Satisfaction

The extent to which the user's physical, cognitive and emotional responses that result from the use of an interactive system meet the user's needs and expectations.

Notes:

1. Effectiveness and efficiency may influence satisfaction. For example, low effectiveness or low efficiency may lead to low satisfaction. Satisfaction may influence effectiveness and efficiency. For example, frustration may cause users to quit a task, which influences effectiveness.

2. Satisfaction is often measured using a questionnaire. See the examples in the definition of questionnaire.

3. The difference between satisfaction and user experience is that satisfaction results from use, while user experience results from discovering, adopting and using the interactive system, through to final use and recollections of use. In addition, user experience can be influenced by more than just use, for example brand image, price and opinion of others, but it is still related to actual or imagined use.

Task

A set of activities undertaken in order to achieve a specific goal.

Notes:

1. Most tasks can be subdivided into subtasks - that is, activities.

2. A subtask does not in itself achieve a goal from the user's point of view but is a necessary decision or action to reach the user's goals.

3. Most subtasks lead to choices or inputs by the user when using the interactive system.

4. Some subtasks can be subdivided into smaller subtasks.

5. Subtasks are unsuitable as usability test tasks, because they are very specific

The information architecture and the navigation structure are developed in parallel with the prototypes. From a human-centred point of view, the information architecture is the naming and structuring of the information that is accessible to users.

The navigation structure is the logical organisation of the screens, pages and windows that comprise the user interface - that is, the links and menus that enable users to get from one set of information to another.