ISO/IEC/IEEE FDIS 26513

• Status: Not Published
• ICS: 35.080 - Software
• Technical Committee: ISO/IEC JTC 1/SC 7 - Software and systems engineering
• Drafting Committee: ISO/IEC JTC 1/SC 7/WG 2 - System software documentation
• Current Stage: 5020 - FDIS ballot initiated: 2 months. Proof sent to secretariat
• Start Date: 03-Aug-2026
• Completion Date: 03-Aug-2026

• Revises: ISO/IEC/IEEE 26513:2017 - Systems and software engineering — Requirements for testers and reviewers of information for users
• Effective Date: 17-Feb-2024

Overview

ISO/IEC/IEEE FDIS 26513:2026 sets out internationally recognized guidelines for the testing and review of information for users in systems and software engineering. This standard is designed to ensure that user documentation - including printed manuals, online help, embedded assistance, websites, and reference materials - is consistent, complete, accurate, and usable. The review and validation processes described are applicable across a range of industries and organization types, supporting both initial product development and subsequent updates.

Effective information for users enhances user satisfaction, reduces training and support costs, and strengthens the brand reputation of software and system producers. Testing and reviewing these materials throughout the information management lifecycle are essential to meeting user needs, regulatory requirements, and quality targets.

Key Topics

ISO/IEC/IEEE FDIS 26513:2026 covers a comprehensive suite of processes and methods for validating user information:

• Review and Assessment Activities: Guidance on planning, conducting, and recording quality reviews of documentation.
• Evaluation Strategy: Outlining requirements, objectives, evaluation criteria, and method selection for assessing user information.
• Testing Processes: Structured procedures for system tests, usability testing, accessibility, and translation/localization reviews.
• AI-based Evaluation: Consideration of artificial intelligence tools as part of the review and assessment workflows.
• Quality Metrics and Reporting: Methods for tracking usability, completeness, efficiency, and effectiveness of user documents.
• Resource Planning: Recommendations for allocating roles, time, and resources in testing and review initiatives.
• Continuous Improvement: Support for integrating feedback and lessons learned into documentation processes.

By employing these techniques, organizations ensure that documentation remains relevant, actionable, and user-focused throughout its lifecycle.

Applications

The standard’s core value lies in its practical application for organizations developing, maintaining, or overseeing information for users alongside their systems or software products. Typical uses include:

• Developing User Manuals and Online Help: Applying validation techniques to ensure documentation enables users to perform tasks efficiently and without errors.
• Supporting Agile and Iterative Development: Incorporating reviews and testing at every stage, not only post-development, to keep documentation aligned with frequent software updates.
• Integrating Accessibility and Usability Standards: Testing for compliance so documentation is accessible to people with diverse abilities and needs.
• Localizing Content: Reviewing and testing translations to deliver consistent, high-quality information in multiple languages and cultural contexts.
• Cross-team Collaboration: Enabling technical writers, subject-matter experts, usability specialists, and support teams to align on documentation quality.
• Regulatory and Quality Audits: Demonstrating adherence to best practices for documentation in regulated environments, boosting trust and market acceptance.

ISO/IEC/IEEE 26513 is relevant whether documentation is managed by dedicated information development teams or by cross-functional groups.

Related Standards

Organizations striving for excellence in user information quality should be aware of these related international standards:

• ISO/TR 25060: Systems and software engineering - Common industry format for usability requirements.
• ISO 25062: Common industry format for usability test reports.
• ISO/IEC 25063 & 25064: Quality models for user documentation.
• ISO/IEC/IEEE 29119-3: Software and systems engineering - Software testing.
• ISO/IEC/IEEE 24765: Systems and Software Engineering Vocabulary for terminology alignment.

Aligning with ISO/IEC/IEEE FDIS 26513 ensures that your documentation processes meet rigorous international best practices, helping deliver value to end users while supporting organizational goals for quality, compliance, and customer satisfaction.

