1、 Reference number ISO/IEC 26513:2009(E) ISO/IEC 2009INTERNATIONAL STANDARD ISO/IEC 26513 First edition 2009-10-15 Systems and software engineering Requirements for testers and reviewers of user documentation Ingnierie des systmes et du logiciel Exigences pour testeurs et vrificateurs de documentatio
2、n utilisateur ISO/IEC 26513:2009(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the
3、 editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file ca
4、n be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretaria
5、t at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2009 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 writin
6、g from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2009 All rights reservedISO/IEC
7、26513:2009(E) ISO/IEC 2009 All rights reserved iiiContents Page Foreword iv Introduction.v 1 Scope1 2 Conformance .2 2.1 Definition of conformance2 2.2 Conformance situations .3 3 Terms and definitions .3 4 User documentation process within the systems/software life cycle .8 5 Documentation evaluati
8、on process requirements, objectives, and constraints9 5.1 General .9 5.2 Documentation evaluation activities .10 5.3 Selection of an evaluation method 10 5.4 Documentation review 10 5.5 Documentation test .11 5.6 Project requirements affecting documentation evaluation.11 5.7 Resource requirements an
9、d planning.12 5.7.1 Impact of evaluation on project schedules.13 6 Documentation evaluation methods and procedures .13 6.1 Documentation review 14 6.1.1 Planning documentation review 14 6.1.2 Documentation review procedures .16 6.1.3 Managing the results of documentation review.17 6.1.4 Problem reso
10、lution and the documentation review cycle.17 6.2 System test of documentation .17 6.2.1 Planning system test of documentation .18 6.2.2 Performing and assessing results of system test of documentation22 6.2.3 Problem resolution and the system test of documentation life cycle .22 6.3 Usability testin
11、g of documentation .22 6.3.1 Objectives for usability testing of documentation.23 6.3.2 Measures and metrics for documentation usability testing .23 6.3.3 Planning usability tests 24 6.3.4 Performing usability test of documentation.26 6.3.5 Problem resolution for documentation usability tests27 6.4
12、Accessibility testing of documentation 27 6.4.1 Planning accessibility tests27 6.4.2 Performing accessibility tests .28 6.5 Localization and customization testing 28 6.5.1 Planning for localization and customization testing .28 6.5.2 Performing localization and customization testing .28 6.6 Problem
13、resolution process.29 Annex A (informative) Checklists for user documentation 30 Annex B (informative) Test and review checklist 37 Bibliography53 ISO/IEC 26513:2009(E) iv ISO/IEC 2009 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (the International Ele
14、ctrotechnical 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 tech
15、nical 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 information technology, ISO and IEC have established a joint techn
16、ical 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 Standards adopted by the joint technical committee are ci
17、rculated 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 the subject of patent rights. ISO and IEC shall not be he
18、ld responsible for identifying any or all such patent rights. ISO/IEC 26513 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering. ISO/IEC 26513:2009(E) ISO/IEC 2009 All rights reserved vIntroduction Anyone who uses appli
19、cation software needs accurate information about how the software will help the users accomplish a task. The documentation might be the first tangible item that the users see, and so influences the first impressions the users have of the product. If the information is supplied in a convenient form a
20、nd is easy to find and understand, the users can quickly become proficient at using the product. Therefore, well- designed documentation not only assists the users and helps to reduce the cost of training and support, but also enhances the reputation of the product, its producer, and its suppliers.
21、This International Standard addresses the evaluation and testing of user documentation. It applies to both initial development and subsequent releases of the software and user documentation. This International Standard is independent of the software tools that might be used to produce documentation,
22、 and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as to software user documentation. This International Standard conforms with ISO/IEC 26514:2008 Systems and software engineering Req
23、uirements for designers and developers of user documentation, ISO/IEC 15288:2008, Systems and software engineering System life cycle processes, and ISO/IEC 12207:2008, Systems and software engineering Software life cycle processes. This International Standard was developed to assist those who test a
24、nd review software user documentation as part of the software life cycle process. This International Standard defines the Documentation Management and Validation processes of ISO/IEC 12207:2008 from the testers standpoint. This International Standard may be used as a conformance or a guidance docume
25、nt for products, projects and organizations claiming conformance to ISO/IEC 15288:2008 or ISO/IEC 12207:2008. INTERNATIONAL STANDARD ISO/IEC 26513:2009(E) ISO/IEC 2009 All rights reserved 1Systems and software engineering Requirements for testers and reviewers of user documentation 1 Scope This Inte
26、rnational Standard supports the interest of software users in receiving consistent, complete, accurate, and usable documentation. This International Standard defines the process in which user documentation products are tested. This International Standard is intended neither to encourage nor discoura
27、ge the use of either printed or electronic (on-screen) media for documentation, or of any particular documentation testing or management tools or methodologies. This International Standard specifies processes for use in testing and reviewing of user documentation (Clause 5). It is not limited to the
28、 test and review phase of the life cycle, but includes activities throughout the Information Management and Documentation Management processes. This International Standard provides the minimum requirements for the testing and reviewing of user documentation (Clause 6), including both printed and on-
29、screen documents used in the work environment by the users of systems software. It applies to printed user manuals, online help, tutorials, and user reference documentation. The order of clauses in this International Standard does not imply that the software user documentation should be tested in th
30、is order. In each clause, the requirements are media-independent, as far as possible. The informative checklists found in Annexes A and B may be used at each phase of the documentation process to verify that the appropriate steps have been carried out, and that the finished product has acceptable qu
31、ality. This International Standard can be helpful for testing and reviewing the following types of documentation: documentation of products other than software, for example, hardware or devices; multimedia systems using animation, video, and sound; computer-based training (CBT) packages and speciali
32、zed course materials intended primarily for use in formal training programs; documentation produced for installers, computer operators, or system administrators who are not end users; maintenance documentation describing the internal operation of systems software. This International Standard is appl
33、icable to testers, reviewers, and other related roles, including a variety of specialists: usability testers, documentation reviewers, and subject-matter experts; information designers and architects who plan the structure and format of products in a documentation set; ISO/IEC 26513:2009(E) 2 ISO/IE
34、C 2009 All rights reserved usability specialists and business analysts who identify the tasks the intended users will perform with the software. The International Standard can also be consulted by those with other roles and interests in the documentation process. Managers of the software development
35、 process or the documentation process should consider the testing of documentation as part of their planning and management activities. Project managers, in particular, have an important role in planning the testing and reviewing of documentation. Testing of the documentation is likely to highlight
36、any defects or nonconformances in tools that are used to create or display on-screen documentation. Similarly, usability testing of the documentation is likely to highlight defects or nonconformances with the presentation or layout of documentation and associated graphics and other media. As a resul
37、t, there are a number of roles that should be involved in the testing of documentation because their work affects the content, display or presentation of documentation for the user, for example, developers of tools for creating on-screen documentation, graphic designers producing material displayed
38、as part of the documentation, and human-factors experts who identify principles for making documentation more accessible and easily used, also user interface designers and ergonomics experts working together to design the presentation of the documentation on-screen. In some organizations these roles
39、 may have different titles, or an individual may perform more than one of these roles. There are other roles that need to understand the test processes for the documentation, for example authors should understand the test processed for the documentation that they have produced and acquirers of docum
40、entation prepared by another department or organization might want to know what testing has been performed and the processes followed for the documentation that they are acquiring from a supplier. This International Standard is intended for use in all types of organizations, whether or not a dedicat
41、ed documentation department is present. In all cases, it may be used as a basis for local standards and procedures. Readers are assumed to have experience or general knowledge of testing or reviewing processes. This International Standard deals with the evaluation of documentation only, and not with
42、 the evaluation of the software it supports. Documentation is also included in evaluation of the software product, as in the ISO/IEC 25000 series of standards. In particular, ISO/IEC 25051:2006 Software engineering Software product Quality Requirements and Evaluation (SQuaRE) Requirements for qualit
43、y of Commercial-Off-The- Shelf (COTS) software product and instructions for testing. The works listed in the Bibliography provide additional guidance on the processes of managing, preparing, and testing user documentation. 2 Conformance This International Standard may be used as a conformance or a g
44、uidance document for projects and organizations claiming conformance to ISO/IEC 15288:2008, Systems and software engineering System life cycle processes, ISO/IEC 12207:2008, Systems and software engineering Software life cycle processes or both. 2.1 Definition of conformance When the selected softwa
45、re life cycle processes are tailored, the organization or project may claim conformance to this International Standard for its documentation process. Throughout this International Standard, “shall“ is used to express a provision that is binding, “should“ to express a recommendation among other possi
46、bilities, and “may“ to indicate a course of action permissible within the limits of this International Standard. When using this International Standard as a guide, replace the term “shall” with “should”. ISO/IEC 26513:2009(E) ISO/IEC 2009 All rights reserved 3This International Standard is meant to
47、be tailored so that only necessary and cost-effective requirements are applied. Tailoring may take the form of specifying approaches to comply with its mandatory requirements, or altering its non-mandatory recommendations and approaches to reflect the particular software and documentation product mo
48、re explicitly. Tailoring decisions should be specified in the contract. NOTE: ISO/IEC 12207:2008 Annex A defines the tailoring process. Use of the nomenclature of this International Standard for the parts of user documentation (that is, chapters, topics, pages, screens, windows, etc.) is not require
49、d to claim conformance. 2.2 Conformance situations Conformance may be interpreted differently for various situations. The relevant situation shall be identified in the claim of conformance: a) When conformance is claimed for an organization, the organization shall make public a document declaring its tailoring of the life cycle process; NOTE 1: One possible way for an organization to deal with clauses that cite “the documentation plan“ or the “test plan“ is to specify that they shall be interpreted in the project plans
copyright@ 2008-2019 麦多课文库（www.mydoc123.com）网站版权所有
备案/许可证编号：苏ICP备17064731号-1