Desktop Interaction C.W. Johnson, Univ ersit y of Glasgo w, - - PDF document

▶
desktop interaction c w johnson univ ersit y of glasgo w
SMART_READER_LITE
LIVE PREVIEW

Desktop Interaction C.W. Johnson, Univ ersit y of Glasgo w, - - PDF document

Jul 19, 2023 137 likes •336 views

Desktop Interaction C.W. Johnson, Univ ersit y of Glasgo w, Glasgo w, G12 8QQ. Scotland. johnson@dcs.gla.ac.uk, h ttp://www.dcs.gla .a c.uk/ johnso n Octob er 2001 c CS-1Q: HCI (Lecture 7) C.W. Johnson, 2001

slide-1
SLIDE 1 Desktop Interaction C.W. Johnson, Univ ersit y
  • f
Glasgo w, Glasgo w, G12 8QQ. Scotland. johnson@dcs.gla.ac.uk, h ttp://www.dcs.gla .a c.uk/ johnso n Octob er 2001 CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001 1
slide-2
SLIDE 2 Desktop Interaction
  • Ho
w do w e implement a desktop system?

STAGE 3 Summative Evaluation Operational Software Interface Benchmarking Formal Experimentation STAGE 2 Formative Evaluation Rapid Prototyping User-Defined Interfaces User-Acceptance Testing Design Objectives Task Analysis Focus On Users Design Guidelines Structured Walk-Through STAGE 1 Initial Design

  • Iterative
development and user-centred design CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-3
SLIDE 3 Desktop Interaction 1. consider users and en vironmen t; 2. design and sp ecication; 3. select dialogue st yle; 4. implemen tation issues; 5. do cumen tation issues; 6. ev aluation issues. CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-4
SLIDE 4 1. Consider Users and Environment
  • Home:
  • cluttered
with b
  • ks,
coee cups etc;
  • distractions
from radio,
  • ther
p eople etc. Ac kno wldgemen t: BBC
  • Oce:
  • time
p ressure to complete tasks;
  • need
to achieve closur e;
  • heat,
noise, interruptions, multiple tasks. CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-5
SLIDE 5 2. Design and Sp ecication
  • T
ask analysis lo
  • ks
from users' p
  • int
  • f
view.
  • Sp
ecications b egin to lo
  • k
at system b ehaviour:
  • fo
cus
  • n
what to do not how to do it.
  • State-transition
diagrams
  • ften
used. CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-6
SLIDE 6 2. Design and Sp ecication
  • States:
  • situations
where system continues to p erfo rm activit y;
  • change
from a state is triggered b y a transition;
  • rep
resented b y no des in the net w
  • rk.
  • T
ransitions:
  • edges
rep resent change b et w een states;
  • usually
triggered b y user actions;
  • can
b e lab elled b y frequency info rmation.
  • Can
do static analysis:
  • can
y
  • u
get from state A to B (reachabilit y);
  • maximum
  • f
N transitions from A to D (spanning). CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-7
SLIDE 7 3. Select Dialogue St yle
  • Dialogue
st yles:
  • text,
fo rms, menus, graphics, mixtures...
  • Dialogue
st yles rely
  • n
widgets:
  • lists,
choices and buttons;
  • checkb
  • xes
and radio buttons;
  • pull-do
wn, tea r-o, p
  • p-up,
scrolling, hyb rid menus CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-8
SLIDE 8 3. Select Dialogue St yle
  • Windo
ws:
  • titles,
b
  • rders
and frames, scroll ba rs.
  • Windo
wing actions:
  • p
en, move, close, resize, select, b ring fo rw a rd,
  • feedback
is crucial to all
  • f
these actions.
  • Some
very complex w eb-b ehaviours:
  • sp
  • ntaneously
  • p
