Chapter 4 - Interaction

 Introduction

 Models of interaction

 Ergonomics

 Interaction styles
 Introduction
 HCI deals with how the human uses the computer as a tool to
perform, simplify or support a task
 Interaction is the communication between user and
system:
 There are a number of ways in which the user can
communicate with the system
 Batch input-user provides all the information to the computer at once
and leaves the machine to perform the task.
 Direct manipulation- user is constantly providing instruction and
receiving feedback. It is the type of interactive system
 d/t models of interaction that enable us to identify and evaluate
components of the interaction
 What is interaction?...
 Interaction involves two participants: the user and the
system
 Both are complex and are very different from each other
 Modeling the interaction between users and computers
helps us
 to understand exactly what is going on in the interaction
and
 To identify the likely root of difficulties
 To provide a framework to compare different interaction
styles and to consider interaction problems.
 Models Of Interaction
 Two common interaction models -
 DonaldNorman’s model
 Abowd and Beale framework
 Some terms in Interaction
 the purpose of an interactive system is to aid a user in
accomplishing goals from some application domain.
 Domain- area of expertise and knowledge in some real-
world activity eg. graphic design, Networking, electricity
 Tasks are operations/actions to manipulate the
concepts of a domain.
 A goal is the desired output from a performed task.
1. Donald Norman’s execution–evaluation
cycle
 Most influential model of interaction due to closeness
to our intuitive understanding of the interaction b/n
human & computer
 describe the interaction in terms of the goals and actions
of the user
 The Donald Norman’s interaction cycle divided into two
major phases:
 Execution and
 Evaluation which are further subdivided into seven stages
1. Norman’s execution–evaluation cycle…

 The stages in Norman’s model of interaction are as follows:

1. Establishing the goal. user’s notion of what needs to
be done
2. Forming the intention- defining more specific
objective
3. Specifying the action sequence.
4. Executing the action.
5. Perceiving the system state.
6. Interpreting the system state.
7. Evaluating the system state with respect to the goals
and intentions.
1. Norman’s execution–evaluation cycle…

Norman’s executing and evaluating cycles

1. Norman’s execution–evaluation cycle…

 Eg. switching on a light- Imagine you need more light

1) Goal:- to get more light
2) Intention:- to switch on the desk lamp
3) Actions sequence:- you or someone else closer will press the
lamp switch
4) Execution:- lamp switch pressed
5) Perceiving:- user observes the result (light is on or not)
6) Interpreting:- interpret this, if the light does not come on, you
may interpret this as indicating the bulb has blown or the lamp is
not plugged into the mains, and you will formulate new goals
7) Evaluating:- is there enough light? If so, the cycle is complete. If
not, you may formulate a new intention
1. Norman’s execution–evaluation cycle…

 Eg2. Deleting a unwanted folder

1) Goal:- to delete the folder in D drive
2) Intention:- to delete folder using short cut
3) Actions sequence:- navigate to folder location, select folder
4) Execution:- press CTRL+Delete keys
5) Perceiving:- user observes the result (folder is deleted or not)
6) Interpreting:- if folder is deleted, Short cut is efficient,
otherwise, folder needs other deleting methods.
7) Evaluating:- if folder deleted successfully, the goal accomplished,
otherwise formulate new intention and repeat the cycle.
 Models Of Interaction
 Norman demonstrated two problems caused by
interfaces :
 Gulfs of execution:- is the difference between the user’s
formulation of the actions to reach the goal and the
actions allowed by the system.
 Gulfs of evaluation:- is the distance between the physical
presentation of the system state and user expectation
 User and system do not use the same terms to
describe the domain and goals
 language of the system (core language) and the
language of the user (task language.)
 2. Abowd and Beale framework
Abowd and Beale framework
 Provides more realistic description of interaction by
including the system explicitly, and breaks it into four
main components
 System, User, Input and Output
 Each component has its own language
 User’s task language
 System’s core language
 Input and Output’s Interface(input/output) language
 Interface sits between the User and the System
 four steps in the interactive cycle, each involves 4
translation from one component to another: articulation,
performance, presentation and observation.
 2. Abowd and Beale framework …

 Translations between components

 2. Abowd and Beale framework …

 There are four steps in the interactive cycle, involves translation

from one component to another
 Input and Output together form the Interface.
 User begins interactive cycle with the formulation of a goal
and a task to achieve that goal
 Articulation - User’s formulation of the desired task to achieve
some goal needs using input language
 Performance - the interface translates the input language into
stimuli for the system (core language)
 Presentation - the system presents the results in the output
language
 Observation - the interface translates the output language into
personal understanding
 Ergonomics

 Is the study of the physical characteristics of

interaction
 how the controls are designed,
 the physical environment in which the interaction
takes place, and
 the layout and physical qualities of the screen

 Also known as human factors – but this can also be

used to mean much of HCI!
 Ergonomics good at defining standards and guidelines

for designing systems

 Ergonomics deals with:
 Arrangement of controls and displays
 e.g. controls grouped according to function or frequency of
use, or sequentially to allow rapid access.
 Surrounding environment
 e.g. seating arrangements adaptable to cope with all sizes of
user: sitting, standing or moving
 Health issues: possible consequences of our designs on the
health and safety of users.
 e.g. physical position, temperature, lighting, noise
 Use of colour
 e.g. use of red for danger & warning, green for okay,
yellow for standby etc.
 Interaction styles

 Common interaction styles

Command Line Interface (CLI)
Menus
Natural language
question/answer and query dialogue
form-fills and spreadsheets
WIMP
 Interaction styles…

 Command line interface

 Way of expressing instructions to the computer
directly using
function keys, single characters, short abbreviations,
whole words, or a combination
 Powerful, Quick, Flexible, and Suitable for repetitive
tasks
 Difficult for inexperienced users,
 Offers direct access to system functionality
 Typical example: Microsoft DOS, Unix system
 Interaction styles…

 Command line interface

 Interaction styles…

 Menus Driven Interface

Set of options displayed on the screen
Selection by:
numbers, letters, arrow keys, mouse
combination (e.g. mouse plus accelerators)
Often options hierarchically grouped
sensible grouping is needed
Restricted form of full WIMP system
 Menu Driven Interfaces
 Menu Driven Applications
 ATM
 Mobile Phone
 MP3 Player
 Video recorder
 Household Devices
 Digital/Cable TV
 Interaction styles…

 Natural language
 Normal speech(talk) recognised by a computer
 Speech recognition and typed input
 They use natural-language-style phrases to query
 Familiar to user
 Used by the disabled
 Interaction styles…

 Form-fills
 Primarily for data entry or data retrieval

 Screen like paper form.

 Data put in relevant place

 Requires good design

 Interaction styles…
 Query interfaces
 Question/answer interfaces
user asked series of questions
suitable for novice users
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
 Interaction styles…
 WIMP Interface
 often called windowing systems
 Windows, Icons, Menus, Pointers
… or windows, icons, mice, and pull-down menus!

 default style for majority of interactive computer

systems, especially PCs and desktop machines
 User friendly

 Easy to use
 Interaction styles…
 WIMP Interface
Good Interface Design

Users should be able to use an interface:

SAFELY Tasks can be completed without risk

EFFECTIVELY Being able to do the right task and do it well

EFFICIENTLY To carry out tasks quickly and correctly

Users should be able to enjoy what they

ENJOYABLY are doing, not be frustrated by the interface
Thank You!