This International 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.<\/p>\n
This International Standard 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.<\/p>\n
This International Standard specifies processes for use in testing and reviewing of user documentation (Clause 5). 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.<\/p>\n
This International Standard provides the minimum requirements for the testing and reviewing of user documentation (Clause 6), 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.<\/p>\n
The order of clauses in this International Standard does not imply that the software user documentation should be tested in this order.<\/p>\n
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.<\/p>\n
This International Standard can be helpful for testing and reviewing the following types of documentation:<\/p>\n
documentation of products other than software, for example, hardware or devices;<\/p>\n<\/li>\n
multimedia systems using animation, video, and sound;<\/p>\n<\/li>\n
computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<\/p>\n<\/li>\n
documentation produced for installers, computer operators, or system administrators who are not end users;<\/p>\n<\/li>\n
maintenance documentation describing the internal operation of systems software.<\/p>\n<\/li>\n<\/ul>\n
This International Standard is applicable to testers, reviewers, and other related roles, including a variety of specialists:<\/p>\n
usability testers, documentation reviewers, and subject-matter experts;<\/p>\n<\/li>\n
information designers and architects who plan the structure and format of products in a documentation set;<\/p>\n<\/li>\n
usability specialists and business analysts who identify the tasks the intended users will perform with the software.<\/p>\n<\/li>\n<\/ul>\n
The International Standard can also be consulted by those with other roles and interests in the documentation process.<\/p>\n
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.<\/p>\n
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.<\/p>\n
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.<\/p>\n
This International Standard 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.<\/p>\n
This International Standard 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 \u2014 Software product Quality Requirements and Evaluation (SQuaRE) \u2014 Requirements for quality of Commercial-Off-The-Shelf (COTS) software product and instructions for testing.<\/i><\/p>\n
The works listed in the Bibliography provide additional guidance on the processes of managing, preparing, and testing user documentation.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 9<\/td>\n | Scope <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | Conformance Definition of conformance <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | Conformance situations Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | User documentation process within the systems\/software life <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | Documentation evaluation process requirements, objectives, a General <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | Documentation evaluation activities Selection of an evaluation method Documentation review <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | Documentation test Project requirements affecting documentation evaluation <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | Resource requirements and planning <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | Impact of evaluation on project schedules Documentation evaluation methods and procedures <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | Documentation review Planning documentation review Requirements for documentation review Objectives for documentation review Developing a plan for documentation review <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | Documentation review procedures <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | Managing the results of documentation review Problem resolution and the documentation review cycle System test of documentation <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | Planning system test of documentation <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | Objectives for system test of documentation Requirements for system test of documentation Metrics and measures for system test of documentation <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | Creating the system documentation test plan Documentation system test plan elements <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | Documentation system test plan entry\/exit criteria Examples of entry criteria Examples of exit criteria <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | Documentation system test plan approvals Performing and assessing results of system test of documenta Problem resolution and the system test of documentation life Usability testing of documentation <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | Objectives for usability testing of documentation Measures and metrics for documentation usability testing <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | Planning usability tests <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | Creating the documentation usability test plan <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | Performing usability test of documentation Usability test reports <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | Problem resolution for documentation usability tests Accessibility testing of documentation Planning accessibility tests <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | Performing accessibility tests Localization and customization testing Planning for localization and customization testing Performing localization and customization testing <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | Problem resolution process <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Systems and software engineering. Requirements for testers and reviewers of user documentation<\/b><\/p>\n |