03 The Interaction
03 The Interaction
03 The Interaction
the interaction
Introduction
goal
execution evaluation
system
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 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 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 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
The Norman’s Execution-Evaluation
cycle : Reasons Why Some Interfaces Cause
Problems to Users
• Gulf of Execution
– The difference between the user’s formulation of the
action to reach the goal and the actions allowed by the
system
– If the actions allowed by the system correspond to
those intended by the user, the interaction will be
effective
• Gulf of Evaluation
– The distance between the physical presentation of the
system state and the expectation of the user
– If the user can readily evaluate the presentation in
terms of his/her goal, the gulf of evaluation is small
• Interface design should aim to reduce the gulfs
The Norman’s Execution Evaluation
cycle : Human Error
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
Limitations
• Articulation Translation
• Articulation is the user's translation of their task
into the input language.
• Consider a user who wants to turn on the lights
at the far end of a room.
– Poor Articulation
• The user sees a bank of unlabelled switches. The
user has no idea which switch controls the lights
at the far end of the room.
• The problem here is that the language provided
(the unlabelled switches) does not allow the user
to articulate the goal (turn on the lights at the far
end of the room).
Cont…
– Good Articulation
• The switches are clearly labelled. The user
articulates their task of pressing the switch that is
labelled "the far end of the room".
• The language provided here (the labelled
switches) allows the user to articulate their task
without difficulty
Cont…
• Performance Translation
• Performance is the interface's translation of the
input language into stimuli to the system. This
translation is determined by the designer or
programmer (not the user).
– Poor Performance
• Consider a remote control for a television without
a button for turning off the television. The user
must go directly to the device and turn it off on
the control panel.
• Presentation Translation
• Presentation is the translation of the system's
new state into the output language of the
interface. This translation is determined by the
designer or programmer.
– Poor Presentation
• Consider writing an essay using a word processor. You need
to see the effects of your editing as a whole.
• However, the word processor only displays the immediate
paragraph without the surrounding text or other pages. The
surrounding text and other pages may have changed as well
during the editing. In effect, all of the state changes cannot
be displayed in the output language. You cannot readily
confirm the effect of your editing throughout the essay.
Using Abowd and Beale’s Model
• User Intensions
– Translated into actions at interface
– Translated into alteration of system state
– Reflected in the output display
– Interpreted by the user
• General Framework
ergonomics
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 0 100 200
multiple representations
of same information
Indirect manipulation
• Familiar to user
• speech recognition or typed natural language
• Problems
– Vague and ambiguous
• The boy hit the dog with the stick
• The word ‘pitch’ may refer to a sports field, a
throw,a waterproofing substance
– 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
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
– 3d interfaces for oculus rift
goggles
• 3D workspaces
– use for extra virtual space
– light and occlusion give depth flat buttons …
– distance effects
click me!
… or sculptured
tg4