User interface design

Designing effective interfaces for software systems Objectives

To suggest some general design principles for user interface design To explain different interaction styles To introduce styles of information presentation To introduce usability attributes and system approaches to system evaluation

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 1

The user interface

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 Most users of business systems interact with these systems through graphical user interfaces (GUIs) In some cases, legacy text-based interfaces are still used
Software Engineering, 6th edition. Chapter 15 Slide 2

Ian Sommerville 2000

GUI characteristics
Characteris ti c Win dows Icon s Men us Po int ing Graph ics Des cripti on Multiple windows allow different information t o be displayed simult aneously on th e users screen. Icon s differen t ty pes of informationOn . some sy st ems, icon s represent files; on ot hers, icon s represen t processes. Co mmands are select ed fro m a menu rat her than t yped in a command lan guage. A point ing device such as a mo use is used for select ing ch oices from a men u or indicat ing it ems o f in terestin a window. Graph ical elemen ts can be mix ed wit h text on t he same display.

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 3

GUI advantages

They are easy to learn and use.

Users without experience can learn to use the system quickly.

The user may switch quickly from one task to another and can interact with several different applications.
Information remains visible in its own window when attention is switched.

Fast, full-screen interaction is possible with immediate access to anywhere on the screen
Software Engineering, 6th edition. Chapter 15 Slide 4

Ian Sommerville 2000

User interface design process

Analyse and understand user activities Produce paperbased design prototype Evaluate design with end-users

Design prototype

Produce dynamic design prototype

Evaluate design with end-users

Executable prototype

Implement final user interface

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 5

UI design principles

User familiarity
The interface should be based on user-oriented terms and concepts rather than computer concepts E.g., an office system should use concepts such as letters, documents, folders etc. rather than directories, file identifiers, etc. The system should display an appropriate level of consistency Commands and menus should have the same format, command punctuation should be similar, etc. If a command operates in a known way, the user should be able to predict the operation of comparable commands
Software Engineering, 6th edition. Chapter 15 Slide 6

Consistency

Minimal surprise

Ian Sommerville 2000

UI design principles (cont.)

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. Some user guidance such as help systems, on-line manuals, etc. should be supplied Interaction facilities for different types of user should be supported E.g., some users have seeing difficulties and so larger text should be available
Software Engineering, 6th edition. Chapter 15 Slide 7

User guidance

User diversity

Ian Sommerville 2000

User-system interaction

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

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 8

Interaction styles

Direct manipulation
Easiest to grasp with immediate feedback Difficult to program User effort and errors minimized Large numbers and combinations of choices a problem Ease of use, simple data entry Tedious, takes a lot of screen space Easy to program and process Difficult to master for casual users Great for casual users Tedious for expert users
Software Engineering, 6th edition. Chapter 15 Slide 9

Menu selection

Form fill-in

Command language

Natural language

Ian Sommerville 2000

Information presentation

Information presentation is concerned with presenting system information to system users The information may be presented directly or may be transformed in some way for presentation The Model-View-Controller approach is a way of supporting multiple presentations of data

Information to be displayed

Presentation software

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Display

Slide 10

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?
Software Engineering, 6th edition. Chapter 15 Slide 11

Ian Sommerville 2000

Analog vs. digital presentation

Digital presentation
Compact - takes up little screen space Precise values can be communicated Easier to get an 'at a glance' impression of a value Possible to show relative values Easier to see exceptional data values

Analog presentation

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 12

Alternative information presentations

Jan 2842 4000 Feb Mar 2851 3164 April 2789 May 1273 June 2835

3000

2000

1000

0 Jan
Ian Sommerville 2000

Feb

Mar

April

May

June
Slide 13

Software Engineering, 6th edition. Chapter 15

Information display
1 4 3 2 0 10 20

Dial with needle

Pie chart

Thermometer

Horizontal bar

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 14

Displaying relative values

Pressure 0 100 200 300 400 0 25

T emper atu re 50 75 100

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 15

Textual highlighting

!
Ian Sommerville 2000

The filename you have chosen h as been used. Please choose an other name Ch. 16 User interface design OK Cancel

Software Engineering, 6th edition. Chapter 15

Slide 16

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 State of a telephone network Chemical plant pressures and temperatures A model of a molecule Hyperweb

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 17

Colour displays

Colour adds an extra dimension to an interface and can help the user understand complex information structures Can be used to highlight exceptional events What are some common mistakes in the use of colour?
The use of colour to communicate meaning Over-use of colour in the display

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 18

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

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 19

Nurse input of a patients name

Please type t he patient name in t he bo Bates , J.

x the n c lick onOK

OK

Cancel

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 20

System and user-oriented error messages

System-or iented err or messag e

User -o rien ted er ror messag e

?
OK

Er ror #27 Invalid patient id entered

Patient J . Bates is n ot r egistered Clic k onP atien ts f or a l ist of register ed patie nts Click on Retr y to re-input a patient name Click on Help f or more information Patients Help Retry Cance l

Cancel

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 21

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

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 22

Usability attributes
Attribute Learnability Speed of operat ion Robust ness Recoverability Adapt ability Des cripti on How long does it t ake a new user to become product ive with t he system? How well does t he system response match t he users work practice? How t olerant is the syst em of user error? How good is t he syst em at recovering from user errors? How closely is t he system t ied t o a single model of work?

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 23

Simple evaluation techniques

Questionnaires for user feedback Video recording of system use and subsequent tape evaluation. Instrumentation of code to collect information about facility use and user errors. The provision of a gripe button for on-line user feedback.

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 24

Key points

Interface design should be user-centred. An interface should be logical and consistent and help users recover from errors 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
Software Engineering, 6th edition. Chapter 15 Slide 25

Ian Sommerville 2000

Key points

Ideally, a user interface should be evaluated against a usability specification What about help for the user?
Systems should provide on-line help. This should include help, Im in trouble and help, I want information A range of different types of user documents should be provided

Ian Sommerville 2000

Software Engineering, 6th edition. Chapter 15

Slide 26