Usability Context Analysis

---

Primary Reference Source

Bevan, N (Ed), (1997) Usability Context Analysis: a Practical Guide. NPL Usability Services, Teddington, UK

Summary description

Usability Context Analysis (UCA) is a structured method for eliciting detailed information about a product and how it will be used, and for deriving a plan for a user based evaluation of a product. For this method stakeholders meet to detail the actual circumstances (or intended use ) of a product. This is produced in a document called the Context Report Form, which is then examined by a usability consultant who decides who decides if each factor is indeed important for the usability of the product. Following this inspection a summary list, called the Context of Evaluation, of these factors is produced. This list specifies important characteristics of the products’ users, their tasks, their environment, and also lays the foundation for an observational evaluation.

Typical Application Areas

Context Analysis meetings should take place as early as possible in the design of a product. However the results of these meetings can be used throughout the lifecycle of the product; being continually updated and used for referral. The method is also of general relevance to a wide range of systems and processes. The objective of the method is to collect information -- this should be done preferably through a well-prepared meeting, but it may also be done through as series of personal interviews (for instance, if schedules in a busy company do not permit essential personnel to attend a general meeting).

Benefits

Context analysis offers a number of benefits. It provides a framework to ensure that all factors which may affect the usability of a product are considered. It also helps to ensure that user-based evaluation produces valid results, by specifying how important factors are to be handled in an evaluation, and by defining how well the evaluation reflects real world use.

Limitations

The success of this method depends upon competent chairing to keep the meeting focused on the relevant issues. Familiarity with the method by the chairperson is essential.

Cost of use

No specific hardware or software is required for this method. A word processor is needed to generate a report. However the facilitator of a context meeting should be familiar with the system to be evaluated and so may require access to a functional prototype or a finished product.

Costs of Acquisition

For a person leading a Context Analysis, training or prior experience is highly recommended, and familiarity with the Context Report Form is essential.

Suitability for requirements engineering in Telematics:

There is considerable experience of this method within the RESPECT consortium. Usability context analysis particularly well integrated with performance measurement methods later in the project lifecycle, and user based questionnaires such as HFRG’s SUMI and MUMMS questionnaires.

How to get it:

Contact Dr Nigel Bevan (n.bevan|@npl.co.uk)at NPL Usability Services

Detailed description of method:

There are a number of steps required to conduct the UCA method:

1. First identify all relevant individuals who will be involved in the process and organise the context meeting. Examine the context report form to identify in advance any factors which do not need to be discussed at length at the meeting.
2. Complete the Product Report Form to define the scope of the term "product" for the analysis.
3. At the meeting, fill in the Context of Use column of the Context Report.
4. After the meeting identify the critical components which may affect usability.
5. If Context Analysis is to be conducted as preparation for an evaluation, identify how the critical components will be handled during the evaluation.
6. Produce an evaluation plan detailing the users, the tasks they will carry out, and the circumstances of the evaluation.

When applying this method it is important that the relevant stakeholders are present.