IEEE 26513-2017 en Systems and software engineering - Requirements for testers and reviewers of information for users (IEEE Computer Society).pdf

《IEEE 26513-2017 en Systems and software engineering - Requirements for testers and reviewers of information for users (IEEE Computer Society).pdf》由会员分享，可在线阅读，更多相关《IEEE 26513-2017 en Systems and software engineering - Requirements for testers and reviewers of information for users (IEEE Computer Society).pdf（49页珍藏版）》请在麦多课文档分享上搜索。

1、Systems and software engineering Requirements for testers and reviewers of information for usersIngnierie des systmes et du logiciel Exigences pour testeurs et INTERNATIONAL STANDARDISO/IEC/IEEE26513Reference numberISO/IEC/IEEE 26513:2017(E) dition2017-10 ISO/IEC 2017 IEEE 2017 ISO/IEC 2017 All righ

2、ts reservedii IEEE 2017 All rights reservedISO/IEC/IEEE 26513:2017(E)COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in Switzerland IEEE 2017 the respective address below. Ch. de Blandonnet 8 CP 401 3 Park Avenue, New YorkCH-1214 Vernier, Geneva, Switzerland NY 10016-5997, USATel. +41 22 749 01

3、 11 Fax +41 22 749 09 47 7 7www.iso.org www.ieee.orgISO/IEC/IEEE 26513:2017(E) iii ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Contents Page 1 Scope . 1 2 Normative references . 2 3 Terms and definitions 2 4 Conformance 9 4.1 Definition of conformance 9 4.2 Conformance situations

4、. 9 5 Review and assessment processes of user documentation within the software lifecycle . 10 5.1 Process overview 10 5.2 Review and assessment activities . 10 6 Documentation evaluation strategy . 12 6.1 Requirements, objectives, and constraints . 12 6.2 Documentation evaluation activities . 13 6.

5、3 Selection of an evaluation method . 14 6.4 Documentation evaluation criteria 14 6.5 Documentation test process . 14 6.6 Project requirements affecting documentation evaluation 15 6.7 Resource requirements and planning . 15 General 15 Resources for documentation evaluation 16 Impact of evaluation o

6、n project schedules 16 7 Documentation evaluation methods and procedures . 17 7.1 General 17 7.2 Documentation review 17 Planning documentation review . 17 Administering quality review . 19 Managing the results of documentation review 20 Configuration change review 20 7.3 System test of documentatio

7、n 20 7.3.3 Creating the system test plan for documentation . 22 System test plan for documentation approvals . 23 Problem management and the system test of documentation lifecycle 23 7.4 Usability testing of documentation 23 General 23 Objectives and activities for usability testing of documentation

8、 24 Measures and metrics for documentation usability testing goals. 25Planning documentation usability tests . 25 Performing usability evaluation of documentation . 27 Problem management for documentation usability tests 28 7.5 Accessibility testing of documentation . 28 Scope of accessibility testi

9、ng 28 Performing accessibility tests 29 7.6 Translation and localization review and testing 29 General 29 Planning for translation and localization review and testing . 29 Performing translation and localization review and testing 29 Annex A (informative) User-centered test and review guidelines 31A

10、.1 Support for an action-oriented approach 31 A.2 Support for real tasks 32 A.3 Support for error recognition and recovery . 33 ISO/IEC/IEEE 26513:2017(E) iv ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved A.4 Support for information access 33 A.5 Content for translation 34 Bibliograp

11、hy 35 ISO/IEC/IEEE 26513:2017(E) v ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that

12、are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other internati

13、onal organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. IEEE Standards documents are developed within the IEEE Societies and the St

14、andards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests t

15、o achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the ac

16、curacy of any of the information contained in its standards. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International Standards adopted by the joint technical co

17、mmittee 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 called to the possibility that implementation of this document may require the use of subject matter covered by patent

18、 rights. By publication of this document, no position is taken with respect to the existence or validity of any patent rights in connection therewith. ISO/IEC and IEEE is not responsible for identifying essential patents or patent claims for which a license may be required, for conducting inquiries

19、into the legal validity or scope of patents or patent claims or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if any, or in any licensing agreements are reasonable or non-dis

20、criminatory. Users of this document are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from ISO or the IEEE Standards Association. This document was prep

21、ared by Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Software sting and Translation and Localization Review and Testing; -centered Test and Review Guidelines; and ISO/IEC/IEEE 26513:2017(E) vi ISO/IEC 2017 All

22、 rights reserved IEEE 2017 All rights reserved Introduction Well-designed documentation not only assists users and helps to reduce the cost of training and support, but also enhances the reputation of the product, its producer, and its suppliers. Verification, validation testing, and expert review o

23、f content during development provides feedback to information developers regarding the accuracy and usability of their work. This document addresses the evaluation and testing of information provided for users to perform tasks, make decisions in context, and gain understanding. It applies to both in

