1. Chapter 29 - Interaction design
Chapter 29 is available online:
Chapter 29 Interaction design

2. Chapter 29 Interaction design
Topics covered
Design issues
The user interface design process
User analysis
User interface prototyping
Interface evaluation
Chapter 29 Interaction design

3. Chapter 29 Interaction design
The user interface
User interfaces should be designed to match the skills, experience and expectations of its anticipated users.
System users often judge a system by its interface rather than its functionality.
A poorly designed interface can cause a user to make catastrophic errors.
Poor user interface design is the reason why so many software systems are never used.
Chapter 29 Interaction design

4. Chapter 29 Interaction design
Activity
Take a look at these images for 15 seconds..
Chapter 29 Interaction design

5. Chapter 29 Interaction design
Activity
On a piece of paper write down what you remember.
How many items did you remember?
Average = 7+/-2
Chapter 29 Interaction design

6. Human factors in interface design
Limited short-term memory
People can instantaneously remember about 7 items of information. If you present more than this, they are more liable to make mistakes.
People make mistakes
When people make mistakes and systems go wrong, inappropriate alarms and messages can increase stress and hence the likelihood of more mistakes.
People are different
People have a wide range of physical capabilities. Designers should not just design for their own capabilities.
People have different interaction preferences
Some like pictures, some like text.
Chapter 29 Interaction design

7. Chapter 29 Interaction design
UI design principles
UI design must take account of the needs, experience and capabilities of the system users.
Designers should be aware of people’s physical and mental limitations (e.g. limited short-term memory) and should recognise that people make mistakes.
UI design principles underlie interface designs although not all principles are applicable to all designs.
Chapter 29 Interaction design

8. User interface design principles
Chapter 29 Interaction design

9. Chapter 29 Interaction design
Design principles
User familiarity
The interface should be based on user-oriented terms and concepts rather than computer concepts. For example, an office system should use concepts such as letters, documents, folders etc. rather than directories, file identifiers, etc.
Consistency
The system should display an appropriate level of consistency. Commands and menus should have the same format, command punctuation should be similar, etc.
Minimal surprise
If a command operates in a known way, the user should be able to predict the operation of comparable commands
Chapter 29 Interaction design

10. Chapter 29 Interaction design
Design principles
Recoverability
The system should provide some resilience to user errors and allow the user to recover from errors. This might include an undo facility, confirmation of destructive actions, 'soft' deletes, etc.
User guidance
Some user guidance such as help systems, on-line manuals, etc. should be supplied
User diversity
Interaction facilities for different types of user should be supported. For example, some users have seeing difficulties and so larger text should be available
Chapter 29 Interaction design

11. Chapter 29 Interaction design
Design issues in UIs
Two problems must be addressed in interactive systems design
How should information from the user be provided to the computer system?
How should information from the computer system be presented to the user?
User interaction and information presentation may be integrated through a coherent framework such as a user interface metaphor.
Chapter 29 Interaction design

12. Chapter 29 Interaction design
Interaction styles
Direct manipulation
Menu selection
Form fill-in
Command language
Natural language
Chapter 29 Interaction design

13. Chapter 29 Interaction design
Interaction styles
Chapter 29 Interaction design

14. Multiple user interfaces
Chapter 29 Interaction design

15. Chapter 29 Interaction design
LIBSYS interaction
Document search
Users need to be able to use the search facilities to find the documents that they need.
Document request
Users request that a document be delivered to their machine or to a server for printing.
Chapter 29 Interaction design

16. Chapter 29 Interaction design
Web-based interfaces
Many web-based systems have interfaces based on web forms.
Form field can be menus, free text input, radio buttons, etc.
In the LIBSYS example, users make a choice of where to search from a menu and type the search phrase into a free text field.
Chapter 29 Interaction design

17. Chapter 29 Interaction design
LIBSYS search form
Chapter 29 Interaction design

18. Information presentation
Information presentation is concerned with presenting system information to system users.
The information may be presented directly (e.g. text in a word processor) or may be transformed in some way for presentation (e.g. in some graphical form).
The Model-View-Controller approach is a way of supporting multiple presentations of data.
Chapter 29 Interaction design

19. Information presentation
Chapter 29 Interaction design

20. Model-view-controller
Chapter 29 Interaction design

21. Information presentation
Static information
Initialised at the beginning of a session. It does not change during the session.
May be either numeric or textual.
Dynamic information
Changes during a session and the changes must be communicated to the system user.
Chapter 29 Interaction design

22. Information display factors
Is the user interested in precise information or data relationships?
How quickly do information values change? Must the change be indicated immediately?
Must the user take some action in response to a change?
Is there a direct manipulation interface?
Is the information textual or numeric? Are relative values important?
Chapter 29 Interaction design

23. Alternative information presentations
Chapter 29 Interaction design

24. Analogue or digital presentation?
Compact - takes up little screen space;
Precise values can be communicated.
Analogue presentation
Easier to get an 'at a glance' impression of a value;
Possible to show relative values;
Easier to see exceptional data values.
Chapter 29 Interaction design

