Walkthrough
Primary Reference Source
J Nielsen and RL Mack(1994) Usability Inspection Methods. J Wiley, NY.
Summary Description
A walkthrough is a process of going step by step through a system design
getting reactions from relevant staff, typically users or experts role-playing
the part of users. Normally one or two members of the design team will
guide the walkthrough, while one or more users will comment as the walkthrough
proceeds.
Typical Application Areas
This technique is most often used where there is a relatively unstable
prototype or a written procedural specification. The ubiquitous presence
of design team members usually inhibits free-floating comments from all
but the most outspoken of users.
Benefits
-
Obtains reactions to a design in an informal manner.
-
Flexible means obtaining reactions, allowing the discussion to range over
issues not originally considered.
Limitations
-
Requires some form of prototype to show for user to react to.
-
Results are opinions rather than objective data.
-
Users may tend to react positively on seeing some prototype in operation.
-
It may be difficult to imagine how the system will operate in the real
environment.
Cost of use
Requires a prototype to be developed. The time overhead in holding the
walkthrough sessions largely depends upon the task domain and the number
of users exposed to the prototype.
Suitability for requirements engineering in Telematics
The tendency of the design team to ‘protect’ their project and for users
to accept verbal reassurances makes this a less than satisfactory method
to use with end users; with experienced HCI personnel role-playing or simulating
end user reactions, walkthroughs may be of use if they are carried out
early enough in the development.
Procedure
The general procedure for implementing this method is outlined in the following.
-
Decide clearly what issues or task scenarios should be covered by the walkthrough.
-
Set up a good recording mechanism, e.g. one person to show the system and
ask questions, another to take notes, or record on tape, peoples comments
for transcription later on.
-
Select appropriate users to take part in the walkthrough, trying to cover
the range of users within the target population or request some HCI experts
not connected with the project to assist.
-
Pilot the walkthrough to work out how much time is needed for each session.
-
Ensure recording facilities are available and functioning.
-
Conduct the walkthrough sessions, making sure that all sessions cover the
issues identified beforehand.
-
Analyse information obtained by issue and comments made. Try to determine
how many users made the same comment. Consider the themes and severity
of the problems identified.