GB/T 25000.62-2014Software engineering -- Software product quality requirements and evaluation (SQuaRE) -- Common industry format (CIF) for usability test reports (English PDF)

Foreword

This part of GB/T 25000 "Software Engineering Software product quality requirements and evaluation (SQuaRE)" Part 62.

This section drafted in accordance with GB/T 1.1-2009 given rules.

This section uses the translation method identical with ISO/IEC 25062:2006 "Software Engineering Software product Quality Requirements and Evaluation (SQuaRE) usability test reports common industry format (CIF) ".

This part of the National Information Technology Standardization Technical Committee (SAC/TC28) and focal points.

This section is drafted. Translation of Guangxi Business Services Co., Ltd., Shandong Computer Science Center, China Electronics Standardization Institute, Beijing Hopen Software Engineering Technology Co., Ltd., Beijing University of Posts and Telecommunications, Beijing CAS software Centre Limited.

Introduction

Ease of use is a key factor in the success of forecasting software deployment. Software vendors in various stages of product development are conducted usability testing test. Some companies make software before purchasing decision also testing software usability. Testing typically includes the following. (1) software target user A representative of a human subject; (2) a representative of the mission; (3) the efficiency, effectiveness and subjective satisfaction measures. Comprising the above the test is known as summative tests, that is, the result is statistically significant measure of trends (such as average or median) and variability (eg standard Standard deviation). Usability test reports common industry format (CIF) aims to assist usability professionals make summative usability testing report.

Common industry format (CIF) specification of the type of information obtained during user test. The main variable is the user statistics, Task description, test contexts (including the equipment used, the protocol test execution environment, when measured by the test administrator and interactive use), as well as the regulation Fan found and selected special measure.

Common industry format (CIF) intended to replace the software vendor and the purchaser conduct its own software usability testing format used. Make Advantages reports in standard formats, including. (1) reduce training time usability testers, because no matter how much a human enterprise work, He just needs to learn to use a format; (2) to further improve the effectiveness of communication between the vendor and the purchaser, as appropriate, as common industry format by readers of the report, they will have a common language and expectations.

This document is intended to promote ease of use become part of the interactive product procurement decision-making process, in order to more easily determine whether the product meets Yi with goals. Examples of such decision-making process, including the purchase, upgrade and automation technology. It ergonomics engineer and supply-side Usability professionals provide a description to customer usability testing methods and results of the common format.

reader

Supplier organizations in usability professionals can take advantage of common industry format (CIF) to generate a report used by the organization for the customer. It is also available Customer Organization confirmed a report meets specific industry common format. Usability testing report itself for the following two types of readers.

--- Customer organizations evaluate the value of usability testing technology and product usability professionals;

--- Other professionals and business decisions based on the results of usability testing manager.

Single organization can also be used to generate common industry format of formal usability testing reports. In this case, the need to provide additional material Material, such as a detailed list of discovery.

The report contains an executive summary and body of two main parts. Text reader is suitable for the above-mentioned first class, including methods and conclusions fruit. These parts. (1) describes the test methods and technical details of the results of such tests can be repeated in the case, allowing other organizations to repeat Testing; (2) support the use of test data products are expected to weigh the costs and benefits. For best results, understand and interpret these parts Ergonomics need usability engineering or technical background. Executive Summary Introduction and body partly in non-usability professionals and managers it provides summary information for the second category of readers. Of course, it could also be of general interest to other computer professionals. No usability work Policymakers process expertise can find useful information in the body, but if necessary, should rely on experts to explain.

Software engineering and software product quality requirements Evaluation (SQuaRE) usability test reports Common industry format (CIF)

1 Scope

This section GB/T 25000 apply to the validity in accordance with GB/T 18978.11-2004 under the particular context of use, efficiency and full Preparation of reports intended degree of usability testing after work.

Note. Other metrics usability requirements can refer to GB/T 16260.2-2006, GB/T 16260.3-2006.

This section applies to the following conditions.

--- Supplier organizations usability professionals reported to the customer organization uses to prepare for the time;

--- When a particular customer organization report compliance with this document verification;

--- Customer ergonomics expert or other usability professionals within the organization evaluate usability testing technologies and products to use value when sex;

--- Other professionals and managers within the customer organization in the use of test results for product suitability and later commercial decisions.

"Executive Summary 5.2" and "5.3 Introduction" non-usability professionals and managers to provide summary information.

5.4 and 5.5 from the technical details describes the test methods and results, but also by the product test data weigh the expected costs and revenues beneficial. For best results, understand and interpret these clauses requires ergonomics or usability engineering technical background.

Reporting format is assumed. in test design and execution, follow a regular practice [1,2]. It should be used to generate beneficial usability test summary Degree of test procedures, that such tests are conclusive. Some usability evaluation method is mainly used to identify the problem, rather than to produce measurement Value, such as the formation of the test. This section does not support the results of this test method is formed.

2 Compliance

If usability test report contains all of the contents of this document requirements (described as "shall"), it meets the requirements of this document. Such as If possible, we recommend using the recommended requirements (described as "appropriate").

This section provides basic information usability test reports should be provided. The user can further increase the necessary information as needed. example for example, if an organization find other useful information, even if the industry does not provide a common format in the part, but also these letters Information included in the report.

3 Normative References

The following documents for the application of this document is essential. For dated references, only the dated version suitable for use herein Member. For undated references, the latest edition (including any amendments) applies to this document.

GB/T 16260.1-2006 Software engineering - Product quality - Part 1. Quality model (ISO/IEC 9126-1:2001, IDT) GB/T 16260.2-2006 Software engineering - Product quality - Part 2. External metrics (ISO/IEC TR9126-2:2001, IDT) GB/T 16260.3-2006 Software engineering - Product quality - Part 3. Internal metrics (ISO/IEC TR9126-3:2001, IDT) GB/T 16260.4-2006 Software engineering - Product quality - Part 4. Measurement quality in use (ISO/IEC TR9126-4.

2001, IDT)