Friday, September 11, 2009

Sep 11 - Usability requirements format (CISU-R part 4)

Usability Requirements Format

Introduction

This annex provides a list of elements that should be used in a usability requirements document, including document and product information elements. It may either be used as a template, or may be used as a checklist for creating a format for usability requirements created with the CISU-R.
The format of the information in this annex is consistent with the CIF (ISO/IEC 25062).

A.2 Title page

The title page contains:
1 Identification of the requirements as conforming to Common Industry Specifications for Usability - Requirements v0.88.
2 The name of the product and version that the requirements are for.
3 The date the requirements were prepared.
4 The organization name.
5 Contact details for questions and/or clarifications.
6 Names of the people who produced the requirements.

A.3 Executive summary

The Executive Summary provides a high level overview of the requirements. The intent of this section is to provide information for people who may not read the technical body of this document. This section should begin on a new page and end with a page break to facilitate its use as a stand-alone summary.

The executive summary:
a)Explains the purpose of the requirements.
b)States the level of conformance.
c)Provides a high level overview of the requirements that includes:
−Name, version, and brief description of the product.
−Summary of the type of users, tasks, any associated equipment (hardware, software, and materials), and the physical and social environments in which the product is intended to be used.
−A list of the task scenarios, with criteria for effectiveness, efficiency, and satisfaction (for level 2 and 3 conformance).
d)Explains the reason for and nature of the requirements.

A.4 Product details

A.4.1 Product description

A product description includes:
1 The formal product name and version.
2 The parts of the product for which requirements are being provided.
3 The user groups for which the product is intended.
4 Whether the product is intended to be "walk up and use", or whether any documentation, training materials or course has to be studied before the product is used.
5 The type of user work that is supported by the product.
6 Description of the environment in which the product should be used.
7 Support for any groups with special needs.

A.4.2 Product objectives

Product objectives include:
- The overall objectives for the product and specific objectives for any subset of usage.
- Any known or intended functions and components that support key objectives.

A.5 Context of use and scenarios

The context of use and scenarios include all of the information and headings specified in Clause 6.2:
a. Stakeholders
b. User groups
c. Goals and tasks
d. Technical environment (equipment)
e. Physical and social environments
f. Scenarios of use for the most important goals

A.6 Usability performance and satisfaction criteria and values

The usability performance and satisfaction criteria include the information specified in Clause 6.3, including
a. The goals that will form the basis of the requirements, with scenarios of usage, with an explanation of why these goals and scenarios were selected.
b. The relative importance of each goal.
c. A definition of the performance and satisfaction criteria appropriate for the scenario and
d. Target values or a range of anticipated values for these criteria, which may be:
−a definite requirement, or
−a provisional requirement subject to further negotiation, or
−an objective for guidance.

A.7 Requirements for testing

If a protocol for a usability test is included, the information specified in Annex C may be used.

No comments:

Post a Comment