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