系统和软件工程.用户文件检验员和评审员详细要求

[中文适用范围]： 本国际标准支持软件用户获得一致、完整、准确且易于使用的文档的兴趣。本国际标准定义了测试用户文档产品的过程。本国际标准既不鼓励也不 discourages 使用印刷或电子（屏幕）媒体进行文档，也不鼓励或 discourages 使用任何特定的文档测试或管理工具或方法。本国际标准规定了用于测试和审查用户文档的过程（第 5 章）。它不仅限于生命周期的测试和审查阶段，还包括信息管理和文档管理过程中的活动。本国际标准提供了测试和审查用户文档的最低要求（第 6 章），包括用户在工作环境中使用的系统和软件的印刷文档和屏幕文档。它适用于印刷用户手册、在线帮助、教程和用户参考文档。本国际标准中的条款顺序并不暗示软件用户文档应按此顺序进行测试。在每个条款中，要求尽可能独立于媒体。附录 A 和 B 中的信息性检查表可用于文档过程的每个阶段，以验证是否已执行适当的步骤，并且成品具有可接受的质量。本国际标准可用于测试和审查以下类型的文档：除软件以外的产品文档，例如硬件或设备；使用动画、视频和声音的多媒体系统；主要为正式培训项目使用的基于计算机的培训（CBT）包和专用课程材料；为安装人员、计算机操作员或系统管理员（而非最终用户）生成的文档；描述系统软件内部操作的维护文档。本国际标准适用于测试人员、审查人员和其他相关角色，包括各种专家：可用性测试人员、文档审查人员和主题专家；规划和设计文档集结构和格式的信息设计师和架构师；识别预期用户将使用软件执行的任务的可用性专家和业务分析师。其他对文档过程有角色和兴趣的人也可以查阅本国际标准。软件开发过程或文档过程的经理应将文档测试视为其计划和管理活动的一部分。项目经理在计划和审查文档测试方面发挥着重要作用。文档测试可能会突出显示用于创建或显示屏幕文档的工具中的任何缺陷或不一致之处。同样，文档的可用性测试可能会突出显示文档及其相关图形和其他媒体的呈现或布局中的缺陷或不一致之处。因此，应让多个角色参与文档测试，因为他们的工作会影响用户文档的内容、显示或呈现，例如用于创建屏幕文档的工具开发人员、制作作为文档一部分显示材料的平面设计师，以及识别使文档更易访问和易于使用的原则的人因专家，以及共同设计屏幕文档呈现的用户界面设计师和人体工程学专家。在某些组织中，这些角色可能有不同的名称，或者个人可能执行多个角色。其他需要了解文档测试过程的人员也需要了解，例如作者应了解他们生成的文档的测试过程，从另一个部门或组织获取文档的采购方可能想知道已执行的测试以及遵循的文档测试过程。本国际标准适用于所有类型的组织，无论是否存在专门的文档部门。在所有情况下，它可用作本地标准和程序的基础。假设读者具有测试或审查过程的经验或一般知识。本国际标准仅涉及文档的评估，而不涉及其所支持软件的评估。文档也包含在软件产品的评估中，如 ISO/IEC 25000 系列标准。特别是 ISO/IEC 25051:2006 软件工程 - 软件产品质量要求和评估 (SQuaRE) - 商业现货 (COTS) 软件产品质量要求和测试说明。参考文献提供了有关管理、准备和测试用户文档过程的额外指导。 [外文原描述]： ISO/IEC 26513:2009 supports the interest of software users in receiving consistent, complete, accurate, and usable documentation. It defines the process in which user documentation products are tested. ISO/IEC 26513:2009 is intended neither to encourage nor discourage the use of either printed or electronic (on-screen) media for documentation, or of any particular documentation testing or management tools or methodologies. ISO/IEC 26513:2009 specifies processes for use in testing and reviewing of user documentation. It is not limited to the test and review phase of the life cycle, but includes activities throughout the Information Management and Documentation Management processes. ISO/IEC 26513:2009 provides the minimum requirements for the testing and reviewing of user documentation, including both printed and on-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 ISO/IEC 26513:2009 does not imply that the software user documentation should be tested in this 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 quality. ISO/IEC 26513:2009 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 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; maintenance documentation describing the internal operation of systems software. ISO/IEC 26513:2009 is applicable 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; usability specialists and business analysts who identify the tasks the intended users will perform with the software. It can also be consulted by those with other roles and interests in the documentation process. Managers of the software development 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 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 result, 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 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 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 documentation 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. ISO/IEC 26513:2009 is intended for use in all types of organizations, whether or not a dedicated 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. ISO/IEC 26513:2009 deals with the evaluation of documentation only, and not with 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 quality of Commercial-Off-The-Shelf (COTS) software product and instructions for testing.