Lecture: 14-15
Human-Computer Interaction
Adnan Bashir
Interaction design basics
Today’s Outline
• Interaction Design Basics
• Interactions And Intervention
• what is design
• Persona
• Central message
• The process of design
interaction design basics
• design:
• what it is, interventions, goals, constraints
• the design process
• what happens when
• users
• who they are, what they are like …
• scenarios
• rich stories of design
• navigation
• finding your way around a system
• iteration and prototypes
• never get it right first time!
interactions and interventions
design interactions not just interfaces
not just the immediate interaction
e.g. stapler in office – technology changes interaction style
• manual: write, print, staple, write, print, staple, …
• electric: write, print, write, print, …, staple
designing interventions not just artefacts/objects
not just the system, but also …
• documentation, manuals, tutorials
• what we say and do as well as what we make
what is design?
what is design?
achieving goals within constraints
• goals - purpose
• who is it for, why do they want it
• constraints
• materials, platforms
• trade-offs/compromises
golden rule of design
understand your materials
for Human–Computer Interaction
understand your materials
• understand computers
• limitations, capacities, tools, platforms
• understand people
• psychological, social aspects
• human error
• and their interaction …
To error is human
• accident reports ..
• aircrash, industrial accident, hospital mistake
• enquiry … blames … ‘human error’
• but …
• concrete lintel/support breaks because too much weight
• blame ‘lintel error’ ?
… no – design error
we know how concrete behaves under stress
• human ‘error’ is normal
• we know how users behave under stress
• so design for it!
• treat the user at least as well as physical materials!
Central message …
the user
The process of design
scenarios
what is task analysis
wanted guidelines
principles
interviews analysis precise
ethnography specification
design
what is there
vs. dialogue implement
what is wanted notations and deploy
evaluation
prototype
heuristics architectures
documentation
help
Steps …
• requirements
• what is there and what is wanted …
• analysis
• ordering and understanding
• design
• what to do and how to decide
• iteration and prototyping
• getting it right … and finding what is really needed!
• implementation and deployment
• making it and getting it out there
… but how can I do it all ! !
• limited time design trade-off
• usability?
• finding problems and fixing them?
• deciding what to fix?
• a perfect system is badly designed
• too good too much effort in design
user focus
know your user
Personae/Identities
cultural probes/analysis/investigation
know your user
• who are they?
• probably not like you!
• talk to them
• watch them
• use your imagination
persona
• description of an ‘example’ user
• not necessarily a real person
• use as surrogate/substitute user
• what would Betty think
• details matter
• makes her ‘real’
example persona
Betty is 37 years old,
She has been Warehouse Manager for five years and worked for Simpkins Brothers
Engineering for twelve years,
She didn’t go to university, but has studied in her evenings for a business diploma.
She has two children aged 15 and 7 and does not like to work late,
She did part of an introductory in-house computer course some years ago, but it
was interrupted when she was promoted and could no longer afford to take the
time,
Her vision is perfect, but her right-hand movement is slightly restricted following
an industrial accident 3 years ago,
She is enthusiastic about her work and is happy to delegate responsibility and take
suggestions from her staff,
However, she does feel threatened by the introduction of yet another new
computer system.
Talk to users
• It is hard to get yourself inside someone else’s head, so the best thing
is usually to ask them
• This can take many forms: structured interviews about their job or
life, open-ended discussions, or bringing the potential users fully into
the design process.
• People may also be able to tell you about how things really happen,
not just how the organization says they should happen.
• To encourage users to tell you this, you will need to win their trust,
since often the actual practices run counter to corporate policy.
cultural probes/inquiry
• direct observation
• sometimes hard
• in the home
• psychiatric patients, …
• probe packs
• items to prompt responses
• e.g. glass to listen at wall, camera, postcard
• given to people to open in their own environment
they record what is meaningful to them
• used to …
• inform interviews, prompt ideas, enculture designers
scenarios
stories for design
use and reuse
Scenarios
• Scenarios are stories for design: rich stories of interaction.
• Communicate with others - other designers, clients or
users. It is easy to misunderstand each other while
discussing abstract ideas. Concrete examples of use are far
easier to share.
• Validate other models - A detailed scenario can be ‘played’
against various more formal representations such as task
models or dialog and navigation models.
Scenarios
• Express dynamics Individual screen shots and pictures give
you a sense of what a system would look like, but not how it
behaves.
• Scenarios are linear – they represent a single path amongst
all the potential interactions.
• Time is linear Our lives are linear as we live in time and so
we find it easier to understand simple linear
narratives/story/description. We are natural storytellers and
story listeners.
Scenarios
• But no alternatives Real interactions have choices, some
made by people, some by systems. A simple scenario does
not show these alternative paths. In particular, it is easy to
miss the unintended things a person may do.
• what will users want to do?
• step-by-step walkthrough
• what can they see (sketches, screen shots)
• what do they do (keyboard, mouse etc.)
• what are they thinking?
… explore the depths
• explore interaction
• what happens when
• explore cognition
• what are the users thinking
• explore architecture
• what is happening inside
use scenarios to ..
• communicate with others
• designers, clients, users
• validate other models
• ‘play’ it against other models
• express dynamics
• screenshots – appearance
• scenario – behaviour
the systems
info and help management messages
start
navigation design add user remove user
local structure – single screen
global structure – whole site
main remove
confirm
screen user
add user
Levels
• widget choice
• menus, buttons etc.
• screen design
• application navigation design
• environment
• other apps, O/S
The web …
• widget choice • elements and tags
– <a href=“...”>
• screen design • page design
• navigation design • site structure
• environment • the web, browser,
external links
Physical devices
• widget choice • controls
– buttons,
• screen design knobs/handles,
• navigation design dials
• environment • physical layout
• modes of device
• the real world
Think about structure
• local
• looking from this screen out
• global
• structure of site, movement between screens
• wider still
• relationship with other applications
local
from one screen looking out
goal seeking
goal
start
goal seeking
goal
start
progress with local knowledge only ...
goal seeking
goal
start
… but can get to the goal
goal seeking
goal
start
… try to avoid these bits!
four golden rules
• knowing where you are
• knowing what you can do
• knowing where you are going
• or what will happen
• knowing where you’ve been
• or what you’ve done
where you are – breadcrumbs
shows path through web site hierarchy
top level category sub-category
web site this page
live links
to higher
levels
Beware the big button trap
things other things
the thing from
more things
outer space
• where do they go?
• lots of room for extra text!
modes
• lock to prevent accidental use …
• remove lock - ‘c’ + ‘yes’ to confirm
• frequent practiced action
• if lock forgotten
• in pocket ‘yes’ gets pressed
• goes to phone book
• in phone book …
‘c’ – delete entry
‘yes’ – confirm
… oops !
global
between screens
within the application
hierarchical diagrams
the system
info and help management messages
add user remove user
Think about dialogue
what does it mean in UI design?
Minister: do you name take this woman …
Man: I do
Minister: do you name take this man …
Woman: I do
Minister: I now pronounce you man and wife
Think about dialogue
what does it mean in UI design?
Minister: do you name take this woman …
• marriage service
• general flow, generic – blanks for names
• pattern of interaction between people
• computer dialogue
• pattern of interaction between users and system
• but details differ each time
network diagrams
main remove
confirm
screen user
add user
• show different paths through system
network diagrams ctd.
• what leads to what
• what happens when
• including branches
• more task oriented then hierarchy
main remove
confirm
screen user
add user
wider still
between applications
and beyond ...
wider still …
• style issues:
• platform standards, consistency
• functional issues
• cut and paste
• navigation issues
• embedded applications
• links to other apps … the web
Dix , Alan
Finlay, Janet
Abowd, Gregory
Beale, Russell
screen design and layout
basic principles
grouping, structure, order
alignment
use of white space
ABCDEFGHIJKLM
NOPQRSTUVWXYZ
basic principles
•ask
• what is the user doing?
•think
• what information, comparisons, order
•design
• form follows function
available tools
•grouping of items
•order of items
•decoration - fonts, boxes etc.
•alignment of items
•white space between items
grouping and structure
logically together physically together
Billing details: Delivery details:
Name Name
Address: … Address: …
Credit card no Delivery time
Order details:
item quantity cost/item cost
size 10 screws (boxes) 7 3.71 25.97
…… … … …
order of groups and items
• think! - what is natural order
• should match screen order!
• use boxes, space etc.
• set up tabbing/labeling right!
• instructions
• beware the cake recipie syndrome/condition!
… mix milk and flour, add the fruit
after beating them
decoration
• use boxes to group logical items
• use fonts for emphasis, headings
• but not too many!!
ABCDEFGHIJKLM
NOPQRSTUVWXYZ
alignment - text
• you read from left to right (English and European)
align left hand side
Willy Wonka and the Chocolate Factory
boring but
Winston Churchill - A Biography readable!
Wizard of Oz
Xena - Warrior Princess
Willy Wonka and the Chocolate Factory
Winston Churchill - A Biography
Wizard of Oz
fine for special effects Xena - Warrior Princess
but hard to scan
alignment - names
• Usually scanning for surnames make it easy!
Alan Dix
Janet Finlay
Gregory Abowd
Dix , Alan
Finlay, Janet
Russell Beale Abowd, Gregory
Beale, Russell
Alan Dix
Janet Finlay
Gregory Abowd
Russell Beale
alignment - numbers
think purpose! 532.56
179.3
which is biggest?
256.317
15
73.948
1035
3.142
497.6256
alignment - numbers
visually: 627.865
long number = big number
1.005763
align decimal points
382.583
or right align integers 2502.56
432.935
2.0175
652.87
56.34
multiple columns
• scanning across gaps hard:
(often hard to avoid with large data base fields)
sherbert 75
toffee 120
chocolate 35
fruit gums 27
coconut dreams 85
multiple columns - 2
• use leaders
sherbert 75
toffee 120
chocolate 35
fruit gums 27
coconut dreams 85
multiple columns - 3
• or greying (vertical too)
sherbert 75
toffee 120
chocolate 35
fruit gums 27
coconut dreams 85
multiple columns - 4
• or even (with care!) ‘bad’ alignment
sherbert 75
toffee 120
chocolate 35
fruit gums 27
coconut dreams 85
white space - the counter
WHAT YOU SEE
THE GAPS BETWEEN
space to separate
space to structure
space to highlight
physical controls
• grouping of items
• defrost settings
defrost settings
• type of food
•type ofcook
time to food
time to cook
physical controls
• grouping of items
• order of items
1) type of heating
1) type of heating
2) temperature 1
2) temperature
3) time to cook
3)
4) time
start to cook
2
4) start
3
4
physical controls
• grouping of items
• order of items
• decoration
• different colours
different coloursfor
for different functions
•different functions
lines around related
buttons
lines around related
buttons (temp up/down)
physical controls
• grouping of items
• order of items
• decoration
• alignment
• centered text in buttons
? easy to scan ?
centred text in buttons
? easy to scan ?
physical controls
• grouping of items
• order of items
• decoration
• alignment
• white space
• gaps to aid grouping
gaps to aid grouping
user action and control
entering information
knowing what to do
affordances
entering information
Name: Alan Dix
• forms, dialogue boxes Address: Lancaster
• presentation + data input
• similar layout issues Name: Alan Dix
• alignment - different label lengths
Address: Lancaster
• logical layout
• use task analysis
• groupings
• natural order for entering information
?
Name: Alan Dix
Address: Lancaster
• top-bottom, left-right (depending on culture)
• set tab order for keyboard entry
N.B. see extra slides for widget choice
knowing what to do
• what is active/dynamic/animated
• what is passive/nonresistent/long suffering
• where do you click
• where do you type
• consistent style helps
• e.g. web underlined links
• labels and icons
• standards for common actions
• language – bold = current state or action
affordances
mug handle
• psychological term
• for physical objects ‘affords’
grasping
• shape and size suggest actions (arrow)
• pick up, twist, throw
• also cultural – buttons ‘afford’ pushing
• for screen objects
• button–like object ‘affords’ mouse click (w machine knob)
• physical-like objects suggest use (ball pen style)
• culture of computer use
• icons ‘afford’ clicking
• or even double clicking … not like real buttons!
appropriate appearance
presenting information
aesthetics and utility
colour and 3D
localisation & internationalisation
presenting information
• purpose matters
name size
• sort order (which column, numeric alphabetic)
• text vs. diagram chap10
chap1 17
12
chap10
chap5 12
16
• scatter graph vs. histogram (a diagram consisting of rectangles)
chap11
chap1 51
17
chap12
chap14 262
22
• use paper presentation principles! chap13
chap20 83
27
chap14
chap8 22
32
…… …
• but add interactivity
• softens design choices
• e.g. re-ordering columns
• ‘dancing histograms’
aesthetics and utility
• aesthetically pleasing designs
• increase user satisfaction and improve productivity
• beauty and utility may conflict
• mixed up visual styles easy to distinguish
• clean design – little differentiation confusing
• backgrounds behind text
… good to look at, but hard to read
• but can work together
• e.g. the design of the counter
• in consumer products – key differentiator (e.g. iMac)
colour and 3D
• both often used very badly!
• colour
• older monitors limited palette (the range of colours used by a particular artist or in a particular picture)
• colour over used because ‘it is there’
• beware colour blind!
• use carefully to reinforce other information
• 3D effects
• good for physical information and some graphs
• but if over used …
e.g. text in perspective!! 3D pie charts
bad use of colour
• over use - without very good reason (e.g. kids’ site)
• colour blindness
• poor use of contrast
• do adjust your set!
• adjust your monitor to greys only
• can you still read your screen?
across countries and cultures
• localisation & internationalisation
• changing interfaces for particular cultures/languages
• globalisation
• try to choose symbols etc. that work everywhere
• simply change language?
• use ‘resource’ database instead of literal text
… but changes sizes, left-right order etc.
• deeper issues
• cultural assumptions and values
• meanings of symbols
e.g tick and cross … +ve and -ve in some cultures
… but … mean the same thing (mark this) in others
prototyping
iteration and prototyping
getting better …
… and starting well
prototyping
• you never get it right first time
• if at first you don’t succeed …
OK?
design prototype evaluate done!
re-design
pitfalls of prototyping
• moving little by little … but to where
• Malvern's or the Matterhorn?
1. need a good start point
2. need to understand what is wrong
HCI in the software process
• Software engineering and the design process for interactive
systems
• Usability engineering
• Iterative design and prototyping
• Design rationale
the software lifecycle
• Software engineering is the discipline for understanding the
software design process, or life cycle
• Designing for usability occurs at all stages of the life cycle,
not as a single isolated activity
The waterfall model
Requirements
specification
Architectural
design
Detailed
design
Coding and
unit testing
Integration
and testing
Operation and
maintenance
Activities in the life cycle
Requirements specification
designer and customer try capture what the system is expected to provide can
be expressed in natural language or more precise languages, such as a task
analysis would provide
Architectural design
high-level description of how the system will provide the services required
factor system into major components of the system and how they are
interrelated needs to satisfy both functional and nonfunctional requirements
Detailed design
refinement of architectural components and interrelations to identify modules
to be implemented separately the refinement is governed by the
nonfunctional requirements