ening a link ed windo w with a w eb page;
  • `where
  • n
ea rth did that come from?'
  • lots
  • f
securit y issues here
  • unsigned
applets. CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-9
SLIDE 9 3. Select Dialogue St yle
  • Windo
w managers b et w een applications.
  • La
y
  • ut
managers within an application.
  • Placement
issues:
  • multiple
  • verlapping
windo ws (ho w to select a windo w?);
  • tiling
strategies (eg p
  • w
erp
  • int
slide view);
  • zo
  • ming
(eg Acrobat page size);
  • ca
rd cascades etc. CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-10
SLIDE 10 4. Implementation Issues
  • Ho
w do y
  • u
get a widget in y
  • ur
co de?
  • T
  • lkits
such as A WT, Swing (o r JEWL). /* do NOT memorise this co de! */ /* T ry to understand what it is doing */ b1 = new Button(); // create a new button b1.setLab el("Disable middle button"); // put a piece
  • f
text in it b1.setActionCommand(DISABLE); // asso ciate a command with it
  • T
  • lkits
a re lib ra ries
  • f
p rograms:
  • thers
have written them to implement common widgets;
  • y
  • u
don't have to write co de to dra w a button etc;
  • can
b e dicult to change these p re-co ded widgets. CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-11
SLIDE 11 4. Implementation Issues
  • What
happ ens when button is click ed? public v
  • id
actionP erformed(ActionEv en t e) f String command = e.getActionCommand(); if (command == DISABLE) fg // b1 w as pressed so do whatev er y
  • u
need to g CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-12
SLIDE 12 4. Implementation Issues
  • User
interface p rogramming is skilled:
  • can
tak e 3-4 months to lea rn the basics.
  • Lots
  • f
to
  • ls
to simplify the p ro cess.
  • Direct
manipulation interface builder:
  • select
widget and place it
  • n
`screen';
  • system
automatically generates co de y
  • u
need;
  • can
b e inexible and inecient.
  • Microsoft
Visual Basic, Bo rland Delphi.
  • Also
scripting to
  • ls
such as Tcl/Tk. CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-13
SLIDE 13 5. Do cumentation Issues
  • Printed
manuals:
  • seldom
read, intimidating and go missing;
  • must
sta y
  • p
en at co rrect page while t yping;
  • must
leave ro
  • m
fo r the k eyb
  • a
rd and mouse!
  • Key
idea
  • f
minimal manuals:
  • sho
rt `get y
  • u
sta rted' summa ries;
  • lists
  • f
available commands and sho rt cuts. CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-14
SLIDE 14 5. Do cumentation Issues
  • On-line
tuto rials and manuals:
  • can
b e quite basic (Unix apropos/man) .
  • On-line
and context-sensitive help:
  • can
b e very dicult to navigate;
  • can
b e
  • ut
  • f
synch with soft w a re installation;
  • can
b e pitched at to
  • simple/complex
a level. CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-15
SLIDE 15 5. Do cumentation Issues
  • But
screen reading is tiring and erro r p rone.
  • The
infamous `Oce Assistant':
  • do
es anthrop
  • mo
rphism alw a ys supp
  • rt
users?
  • `Tip
  • f
the da y'
  • can
b e patronising. CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-16
SLIDE 16 6. Evaluation Issues
  • Recap
lecture 4:
  • what
is fo rmative evaluation?
  • what
is summative evaluation?
  • Recap
lecture 4:
  • name
  • ne
fo rmative technique?
  • name
  • ne
summative technique? CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001
slide-17
SLIDE 17 Summa ry 1. consider users and en vironmen t; 2. design and sp ecication; 3. select dialogue st yle; 4. implemen tation issues; 5. do cumen tation issues; 6. ev aluation issues. CS-1Q: HCI (Lecture 5) c
  • C.W.
Johnson, 2001
slide-18
SLIDE 18 F urther Reading
  • Shneiderman
  • n:
  • soft
w a re to
  • ls
  • pp.
155-179. CS-1Q: HCI (Lecture 7) c
  • C.W.
Johnson, 2001