| Preece et al. define testing or | | | | on 'real problems, not imaginary ones'. |
| evaluation as the process of | | | | (ibid. 2002:321) |
| 'systematically collecting data that | | | | Evaluation with users underpins a |
| informs us about what it is like for a | | | | user-centred approach to design. Preece |
| particular user or group of users to use | | | | et al. refer to Gould and Lewis who |
| a product for a particular task in a | | | | identify three main characteristics of |
| certain type of environment'. (Preece et | | | | this approach. There is an 'early focus |
| al. 2002:317) That is to say that it is | | | | on users and tasks' which means |
| a process where the interface is tested | | | | understanding users and tasks through |
| against the practices and needs of the | | | | observation and analysis, whilst |
| user. (Faulkner 1998:109) Evaluation is | | | | actively involving users from the early |
| important in design as it aims to | | | | stages of design. 'Empirical |
| 'eradicate any problems that may be | | | | measurement' gauges the performance and |
| present in a system'. (ibid. 1998:124) | | | | reactions of users to storyboards and |
| Evaluation and amendment of the design | | | | paper prototypes for example, in the |
| at various stages of development helps | | | | early stages of development and |
| the designer to verify that the product | | | | subsequently to software prototypes or |
| is suitable for the users' needs, that | | | | simulations for example. Another feature |
| they can use the product and indeed they | | | | of a user-centred approach is 'iterative |
| like the product. (Preece et al. | | | | design' characterised by cycles of |
| 2002:317-319) Preece et al. refer to | | | | 'design, test, measure and redesign'. |
| Tognazzini who asserts that evaluation | | | | (Preece et al. |
| also ensures that the design team focus | | | | |