Can the System Be Improved?

  • Jan Noyes
  • Chris Baber
Part of the Applied Computing book series (APPLCOMP)


The preceding three chapters have focused on formative evaluation, the assessment of the system as part of the overall iterative design process (as described in Chapter 5). The main point of this evaluation is to find out about the design of the system during its development, in order to address those aspects that need modification and revision. This will allow changes to be made before product release. In contrast, summative evaluation takes place when the system or product has moved from being experimental to operational, and is usually carried out towards the end of the design life cycle. Consequently, the broad difference between formative and summative evaluation concerns the nature of the purpose. Formative evaluation (as implied by the term) is carried out to help the system designer refine and ‘form’ the design, while summative evaluation is concerned with the overall performance of the system. Hewett (1986) defines summative evaluation as follows: ‘Summative evaluation involves assessing the impact, usability and effectiveness of the system - the overall performance of User and system.’ Implicit here is the suggestion that the system or product is close to being launched.


Summative Evaluation Automatic Speech Recognition International Standard Organisation Verbal Protocol Slide Show 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. The bulk of the references on summative methods are those on usability. Often, books on this topic approach usability by considering other methods that may be engaged in conducting a usability assessment, e.g. heuristic evaluation, experimental studies.Google Scholar
  2. Jakob Nielsen, Usability Engineering, Academic Press, 1993. (See’ selected References’, Chapter 6.)Google Scholar
  3. Michael E. Wiklund (ed.), Usability in Practice: How Companies Develop User-friendly Products, Academic Press, London, 1994.Google Scholar
  4. Seventeen leading companies (mainly in the USA) outline their programmes to ensure usability, providing a unique insight into what organisations are doing in terms of usability in the 1990s.Google Scholar
  5. Jeffrey Rubin, Handbook of Usability Testing, Wiley, New York, 1994.Google Scholar
  6. This book assumes no prior knowledge of usability testing on the part of the reader. It takes you through step-by-step how to plan, design and conduct effective usability tests. It also points out common problems, with the use of reallife examples and case histories.Google Scholar
  7. Patrick W. Jordan, An Introduction to Usability, Taylor and Francis, London, 1998.Google Scholar
  8. This book, as the title suggests, provides a broad introduction to the topic, covering concepts and definitions of usability, principles of design, and advantages and disadvantages of methods for usability evaluation.Google Scholar

Copyright information

© Springer-Verlag London 1999

Authors and Affiliations

  • Jan Noyes
    • 1
  • Chris Baber
    • 2
  1. 1.Department of PsychologyUniversity of BristolBristolUK
  2. 2.School of Manufacturing and Mechanical EngineeringUniversity of BirminghamEdgbaston, BirminghamUK

Personalised recommendations