Although much has been published on how to collect user requirements, there is surprisingly little guidance on the specific information that should be included in a user requirements specification, or on the syntax of user requirements statements. An ISO working group that has been developing a series of documents to define good practice for the content of human-centred design deliverables is now working to get consensus on the content of user requirements specifications. Two types of user requirements have been identified: (a) requirements for a user to be able to recognize, select, input or receive physical entities and information, and (b) use-related quality requirements that specify criteria for outcomes such as effectiveness, efficiency, satisfaction, accessibility, user experience and avoidance of harm from use. A user requirements specification should also contain information about constraints, the context of use, goals and tasks to be supported, design guidelines and any recommendations for design solutions emerging from the user requirements. This paper explains some of the challenges in developing the standard.

Kansei Engineering can be used to create scales to measure perceptions and evaluations of products in a particular context. To what extent do specifically constructed Kansei scales reveal more information about a product than a more generic, prestructured instrument, such as AttrakDiff? This case study identified relevant affective and pragmatic Kansei attributes that influence the purchase of a range hood (cooker hood). 102 customers rated the extent to which each of 10 range hoods possessed these attributes. In addition, AttrakDiff was used to measure hedonic and pragmatic quality perceptions. There was a general high correspondence between AttrakDiff and Kansei. While Kansei provided richer and more specific feedback, it was more resource intensive to carry out.

Several new and revised ISO standards will be published in 2016/17 that define the basic terms and concepts of usability (ISO 9241-11), give guidance on processes and outcomes of human-centred design (ISO 9241-220), provide examples of measures that can be used in usability evaluation (ISO/IEC 25022 and 25023) and define what should be included in usability evaluation reports for usability tests, inspections and surveys (ISO/IEC 25066). The paper explains some of the new content and how it can be used.

A revision is currently being undertaken of ISO 9241-11, published in 1998 to provide guidance on usability. ISO-9241-11 defines usability in terms of effectiveness, efficiency and satisfaction in a particular context of use. The intention was to emphasise that usability is an outcome of interaction rather than a property of a product. This is now widely accepted. However, the standard also places emphasis on usability measurement and it is now appreciated that there is more to usability evaluation than measurement. Other developments include an increasing awareness of the importance of the individual user's emotional experience as discretionary usage of complex consumer products and use of the World Wide Web have became more widespread. From an organisational perspective, it is now appreciated that usability plays an important role in managing the potentials risks that can arise from inappropriate outcomes of interaction. The revision of ISO 9241-11 takes account of these issues and other feedback.

The course explains how international standards can provide a sound basis for education and training, can provide authority for design and development, and are a rich source of guidance and reference material.

This paper documents a consistent and considerable evaluator effect in the ratings of usability problem severity carried out by experienced usability professionals. The CUE-9 study, conducted in 2011, showed a reasonable level of rater agreement in problem identification, but the severity assigned to problems varied wildly from "not a problem" to "disaster". This paper documents the variations we observed and the need for a better rating scale and better training. The paper calls for more caution when using extreme ratings. Our results also show that simple attempts to fix the traditional rating scales may not work.

This paper documents a consistent and considerable evaluator effect in the ratings of usability problem severity carried out by experienced usability professionals. The CUE-9 study, conducted in 2011, showed a reasonable level of rater agreement in problem identification, but the severity assigned to problems varied wildly from "not a problem" to "disaster". This paper documents the variations we observed and the need for a better rating scale and better training. The paper calls for more caution when using extreme ratings. Our results also show that simple attempts to fix the traditional rating scales may not work.

The ISO/IEC 25063 standard provides a Common Industry Format for documenting the context of use. It defines the context of use as the "users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a system, product or service is used", and specifies what should be included in a description of the context of use. This paper explains the importance of identifying the context of use as part of the human centred design process, provides an outline of the information that needs to be included in a description of the context of use, and explains how the scope of the context of use needs to be identified and how multiple contexts of use can be differentiated.

Public policy increasingly plays a role in influencing the work that we do as HCI researchers, interaction designers, and practitioners. "Public policy" is a broad term that includes both government policy and policy within non-governmental organizations, such as standards bodies. The Interacting with Public Policy forum focuses on topics at the intersection of human-computer interaction and public policy. Jonathan Lazar, Editor

Public policy increasingly plays a role in influencing the work that we do as HCI researchers, interaction designers, and practitioners. "Public policy" is a broad term that includes both government policy and policy within non-governmental organizations, such as standards bodies. The Interacting with Public Policy forum focuses on topics at the intersection of human-computer interaction and public policy. Jonathan Lazar, Editor

Identifying and defining user requirements is an essential input to good user centred design, but there is little guidance on content. The workshop will share and review examples of user requirements provided by the participants, to generate a contents list that could help practitioners identify and document the relevant requirements.

There is increasing pressure on developers to produce usable systems, which requires the use of appropriate methods to support user centred design during development. There is currently no consistent advice on which methods are appropriate in which circumstances, so the selection of methods relies on individual experience and expertise. Considerable effort is required to collate information from various sources and to understand the applicability of each method in a particular situation. Usability Planner is a tool aimed to support the selection of the most appropriate methods depending on project and organizational constraints. Many of the rules employed are derived from ISO standards, complemented with rules from the authors' experience.

The current ISO 20282 standard is intended to provide a test method that can be used to assess the ease of operation of walk-up-and-use products and consumer products. The standard is currently being revised to improve the cost-effectiveness of the test method, to broaden the scope to include aspects of usability that go beyond ease of operation, and to more clearly define how to obtain reliable results. But the challenge remains to provide a standard that will be cost-effective and useful to manufacturers, purchasers and test houses.

The diversity of User Centred Design (UCD) methods and the difficulties for estimating their cost-effectiveness make planning usability activities in systems development a hard task. Usability Planner is a tool to support the selection of UCD methods to be applied in a particular project or organization, and to estimate the relative cost benefits of applying usability methods at different stages.

Despite a growing interest in usability techniques in the overall systems development practice, and the existence of standards aiming to guide the selection of UCD (User-Centred Design) methods, the diversity of usability methods available for application, and the lack of easy to use rules for selecting and applying them makes selecting and planning UCD activities a hard task with little or no support available. This paper presents the Usability Planner tool, aimed to provide such support. Usability Planner suggests appropriate UCD methods for each software life cycle stage taking account of the particular constraints to consider, and includes support for prioritising types of methods based on potential business benefits and risks. Usability Planner is being developed as an open access and open source project. It has proceeded so far with iterations of wire frame prototypes, allowing feedback to be gathered from usability professionals and software developers, and with the building of the first software prototype.

Despite the authoritative nature of international standards for usability, many of them are not widely used. This paper explains both the benefits and some of the potential problems in using usability standards in areas including user interface design, usability assurance, software quality, and usability process improvement.

This chapter introduces a range of evaluation methods that assist developers in the creation of interactive electronic products, services and environments (eSystems) that are both easy and pleasant to use for the target audience. The target audience might be the broadest range of people, including people with disabilities and older people or it might be a highly specific audience, such as university students studying biology. The chapter will introduce the concepts of accessibility, usability and user experience as the criteria against which developers should be evaluating their eSystems, and the iterative user- centred design lifecycle as the framework within which the development and evaluation of these eSystems can take place. Then a range of methods for evaluating accessibility, usability and user experience will be outlined, with information about their appropriate use and strengths and weaknesses.