25. Chapter 29 Interaction design
Presentation methods
Chapter 29 Interaction design

26. Displaying relative values
Chapter 29 Interaction design

27. Chapter 29 Interaction design
Data visualisation
Concerned with techniques for displaying large amounts of information.
Visualisation can reveal relationships between entities and trends in the data.
Possible data visualisations are:
Weather information collected from a number of sources;
The state of a telephone network as a linked set of nodes;
Chemical plant visualised by showing pressures and temperatures in a linked set of tanks and pipes;
A model of a molecule displayed in 3 dimensions;
Web pages displayed as a hyperbolic tree.
Chapter 29 Interaction design

28. Chapter 29 Interaction design
Colour displays
Colour adds an extra dimension to an interface and can help the user understand complex information structures.
Colour can be used to highlight exceptional events.
Common mistakes in the use of colour in interface design include:
The use of colour to communicate meaning;
The over-use of colour in the display.
Chapter 29 Interaction design

29. Chapter 29 Interaction design
Colour use guidelines
Limit the number of colours used and be conservative in their use.
Use colour change to show a change in system status.
Use colour coding to support the task that users are trying to perform.
Use colour coding in a thoughtful and consistent way.
Be careful about colour pairings.
Chapter 29 Interaction design

30. Chapter 29 Interaction design
Error messages
Error message design is critically important. Poor error messages can mean that a user rejects rather than accepts a system.
Messages should be polite, concise, consistent and constructive.
The background and experience of users should be the determining factor in message design.
Chapter 29 Interaction design

31. Design factors in message wording
Chapter 29 Interaction design

32. Chapter 29 Interaction design
User error
Assume that a nurse misspells the name of a patient whose records he is trying to retrieve.
Chapter 29 Interaction design

33. Good and bad message design
Chapter 29 Interaction design

34. Chapter 29 Interaction design
The UI design process
UI design is an iterative process involving close liaisons between users and designers.
The 3 core activities in this process are:
User analysis. Understand what the users will do with the system;
System prototyping. Develop a series of prototypes for experiment;
Interface evaluation. Experiment with these prototypes with users.
Chapter 29 Interaction design

35. Chapter 29 Interaction design
The design process
Chapter 29 Interaction design

36. Chapter 29 Interaction design
User analysis
If you don’t understand what the users want to do with a system, you have no realistic prospect of designing an effective interface.
User analyses have to be described in terms that users and other designers can understand.
Scenarios where you describe typical episodes of use, are one way of describing these analyses.
Chapter 29 Interaction design

37. User interaction scenario
Jane is a student of Religious Studies and is working on an essay on Indian architecture and how it has been influenced by religious practices. To help her understand this, she would like to access some pictures of details on notable buildings but can’t find anything in her local library.
She approaches the subject librarian to discuss her needs and he suggests some search terms that might be used. He also suggests some libraries in New Delhi and London that might have this material so they log on to the library catalogues and do some searching using these terms. They find some source material and place a request for photocopies of the pictures with architectural detail to be posted directly to Jane.
Chapter 29 Interaction design

38. Requirements from the scenario
Users may not be aware of appropriate search terms so need a way of helping them choose terms.
Users have to be able to select collections to search.
Users need to be able to carry out searches and request copies of relevant material.
Chapter 29 Interaction design

39. User interface prototyping
The aim of prototyping is to allow users to gain direct experience with the interface.
Without such direct experience, it is impossible to judge the usability of an interface.
Prototyping may be a two-stage process:
Early in the process, paper prototypes may be used;
The design is then refined and increasingly sophisticated automated prototypes are then developed.
Chapter 29 Interaction design

40. Chapter 29 Interaction design
Paper prototyping
Work through scenarios using sketches of the interface.
Use a storyboard to present a series of interactions with the system.
Paper prototyping is an effective way of getting user reactions to a design proposal.
Chapter 29 Interaction design

41. User interface evaluation
Some evaluation of a user interface design should be carried out to assess its suitability.
Full scale evaluation is very expensive and impractical for most systems.
Ideally, an interface should be evaluated against a usability specification. However, it is rare for such specifications to be produced.
Chapter 29 Interaction design

42. Chapter 29 Interaction design
Usability attributes
Chapter 29 Interaction design

43. Chapter 29 Interaction design
Key points
User interface design principles should help guide the design of user interfaces.
Interaction styles include direct manipulation, menu systems form fill-in, command languages and natural language.
Graphical displays should be used to present trends and approximate values. Digital displays when precision is required.
Colour should be used sparingly and consistently.
Chapter 29 Interaction design

44. Chapter 29 Interaction design
Key points
The user interface design process involves user analysis, system prototyping and prototype evaluation.
The aim of user analysis is to sensitise designers to the ways in which users actually work.
UI prototyping should be a staged process with early paper prototypes used as a basis for automated prototypes of the interface.
The goals of UI evaluation are to obtain feedback on how to improve the interface design and to assess if the interface meets its usability requirements.
Chapter 29 Interaction design