§8-GOMS + Fitts’ Law + Hick's Law Flashcards

1
Q

Rule based evaluation in the waterfall model

A

evaluating and refining requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

list three techniques for rule based evaluation

A

GOMS with KLM
 Fitts’ law
 Hicks law

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Describe GOMS

A
  1. Describe user behaviour in terms of goals, operators, methods, selection rules
    - Goals: high level task that user is trying to accomplish
    - Operators: elementary perceptual, motor or cognitive acts,
    - Methods: any procedure which combines operators into a sequence to achieve one of the goals
    - Selection rules: used to decide on a particular method when multiple methods are available for accomplishing a particular goal.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Examples of GOMS

A

Editing a text:

  1. G - editing a manuscript, or, locating a line
  2. O – keystrokes, mouse clicks
  3. Methods – control F, enter search query, press next, click on line
  4. Selection rules (skim read text if very short, use Find and Replace if document is very large or unfamiliar)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Purpose of GOMS analysis

A
  1. To check that frequent goals can be achieved quickly
  2. Imposing a hierarchy on operators
    - confirm that UI contains all needed functions
    - that similar tasks are performed similarly
    => coverage, consistency
    - determine operator sequencing – the order in which individual operations are done

issues with GOMS analysis:

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Explain how interacting with a GUI can be considered in terms of GOMS

A

Involves:

  1. establishing a goal ~ editing a text
  2. forming an intention/sub-goal (~ deleting a phrase)
  3. specifying a sequence of actions (= a method)
  4. executing the actions
  5. perceiving the state of the system
  6. interpreting/inferring from the state of the system
  7. evaluating the state of the system with respect to the goals and intentions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Steps needed to perform GOMS analysis

A
  1. Generate the task description by
    - picking a high level user Goal
    - write Methods for reaching the goal which may invoke sub-goals
    - write Methods for sub-goals
    - decomposition into sub-goals is recursive and stops when Operators are reached
  2. evaluate your description of the task (KLM calculations, Hicks/Fitts)
  3. Apply the results to the user interface (decide among alternative methods)
    (4. Iterate)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Draw a diagram reducing the goal of editing a text to subgoals, operators and methods (LABELLING)

A

cf with p9 of §8

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

issues related to GOMS models in general

A
  1. lowest level operators should have constant execution time for a particular user
  2. predict time taken for a user/computer to perform the task – sum the serial operators that the task comprises
  3. GOMS allows ``prediction” of time taken for a user to perform a particular task when using a GIVEN GUI DESIGN (… comparison, assumption shouldn’t change …)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

issues about GOMS KLM (keystroke level model) + what is it

