Introduction to the HUFIT Toolkit and the Development of Usability Evaluation Plan

ICT325 Semester 1, 2005 - Tutorial - Weeks 2 & 3

Introduction to the HUFIT toolkit and the development of usability evaluation plan:

HUFIT Forms 1-10 - copies at ftp://ftp.it.murdoch.edu.au/pub/units/ict325/

Preparation of a usability evaluation plan for a system - (see Reader pp. 64-70)

Usability goals (criteria/dimensions):

Some options for usability goals for User Interfaces:

·  Efficiency (initial performance; long-term performance) - speed; error rates; etc

·  Effectiveness (initial performance; long-term performance) - for required range of tasks, accomplished at better than some required level of performance, by some required percentage of the specified target range of users;

·  Advanced feature usage - for specific set of system features;

·  Learnability (and retainability) - of specified user commands;

·  Utility of Help and Documentation (if provided);

·  Flexibility (adaptability) - can the system be used in different ways;

·  Attitude (first impression; long-term user satisfaction) - in terms of: satisfaction; tiredness; discomfort; frustration; personal effort; etc.

·  Etc.

Some options for usability goals for Multimedia (Reeves - see Reader p. 240):

·  Ease of Use;

·  Navigation;

·  Cognitive Load;

·  Mapping;

·  Screen Design;

·  Knowledge Space Compatibility

·  Information Presentation;

·  Media Integration;

·  Aesthetics;

·  Overall Functionality.

Some options for usability goals for websites (dimensions of usability):

·  Content:

·  Usefulness / relevance

·  Accuracy / truthfulness

·  Completeness

·  Currency

·  Hyperlinks:

·  Quantity

·  Quality/relevance/currency (dangling?)

·  Clarity / Presentation:

·  Simplicity / elegance

·  Layout / structure

·  Use of graphics/diagrams

·  Readability

·  Adherence to Conventions / Standards

·  Navigation support:

·  Structured layout

·  Overview diagram/site map

·  Navigation buttons

·  Search / keywords / links panel / frames

·  Different design for different types of pages, e.g. Colour

·  Search facilities:

·  Functionality

·  Utility

·  Attractiveness / Annoyance (attention getting/keeping):

·  Colour use

·  Text fonts - appropriate?

·  Use of graphics / images / videos

·  Music / sounds

·  Animations / blinking / wobbling - effective or annoying?

·  Banners - too distracting?

·  Creativity / uniqueness / innovations

·  Opportunities for Interaction:

·  Functionality

·  Utility

·  Error reduction and recovery

·  Help / documentation - availability and utility

·  Download Speed

·  Number /size / format of graphics

·  Thumbnails, progressive build up, etc

·  H/W and S/W requirements:

·  H/W restrictions

·  Reliance on downloads

·  Needing latest versions of s/w

·  Reliability - does server go down often

·  Customisability / user model/profile:

·  Cookies for user attributes

·  Ease of download of information:

·  Formats of text files

·  Integrity / ethics

·  Security (e.g. use of credit card no / email address)

·  Race / gender treatment

Appropriate measures for usability goal:

Some options for measures:

·  Time to complete task;

·  Number of keystrokes;

·  Number or percentage of errors;

·  Percentage of a task completed in a given time;

·  Ratio of successes to failures;

·  Ease of navigation through system functionality / data;

·  Suitability of screen design / layout / terminology / feedback;

·  Consistency of terminology, screen design, etc.;

·  Time spent in errors or recovery;

·  Number of commands/actions used to perform task(s);

·  Frequency of help and documentation use;

·  Number of repetitions of failed commands;

·  Number of available commands not invoked;

·  Time taken to learn a specific set of commands / interaction sequence;

·  Number of commands remembered

·  Number of times user expresses frustration or satisfaction;

·  Users' attitudes and opinions re specific aspects of system use.

plus others

Critical review of usability specification for specific system:

Some relevant questions:

·  Is each usability attribute practically measurable?

·  Are user groups (classes) specified clearly enough?

·  Is the number of attributes to be measured reasonable?

·  How well do the attributes capture usability for the design?

B325 Sem. 1, 2003 - Tutorial - Weeks 2-4 Handout page 1