1、 g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58Quality Requirements and Evaluation (SQuaRE) Common Industry Format (CIF) for usability test report
2、sICS 35.080Software engineering Software product BRITISH STANDARDBS ISO/IEC 25062:2006BS ISO/IEC 25062:2006This British Standard was published under the authority of the Standards Policy and Strategy Committee on 29 September 2006 BSI 2006ISBN 0 580 47058 XThe British Standards which implement inter
3、national publications referred to in this document may be found in the BSI Catalogue under the section entitled “International Standards Correspondence Index”, or by using the “Search” facility of the BSI Electronic Catalogue or of British Standards Online.This publication does not purport to includ
4、e all the necessary provisions of a contract. Users are responsible for its correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations.Summary of pagesThis document comprises a front cover, an inside front cover, the ISO/IEC title page, pages ii
5、 to vi, pages 1 to 46, an inside back cover and a back cover.The BSI copyright notice displayed in this document indicates when the document was last issued.Amendments issued since publicationAmd. No. Date CommentsA list of organizations represented on this committee can be obtained on request to it
6、s secretary.Cross-referencesenquiries on the interpretation, or proposals for change, and keep UK interests informed; monitor related international and European developments and promulgate them in the UK.National forewordThis British Standard reproduces verbatim ISO/IEC 25062:2006 and implements it
7、as the UK national standard.The UK participation in its preparation was entrusted to Technical Committee IST/15, Software engineering, which has the responsibility to: aid enquirers to understand the text; present to the responsible international/European committee any Reference numberISO/IEC 25062:
8、2006(E)INTERNATIONAL STANDARD ISO/IEC25062First edition2006-04-01Corrected version2006-09-01Software engineering Software productQuality Requirements and Evaluation (SQuaRE) Common Industry Format (CIF) for usability test reports Ingnierie du logiciel Exigences de qualit du produit logiciel et valua
9、tion (SQuaRE) Format commun de lindustrie (CIF) pour les rapports dessai de rentabilit BS ISO/IEC 25062:2006ii iiiContents Page Foreword iv Introduction v 1 Scope . 1 2 Conformance. 1 3 Normative references . 2 4 Terms and definitions. 2 5 Report Format . 4 5.1 Title page . 4 5.2 Executive summary 4
10、 5.3 Introduction . 5 5.4 Method . 5 5.5 Results . 11 5.6 Appendices 14 Annex A (informative) Checklist . 15 Annex B (informative) Glossary 19 Annex C (informative) Report Template. 23 Annex D (informative) Example 29 Bibliography . 46 BS ISO/IEC 25062:2006iv Foreword ISO (the International Organiza
11、tion for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respec
12、tive organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of informatio
13、n technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International S
14、tandards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be t
15、he subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 25062 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and system engineering. BS ISO/IEC 25062:2006vIntroduction
16、Usability of software is a key factor in predicting successful deployment of that software. Software manufacturers subject software to usability testing at various stages in a products development; some companies that purchase software also test products for usability before making purchasing decisi
17、ons. Testing often involves (1) subjects who are representative of the target population of users of the software, (2) representative tasks, and (3) measures of efficiency, effectiveness and subjective satisfaction. When this type of experimental situation exists, the testing is termed summative, i.
18、e., the results can be expressed as statistically meaningful measures of central tendency (e.g. mean or median) and variability (e.g. standard deviation). The Common Industry Format (CIF) for Usability Test Reports is intended for use by usability professionals to report the results of summative usa
19、bility testing. The CIF standardizes the types of information that are captured about testing with users. The level of detail allows the same or another organization to replicate the test procedure. The major variables are user demographics, task descriptions, context of the test, including the equi
20、pment used, the environment in which the test is conducted, and the protocol by which the subjects and the test administrator(s) interact, as well as the particular metrics chosen to code the findings of the study. The CIF is intended to replace the proprietary formats employed by companies that per
21、form usability testing, both vendors and purchasers of software. Until now there has been no standard format for reporting usability testing results. Advantages of using a standardized reporting format include (1) a reduction in training time for usability staff since an individual only needs to lea
22、rn to use one form regardless of how many companies he works for and (2) enhanced potential for increased communication between vendors and purchasing organizations since readers of CIF-compliant reports will share a common language and expectations. The purpose of this International Standard is to
23、facilitate incorporation of usability as part of the procurement decision-making process for interactive software products so that it is easier to judge whether a product meets usability goals. Examples of decisions include purchasing, upgrading and automating. It provides a common format for human
24、factors engineers and usability professionals in supplier companies to report the methods and results of usability tests to customer organizations. Audience The Common Industry Format (CIF) is meant to be used by usability professionals within supplier organizations to generate reports that can be u
25、sed by customer organizations in the CIF report. The CIF is also meant to be used by customer organizations to verify that a particular report is CIF-compliant. The Usability Test Report itself is intended for two types of readers: Usability professionals in customer organizations who are evaluating
26、 both the technical merit of usability tests and the usability of the products; and Other technical professionals and managers who are using the test results to make business decisions. The CIF may also be used within a single organization if a formal report of a summative usability test needs to be
27、 generated. In this case additional material such as a list of detailed findings may be included. The report is in two main sections, an Executive Summary and a main body. The main body contains the Methods and Results sections and is aimed at the first audience above. These sections (1) describe th
28、e test methodology and results in sufficient technical detail to allow replication by another organization if the test is repeated, and (2) support application of test data to questions about the products expected costs and benefits. Understanding and interpreting these sections will require technic
29、al background in human factors or usability engineering for optimal use. The second audience is directed to the Introduction, which provides summary information for non-usability professionals and managers. The Introduction may also be of general interest to other computing professionals. Decision m
30、akers without usability engineering expertise may find the information in the main body to be useful but should rely on expert interpretation when necessary. Organization Clause 1 describes the scope of this specification and the conformance criteria. Clause 4 provides definitions BS ISO/IEC 25062:2
31、006vi of the terms used throughout the document. Clause 5 is the main description of the specification. Additional Information Annex A provides a checklist that can be used to ensure inclusion of required and recommended information. A glossary is provided in Annex B to define terminology used in th
32、e report format description. A Word template for report production can be found at: http:/www.ncits.org/ref-docs/CIF/CIF_template.dot. A printed version of the template can be found in Annex C. An example is provided in Annex D illustrating how the format is used followed by an informative bibliogra
33、phy. BS ISO/IEC 25062:20061Software engineering Software product Quality Requirements and Evaluation (SQuaRE) Common Industry Format (CIF) for usability test reports 1 Scope This International Standard is intended to be used to report the measures obtained from a test of usability as defined in ISO
34、9241-11: effectiveness, efficiency and satisfaction in a specified context of use. NOTE Metrics for other more-detailed usability requirements can be found in ISO/IEC 9126 parts 2 and 3. This International Standard is intended to be used by: usability professionals within supplier organizations to g
35、enerate reports that can be used by customer organizations; customer organizations to verify that a particular report conforms to this International Standard; human factors or other usability professionals in customer organizations who are evaluating both the technical merit of usability tests and t
36、he usability of the products; and other technical professionals and managers in the customer organization who are using the test results to make business decisions about product suitability and purchase. The Executive Summary and Introduction in 5.2 and 5.3 provide summary information for nonusabili
37、ty professionals and managers. Subclauses 5.4 and 5.5 describe the test methodology and results in technical detail suitable for replication, and also support application of test data to questions about the products expected costs and benefits. Understanding and interpreting these sections will requ
38、ire technical background in human factors or usability engineering for optimal use. The report format assumes sound practice 1, 2 has been followed in the design and execution of the test. Test procedures which produce measures that summarize usability should be used, i.e. the test is summative in n
39、ature. Some usability evaluation methods, such as formative tests, are intended to identify problems rather than produce measures; the format is not structured to support the results of such testing methods. 2 Conformance A usability test report conforms to this International Standard if it complies
40、 with all the requirements in this International Standard (stated as “shall”). The recommendations (stated as “should”) should be implemented whenever appropriate. This International Standard specifies the minimum information that should be provided. Additional information may be included. For examp
41、le, if an organization finds that an additional list of findings is useful, the list may be included even though it is not specified as part of a conformant CIF report. BS ISO/IEC 25062:20062 3 Normative references The following referenced documents are indispensable for the application of this docu
42、ment. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 9126-1:2001, Software engineering Product quality Part 1: Quality model ISO/IEC 9126-2:2001, Software engineering Product qual
43、ity Part 2: External metrics ISO/IEC 9126-3:2001, Software engineering Product quality Part 3: Internal metrics ISO/IEC 9126-4:2001, Software engineering Product quality Part 4: Quality in use metrics ISO 9241-11:1998, Ergonomic requirements for office work with visual display terminals (VDTs) Part
44、11: Guidance on usability ISO 13407:1999, Human-centred design processes for interactive systems Annex C ISO/IEC 14598-5:1998, Information technology Software product evaluation Part 5: Process for evaluators 4 Terms and definitions For the purposes of this document, the following definitions apply.
45、 The source for definitions 4.1 to 4.9 is ISO 9241-11:1998. NOTE Efficiency, effectiveness, and satisfaction are defined in ISO/IEC 9126 in a similar way to the definitions in ISO/IEC 9241. However, in ISO/IEC 9126 they are defined in terms of the software product where as in ISO/IEC 9241 they are d
46、efined in terms of the users view. The term efficiency in this International Standard is equivalent to the term productivity in ISO 9126, as the term efficiency has been defined with a different meaning in ISO 9126. 4.1 usability the extent to which a product can be used by specified users to achiev
47、e specified goals with effectiveness, efficiency and satisfaction in a specified context of use NOTE Quality in use is defined in ISO/IEC 9126 in a similar way to the definition of usability in ISO/IEC 9241. Quality in use may be influenced by any of the quality characteristics, and is thus broader
48、than the definition of usability in ISO/IEC 9126 that is in terms of understandability, learnability, operability, attractiveness and compliance. 4.2 effectiveness the accuracy and completeness with which users achieve specified goals 4.3 efficiency resources expended in relation to the accuracy and
49、 completeness with which users achieve goals NOTE Efficiency in the context of usability is related to “productivity” rather than to its meaning in the context of software efficiency. 4.4 satisfaction freedom from discomfort, and positive attitudes towards the use of the product BS ISO/IEC 25062:200634.5 context of use users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a product is used 4.6 user person who interacts with the p