A
  1. Operators are said to be `keystroke-level’ if they are at a level of actions like pressing keys, moving mouse, pressing buttons.
  2. a standard set of operators whose (relative) execution times have been estimated from experimental data
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What are the standard set of five operators in the GOMS KLM?

A
KP, H, M, R
Keying
Pointing
Homing
Mentally preparing
Responding (computer, that is)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Keying

A

The time it takes to tap a key on the keyboard or click a mouse button

Not independent of what is being typed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Pointing

A

Time it takes user to point to a position on a display

excludes button press

Depends on accuracy, target distance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Homing

A

Time taken for user’s hand to move from keyboard to mouse or vice versa

Targets are large, movement is well practiced,

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Mentally preparing

A

time taken for user to prepare for next step

depends on cognitive processes involved

e. g.
- remembering a filename
- finding something on the screen

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Responding

A

the time that a user must wait for a computer to respond to input

  • if response seems to have occurred then the user is likely to become uneasy – therefore important for interfaces to provide feedback if delays are unavoidable (e.g. progress bar that accurately reflects time remaining else unease again)
17
Q

Things to remember when doing KLM calculations in the exam

A
  1. spell out assumptions e.g. “assume focus is on the dialog box, so typing on the keyboard will enter text in the text field directly”
  2. one K for each keypress
  3. H when switching from keyboard/mouse and back
  4. use consistent rules for deciding when to insert Ms
  5. spell out assumptions about the initial state (e.g. hand is on the keyboard, current state of the system)
  6. Be consistent in the assumptions used – the whole point of rule based evaluation is for COMPARISONS of alternative designs – limited in use for predictions
  7. ** choose the design which requires the shortest time under the same set of assumptions
18
Q

Examples of KLM calculations (***********DO THE ONES ON THE SLIDES and compare your answers)

A
  1. UI in correct state, just need to enter the keystrokes
  2. hand on keyboard, wrong button selected
  3. presenting partial result as it is typed
  4. textual prompt
  5. ignore time to read and understand what needs to be done – ask user “are you ready to perform the task” before we start timing.
19
Q

List of six activities that require an M

A

listing the gestures is unambiguous given precise statement of the initial conditions (K, L, M = gestures)

Examples of activities that take an M:

  1. initiating a task
  2. making a strategy decision
  3. retrieving a chunk from memory
  4. finding something on the screen
  5. thinking of a task parameter
  6. verifying that an action is correct
20
Q

6 heuristics for placing mental preparation operations

A

Follow in sequence:
0 – initial insertion of candidate Ms
1 – deletion of anticipated Ms
2 – deletion of Ms within cognitive units
3 – deletion of Ms before consecutive terminators
4 – deletion of Ms that are terminators of a command
5 – deletion of overlapped Ms

21
Q

rule0: initial insertion of candidate Ms

A
  1. Insert M in front of all Ks
  2. Place Ms in front of any P that selects a command
  3. do not place Ms in front of any Ps that point to arguments of those commands

P -> MP
K -> MP
unless P selects args for command rather than command itself

22
Q

rule1: deletion of anticipated Ms

A
  1. delete M if the operator after is fully anticipated by the operator before

e.g. move mouse with intent of tapping button when reach the target
MPMK –> MPK

MAMB -> MAB
if B is fully anticipated by A

23
Q

rule2: deletion of Ms within cognitive units

A

if a string of Ms belongs to the same cognitive unit then delete all but the first

MKMKMK -> MKKK

if the three keystrokes are part of the same cognitive unit

a cognitive unit is a contiguous sequence of typed characters that form a command name, or that is required as an argument to a command

24
Q

rule3: deletion of Ms before consecutive terminators

A

Delete Ms that occur before a redundant delimiter of a cognitive unit

or if there are multiple keys in the delimiter (ctrl alt del, then delete Ms between the keystrokes in the delimiter)

(…) = delimiter
M(KMKMKMK) -> M(KKKK)

25
Q

rule4: deletion of Ms that are terminators of a command

A

If K is a delimiter following a constant string (e.g. command name) then delete M in front of it

delete M before K for enter after a command

**but keep M before K if the string was not well known / an argument – we think for a bit before committing an argument

** but delete if the string was not an argument or was a constant (we don’t think after typing ls -la before pressing enter)

26
Q

rule5: deletion of overlapped Ms

A

delete any Ms that overlap an R – a delay with the user waiting for a response from the computer

27
Q

What can GOMS model

A
  1. helps in comparing different UI designs
  2. task must be goal directed, can’t model creative activities
  3. task must be a routine cognitive skill rather than problem solving; good for machine operators
28
Q

Pros of GOMS

A
  1. qualitative measures (comparison, identifying subgoals, …) and quantitative measures (time predictions and comparisons)
  2. less work than in-lab user observation – no users
  3. easy to modify when the UI is revisited (since underlying timings/KLM operators are the same)
29
Q

Cons of GOMS

A
  1. rule based evaluation is more complex than heuristic evaluation
  2. time/effort
  3. only works for goal directed tasks
  4. assumes tasks with expert performance, ignores role of error
  5. does not address many UI issues – readability, ease of memorising icons, commands.
  6. does not model learning/increasing proficiency over time/changes in workflows
30
Q

Define Fitts’ Law

A
  • empirical model of estimated movement time to select a target on a computer display
  • define D, S, a, b, MT
  • a, b are empirically derived constants
  • D is distance to target centre
  • S is size of target
    ID = lg(D/S + 1), index of difficulty, independent of user.

MT = a + b ID

MT increases with smaller S, larger D

smaller ID -> “easier”

coefficients a, b in Fitts law are mainly determined by the pointing device and is fairly uniform across users

31
Q

Define Hicks Law

A
  • empirically models the time to make a selection decision
  • the more choices of a given kind you have, the longer it takes you to come to a decision

DT = a + b lg(n+1)

where n = # choices

coefficients a, b in Hick’s law are user dependent – how the choices are presented, and how habituated to the system the user has become

choices presented in a confusing manner? -> both a and b increase

habituation decreases b (dependence upon number of choices) ~~ for a given number of choices, time decreases over time; marginal increase in decision time arising from new choices decreases over time.

32
Q

Applicability of Fitts law

A
  1. assumes rapid, aimed movement (not drawing, writing)
  2. movement time is a function of the distance moved and precision demanded by the size of the target
  3. precision is measured by the target’s index of difficulty
  4. only applies to motions that are small relative to human body size and that are uninterrupted (i.e. can be made in one continuous motion) – usually reasonable for most GUIs
  5. assists in estimating operator execution time, choice of object sizes
  6. may also be used to evaluate input devices
33
Q

Apply Fitts law to larger icons on MS toolbar

A
  • larger icons -> lower time
  • recall -> recognition
  • … is one reason why labelled tools can be accessed faster
34
Q

Implications of Hick’s law for design

A
  1. more stimuli/choices faced -> longer it takes for users to make a decision