Download Deliverable Template IMAT

ESPRIT 29175 IMAT R.IV.2
Scenarios and guidelines, version 2 Keystroke aspects
These questions are about menu­options, buttons, mouse­clicks etceteras.
Keystroke 1. Are there any intended actions, like “open” or “cut”, difficult or impossible to
carry out using the menu­options, buttons, mouse­clicks and keyboard?
Task
No Yes
If there are – can you specify these?
1
2
3
Keystroke 2. Are there any actions, like “close” or “save”, you can perform with the menu­
options, buttons, mouse­clicks and keyboard you are unfamiliar with?
Task
No Yes
If there are – can you specify these?
1
2
3
Keystroke 3. Is there an action (e.g. double­click) that has different results (e.g. select and
open)?
Task
No Yes
If there is – can you specify this?
1
2
3
Keystroke 4. Are there different ways, using different keystrokes (e.g. menu option and
double­click), to obtain a single result (e.g. open)?
Task
1
2
3
No Yes
If there are – can you specify these?
Process aspects
These questions are about series or sequences of user actions: the way things are done.
Process 1. Is the order of actions right? An example of a set of ordered actions is: you first
open a tool, then load a file, then edit the file and save it.
Task
No Yes
If the is not right – can you specify it?
1
2
3
Process 2. To attain a certain end, e.g. “add instructional index”, do you think too many
actions need to be performed? Could this end be attained more directly? For example,
suppose that ­ to save a file – you’d have to click save, specify a name, confirm the name
and close the window. These could be too many actions to perform the task of saving a file.
Task
No Yes
If too many actions need to be performed – can you
specify these?
1
2
3
System image aspects
Version 2
Page 43 of 48