HCI-chapter 4
HCI-chapter 4
HCI-chapter 4
Human-Computer Interaction
(HCI)
Chapter Four
Interaction
1
The Interaction
• Interaction models
– translations between user and system
• Ergonomics
– physical characteristics of interaction
• Interaction styles
– the nature of user/system dialog
• Context
– social, organizational, motivational
Why study interaction models?
• Help us to understand what is going on in
the interaction between user and system
• Help us to identify problematic areas within
the design
• Address differences, if any, between what
user wants and system does
3
What is interaction?
Communication between the user and
the system
user system
Models of Interaction
Terms of interaction Norman
model Interaction framework
Some terms of interaction
Domain – the area of work under study
e.g. graphic design
Goal – what you want to achieve
e.g. create a solid red triangle
Task – how you go about doing it
Intention – ultimately in terms of operations or actions
e.g. … select fill tool, click over triangle
Note …
– traditional interaction …
– use of terms differs a lot especially task/goal !!!
Donald Norman’s model
• Seven stages
– user establishes the goal
– formulates intention
– specifies actions at interface
– executes action
– perceives system state
– interprets system state
– evaluates system state with respect to goal
• Norman‘s model concentrates on user‘s view
of the interface
User establishes the goal Move a sentence from one paragraph to
another paragraph in a WORD document
Formulates intention Use Edit menu to move a piece of text from one
paragraph to another (Shortcut keys can be used)
Evaluates system User knows that the goal has been completed
8
Execution/Evaluation loop
Goal
Execution Evaluatio
n
System
• User establishes the goal
• Formulates intention
• Specifies actions at interface
• Executes action
• Perceives system state
• Interprets system state
• Evaluates system state with respect to goal
Execution/Evaluation loop
Goal
Execution Evaluatio
n
System
• User establishes the goal
• Formulates intention
• Specifies actions at interface
• Executes action
• Perceives system state
• Interprets system state
• Evaluates system state with respect to goal
Execution/Evaluation loop
Goal
Execution Evaluation
System
• User establishes the goal
• Formulates intention
• Specifies actions at interface
• Executes action
• Perceives system state
• Interprets system state
• Evaluates system state with respect to goal
Execution/Evaluation loop
Goal
Execution Evaluatio
n
System
• User establishes the goal
• Formulates intention
• Specifies actions at interface
• Executes action
• Perceives system state
• Interprets system state
• Evaluates system state with respect to goal
Using Norman’s model
Some systems are harder to use than others
Gulf of Execution
user‘s formulation of actions
≠ actions allowed by the system
Gulf of Evaluation
user‘s expectation of changed system state
≠ actual presentation of this state
Gulfs of execution
• Mismatch between user‘s intention and actions allowed
by the system,
E.g.,
– The system does not support the user‘s goal
– Sequence of actions is invalid
• Does the interface allow us to carry out the actions
required by the intention?
E.g. Goal is to save a file
– Intention is to use the file menu
– Action is to click the save option
– Is there a save option in the file menu?
Gulfs of evaluation
• Mismatch between system‘s presentation and user‘s
expectation, e.g.,
– Failure to notice current system status
– Poor feedback from system
• Given a particular interface design, how easily can
you:
– Determine the function of the device?
– Determine whether the system is in the desired state?
– Determine what actions are possible?
– Perform the action?
15
Human error - slips and mistakes
Slip
understand system and goal correct formulation
of action
incorrect action
Mistake
may not even have right goal!
Fixing things?
slip – better interface design
mistake – better understanding of system
Abowd and Beale framework
Extension of Norman…
their interaction framework has 4 parts
– user
– input
– system
– output
Each has its own unique language
Interaction translation between
languages
problems in interaction = problems in
translation
Using Abowd & Beale’s model
user intentions
translated into actions at the interface
translated into alterations of system state
reflected in the output display
interpreted by the user
• use of colour
e.g. use of red for warning, green for okay,
awareness of colour-blindness etc.
Industrial interfaces
Context matters!
office industrial
type of data textual numeric
rate of change slow fast
environment clean dirty
• industrial interface:
– traditional … dials and knobs
– now … screens and keypads
• glass interface
+ cheaper, more flexible, Vessel B Temp
multiple representations,
precise values 200
0 100
– not physically located,
loss of context, complex 113
interfaces
• may need both
multiple representations
of same information
Indirect manipulation
• Familiar to user
• speech recognition or typed natural language
• Problems
– vague
– ambiguous
– hard to do well!
• Solutions
– try to understand a subset
– pick on key words
Query interfaces
• Question/answer interfaces
– user led through interaction via series of
questions
– suitable for novice users but restricted
functionality
– often used in information systems
• Query languages (e.g. SQL)
– used to retrieve information from database
– requires understanding of database structure and
language syntax, hence requires some expertise
Form-fills
• Primarily for data entry or data retrieval
• Screen like paper form.
• Data put in relevant place
• Requires
– good design
– obvious correction
facilities
Spreadsheets
• first spreadsheet VISICALC, followed by Lotus 1-
2-3
MS Excel most common today
• sophisticated variation of form-filling.
– grid of cells contain a value or a formula
– formula can involve values of other cells
e.g. sum of all cells in this column
– user can enter and alter data spreadsheet maintains
consistency
WIMP Interface
Windows
Icons
Menus
Pointers
… or windows, icons, mice, and pull-down menus!
• used in ..
– multimedia
– web browsers
– hypertext
• minimal typing
Three dimensional interfaces
• virtual reality
• ‗ordinary‘ window systems
– highlighting flat buttons …
– visual affordance
– indiscriminate use
click me!
just confusing!
• 3D workspaces … or sculptured
– use for extra
virtual space
– light and
occlusion give
depth
– distance
elements of the wimp interface
• scrollbars
– allow the user to move the contents of the window up and down
or from side to side
• title bars
– describe the name of the window
Icons
• important component
– WIMP style relies on pointing and selecting things
• uses mouse, trackpad, joystick, trackball, cursor keys or
keyboard shortcuts
• wide variety of graphical images
Menus
• Choice of operations or services offered on the
screen
• Required option selected with pointer
File Edit Options Font
Typewriter
Screen
Times
• Cascading menus
– hierarchical menu structure
– menu selection opens new menu
– and so in ad infinitum
• Keyboard accelerators
– key combinations - same effect as menu item
– two kinds
• active when menu open – usually first letter
• active when menu closed – usually Ctrl + letter
usually different !!!
Menus design issues
• Special kinds
– radio buttons
– set of mutually exclusive choices
– check boxes
– set of non-exclusive choices
Toolbars
• often customizable:
– choose which toolbars to see
– choose what options are on it
Palettes and tear-off menus
• Problem
menu not there when you want it
• Solution
palettes – little windows of actions
– shown/hidden via menu
option
e.g. available shapes in drawing package
tear-off and pin-up menus
– menu ‗tears off‘ to become
palette
Dialogue boxes
• WIMP exceptions …
pre-emptive parts of the interface
• modal dialog boxes
– come and won‘t go away!
– good for errors, essential steps
– but use with care
Error and repair
• other people
– desire to impress, competition, fear of failure
• motivation
– fear, allegiance, ambition, self-satisfaction
• inadequate systems
– cause frustration and lack of motivation
Managing value
BUT NOTE
• exceptions (e.g. habit)
• value NOT necessarily personal gain or
money
Weighing up value
value
• helps me get my work done
• fun
• good for others
cost
• download time
• money £, $, €
• learning effort
General lesson …
57
Why Study Paradigms?
Concerns
– How can an interactive system be developed to ensure its usability?
– How can the usability of an interactive system be demonstrated or
measured?
58
Paradigms of interaction
59
The initial paradigm
• Batch processing
Complete jobs processed individually.
Impersonal
computing
60
Example Paradigm Shifts
• Batch processing
• Time-sharing
Interactive
computing
61
Example Paradigm Shifts
???
Community
computing
Example Paradigm Shifts
• Networking
• Graphical displays % foo.bar
ABORT
dumby!!!
Direct manipulation
63
Example Paradigm Shifts
• Batch processing
• Timesharing
• Networking
• Graphical display
• Microprocessor
Personal computing
64
Example Paradigm Shifts
• Batch processing
• Timesharing
• Networking
• Graphical display
• Microprocessor
• WWW
Global
information
65
Example Paradigm Shifts
• Batch processing • A symbiosis of physical and
electronic worlds in service
• Timesharing of everyday activities.
• Networking
• Graphical display
• Microprocessor
• WWW
• Ubiquitous Computing
66
Exercise