24、itial development and subsequent releases of the software and user documentation. This document is independent of the software tools that may be used to produce documentation and applies to printed and electronic documentation, embedded content in the software, and online documentation. Much of its

25、guidance is applicable to user documentation for systems including software user documentation as well as the software used to control machinery or hardware devices. This document was developed to assist those who test and review software user documentation as part of the software lifecycle process.

26、 This document defines the information management and validation processes of ISO/IEC/IEEE 12207:2017 from the information assessors and testers standpoints. This document can be used as a conformance or a guidance document for products, projects, and organizations claiming conformance to ISO/IEC/IE

27、EE 15288:2015 or ISO/IEC/IEEE 12207:2017. Readers are assumed to have experience with or general knowledge of reviewing and testing processes. ISO/IEC/IEEE txwsutrsy INTERNATIONAL STANDARD 1 ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Systems and software engineering Requirements

28、for testers and reviewers of information for users 1Scope This document supports the interest of software users in receiving consistent, complete, accurate, and usable documentation and specifies processes for use in testing and reviewing of user documentation (Clause 6). It is not limited to the te

29、st and review stage of the lifecycle, but includes activities throughout the information management and documentation management process. This document is intended for use in all types of organizations, whether or not a dedicated documentation department is present. In all cases, it can be used as a

30、 basis for local standards and procedures. Readers are assumed to have experience or general knowledge of testing or reviewing processes. This document deals with the evaluation of end-user content only, and not with the evaluation of the software it supports. NOTE 1 Documentation is also included i

31、n evaluation of the software product, as in the ISO/IEC 25000 and 29000 series of standards. In particular: ISO/IEC TR 25060; ISO/IEC 25062; ISO/IEC 25063:2014; ISO/IEC 25064:2013; and ISO/IEC/IEEE 29119-3:2013. This document provides the minimum requirements for testing and reviewing user documenta

32、tion (Clause 7), including both printed and online documents used in work and other environments by the users of software which includes application software, systems software, apps on mobile devices, and software that controls machinery or hardware devices. It applies to printed user manuals, onlin

33、e help, user assistance, tutorials, websites, and user reference documentation. This document can also be helpful for testing and reviewing the following types of documentation: documentation of products other than software, for example, ha rdware or devices; multimedia systems using animation, vide

34、o, and sound; tutorial packages and specialized course materials intended primarily for use in formal training programs; documentation produced for installers, computer operators, or system administrators who are not end users; and maintenance documentation descr ibing the internal operation of syst

35、ems software. ISO/IEC/IEEE 26513:2017(E) 2 ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved This document is applicable to testers, reviewers, and other related roles, including a variety of specialists: usability testers, documentation reviewers, and subject-matter experts; informatio

36、n developers and arch itects who plan the structure and format of products in a documentation set; usability analysts and business analysts who identify the task s the intended users perform with the software; editors; test participants; installers, computer operators, or system administrators; and

37、customer support groups such as training, help desks, repair, and return. The document can also be consulted by those with other roles and interests in the information management process. Managers of the software development process or the information management process consider the testing of docum

38、entation as part of their planning and management activities. Project managers, in particular, have an important role in supporting the review and testing of documentation. Testing of the documentation is likely to highlight any defects or nonconformances in tools that are used to create or display

39、online documentation. Similarly, usability testing of the documentation is likely to identify additional operational concerns or misunderstandings of end users. NOTE 2 Testing of documentation can highlight problems with the software being documented. Resolving problems with the software is not in t

40、he scope of this document. There are other roles that need to understand the test processes for the documentation; for example, information developers should understand the test processes for the documentation that they have produced, and acquirers of documentation prepared by another department or

41、organization might want to know what testing has been performed and the processes followed for the documentation that they are acquiring from a supplier. The order of clauses in this document does not imply that software user documentation is meant to be reviewed, assessed, edited, or tested in this

42、 order. In each clause, the requirements are media-independent, as far as possible. The informative guidelines found in Annex A, User-Centered Test and Review Guidelines, can be used at each stage of the information management process to verify that the correct steps have been carried out and that t

43、he finished product has acceptable quality. The works listed in the Bibliography provide additional guidance on the processes of managing, preparing, and testing of user documentation. 2 Normative references There are no normative references in this document. 3 Terms and definitions For the purposes

44、 of this document, the following terms and definitions apply. ISO/IEC/IEEE 26513:2017(E) 3 ISO/IEC 2017 All rights reserved IEEE 2017 All rights reservedISO, IEC and IEEE maintain terminological databases for use in standardization at the following addresses: IEC Electropedia: available at http:/www

45、.electropedia.org ISO Online browsing platform: available at http:/www.iso.org/obp IEEE Standards Dictionary Online: available at http:/dictionary.ieee.org NOTE ISO/IEC/IEEE 24765 Software and Systems Engineering Vocabulary can be referenced for terms not defined in this clause. This source is available at the following web site: http:/puter.org/sevocab.