Human Computer Interaction: Usability Inspection Methods
Human Computer Interaction: Usability Inspection Methods
Human Computer Interaction: Usability Inspection Methods
Lecture 11:
Usability inspection methods
Usability inspection
Usability inspection is the generic name for a set of methods based on having
evaluators inspect a user interface.
Typically, usability inspection is aimed at finding:
usability problems in the design,
though some methods also address issues like
the severity of the usability problems and the overall usability of an entire system.
Usability inspectors can be:
usability specialists,
software development consultants with special expertise (e.g. knowledge of a particular interface
style for graphical user interfaces),
end users with content or task knowledge, or other types of professionals.
Usability inspection methods
Different inspection methods have slightly different goals, but normally usability
inspections is intended for evaluating user interface design.
Commonly used inspection methods are:
• Heuristic (Expert) Evaluation
• Cognitive Walkthroughs
• Formal Usability Inspections
• Pluralistic Walkthroughs
• Feature Inspection
• Consistency Inspection
• Standards Inspection
• Guideline Checklists
Heuristic (Expert) Evaluation
Heuristic evaluation is where a group of usability experts analyze a web site and
evaluate each element of the site against a list of commonly accepted principles or
rules of thumb.
They apply their training and experience to conduct independent evaluations.
Research shows that such evaluations can identify a majority of the usability
problems.
Cognitive walkthrough
A cognitive walkthrough starts with the sequence of steps or actions required by a
user to accomplish a task, and the system responses to those actions.
The designers and developers of the software then walk through the steps as a group,
asking themselves a set of questions at each step.
Data is gathered during the walkthrough, and afterwards a report of potential issues
is compiled. Finally the software is redesigned to address the issues identified.
Cognitive walkthrough
At each step, expert asks:
Will the user try to take this action to achieve their goal?
Is the correct action visible?
Will the user recognize this action as the correct one?
Will the user understand the feedback that is given? Will they recognize that
progress has been made?
Formal Usability Inspections
In this method, the various participants have well-defined responsibilities:
A moderator is appointed to manage both individual and focused inspections, and the full
team inspection meeting
A design owner is responsible for design an redesigns
The inspectors have the job of finding problems; and records all defects and issues
identified during the meeting
Inspections are performed through a six-step process;
planning,
a kick-off meeting,
a preparation phase where inspectors review the interface individually,
the main inspection review when the inspectors lists of usability problems are merged,
and a follow-up phase where the effectiveness of the inspection process itself is evaluated.
Pluralistic Walkthroughs
The main modification, was to include three types of participants: representative
users, product developers, and human factors (usability) professionals.
Hard-copy screens (panels) are presented in the same order in which they would
appear online.
A task scenario is defined, and participants confront the screens in a linear path,
through a series of user interface panels, just as they would during the successful
conduct of the specified task online, as the site/software is currently designed.
Participants are all asked to assume the role of the user for whatever user population
is being tested. Thus, the developers and the usability professionals are supposed to
try to put themselves in the place of the users when making written responses.
Pluralistic Walkthroughs
The participants write down the action they would take in pursuing the designated
task online, before any further discussion is made.
It is only after all participants have written the actions they would take that
discussion would begin. The representative users offer their discussion first and
discuss each scenario step. Only after the users have exhausted their suggestions do
the usability experts and product developers offer their opinions.
Feature Inspection
Feature inspections analyse only the feature set of a site
Usually given end user scenarios for the end result to be obtained from the use of the
web site.
For example,
A scenario for the training site would be to register for a workshop.
The features that would be used are navigating to the workshop site, selecting a
class, adding it to their shopping cart, filling out the registration form, and
pressing the submit button.
Each set of features used to produce the required output (a registration) is
analysed for its availability, understandability, and general usefulness.
Consistency Inspection
Consistency inspections ensure consistency across multiple products from the same
development effort.
For example, in a suite of office productivity applications, common functions should
look and work the same whether the user is using the word processor, spreadsheet,
presentation, or database program.
Consistency inspections begin with a usability professional analysing the interfaces
to all of the products and noting the various ways that each product implements a
particular user interaction or function.
During the meeting, the team discusses the user interfaces to their products in terms
of the usability professional's document, and for each element, comes to an
agreement on what that element should look and work like in all of the products
Standards Inspection
In Standards inspections, industry standards are observe.
Have an expert on some interface standard inspect the interface for compliance
(observing a rule).
Thus, standards are aimed at increasing the degree to which a given interface is in the
range of other systems on the market that follow the same standards.
Guideline Checklists
Are inspections where an interface is checked with a list of usability guidelines.
However, since guideline documents contain on the order of 1000 guidelines,
guideline reviews require a high degree of expertise and are fairly rare in practice.
The method can be considered as somewhat of a cross between heuristic evaluation
and standard inspection.
Usability testing methods
Usability testing methods
In a usability-testing session, a researcher (called a “facilitator” or a “moderator”)
asks a participant to perform tasks, usually using one or more specific user interfaces.
While the participant completes each task, the researcher observes the participant’s
behaviour and listens for feedback.
The phrase “usability testing” is often used interchangeably with “user testing.”
One objection sometimes raised against the phrase “user testing” is that it sounds like
researchers are testing the participant — we never test the user, only the interface.
However, the term is intended to mean testing with users, which is exactly the point
of empirical studies.
Why Usability Test?
The goals of usability testing vary by study, but they usually include:
• Identifying problems in the design of the product or service
• Uncovering opportunities to improve
• Learning about the target user’s behaviour and preferences