ISO/IEC/IEEE 26513:2017
(Main)Systems and software engineering — Requirements for testers and reviewers of information for users
Systems and software engineering — Requirements for testers and reviewers of information for users
Ingénierie des systèmes et du logiciel — Exigences pour testeurs et vérificateurs de documentation utilisateur
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC/
STANDARD IEEE
Second edition
2017-10
Systems and software engineering —
Requirements for testers and
reviewers of information for users
Ingénierie des systèmes et du logiciel — Exigences pour testeurs et
vérificateurs de documentation utilisateur
Reference number
©
ISO/IEC 2017
©
IEEE 2017
© ISO/IEC 2017, Published in Switzerland
© IEEE 2017
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any
means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ISO, IEC or IEEE at
the respective address below.
ISO copyright office Institute of Electrical and Electronics Engineers, Inc
Ch. de Blandonnet 8 • CP 401 3 Park Avenue, New York
CH-1214 Vernier, Geneva, Switzerland NY 10016-5997, USA
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org stds.ipr@ieee.org
www.iso.org www.ieee.org
© ISO/IEC 2017 – All rights reserved
ii © IEEE 2017 – All rights reserved
ISO/IEC/IEEE 26513:2017(E)
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 . 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.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 on 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 documentation . 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 . 24
Measures and metrics for documentation usability testing goals . 25
Planning 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 testing . 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 . 31
A.1 Support for an action-oriented approach . 31
A.2 Support for real tasks . 32
A.3 Support for error recognition and recovery . 33
iii
© ISO/IEC 2017 – All rights reserved
© IEEE 2017 – All rights reserved
A.4 Support for information access . 33
A.5 Content for translation . 34
Bibliography . 35
iv
© ISO/IEC 2017 – All rights reserved
© IEEE 2017 – All rights reserved
ISO/IEC/IEEE 26513:2017(E)
Foreword
ISO (the International Organization 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
respective 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 nongovernmental, 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 Standards Coordinating Committees of
the IEEE Standards Association (IEEESA) 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 to 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 accuracy 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 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 called to the possibility that implementation of this document may require the use of subject matter
covered by patent 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 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 nondiscriminatory. 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 prepared by Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7,
Software and systems engineering, in cooperation with the Software & Systems Engineering Standards Committee
of the IEEE Computer Society, under the Partner Standards Development Organization cooperation agreement
between ISO and IEEE.
This second edition of ISO/IEC/IEEE 26513 cancels and replaces ISO/IEC 26513:2009 which has been
technically revised. The main changes compared to the previous edition are as follows:
― additions to the Terms and Definitions;
― updates to the Documentation Review and System Test of Documentation sections;
― expanded sections for Accessibility Testing and Translation and Localization Review and Testing;
― replacement of the editorial checklists in Annex A with Usercentered Test and Review Guidelines;
― editorial changes; and
― additions to the bibliography.
v
© ISO/IEC 2017 – All rights reserved
© IEEE 2017 – All rights reserved
Introduction
Welldesigned 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 of 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 initial 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
guidance i
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.