FINAL DRAFT
International
Standard
ISO/IEC/IEEE
FDIS
ISO/IEC JTC 1/SC 7
Systems and software
Secretariat: BIS
engineering — Testing and
Voting begins on:
reviewing of information for users
2026-08-03
Ingénierie des systèmes et du logiciel — Exigences pour testeurs
Voting terminates on:
et vérificateurs de documentation utilisateur
2026-09-28
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
Reference number © ISO/IEC 2026
FINAL DRAFT
International
Standard
ISO/IEC/IEEE
FDIS
ISO/IEC JTC 1/SC 7
Systems and software
Secretariat: BIS
engineering — Testing and
Voting begins on:
reviewing of information for users
Ingénierie des systèmes et du logiciel — Exigences pour testeurs
Voting terminates on:
et vérificateurs de documentation utilisateur
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
© ISO/IEC 2026
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
© IEEE 2026
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO or IEEE at the INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
respective address below or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
ISO copyright office Institute of Electrical and Electronics Engineers, Inc MADE IN NATIONAL REGULATIONS.
CP 401 • Ch. de Blandonnet 8 3 Park Avenue, New York
CH-1214 Vernier, Geneva NY 10016-5997, USA
Phone: [phone]
Email: [e-mail] Email: [e-mail]
Website: www.iso.org Website: www.ieee.org
Published in Switzerland
Reference number © ISO/IEC 2026
© ISO/IEC 2026, © IEEE 2026 – All rights reserved
ii
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Review and evaluative testing processes of information for users . 7
4.1 Process overview .7
4.2 Review and assessment activities .7
5 Evaluation strategy for reviewing and testing information for users . 9
5.1 Requirements, objectives, and constraints .9
5.2 Evaluation activities for information for users .10
5.3 Selection of an evaluation method .11
5.4 Evaluation criteria .11
5.5 Test process for information for users .11
5.6 Project requirements affecting the evaluation of information for users . 12
5.7 Resource requirements and planning . 12
5.7.1 General . 12
5.7.2 Resources for evaluation of information for users . 13
5.8 Impact of evaluation on project schedules . 13
6 Evaluation methods and procedures for information for users . 14
6.1 General .14
6.2 Review of Information for users .14
6.2.1 General .14
6.2.2 Objectives for review of information for users . 15
6.2.3 Requirements for review of information for users . 15
6.2.4 Plan for reviewing information for users . 15
6.2.5 Administering quality review .16
6.2.6 Managing the review results .17
6.3 Reviewing using Artificial Intelligence (AI)-based tools.17
6.4 Configuration change review .18
6.5 System test of information for users . .18
6.5.1 General .18
6.5.2 Planning system test of information for users .19
6.5.3 Creating the system test plan for information for users .19
6.5.4 Entry and exit criteria of system test plan for information for users . 20
6.5.5 Approval of system test plan for information for users .21
6.5.6 Problem management for system testing of information for users .21
6.6 Usability testing of information for users .21
6.6.1 General .21
6.6.2 Types of usability evaluation. 22
6.6.3 Objectives and activities for usability testing of information for users . 22
6.6.4 Measures and metrics for usability targets . 23
6.6.5 Planning usability tests for information for users . 23
6.7 Usability evaluation reports of information for users . 25
6.7.1 General . 25
6.7.2 Reports of the usability evaluation for information for users . 25
6.7.3 Problem management for usability testing of information for users . 26
6.8 Accessibility testing of information for users. 26
6.8.1 Scope of accessibility testing . 26
6.8.2 Performing accessibility tests .27
6.9 Translation and localization review and testing .27
6.9.1 General .27
6.9.2 Planning for translation and localization review and testing .27

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
iii
6.9.3 Performing translation and localization review and testing .27
6.10 AI-based usability testing . 28
Annex A (informative) Guidelines for reviewing and testing .29
Bibliography .34
Important Notices and Disclaimers Concerning IEEE Standards Documents .37

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
iv
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 non-governmental, in liaison with ISO and IEC, also take part in the work.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/
IEC Directives, Part 2 (see www.iso.org/directives or www.iec.ch/members_experts/refdocs).
IEEE Standards documents are developed within IEEE Societies and subcommittees of IEEE Standards
Association (IEEE SA) Board of Governors. IEEE develops its standards through an accredited consensus
development process, which brings together volunteers representing varied viewpoints and interests to
achieve the final product. IEEE standards are documents developed by volunteers with scientific, academic,
and industry-based expertise in technical working groups. Volunteers are not necessarily members of
IEEE or IEEE SA and participate without compensation from IEEE. While IEEE administers the process and
establishes rules to promote fairness in the consensus development process, IEEE does not independently
evaluate, test, or verify the accuracy of any of the information or the soundness of any judgments contained
in its standards.
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not
received notice of (a) patent(s) which may be required to implement this document. However, implementers
are cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 7, Software and systems engineering, in cooperation with the Systems and Software
Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards Development
Organization cooperation agreement between ISO and IEEE.
This second edition replaces the first edition (ISO/IEC/IEEE 26513:2017), which has been technically
revised.
The main changes are as follows:
— replacement of terms to reflect ‘information for users’ throughout to align with related standards;
— updates to roles, process and evaluation approaches (impact of Agile development methods in industry);
— identification of AI implications in review and testing of information for users.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
v
Introduction
Well-designed information for users not only assists end 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 information for users during development provides feedback to
information developers regarding the accuracy and usability of their work. This document addresses
the evaluation and testing of information for users to perform tasks, make decisions in context, and gain
understanding of software and systems. It applies to both initial development and subsequent releases of
software and systems.
This document is independent of the software tools that can be used to produce information for users and
applies to any modality of information for users, embedded in the software and integrated user interface
(labels, icons, navigation, etc.). Much of its guidance is applicable to information for users for systems as well
as to the software used to control machinery or hardware devices. Increasingly, information developers are
responsible for interface design and interaction behaviour.
This document is developed to assist those who review and test information for users as part of the
information management process. This document defines the information management and validation
processes of ISO/IEC/IEEE 12207 from the information assessors' and testers' standpoints. Readers are
assumed to have experience with or general knowledge of reviewing and testing processes.
The order of clauses in this document does not imply that information for users is meant to be reviewed,
assessed, edited, or tested in this order.
NOTE 1 Information for users is also included in evaluation of the software or system, as specified in the following
documents:
— ISO/TR 25060;
— ISO 25062;
— ISO/IEC 25063;
— ISO/IEC 25064;
— ISO/IEC/IEEE 29119-3.
This document supports the interest of software and systems users in receiving consistent, complete,
accurate, and usable information for users and specifies processes for use in reviewing and testing of
information for users (Clause 5, 6 & 7). It is not limited to the review and test stage of the software and
system lifecycle but includes activities throughout the information management process. The principles may
also support earlier design activities (see Annex A). Information for users may be provided for application
software, systems software, applications on mobile devices, software that controls machinery, and hardware
devices.
© ISO/IEC 2026, © IEEE 2026 – All rights reserved
vi
FINAL DRAFT International Standard ISO/IEC/IEEE FDIS 26513:2026(en)
Systems and software engineering — Testing and reviewing of
information for users
1 Scope
This document applies to information such as printed or electronic user manuals, online help, embedded
user assistance, tutorials, websites, or reference materials.
This document is applicable to all types of organizations, whether a dedicated information development
team is present or not. In all cases, it can be used as a basis for local guidelines and procedures.
This document is applicable to reviewers, testers, and other related roles, including a variety of specialists:
— reviewers of information for users, and subject-matter experts;
— information developers and architects who plan the structure and format of products for information for
users;
— usability specialists and business analysts who identify the tasks the intended users perform with the
software;
— editors;
— customer support groups such as training, technical support, installers, system administrators.
This 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 information for users as part of their planning and management activities.
NOTE 2 Testing of information for users can highlight problems with the software. Resolving problems with the
software is not in the scope of this document.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this standard, the following terms and definitions apply.
ISO, IEC and IEEE maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org
— IEEE Standards Dictionary Online: available at http:// dictionary .ieee .org
NOTE For additional terms and definitions in the field of systems and software engineering, see
ISO/IEC/IEEE 24765, which is published periodically as a “snapshot” of the SEVOCAB (Systems and Software
Engineering Vocabulary) database and is publicly accessible at www .computer .org/ sevocab.

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
3.1
A/B testing
technique to determine the effectiveness (3.10) of minor changes in a product or design where “A” represents
the original version and “B” represents the modified version
Note 1 to entry: This notation is typically used in usability testing (3.42). In this instance, A/B does not refer to alpha
and beta testing (3.38).
3.2
accessibility
extent to which products, systems, services, environments and facilities can be used by people from a
population with the widest range of user needs, characteristics, and capabilities to achieve identified goals
in identified contexts of use
Note 1 to entry: Context of use includes direct use or use supported by assistive technologies.
[SOURCE: ISO 9241-940:2017, 3.1]
3.3
artificial intelligence
AI
capability of an engineered system to acquire, process and apply knowledge and skills
[SOURCE: ISO/IEC TR 29119-11:2020, 3.1.13]
3.4
audience
category of users sharing the same or similar characteristics and needs (e.g. purpose in using the information
for users (3.2), tasks, education level, abilities, training, experience) that determine the content, structure,
and use of the intended information
Note 1 to entry: There can be different audiences for information for users (e.g. management, data entry, maintenance,
engineering, business professionals).
[SOURCE: ISO/IEC/IEEE 23026:2023, 3.1.2]
3.5
caution
advisory information that states that performing some action can result in minor or moderate injury or lead
to consequences that are unwanted or undefined, such as loss of data or an equipment problem
Note 1 to entry: See also danger (3.8) and warning (3.48).
[SOURCE: ISO/IEC/IEEE 26514:2022, 3.1.8]
3.6
complete information
information including all critical information (3.7) and any necessary, relevant information for the intended
audience (3.4) and purpose
[SOURCE: ISO/IEC/IEEE 15289:2019, 3.1.3, modified — The term has been changed from "complete" to
"complete information"; the words "and purpose" have been added.]
3.7
critical information
information on the safe use of the product, the security of the information created with the product, or the
privacy of the information created by or stored with the product
3.8
danger
hazardous situation, which if not avoided, can result in death or serious injury
Note 1 to entry: See also caution (3.5) and warning (3.48).

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
[SOURCE: ISO 3864-2:2016, 3.3, modified — The words "signal word used to indicate" have been removed
from the definition; note 1 to entry has been added.]
3.9
document,noun
uniquely identified unit of information for human use
EXAMPLE A report, specification, manual or book, in printed or electronic form.
Note 1 to entry: A document can be a single information item or part of a larger information item.
[SOURCE: ISO/IEC/IEEE 15289:2019, 3.1.10, modified — ", noun" has been added.]
3.10
effectiveness
accuracy and completeness with which users achieve specified goals
[SOURCE: ISO 9241-11:2018, 3.1.12]
3.11
efficiency
resources expended in relation to the effectiveness (3.10)
Note 1 to entry: Typical resources include time, human effort, costs and materials.
[SOURCE: ISO 9241-11:2018, 3.1.13, modified — "used" has been replaced by "expended"; "results achieved"
has been replaced by "accuracy and completeness with which users achieve goals".]
3.12
evaluation
systematic determination of the extent to which an entity meets its specified criteria
3.13
function
part of a software application providing functionality including features for users to carry out their tasks
3.14
hazard
source of potential harm
[SOURCE: ISO 3864-2:2016, 3.6, modified — Note 1 to entry has been removed.]
3.15
heuristic evaluation
assessment by one or more experts who judge conformance to a recognized set of principles
3.16
illustration
graphical element set apart from the main body of text and normally cited within the main text
Note 1 to entry: In this document, the term "illustration" is used as the generic term for tables, figures, exhibits, screen
captures, flow charts, diagrams, drawings, icons, and other graphical elements.
3.17
information architect
person who develops the structure of an information space and the semantics for accessing information on
tasks, system functions (3.13) and features, and other information
[SOURCE: ISO/IEC/IEEE 26514:2022, 3.1.26]

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
3.18
information development
process of development concerned with determining what content is provided in information for users (3.21)
and what the nature of the information is
3.19
information developer
person who creates information for users (3.21)
3.20
information development lead
person who leads the activities of preparing information for users (3.21)
3.21
information for users
information provided by the supplier that provides the target audience (3.4) with concepts, procedures (3.28)
and reference material for the safe, effective, and efficient use of a supported product during its life cycle
EXAMPLE Printed manuals, onscreen information, and stand-alone online help are examples of information for
users (3.21).
Note 1 to entry: It can be provided separately or embedded in the product or both.
Note 2 to entry: The term “information for users” in this document is intended as a synonym for “information for use”
as used in IEC/IEEE 82079-1 and is defined as such, although it is recognised that the respective ideas, while similar,
are not identical.
[SOURCE: IEC/IEEE 82079-1:2019, 3.17, modified — The preferred term has been changed from "information
for use" to "information for users"; the admitted term "instructions for use" has been removed; the original
EXAMPLE and notes to entry have been removed and replaced by new ones.]
3.22
link
hyperlink
reference from some part of content to some other part of content or object
3.23
localization
creation of a national or specific regional version of a product or its information for users (3.21)
Note 1 to entry: Information for users can be localized even if the product has not been localized.
3.24
mobile device
portable computing device, typically having a wireless internet connection and a small display screen with
touch, pen, or keyboard input, and auditory input and output features
Note 1 to entry: Mobile devices must fulfil special usability (3.41) requirements due to their size and available features
for input and output.
3.25
navigation
act of accessing information for users (3.21) and viewing different topics (3.39)
[SOURCE: ISO/IEC/IEEE 26514:2022 3.1.35]
3.26
onscreen information for users
information for users (3.21) that is intended to be read on the screen by the user (3.45) while using the
software
EXAMPLE Pop-up help and help text on a screen.

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
[SOURCE: ISO/IEC/IEEE 26514:2022 3.1.36]
3.27
platform
combination of software and hardware that makes up the operating environment in which a program runs
3.28
procedure
ordered series of steps (3.32) that specify how to perform a task
3.29
project
endeavour with defined start and finish criteria undertaken to create a product or service in accordance
with specified resources and requirements
[SOURCE: ISO/IEC/IEEE 26514:2022, 3.1.4]
3.30
project manager
person with overall responsibility for the management and running of a project (3.29)
3.31
satisfaction
extent to which the user's physical, cognitive and emotional responses that result from the use of a system,
product or service meet the user’s needs and expectations
[SOURCE: ISO 25062:2025, 3.12]
3.32
step
element (numbered list item) in a procedure (3.28) that tells a user (3.45) to perform an action (or actions)
Note 1 to entry: Responses by the software are not considered to be steps.
[SOURCE: ISO/IEC/IEEE 26514:2022, 3.1.48]
3.33
style
set of language-specific editorial conventions covering grammar, terminology, punctuation, capitalization,
usage, word choice, structured authoring elements, and media
3.34
tailoring
process by which individual requirements in specifications, standards, and related documents (3.9) are
evaluated and made applicable to a specific project (3.29) by selection, and in some exceptional cases,
modification of existing or addition of new requirements
3.35
test lead
person who leads entire testing (3.38) process
3.36
test participant
person who provides feedback and allows data collection during testing (3.38)
3.37
test protocol
list of the steps (3.32) to be followed in the test

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
3.38
testing
activity in which a system or component is executed under specified conditions, the results are observed or
recorded, and an evaluation (3.12) is made of some aspect of the system or component
3.39
topic
coherent part of an information product with a heading that deals with a single subject
EXAMPLE Instructions on how to print the current document (3.9).
[SOURCE: IEC/IEEE 82079-1:2019, 3.43]
3.40
transparency
AI level of accessibility to the algorithm and data used by the AI-based system
[SOURCE: ISO/IEC TR 29119-11:2020]
3.41
usability
extent to which a system, product, or service can be used by specified users to achieve specified goals with
effectiveness (3.10), efficiency (3.11), and satisfaction (3.31) in a specified context of use
[SOURCE: ISO 9241-210:2019, modified — Notes 1 and 2 to entry have been removed.]
3.42
usability testing
evaluation (3.12) that involves representative users performing specific tasks with the system to enable the
measurement of effectiveness (3.10), efficiency (3.11), and/or user satisfaction (3.31)
[SOURCE: ISO TR 25060:2023, 3.4.1]
3.43
usability specialist
person who observes users performing tasks using the system, product or service and information for users
(3.21), and records the actions the user (3.45) took, problems the user encountered, and comments the user
made during the test, and interprets these records to evaluate the results of the testing (3.38)
3.44
use case
description of the behavioural requirements of a system and its interaction with a user (3.45)
[SOURCE: ISO/IEC/IEEE 26515:2018, 3.15]
3.45
user
person who interacts with a system, product or service
Note 1 to entry: Users of a system, product or service include people who operate the system, people who make use of
the output of the system and people who support the system (including providing maintenance and training).
[SOURCE: ISO 9241-11:2018, 3.1.7]
3.46
validation
confirmation, through the provision of objective evidence, that the requirements for a specific intended use
or application have been fulfilled
Note 1 to entry: A system is able to accomplish its intended use, goals, and objectives (i.e., meet stakeholder
requirements) in the intended operational environment.
[SOURCE: ISO/IEC/IEEE 12207:2017, 3.1.71]

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
3.47
verification
confirmation, through the provision of objective evidence, that specified requirements have been fulfilled
Note 1 to entry: Verification is a set of activities that compares a system or system element against the required
characteristics. This includes, but is not limited to, specified requirements, design description, and the system itself.
[SOURCE: ISO/IEC/IEEE 12207:2017, 3.1.72]
3.48
warning
advisory information in information for users (3.21) that states that performing some action can lead to a
potentially hazardous situation which, if not avoided, can result in death or serious injury
[SOURCE: ISO/IEC/IEEE 26514:2022, 3.1.56]
4 Review and evaluative testing processes of information for users
4.1 Process overview
This clause covers the processes involved in review and evaluative testing of information for users.
Reviewers and testers of information for users work within the software lifecycle processes or system
lifecycle processes, which are defined in ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288. The applicable
processes are the following:
— implementation;
— validation;
— verification;
— maintenance.
4.2 Review and assessment activities
The typical lifecycle of information for users and its review and testing includes the following activities:
— user needs assessment;
— task analysis;
— requirements definition for information for users;
— design specification for information for users;
— draft or prototype of information for users;
— revision;
— early testing (prototype, information architecture, issue identification);
— beta review (accuracy, editing);
— evaluative testing (efficiency, effectiveness, satisfaction, accessibility);
— final release;
— evaluative testing, optional (performance, learnability, A/B testing);
— testing of support content, such as release notes, accompanying system, or software updates.
Some of these activities can be shared responsibilities across the development team. The information
developer focuses on the information for users and how it will be developed, reviewed, and assessed. In

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
addition to leading the activities of preparing information for users, the information development lead
identifies reviewers during the design and development stages. Review activities include review of structure,
format, media and technical accuracy against established guidelines and standards on information for
users. Within the validation process described in ISO/IEC/IEEE 12207, the relevant functions are performed
so that representative users can successfully complete their intended tasks and the product satisfies its
intended use.
Testing and reviewing information for users includes media, embedded information, user interface,
navigation, and information architecture. These should be part of the same processes as the product
lifecycle and should be performed in conjunction with the development of the - system so that the system
and the information for users are tested, distributed, and maintained together. The evaluative testing of
the information for users should be a part of the development of the product as a whole and not a separate
exercise. Although accurate information for users cannot be completed until the system has been fully
developed, the information for users and the product both benefit from concurrent development and testing.
The validation and verification processes apply to information for users developed under both the classic
information development process (development of a new product with new information for users), and more
complex circumstances, such as reuse of legacy information for users that should be:
— converted to a different format or different media;
— converted into different information products such as tutorials, online help, chatbots, or troubleshooting
guides;
— adapted for different products acquired or supplied by an organization;
— modified to adhere to new regulations, business process guidelines, or compliance requirements;
— converted into different languages or variants including localization and tailoring;
— contextually modified for multiple software/hardware devices.
In addition, the test process should also be applied in the following circumstances:
— a previous software or system is being upgraded, offered in a new version or on different operating
systems, or tailored as part of system integration requiring the revision of previous information for
users;
— information for users developed along with software or system development methods such as Agile
methods that require multiple iterations before release;
— software interfaces or information for users delivered on multiple platforms with tailoring for these
environments;
— information migrated from unstructured content to structured content.
Testing and reviewing information for users is greatly assisted by the presence of other project materials
produced during the system lifecycle, such as development plans, interface design specifications, prototypes,
system design specification, system test plan, release records, and usability evaluation protocols. Other
content specific to the information management process may be produced, such as style guides and business
processes for content management, information review guidelines, and accessibility standards.
NOTE 1 ISO/IEC/IEEE 15289 provides recommendations for the required documents throughout the systems and
software lifecycle.
NOTE 2 This document is also related to ISO/IEC 25000 and ISO/IEC 14598-6. These documents describe the quality
metrics characteristics of software and the evaluation process for providing quality in a software or system. The
same processes can be used to help the information for users meet the required quality through the use of evaluation
metrics (such as effectiveness and satisfaction, learnability, errors, and safety).
NOTE 3 Of relevance is ISO 25062 as usability performance targets are often closely associated with information
design and content.
© ISO/IEC 2026, © IEEE 2026 – All rights reserved
For the sake of simplicity, this document describes the lifecycle as if there were a clear starting point for
developing information for users and a clear end point. However, there is no sequence of activities that
can be followed in all cases for all products and all types of information. For example, implementation and
review activities are very closely related, as are testing and maintenance, and the way they relate together
varies among projects.
NOTE 4 ISO 21500 can be consulted for managing a content management project.
NOTE 5 ISO/IEC/IEEE 26511 provides details on the management of information development.
5 Evaluation strategy for reviewing and testing information for users
5.1 Requirements, objectives, and constraints
The purpose of evaluating information for users is to help ensure that the information for users assists users
achieve their goals. This clause describes the processes of evaluating information for users in two forms:
reviewing and evaluative testing. Evaluations are performed throughout the development, production, and
maintenance lifecycle.
Evaluation shall check whether information developed is able to meet user needs, expectations, and
requirements. Managers, developers, testers, and maintainers evaluate the quality of the information for
users. Managers shall be responsible for assuring that the quality of information for users has been evaluated.
Evaluations can be performed by developers, testers, maintainers, managers, and other roles. Ultimately, the
users should be satisfied with the quality; however, managers, developers, testers, and maintainers shall
accept the quality before the information for users is released to the users. The quality of the evaluation
depends on the participation of various roles:
— Managers. Managers are more concerned with overall quality than with specific quality characteristics.
They can assign different weights to certain characteristics to reflect the business needs of the
organization, comparing the information for users to what is commercially available in the market and
what is less costly to produce. Managers should be aware that the quality of information for users can
appreciably affect costs for customer support, legal requirements, and future sales.
— Product developers. Product developers are concerned with the conformance of information for users to
the product functionality.
— Information developers. Information developers transform technical content into information for users
to support users performing tasks with the system or software.
— Product testers. Product testers are concerned with how the product operates in its intended functions in
the same way as product developers but should have a better understanding of how the product supports
the users' tasks, and whether the information for users matches the product, and helps the users to
accomplish tasks. For information for users, interface design, navigation, media, and legal requirements,
the product test team can provide valuable assessment of accuracy. Product testers can stress-test to
assess performance under various conditions including extreme or sensitive conditions.
— Technical support staff. Staff who maintain the software and systems after the product release have
special requirements for quality. Technical support staff can be concerned with the accuracy, the
availability, and the searchability of different versions of the information for users.
— Content managers. Content managers are concerned with how information can be controlled for
subsequent product releases, different versions, information reuse, metadata associated with content
for search and retrieval, and translation and localization.
— Editors. Editors are concerned with conformance to organizational style, formats, language, terminology,
and structure. Editors also check for the use of plain language.
NOTE Resources are identified in the ISO plain language standard - bibliography. International Plain Language
Federation. Available at: https:// www .iplfederation .org/ plain -language/ bibliography/ , See ISO 24495-1.

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
— Usability specialists. Usability specialists plan and oversee usability testing. They recruit and record the
actions of test participants, the problems the participants encountered, and comments made during and
after the test activity. They also interpret records of usability test data (
...

Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
ISO/IEC JTC 1/SC 7
Style Definition
...
Secretariat: BIS
Style Definition
...
Style Definition
...
Date: 2026-04-2307-17
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Systems and software engineering — Testing and reviewing of information
Style Definition
...
for users Style Definition
...
Style Definition
...
Ingénierie des systèmes et du logiciel — Tester — Exigences pour testeurs et réviser les informations destinées aux
Style Definition
...
utilisateursvérificateurs de documentation utilisateur
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
FDIS stage
Formatted: Font: Bold
Formatted: HeaderCentered
© ISO/IEC 2026, /Published in Switzerland
Formatted: Default Paragraph Font
© IEEE 2026
Formatted: Left: 1.5 cm, Right: 1.5 cm, Top: 1.4 cm,
Bottom: 1 cm, Header distance from edge: 1.27 cm,
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication
Footer distance from edge: 0.5 cm
may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying
Formatted: Default Paragraph Font
and microfilm, or posting on the internet or an intranet, without prior written permission in writing. Permission can be
requested from either ISO, IEC or IEEE at the respective address below or ISO’s member body in the country of the
Formatted: Default Paragraph Font
requester.
ISO copyright office Institute of Electrical and Electronics Engineers, Inc
Formatted: zzCopyright address
CP 401 • Ch. de Blandonnet 8 • CP 401 3 Park Avenue, New York
CH-1214 Vernier, Geneva, Switzerland NY 10016-5997, USA Tel. +
Phone: + 41 22 749 01 11
Formatted: zzCopyright address
E-mail: [e-mail]
Website: www.iso.org
Published in Switzerland
Fax [phone]
[e-mail] www.iso.org
[e-mail] gwww.ieee.org

Formatted: FooterPageRomanNumber
© ISO/IEC/IEEE 2026 – All rights reserved
ii
Formatted: Font: 11 pt
Formatted: HeaderCentered, Left, Space After: 0 pt,
Line spacing: single, Tab stops: Not at 0.71 cm

Formatted: Font: 10 pt
Formatted: Font: 10 pt
Formatted: FooterCentered, Left, Space Before: 0 pt,
Tab stops: Not at 17.2 cm
Formatted: Font: 11 pt
Formatted: FooterPageRomanNumber, Left, Space
After: 0 pt, Tab stops: Not at 17.2 cm
© ISO/IEC 2026, © /IEEE 2026 – All rights reserved
iii
Formatted: Font: Bold
Formatted: HeaderCentered
Contents Formatted: Widow/Orphan control, Adjust space
between Latin and Asian text, Adjust space between
Asian text and numbers
Foreword . vii
Introduction . ix
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Review and evaluative testing processes of information for users . 8
4.1 Process overview . 8
4.2 Review and assessment activities . 8
5 Evaluation strategy for reviewing and testing information for users . 10
5.1 Requirements, objectives, and constraints . 10
5.2 Evaluation activities for information for users . 11
5.3 Selection of an evaluation method . 12
5.4 Evaluation criteria . 12
5.5 Test process for information for users . 13
5.6 Project requirements affecting the evaluation of information for users . 13
5.7 Resource requirements and planning . 14
5.8 Impact of evaluation on project schedules . 15
6 Evaluation methods and procedures for information for users . 15
6.1 General . 15
6.2 Review of Information for users . 16
6.3 Reviewing using Artificial Intelligence (AI)-based tools . 19
6.4 Configuration change review . 20
6.5 System test of information for users . 20
6.6 Usability testing of information for users . 23
6.7 Usability evaluation reports of information for users . 28
6.8 Accessibility testing of information for users. 30
6.9 Translation and localization review and testing . 31
6.10 AI-based usability testing . 32
Annex A (informative) Guidelines for reviewing and testing . 33
Bibliography . 38
Important Notices and Disclaimers Concerning IEEE Standards Documents . 41

Foreword . vi
Introduction . viii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Review and evaluative testing processes of information for users . 8
4.1 Process overview . 8
4.2 Review and assessment activities . 8
5 Evaluation strategy for reviewing and testing information for users . 10
5.1 Requirements, objectives, and constraints . 10
5.2 Evaluation activities for information for users . 11
5.3 Selection of an evaluation method . 11
5.4 Evaluation criteria . 12
Formatted: FooterPageRomanNumber
© ISO/IEC/IEEE 2026 – All rights reserved
iv
Formatted: Font: 11 pt
Formatted: HeaderCentered, Left, Space After: 0 pt,
Line spacing: single, Tab stops: Not at 0.71 cm
5.5 Test process for information for users . 12
5.6 Project requirements affecting the evaluation of information for users . 13
5.7 Resource requirements and planning . 13
5.7.1 General 13
5.7.2 Resources for evaluation of information for users . 14
5.8 Impact of evaluation on project schedules . 14
6 Evaluation methods and procedures for information for users . 15
6.1 General 15
6.2 Review of Information for users . 15
6.2.1 General 15
6.2.2 Objectives for review of information for users . 16
6.2.3 Requirements for review of information for users . 16
6.2.4 Plan for reviewing information for users . 16
6.2.5 Administering quality review. 17
6.2.6 Managing the review results . 18
6.3 Reviewing using Artificial Intelligence (AI)-based tools . 18
6.4 Configuration change review . 19
6.5 System test of information for users . 19
6.5.1 General 19
6.5.2 Planning system test of information for users . 20
6.5.3 Creating the system test plan for information for users . 21
6.5.4 Entry and exit criteria of system test plan for information for users . 21
6.5.5 Approval of system test plan for information for users . 22
6.5.6 Problem management for system testing of information for users . 22
6.6 Usability testing of information for users . 22
6.6.1 General 22
6.6.2 Types of usability evaluation . 23
6.6.3 Objectives and activities for usability testing of information for users . 23
6.6.4 Measures and metrics for usability targets . 24
6.6.5 Planning usability tests for information for users . 24
6.7 Usability evaluation reports of information for users . 26
6.7.1 General 26
6.7.2 Reports of the usability evaluation for information for users . 26
6.7.3 Problem management for usability testing of information for users . 27
6.8 Accessibility testing of information for users. 27
6.8.1 Scope of accessibility testing . 27
6.8.2 Performing accessibility tests . 28
6.9 Translation and localization review and testing . 28
6.9.1 General 28
6.9.2 Planning for translation and localization review and testing . 28
6.9.3 Performing translation and localization review and testing . 28
6.10 AI-based usability testing . 29
Annex A (informative) Guidelines for reviewing and testing . 31
A.1 User-centred test and review guidelines . 31
A.1.1 General . 31
A.1.2 Support for an action-oriented approach . 31
A.1.3 Assistance for users to easily understand and use task instructions . 31
Formatted: Font: 10 pt
A.1.4 Support for real task . 32
A.1.5 Support for using AI-based information . 32 Formatted: Font: 10 pt
A.2 Support for error recognition and recovery . 33
Formatted: FooterCentered, Left, Space Before: 0 pt,
A.3 Support for information access . 33
Tab stops: Not at 17.2 cm
A.4 Content for translation . 34
Formatted: Font: 11 pt
Bibliography . 36
Formatted: FooterPageRomanNumber, Left, Space
Important Notices and Disclaimers Concerning IEEE Standards Documents . 39
After: 0 pt, Tab stops: Not at 17.2 cm
© ISO/IEC 2026, © /IEEE 2026 – All rights reserved
v
Formatted: Font: Bold
Formatted: HeaderCentered
Formatted: FooterPageRomanNumber
© ISO/IEC/IEEE 2026 – All rights reserved
vi
Formatted: Font: 11 pt
Formatted: HeaderCentered, Left, Space After: 0 pt,
Line spacing: single, Tab stops: Not at 0.71 cm
Foreword
Formatted: Adjust space between Latin and Asian text,
Adjust space between Asian text and numbers
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 non-governmental, in liaison with ISO and IEC, also take part in the work.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of
document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC
Directives, Part 2 (see www.iso.org/directives or www.iec.ch/members_experts/refdocs).
Formatted: Hyperlink, No underline, Font color: Auto
IEEE Standards documents are developed within IEEE Societies and subcommittees of IEEE Standards
Association (IEEE SA) Board of Governors. IEEE develops its standards through an accredited consensus
development process, which brings together volunteers representing varied viewpoints and interests to
achieve the final product. IEEE standards are documents developed by volunteers with scientific, academic,
and industry-based expertise in technical working groups. Volunteers are not necessarily members of IEEE or
IEEE SA and participate without compensation from IEEE. While IEEE administers the process and establishes
rules to promote fairness in the consensus development process, IEEE does not independently evaluate, test,
or verify the accuracy of any of the information or the soundness of any judgments contained in its standards.
ISO and IEC draw attention to the possibility that the implementation of this document may involve the use of
(a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any claimed
patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not received
notice of (a) patent(s) which may be required to implement this document. However, implementers are
cautioned that this may not represent the latest information, which may be obtained from the patent database
available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held responsible for
identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
Formatted: Default Paragraph Font
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
Formatted: Default Paragraph Font
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Formatted: Widow/Orphan control, Adjust space
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see
between Latin and Asian text, Adjust space between
www.iso.org/iso/foreword.html.www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-
Asian text and numbers
standardswww.iec.ch/understanding-standards.
Formatted: Default Paragraph Font
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Formatted: Default Paragraph Font
Subcommittee SC 7, Software and systems engineering, in cooperation with the Systems and Software
Formatted: Default Paragraph Font
Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards Development
Formatted: Adjust space between Latin and Asian text,
Organization cooperation agreement between ISO and IEEE.
Adjust space between Asian text and numbers, Tab
stops: Not at 0.7 cm + 1.4 cm + 2.1 cm + 2.8 cm +
This second edition replaces the first edition (ISO/IEC/IEEE 26513:2017), which has been technically revised.
3.5 cm + 4.2 cm + 4.9 cm + 5.6 cm + 6.3 cm + 7 cm
The main changes are as follows: Formatted: Font: 10 pt
Formatted: Font: 10 pt
— — replacement of terms to reflect ‘information for users’ throughout to align with related standards;
Formatted: FooterCentered, Left, Space Before: 0 pt,
Tab stops: Not at 17.2 cm
— — updates to roles, process and evaluation approaches (impact of Agile development methods in
industry);
Formatted: Font: 11 pt
Formatted: FooterPageRomanNumber, Left, Space
identification of AI implications in review and testing of information for users.
— —
After: 0 pt, Tab stops: Not at 17.2 cm
© ISO/IEC 2026, © /IEEE 2026 – All rights reserved
vii
Formatted: Font: Bold
Formatted: HeaderCentered
Any feedback or questions on this document should be directed to the user’s national standards body. A
Formatted: Adjust space between Latin and Asian text,
complete listing of these bodies can be found at www.iso.org/members.html and www.iec.ch/national-
Adjust space between Asian text and numbers
committees.
Formatted: FooterPageRomanNumber
© ISO/IEC/IEEE 2026 – All rights reserved
viii
Formatted: Font: 11 pt
Formatted: HeaderCentered, Left, Space After: 0 pt,
Line spacing: single, Tab stops: Not at 0.71 cm
Introduction
Formatted: Widow/Orphan control, Adjust space
between Latin and Asian text, Adjust space between
Asian text and numbers
Well-designed information for users not only assists end 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,
Formatted: Adjust space between Latin and Asian text,
validation testing, and expert review of information for users during development provides feedback to Adjust space between Asian text and numbers
information developers regarding the accuracy and usability of their work. This document addresses the
evaluation and testing of information for users to perform tasks, make decisions in context, and gain
understanding of software and systems. It applies to both initial development and subsequent releases of
software and systems.
This document is independent of the software tools that can be used to produce information for users and
applies to any modality of information for users, embedded in the software and integrated user interface
(labels, icons, navigation, etc.). Much of its guidance is applicable to information for users for systems as well
as to the software used to control machinery or hardware devices. Increasingly, information developers are
responsible for interface design and interaction behaviour.
This document is developed to assist those who review and test information for users as part of the
information management process. This document defines the information management and validation
processes of ISO/IEC/IEEE 12207 from the information assessors' and testers' standpoints. Readers are
Formatted: Default Paragraph Font
assumed to have experience with or general knowledge of reviewing and testing processes.
Formatted: Default Paragraph Font
The order of clauses in this document does not imply that information for users is meant to be reviewed,
assessed, edited, or tested in this order.
Formatted: Adjust space between Latin and Asian text,
Adjust space between Asian text and numbers, Tab
NOTE 1 Information for users is also included in evaluation of the software or system, as specified in the following
documents: stops: Not at 0.7 cm + 1.4 cm + 2.1 cm + 2.8 cm +
3.5 cm + 4.2 cm + 4.9 cm + 5.6 cm + 6.3 cm + 7 cm
— — ISO/TR 25060;
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
— — ISO 25062;
Formatted: Default Paragraph Font
— — ISO/IEC 25063;
Formatted: Default Paragraph Font
— — ISO/IEC 25064;
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
— — ISO/IEC/IEEE 29119-3.
Formatted: Default Paragraph Font
This document supports the interest of software and systems users in receiving consistent, complete, accurate,
Formatted: Default Paragraph Font
and usable information for users and specifies processes for use in reviewing and testing of information for
Formatted: Default Paragraph Font
users (Clause 5, 6 & 7).(Clause 5, 6 & 7). It is not limited to the review and test stage of the software and system
lifecycle but includes activities throughout the information management process. The principles may also
Formatted: Default Paragraph Font
support earlier design activities (see Annex A). Information for users may be provided for application
Formatted: Default Paragraph Font
software, systems software, applications on mobile devices, software that controls machinery, and hardware
Formatted: Default Paragraph Font
devices.
Formatted: Normal, Adjust space between Latin and

Asian text, Adjust space between Asian text and
numbers
Annex A).
Formatted: Font: 10 pt
Formatted: Font: 10 pt
Formatted: FooterCentered, Left, Space Before: 0 pt,
Tab stops: Not at 17.2 cm
Formatted: Font: 11 pt
Formatted: FooterPageRomanNumber, Left, Space
After: 0 pt, Tab stops: Not at 17.2 cm
© ISO/IEC 2026, © /IEEE 2026 – All rights reserved
ix
Systems and software engineering — Testing and reviewing of
information for users
1 Scope Formatted: Left: 1.5 cm, Right: 1.5 cm, Top: 1.4 cm,
Bottom: 1 cm, Header distance from edge: 1.27 cm,
Footer distance from edge: 0.5 cm
This document describes testing and review activities that result in consistent, complete, accurate, and usable
information for users (Clause 5, 6 & 7). It is not limited to the review and test stage of the software and system
lifecycle but includes activities throughout the information management process. The principles may also
support earlier design activities (see Annex A). Information for users may be provided for application
software, systems software, applications on mobile devices, software that controls machinery, and hardware
devices.
© ISO/IEC/IEEE 2026 – All rights reserved
ii
DRAFT International Standard ISO/IEC/IEEE FDIS 26513:2026(en)

Systems and software engineering It — Testing and reviewing of
information for users
Formatted: Left: 1.5 cm, Right: 1.5 cm, Top: 1.4 cm,
1 Scope
Bottom: 1 cm, Header distance from edge: 1.27 cm,
Footer distance from edge: 0.5 cm
This document applies to information such as printed or electronic user manuals, online help, embedded user
assistance, tutorials, websites, or reference materials.
Formatted: Adjust space between Latin and Asian text,
Adjust space between Asian text and numbers
This document is applicable to all types of organizations, whether a dedicated information development team
is present or not. In all cases, it can be used as a basis for local guidelines and procedures.
This document is applicable to reviewers, testers, and other related roles, including a variety of specialists:
— — reviewers of information for users, and subject-matter experts;
Formatted: Adjust space between Latin and Asian text,
Adjust space between Asian text and numbers, Tab
— — information developers and architects who plan the structure and format of products for information
stops: Not at 0.7 cm + 1.4 cm + 2.1 cm + 2.8 cm +
for users;
3.5 cm + 4.2 cm + 4.9 cm + 5.6 cm + 6.3 cm + 7 cm
— — usability specialists and business analysts who identify the tasks the intended users perform with the
software;
— — editors;
— — customer support groups such as training, technical support, installers, system administrators.
This document can also be consulted by those with other roles and interests in the information management
Formatted: Adjust space between Latin and Asian text,
process. Managers of the software development process or the information management process consider the Adjust space between Asian text and numbers
testing of information for users as part of their planning and management activities.
NOTE 2 Testing of information for users can highlight problems with the software. Resolving problems with the
Formatted: Adjust space between Latin and Asian text,
software is not in the scope of this document.
Adjust space between Asian text and numbers, Tab
stops: Not at 0.7 cm + 1.4 cm + 2.1 cm + 2.8 cm +
2 Normative references
3.5 cm + 4.2 cm + 4.9 cm + 5.6 cm + 6.3 cm + 7 cm
Formatted: Adjust space between Latin and Asian text,
There are no normative references in this document.
Adjust space between Asian text and numbers
3 Terms and definitions
For the purposes of this standard, the following terms and definitions apply.
Formatted: Adjust space between Latin and Asian text,
Adjust space between Asian text and numbers, Tab
ISO, IEC and IEEE maintain terminology databases for use in standardization at the following addresses:
stops: Not at 0.7 cm + 1.4 cm + 2.1 cm + 2.8 cm +
3.5 cm + 4.2 cm + 4.9 cm + 5.6 cm + 6.3 cm + 7 cm
— — ISO Online browsing platform: available at https://www.iso.org/obphttps://www.iso.org/obp
Formatted: Hyperlink, No underline, Underline color:
Auto, Font color: Auto
— — IEC Electropedia: available at http://www.electropedia.org
Formatted: Hyperlink, No underline, Underline color:
Auto, Font color: Auto
— — IEEE Standards Dictionary Online: available at http://dictionary.ieee.org
Formatted: Font: 11 pt
Formatted: Footer, Space After: 0 pt, Line spacing:
single, Tab stops: Not at 17.2 cm
© ISO/IEC 2026 © IEEE 2026 – All rights reserved
Formatted: Font: Bold
Formatted: HeaderCentered
NOTE For additional terms and definitions in the field of systems and software engineering, see
ISO/IEC/IEEE 24765, which is published periodically as a “snapshot” of the SEVOCAB (Systems and Software Engineering
Vocabulary) database and is publicly accessible at www.computer.org/sevocab.
Formatted: Hyperlink, No underline, Underline color:
Auto, Font color: Auto
3.1 3.1
Formatted
...
A/B testing
technique to determine the effectiveness (3.10)(3.10) of minor changes in a product or design where “A”
Formatted: Font: Not Italic
represents the original version and “B” represents the modified version
Formatted
...
Note 1 to entry: This notation is typically used in usability testing (3.42).(3.42). In this instance, A/B does not refer to
Formatted: Font: Not Italic
alpha and beta testing (3.38).(3.38).
Formatted
...
3.2 3.2
Formatted
...
accessibility
extent to which products, systems, services, environments and facilities can be used by people from a
Formatted: Default Paragraph Font
population with the widest range of user needs, characteristics, and capabilities to achieve identified goals in
Formatted: Default Paragraph Font
identified contexts of use
Formatted: Default Paragraph Font
Note 1 to entry: Context of use includes direct use or use supported by assistive technologies.
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
[SOURCE: ISO 9241-940:2017, 3.1]
Formatted
...
3.3 3.3
Formatted: Default Paragraph Font
artificial intelligence
Formatted: Default Paragraph Font
AI
capability of an engineered system to acquire, process and apply knowledge and skills
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
[SOURCE: ISO/IEC TR 29119-11:2020, 3.1.13]
Formatted: Default Paragraph Font
3.4 3.4
Formatted: Default Paragraph Font
audience
Formatted: Font: Not Italic
category of users sharing the same or similar characteristics and needs (e.g. purpose in using the information
for users (3.2),(3.2), tasks, education level, abilities, training, experience) that determine the content,
Formatted
...
structure, and use of the intended information
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
Note 1 to entry: There can be different audiences for information for users (e.g. management, data entry, maintenance,
engineering, business professionals).
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
[SOURCE: ISO/IEC/IEEE 23026:2023, 3.1.2]
Formatted
...
3.5 3.5
Formatted
...
caution
Formatted: Default Paragraph Font
advisory information that states that performing some action can result in minor or moderate injury or lead
to consequences that are unwanted or undefined, such as loss of data or an equipment problem
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
Note 1 to entry: See also danger (3.8)(3.8) and warning (3.48).(3.48).
Formatted
...
[SOURCE: ISO/IEC/IEEE 26514:2022, 3.1.8]
Formatted: Font: Not Italic
3.6 3.6
Formatted: Font: Not Italic
complete information
Formatted: Default Paragraph Font
information including all critical information (3.7)(3.7) and any necessary, relevant information for the
Formatted: Default Paragraph Font
intended audience (3.4)(3.4) and purpose
Formatted: Default Paragraph Font
[SOURCE: ISO/IEC/IEEE 15289:2019, 3.1.3, modified — The term has been changed from "complete" to
Formatted: Default Paragraph Font
"complete information"; the words "and purpose" have been added.]
Formatted: FooterPageNumber
© ISO/IEC/IEEE 2026 – All rights reserved
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
3.7 3.7
critical information Formatted
...
information on the safe use of the product, the security of the information created with the product, or the
Formatted
...
privacy of the information created by or stored with the product
Formatted
...
3.8 3.8
Formatted
...
danger
Formatted
...
hazardous situation, which if not avoided, can result in death or serious injury
Formatted
...
Note 1 to entry: See also caution (3.5)(3.5) and warning (3.48).(3.48).
Formatted
...
Formatted
[SOURCE: ISO 3864-2:2016, 3.3, modified — The words "signal word used to indicate" have been removed .
from the definition; note 1 to entry has been added.]
Formatted
...
Formatted
...
3.9 3.9
Formatted
document, noun
...
uniquely identified unit of information for human use
Formatted
...
Formatted
...
EXAMPLE: A report, specification, manual or book, in printed or electronic form.
Formatted
...
Note 1 to entry: A document can be a single information item or part of a larger information item.
Formatted
...
[SOURCE: ISO/IEC/IEEE 15289:2019, 3.1.10, modified — ", noun" has been added.] Formatted
...
Formatted
...
3.10 3.10
Formatted
effectiveness .
accuracy and completeness with which users achieve specified goals
Formatted
...
Formatted
...
[SOURCE: ISO 9241-11:2018, 3.1.12]
Formatted
...
3.11 3.11
Formatted
...
efficiency
Formatted
...
resources expended in relation to the effectiveness (3.10)(3.10)
Formatted
...
Note 1 to entry: Typical resources include time, human effort, costs and materials.
Formatted
...
[SOURCE: ISO 9241-11:2018, 3.1.13, modified — "used" has been replaced by "expended"; "results achieved"
Formatted
...
has been replaced by "accuracy and completeness with which users achieve goals".]
Formatted
...
Formatted
3.12 3.12
...
evaluation
Formatted
...
systematic determination of the extent to which an entity meets its specified criteria
Formatted
...
3.13 3.13 Formatted
...
function
Formatted
...
part of a software application providing functionality including features for users to carry out their tasks
Formatted
...
3.14 3.14
Formatted
...
hazard
Formatted
...
source of potential harm
Formatted
...
[SOURCE: ISO 3864-2:2016, 3.6, modified — Note 1 to entry has been removed.]
Formatted
...
Formatted
...
3.15 3.15
heuristic evaluation Formatted
...
assessment by one or more experts who judge conformance to a recognized set of principles
Formatted
...
Formatted
...
© ISO/IEC 2026, © /IEEE 2026 – All rights reserved
Formatted
...
Formatted
...
Formatted: Font: Bold
Formatted: HeaderCentered
3.16 3.16
illustration
graphical element set apart from the main body of text and normally cited within the main text
Note 1 to entry: In this document, the term "illustration" is used as the generic term for tables, figures,
Formatted: Adjust space between Latin and Asian text,
exhibits, screen captures, flow charts, diagrams, drawings, icons, and other graphical elements.
Adjust space between Asian text and numbers, Tab
stops: Not at 0.7 cm + 1.4 cm + 2.1 cm + 2.8 cm +
3.17 3.17
3.5 cm + 4.2 cm + 4.9 cm + 5.6 cm + 6.3 cm + 7 cm
information architect
Formatted: TermNum2, Widow/Orphan control, Adjust
person who develops the structure of an information space and the semantics for accessing information on
space between Latin and Asian text, Adjust space
tasks, system functions (3.13)(3.13) and features, and other information
between Asian text and numbers
[SOURCE: ISO/IEC/IEEE 26514:2022, 3.1.26]
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
3.18 3.18
Formatted: Default Paragraph Font
information development
process of development concerned with determining what content is provided in information for users
Formatted: Default Paragraph Font
(3.21)(3.21) and what the nature of the information is
Formatted: Adjust space between Latin and Asian text,
Adjust space between Asian text and numbers
3.19 3.19
information developer Formatted: TermNum2, Widow/Orphan control, Adjust
person who creates information for users (3.21)(3.21) space between Latin and Asian text, Adjust space
between Asian text and numbers
3.20 3.20
Formatted: Font: Not Italic
information development lead
Formatted: Font: Not Italic
person who leads the activities of preparing information for users (3.21)(3.21)
Formatted: Font: Not Italic
3.21 3.21
Formatted: Adjust space between Latin and Asian text,
information for users
Adjust space between Asian text and numbers, Tab
information provided by the supplier that provides the target audience (3.4)(3.4) with concepts, procedures
stops: Not at 0.7 cm + 1.4 cm + 2.1 cm + 2.8 cm +
(3.28)(3.28) and reference material for the safe, effective, and efficient use of a supported product during its
3.5 cm + 4.2 cm + 4.9 cm + 5.6 cm + 6.3 cm + 7 cm
life cycle
Formatted: Default Paragraph Font
EXAMPLE: Printed manuals, onscreen information, and stand-alone online help are examples of information for users Formatted: Default Paragraph Font
(3.21).(3.21).
Formatted: Default Paragraph Font
Note 1 to entry: It can be provided separately or embedded in the product or both.
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
Note 2 to entry: The term “information for users” in this document is intended as a synonym for “information for use”
as used in IEC/IEEE 82079-1 and is defined as such, although it is recognised that the respective ideas, while similar, are Formatted: Default Paragraph Font
not identical.
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
[SOURCE: IEC/IEEE 82079--1:2019, 3.17, modified — The preferred term has been changed from
"information for use" to "information for users"; the admitted term "instructions for use" has been removed;
Formatted: Adjust space between Latin and Asian text,
the original EXAMPLE and notes to entry have been removed and replaced by new ones.]
Adjust space between Asian text and numbers
Formatted: TermNum2, Widow/Orphan control, Adjust
3.22 3.22
space between Latin and Asian text, Adjust space
link
between Asian text and numbers
hyperlink
Formatted: Regular, Font: Bold
reference from some part of content to some other part of content or object
Formatted: Font: Bold
3.23 3.23
Formatted: Adjust space between Latin and Asian text,
localization
Adjust space between Asian text and numbers, Tab
creation of a national or specific regional version of a product or its information for users (3.21)(3.21)
stops: Not at 0.7 cm + 1.4 cm + 2.1 cm + 2.8 cm +
3.5 cm + 4.2 cm + 4.9 cm + 5.6 cm + 6.3 cm + 7 cm
Note 1 to entry: Information for users can be localized even if the product has not been localized.
Formatted: FooterPageNumber
© ISO/IEC/IEEE 2026 – All rights reserved
Formatted
...
Formatted
...
Formatted
3.24 3.24
...
mobile device
Formatted
...
portable computing device, typically having a wireless internet connection and a small display screen with
Formatted
...
touch, pen, or keyboard input, and auditory input and output features
Formatted
...
Note 1 to entry: Mobile devices must fulfil special usability (3.41)(3.41) requirements due to their size
Formatted
...
and available features for input and output.
Formatted
...
3.25 3.25
Formatted
...
navigation
Formatted
...
act of accessing information for users (3.21)(3.21) and viewing different topics (3.39)(3.39)
Formatted
...
[SOURCE: ISO/IEC/IEEE 26514:2022 3.1.35]
Formatted
...
Formatted
3.26 3.26 .
onscreen information for users
Formatted
...
information for users (3.21)(3.21) that is intended to be read on the screen by the user (3.45)(3.45) while using
Formatted
...
the software
Formatted
...
EXAMPLE: Pop-up help and help text on a screen.
Formatted
...
Formatted
[SOURCE: ISO/IEC/IEEE 26514:2022 3.1.36]
...
Formatted
...
3.27 3.27
Formatted
...
platform
combination of software and hardware that makes up the operating environment in which a program runs Formatted
...
Formatted
...
3.28 3.28
Formatted
procedure .
ordered series of steps (3.32)(3.32) that specify how to perform a task
Formatted
...
Formatted
...
3.29 3.29
project Formatted
...
endeavour with defined start and finish criteria undertaken to create a product or service in accordance with
Formatted
...
specified resources and requirements
Formatted
...
[SOURCE: ISO/IEC/IEEE 26514:2022, 3.1.4]
Formatted
...
Formatted
...
3.30 3.30
Formatted
project manager
...
person with overall responsibility for the management and running of a project (3.29)(3.29)
Formatted
...
Formatted
...
3.31 3.31
satisfaction Formatted
...
extent to which the user's physical, cognitive and emotional responses that result from the use of a system,
Formatted
...
product or service meet the user’s needs and expectati
...