| Preece et al. define testing or
| |
| | the design team focus on 'real problems,
|
| evaluation as the process of
| |
| | not imaginary ones'. (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 a
| |
| | on users and tasks' which means
|
| process where the interface is tested
| |
| | understanding users and tasks through
|
| against the practices and needs of the
| |
| | observation and analysis, whilst actively
|
| user. (Faulkner 1998:109) Evaluation is
| |
| | involving users from the early stages of
|
| important in design as it aims to
| |
| | design. 'Empirical measurement' gauges
|
| 'eradicate any problems that may be
| |
| | the performance and reactions of users to
|
| present in a system'. (ibid. 1998:124)
| |
| | storyboards and paper prototypes for
|
| Evaluation and amendment of the design at
| |
| | example, in the early stages of
|
| various stages of development helps the
| |
| | development and subsequently to software
|
| designer to verify that the product is
| |
| | prototypes or simulations for example.
|
| suitable for the users' needs, that they
| |
| | Another feature of a user-centred
|
| can use the product and indeed they like
| |
| | approach is 'iterative design'
|
| the product. (Preece et al. 2002:317-319)
| |
| | characterised by cycles of 'design, test,
|
| Preece et al. refer to Tognazzini who
| |
| | measure and redesign'. (Preece et al.
|
| asserts that evaluation also ensures that
| |
| |
|
