ISO/IEC/IEEE FDIS 29119-8

• Abstract:

  This standard provides requirements and guidelines on applying model-based testing (MBT) in accordance with the test processes defined in ISO/IEC/IEEE 29119-2. This document covers the following areas: a) Definitions for MBT b) Implementing ISO/IEC/IEEE 29119-2 for MBT c) Implementing ISO/IEC/IEEE 29119-3 for MBT Using MBT, the generation of testware is automated. This standard assumes that test execution is also automated. The implementation of the generation algorithm is tool dependent and therefore is out of the scope for this document. MBT tool selection is also out of the scope for this document. The MBT models and the information generated by the supporting MBT tools can be used, in part or whole, to satisfy the documentation requirements of ISO/IEC/IEEE 29119-3. Many MBT tools implement one or more of the test techniques and associated measures defined in ISO/IEC/IEEE 29119-4. These techniques are associated with individual tool implementation and are outside the scope of this document. This standard is applicable to model-based testing in all development lifecycle models.

• 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 26 - Software testing
• Current Stage: 5060 - Close of voting Proof returned by Secretariat
• Start Date: 12-Aug-2026
• Completion Date: 11-Aug-2026

Overview

ISO/IEC/IEEE FDIS 29119-8: Software and systems engineering - Software testing - Part 8: Model-based testing is an international standard published by ISO, IEC, and IEEE. This standard establishes globally recognized requirements and guidelines for using model-based testing (MBT) within software and systems engineering, in alignment with the ISO/IEC/IEEE 29119 software testing series. Model-based testing leverages formal and informal models of system behavior to support the definition, generation, and, typically, automation of test cases and test execution-improving efficiency and coverage in software validation processes.

This standard is designed to be applicable for organizations using any software development lifecycle model. It clarifies how MBT integrates with test processes (ISO/IEC/IEEE 29119-2) and test documentation (ISO/IEC/IEEE 29119-3), and highlights the role of MBT in automating the production of testware and test execution.

Key Topics

ISO/IEC/IEEE FDIS 29119-8 addresses several essential aspects of model-based testing, including:

• Definitions for MBT: Glossary of terms and concepts relating to model-based testing, ensuring common understanding across teams and organizations.
• Implementation of MBT: Guidance on applying MBT in accordance with the test process requirements of ISO/IEC/IEEE 29119-2, including process modifications for MBT at the strategic, planning, design, and implementation levels.
• Test Documentation: Requirements and strategies for documenting MBT activities to comply with ISO/IEC/IEEE 29119-3, including the use of MBT-generated testware for reporting and traceability.
• Automation Focus: Emphasis on automation for both test generation and test execution, streamlining regression, acceptance, and continuous integration testing.
• Relationship with Test Techniques: Explanation of how MBT models can satisfy various test techniques as outlined by ISO/IEC/IEEE 29119-4.
• Roles and Responsibilities: Typical roles involved in MBT, from test strategists and designers to automation engineers.

Applications

Implementing model-based testing according to ISO/IEC/IEEE FDIS 29119-8 brings concrete benefits and practical value in a range of software and system engineering contexts:

• Quality Assurance Automation: MBT enables systematic and automated generation of test cases directly from system models, significantly increasing consistency and repeatability.
• Complex System Verification: Particularly suited for large-scale, complex systems where manual test design is infeasible or error-prone.
• Continuous Integration and DevOps: Supports automated test execution pipelines, providing rapid feedback and facilitating agile/DevOps practices.
• Documentation and Compliance: The outputs of MBT, including models and generated testware, support compliance with organizational and regulatory requirements by ensuring traceability and conformance with the broader ISO/IEC/IEEE 29119 suite.
• Adaptability: Can be tailored to various domains, including embedded systems, business applications, and web services development, across different software lifecycle models.

Organizations adopting ISO/IEC/IEEE 29119-8 for MBT can improve their software testing maturity, reduce manual effort, and achieve higher confidence in system validation results.

Related Standards

This standard is part of the broader ISO/IEC/IEEE 29119 software testing framework, including:

• ISO/IEC/IEEE 29119-1: Concepts and definitions for software testing.
• ISO/IEC/IEEE 29119-2: Test process models, including organizational, management, and dynamic testing processes.
• ISO/IEC/IEEE 29119-3: Test documentation templates and guidance.
• ISO/IEC/IEEE 29119-4: Specification and description of test techniques, many of which can be addressed by MBT approaches.
• ISO/IEC/IEEE 29119-5: Guidance on keyword-driven testing, which can be integrated with MBT.

For organizations pursuing international best practices, adherence to ISO/IEC/IEEE 29119-8 ensures alignment with modern, systematic approaches to software testing and quality assurance, leveraging automation and model-based methodologies for maximum testing effectiveness.

FINAL DRAFT
International
Standard
ISO/IEC/IEEE
FDIS
29119-8
ISO/IEC JTC 1/SC 7
Software and systems
Secretariat: BIS
engineering — Software testing —
Voting begins on:
2026-06-16
Part 8:
Model-based testing
Voting terminates on:
2026-08-11
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
ISO/IEC/IEEE FDIS 29119­8:2026(en) © IEEE 2026

FINAL DRAFT
International
Standard
ISO/IEC/IEEE
FDIS
29119-8
ISO/IEC JTC 1/SC 7
Software and systems
Secretariat: BIS
engineering — Software testing —
Voting begins on:
Part 8:
Model-based testing
Voting terminates on:
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/IEEE FDIS 29119­8:2026(en) © IEEE 2026

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
3.1 Defined terms .2
3.2 Abbreviated terms .6
4 Conformance . 6
4.1 Intended usage .6
4.2 Full conformance .7
4.3 Tailored conformance .7
5 Introduction to MBT
........................................................................................................................................... .......................................................... 7
5.1 MBT concepts.7
5.2 MBT modes in test case generation and execution .8
6 Implementing ISO/IEC/IEEE 29119-2 for MBT . 9
7 MBT modifications of the ‘test strategy and planning’ process .10
7.1 Overview .10
7.2 Additional outcomes .11
7.3 Implementation of the design test strategy activity (TP5) for the MBT strategy .11
7.4 MBT strategy documentation . 12
7.4.1 Overview . 12
7.4.2 MBT strategy . 12
8 MBT modifications of the ‘test design and implementation’ process .13
8.1 Overview . 13
8.2 Implementation of the create test model (TD1) activity for MBT model creation . 13
Annex A (informative) MBT deployment with automated test execution .15
Annex B (informative) Additional considerations for MBT .23
Annex C (informative) Automated test case generation in MBT .33
Annex D (informative) Examples of MBT.37
Annex E (informative) Formal MBT . 51
Annex F (informative) Roles and responsibilities for the MBT tasks .55
Annex G (Normative) Mapping of MBT activities to ISO/IEC/IEEE 29119-2, ISO/IEC/IEEE 29119-
3 and ISO/IEC/IEEE 29119-4 .56
Bibliography .59
IEEE notices and abstract .60

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
iii
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 ISO/IEC documents should be noted. This document was drafted in accordance with the rules given in 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 involved in technical
working groups 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.
A list of all parts in the ISO/IEC/IEEE 29119 series can be found on the ISO and IEC websites.
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
iv
Introduction
The purpose of the ISO/IEC/IEEE 29119 series is to define an internationally agreed set of standards for
software testing that can be used by any organization when performing any form of software testing and
using any life cycle. This document explains how the ISO/IEC/IEEE 29119 series can be adopted to support
model-based testing (MBT).
Models can form an abstract or a complete description of a system from a particular perspective, for
example, software behaviour and design. Software testers can use this document to understand how models
of expected behaviour can be used in test design and implementation to derive test cases, including test
inputs and expected results.
The concepts relating to software testing defined in ISO/IEC/IEEE 29119-1 are also applicable to this
document.
The test process model on which MBT is based is defined in ISO/IEC/IEEE 29119-2. It comprises test process
descriptions that define the software testing processes at the organizational level, test management level and
dynamic test level. Supporting diagrams describing the processes are also provided in ISO/IEC/IEEE 29119-2.
The processes defined in ISO/IEC/IEEE 29119-2 are extended to support MBT.
The templates and examples of test documentation defined in ISO/IEC/IEEE 29119-3 also apply to this
document.
Software test design techniques that can be used during test design are defined in ISO/IEC/IEEE 29119-4.
Each test design technique defines a test model with syntax, semantics of the model and the way to derive
the test case from the test model in ISO/IEC/IEEE 29119-4. MBT models and the associated MBT tools can be
used to produce a test case that, in part or as a whole, satisfies the test techniques of ISO/IEC/IEEE 29119-4.
ISO/IEC/IEEE 29119-5 addresses using keywords to support testing. A MBT approach can generate keyword
test cases as defined in ISO/IEC/IEEE 29119-5.

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
v
FINAL DRAFT International Standard ISO/IEC/IEEE FDIS 29119-8:2026(en)
Software and systems engineering — Software testing —
Part 8:
Model-based testing
1 Scope
This document provides requirements and guidelines on applying model-based testing (MBT) following the
test processes defined in ISO/IEC/IEEE 29119-2. This document covers the following areas:
a) definitions for MBT;
b) implementing ISO/IEC/IEEE 29119-2 for MBT;
c) implementing ISO/IEC/IEEE 29119-3 for MBT.
Using MBT, the generation of a test case is systemized and automated. This document assumes that test
execution is also automated. The implementation of the generation algorithm is tool-dependent and,
therefore, is outside the scope of this document. MBT tool selection is also outside the scope of this document.
The test models and the information generated by the supporting MBT tools can be used, in part or whole, to
satisfy the documentation requirements of ISO/IEC/IEEE 29119-3. Many MBT tools implement one or more
test techniques and associated measures defined in ISO/IEC/IEEE 29119-4. These techniques are associated
with individual tool implementation and are outside the scope of this document.
This document applies to MBT in all development lifecycle models.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
the requirements of this document. For dated references, only the edition cited applies. The latest edition of
the referenced documents (including any amendments) applies for undated references.
ISO/IEC/IEEE 29119-2, Software and systems engineering — Software testing — Part 2: Test processes
ISO/IEC/IEEE 29119-3, Software and systems engineering — Software testing — Part 3: Test documentation
ISO/IEC/IEEE 29119-4, Software and systems engineering — Software testing — Part 4: Test techniques
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO, IEC and IEEE maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
— IEEE Standards Dictionary Online: available at https:// ieeexplore .ieee .org/ xpls/ dictionary .jsp
NOTE For additional terms and definitions in the field of systems and software engineering, see
[3]
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 https:// www .computer .org/ sevocab.

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
3.1 Defined terms
3.1.1
actual results
set of behaviours or conditions of a test item (3.1.25), or set of conditions of associated data or the test
environment (3.1.23), observed as a result of test execution (3.1.24)
EXAMPLE Outputs to screen, outputs to hardware, changes to data, reports and communication messages sent.
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.1]
3.1.2
expected results
observable predicted behaviour of the test item (3.1.25) under specified conditions based on its specification
or another source
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.4]
3.1.3
formal language-based testing
formal testing
testing (3.1.32) based on the integrated use of two or more formal languages
EXAMPLE Integrated use of a formal specification and a programming language for test case (3.1.19) generation.
3.1.4
formal MBT
MBT (3.1.10), in which the models are represented in a formal specification language (3.1.5)
3.1.5
formal specification language
precise, mathematically based language used to describe the behaviour and requirements of a system
[1]
EXAMPLE B, VDM, Z .
3.1.6
generation parameters
test selection criteria
parameters used by an MBT tool (3.1.9) to control the generation of test cases (3.1.19)
3.1.7
MBT model
test model (3.1.27) used in MBT (3.1.10)
3.1.8
MBT test environment
test environment (3.1.23) that includes MBT tools (3.1.9)
3.1.9
MBT tool
software tool used to support MBT (3.1.10) activities
EXAMPLE 1 A software tool that supports modelling can be used for MBT model creation.
EXAMPLE 2 A software tool that supports test case (3.1.19) generation from the MBT model.
3.1.10
model-based testing
MBT
model-driven testing
MDT
methodology to automatically generate and execute test cases (3.1.19) from models of expected behaviour

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
3.1.11
model element
identifiable part of a model
EXAMPLE A single state in a state diagram.
3.1.12
model fidelity
degree to which the MBT (3.1.10) model matches the precondition, the input and the expected behaviour of
the test item (3.1.25)
3.1.13
modelling language
notations and structures to describe models that have an explicit definition of the syntax
Note 1 to entry: Some modelling languages also have a definition of semantics.
3.1.14
offline MBT mode
MBT (3.1.10) approach in which test cases (3.1.19) are generated and stored in a repository or the MBT tool
(3.1.9) for execution later
3.1.15
online MBT mode
MBT (3.1.10) approach in which test cases (3.1.19) are created and immediately executed before the next test
case is generated
3.1.16
performance testing
type of testing (3.1.32) conducted to evaluate the degree to which a test item (3.1.25) accomplishes its
designated functions within given constraints of time and other resources
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.11]
3.1.17
security testing
test type (3.1.30) conducted to evaluate the degree to which a test item (3.1.25), and associated data and
information, are protected so that unauthorized persons or systems cannot use, read, or modify them, and
authorized persons or systems are not denied access to them
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.19]
3.1.18
test
activity in which a system or component is executed under specified conditions, the results are observed or
recorded, and an evaluation is made of some aspect of the system or component
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.21]
3.1.19
test case
set of preconditions, inputs and expected results (3.1.2), developed to drive the execution of a test item
(3.1.25) to meet test objectives (3.1.28)
Note 1 to entry: A test case is the lowest level of test implementation documentation (i.e. test cases are not made up of
test cases) for the test level (3.1.26) or test type (3.1.30) for which it is intended.
Note 2 to entry: Test case preconditions include the required state of the test environment (3.1.23), data (e.g. databases)
used by the test item, and the test item itself.
Note 3 to entry: Inputs are the data information and actions, where applicable, used to drive test execution (3.1.24).
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.23]

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
3.1.20
test condition
testable aspect of a component or system, such as a function, transaction, feature, quality attribute, or
structural element identified as a basis for testing (3.1.32)
Note 1 to entry: The ISO/IEC/IEEE 29119 series does not use the concept of test conditions but instead uses the concept
of a test model (3.1.27) for test design.
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.27]
3.1.21
test coverage
degree, expressed as a percentage, to which specified test coverage items (3.1.22) have been exercised by a
test case (3.1.19) or test cases
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.28]
3.1.22
test coverage item
measurable attribute of a test item (3.1.25) that is the focus of testing (3.1.32)
EXAMPLE Equivalence partitions, transitions between states, executable statements.
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.29, modified — The admitted term "coverage item" has been
removed.]
3.1.23
test environment
environment containing facilities, hardware, software, firmware, and procedures needed to conduct a test
(3.1.18)
Note 1 to entry: A test environment can contain multiple environments to accommodate specific test levels (3.1.26) or
types (e.g. a unit test environment, a performance test environment).
Note 2 to entry: A test environment can comprise several interconnected systems or virtual environments.
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.34]
3.1.24
test execution
process of running a test (3.1.18) on the test item (3.1.25), producing actual results (3.1.1)
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.38]
3.1.25
test item
test object
work product to be tested
EXAMPLE Software component, system, requirements document, design specification, user guide.
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.42]
3.1.26
test level
one of a sequence of test stages, each of which is typically associated with the achievement of particular
objectives and used to treat particular risks
EXAMPLE The following are common test levels, listed sequentially: unit/component testing (3.1.32), integration
testing, system testing, system integration testing, and acceptance testing.
Note 1 to entry: It is not always necessary for a test item (3.1.25) to be tested at all test levels, but the sequence of test
levels generally stays the same.

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
Note 2 to entry: Typical objectives can include consideration of basic functionality for unit/component testing,
interaction between integrated components for integration testing, acceptability to end users for acceptance testing
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.43]
3.1.27
test model
representation of the test item (3.1.25), which allows the testing (3.1.32) to be focused on particular
characteristics or qualities
EXAMPLE Requirements statements, equivalence partitions, state transition diagram, use case description,
decision table, input syntax, source code, control flow graph, parameters and values, classification tree, natural
language.
Note 1 to entry: The test model and the required test coverage (3.1.21) are used to identify test coverage items (3.1.22).
Note 2 to entry: A separate test model can be required for each type of required test coverage included in the test
completion criteria.
Note 3 to entry: A test model can include one or more test conditions (3.1.20).
Note 4 to entry: Test models are commonly used to support test design (e.g. they are used to support test design in
ISO/IEC/IEEE 29119-4, and they are used in model-based testing (3.1.10). Other types of models exist to support other
aspects of testing, such as test environment (3.1.23) models, test maturity models and test architecture models.
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.46]
3.1.28
test objective
reason for performing testing (3.1.32)
EXAMPLE Checking for correct implementation, identification of defects, measuring quality.
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.49]
3.1.29
test oracle
source of information for determining whether a test (3.1.18) has passed or failed
Note 1 to entry: The test oracle is often a specification used to generate expected results (3.1.2) for individual test cases
(3.1.19), but other sources may be used, such as comparing actual results (3.1.1) with those of another similar program
or system or asking a human expert.
[SOURCE: ISO/IEC/IEEE 29119-1:2022, 3.115]
3.1.30
test type
testing (3.1.32) that is focused on specific quality characteristics
EXAMPLE Security testing (3.1.17), functional testing, usability testing, and performance testing (3.1.16).
Note 1 to entry: A test type can be performed at a single test level (3.1.26) or across several test levels (e.g., performance
testing performed at unit and system test levels).
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.60]
3.1.31
testware
artefacts produced during the test (3.1.18) process required to plan, design, and execute tests
Note 1 to entry: Testware can include such things as documentation, scripts, inputs, expected results (3.1.2), files,
databases, environment, and any additional software or utilities used in the course of testing (3.1.32).
[SOURCE: ISO/IEC/IEEE 29119-1:2022, 3.132]

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
3.1.32
testing
set of activities conducted to facilitate the discovery and/or evaluation of properties of one or more test
items (3.1.25)
Note 1 to entry: Testing activities include planning, preparation, execution, reporting, and management activities
insofar as they are directed towards testing.
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.61]
3.1.33
traceability information
records of the relationship between products of the development and test (3.1.18) process
Note 1 to entry: Products of the development and test process include requirements, quality attributes, MBT models
(3.1.7) and test cases (3.1.19).
3.2 Abbreviated terms
BNF Backus-Naur form
BPMN Business Process Model and Notation
CI Continuous Integration
CT Continuous Test
ESS Employee Self-Service Users
FPGA Field Programmable Gate Array
GUI Graphical User Interface
HRM Human Resource Management
MBT Model-Based Testing
MCDC Modified Condition Decision Coverage
MDT Model-Driven Testing
OSLC Open Service for Lifecycle Collaboration
TMS Test Management System
UML Unified Modelling Language
Z Z formal specification notation
4 Conformance
4.1 Intended usage
The requirements in this document are contained in Clause 6, Clause 7 and Clause 8.
This document provides requirements and recommendations for MBT. It is recognized that particular
projects or organizations may not need to use all the activities or tasks described in this document.
Therefore, implementation of this document typically involves selecting a set of activities suitable for the
organization or project.
© ISO/IEC 2026, © IEEE 2026 – All rights reserved
There are two ways that an organization or tool vendor can claim to conform to this document – full
conformance or tailored conformance.
The organization or tool vendor shall assert whether it claims full or tailored conformance to this document.
4.2 Full conformance
Full conformance is achieved by providing evidence that all of the requirements of the activities defined in
this document have been satisfied.
4.3 Tailored conformance
When this document is used to establish MBT practices that do not qualify for full conformance, the subset
of requirements defined in Clauses 7 and 8 for which conformance is claimed should be recorded. Tailored
conformance is achieved by demonstrating that the recorded subset of requirements has been satisfied.
Where tailoring occurs, the justification shall be provided, either directly or by reference, whenever a
requirement defined in Clauses 7 or 8 is not followed.
5 Introduction to MBT
5.1 MBT concepts
MBT uses models to systematically and automatically generate test cases. The model is amenable to at least
partial automatic processing to generate testware (especially test cases). With systematic and automatic
test case generation, MBT can achieve improved test coverage and reduce the effort and duration of
software testing. In addition to the process extensions, several factors related to the deployment of MBT are
considered. Refer to Annex A for examples of MBT deployment with automated test execution. The factors
include MBT tool selection, abstraction level definition, traceability requirement, model fidelity and MBT
style guide. Refer to Annex B for detailed explanations of the factors.
There are various approaches to using a model to support testing. These approaches can generate test inputs
(partial), test oracles (partial), or generate complete test cases. This document focuses on the approach of
generating complete test cases. Annex D provides two examples of application of MBT.
MBT generates and executes test cases automatically. The implementation of the generation algorithm
is tool-dependent and out of the scope of this document. The requirement or capability of the generation
algorithm is common. Annex C lists and explains examples of test case generation requirements.
Models can be developed for a complete software system or a part of it. Models are defined with formal or
semi-formal languages to represent different aspects of a test item. Generally, the more formal the notation
used to construct a model, the more precise testware can be generated. Refer to Annex E for a description of
applying MBT using formal specification languages to build models (practice known as formal MBT) in the
context of formal language-based testing.
It is optimal if the testers create an MBT model independently. By independently developing an MBT model,
missing information or defects in the development model are less likely to be duplicated in the test artefacts.
[9] [8]
When development models are used as the basis for MBT , it is typically to save time and money while
accepting the associated risks. The possible roles and responsibilities are explained in Annex F.
An MBT model describes aspects of behaviour. Behaviours modelled include desired functionality and
desired quality attributes, such as reliability.
Example notations used for behavioural descriptions in MBT include:
— Unified Modelling Language (UML) sequence diagram;
— UML state diagram;
— Business Process Model and Notation (BPMN) diagram.

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
MBT models are usually developed using graphical, tabular, and/or textual information to support test
automation. Since MBT models are abstractions, to be executed, they are transformed into another
[5]
representation, such as test procedures, scripts, or keyword-based test cases . An MBT tool transforms
abstract models into detailed test cases or procedures. Once placed in the proper tool environment, the test
case generated from the model can support automated test execution.
5.2 MBT modes in test case generation and execution
MBT has two basic modes that integrate with automated test execution: online MBT mode and offline MBT
mode.
Figure 1 shows the MBT activities in online MBT mode.
Figure 1 — MBT activities in online MBT mode
In online MBT mode, an MBT tool can connect directly to the test item and test it dynamically. The
generation algorithm in the test case generation activity can generate one single test case or test step at a
time based on the MBT model and the required test coverage in the MBT strategy. The test case can then be
automatically executed in a dynamic test execution environment. The test result is then fed back into the
generation algorithm. The generation algorithm can use the test result of the former test cases to optimise
the subsequent test case generation.
There can be four types of feedback in online MBT:
— feedback on required test coverage;
— feedback on test coverage item;
— feedback on the test case;
— feedback on the test procedure.
EXAMPLE 1 When an executed test case generates a failure result, the test case generation algorithm can stop
generating further test cases associated with that test case or failure. It then can potentially generate different test
cases which do not fail. A test item can crash during testing after a sequence of test steps, and then when the test item
exercises other test cases with a similar sequence, a crash can happen again. Thus, this can cause inefficiencies or
harm the hardware if a system crash occurs frequently. In some embedded systems, the CPU software controls the
download of files to the FPGA (Field Programmable Gate Array), and if the control logic is wrong, then an incorrect file
written to the FPGA can reduce the lifetime of the FPGA. So, if the failure happens again and again, then the FPGA can
possibly be damaged.
© ISO/IEC 2026, © IEEE 2026 – All rights reserved
When the required level of test coverage is achieved, the algorithm in the test case generation step chooses
to stop generating other test cases.
Figure 2 shows the MBT activities in offline MBT mode.
Figure 2 — MBT tasks in offline MBT mode
In offline MBT mode, the generation algorithm can generate a set of test cases in the test case generation
activity. These test cases can be optionally reviewed, typically determining if the test cases provide the
required coverage of the MBT model. When this is not achieved (and it appears possible to improve MBT
model coverage), the generation parameters can be modified, and a new set of tests can be generated. In
some situations, the generated tests can also be approved at this stage. Test cases generated in offline
MBT mode can be executed automatically by a test automation system when the test cases are machine-
executable. The manual execution of a generated test case in offline MBT mode can also be possible when
the test cases are human-readable.
The MBT mode can be chosen based on the following:
— MBT tool and test execution tool capability;
— the maturity of the test item;
— test objectives.
NOTE 1 The online MBT mode can be preferred when the maturity of the test item is low and supported by the tool.
Also, when the maturity of the test item is low, the test cases can fail frequently. In online MBT mode, the tool can skip
testing a failed function and generate test cases for other functions. This action is done so that test execution time is
not wasted by continually running a low-maturity function. Both online and offline MBT modes can be applied when
the system's maturity is high.
NOTE 2 When regression testing is planned, the offline MBT mode is likely to be preferred.
6 Implementing ISO/IEC/IEEE 29119-2 for MBT
MBT shall be performed in accordance with the processes defined in ISO/IEC/IEEE 29119-2 and described in
Annex G. The two processes, the test strategy and planning process and the test design and implementation
process, are modified for application in MBT, as highlighted in Figure 3.

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
Figure 3 — MBT modifications in the ISO/IEC/IEEE 29119 processes model
For detailed modifications of the test strategy and planning process, refer to 7.3. ISO/IEC/IEEE 29119-2,
ISO/IEC/IEEE 29119-3 and ISO/IEC/IEEE 29119-4 explicitly describe the use of test models. Refer to
Annex G for a mapping of MBT models to ISO/IEC/IEEE 29119-4. By using these test models, a test case can
be derived. In MBT, the test case can be derived automatically using test case generation algorithms, which
follow the steps of ISO/IEC/IEEE 29119-2. These generation algorithms can create test cases more efficiently
and effectively than manual effort. For detailed modifications of ‘test design and implementation process’,
refer to 8.2.
Information can be automatically extracted from the MBT model for inclusion in test documentation,
facilitating full or partial conformance with ISO/IEC/IEEE 29119-3 requirements.
7 MBT modifications of the ‘test strategy and planning’ process
7.1 Overview
The test strategy and planning process defined in ISO/IEC/IEEE 29119-2 shall be applied with the ‘design
test strategy’ (TP5) activity adjusted as described in 7.3. In TP5, MBT focuses on the design of an MBT
strategy. The MBT strategy defines the MBT scope, the required test coverage, the MBT modelling language,
model abstraction levels, the MBT style guide, the MBT environment, and MBT metrics.
The overview and purpose of the test strategy and planning process remain unchanged.
The remaining activities, ‘understand context’ (TP1), ‘organize test plan development’ (TP2), ‘identify and
analyse risks’(TP3), ‘identify risk treatment approaches’(TP4), ‘determine staffing and scheduling’(TP6),
‘record test plan’(TP7),’ gain consensus on test plan’(TP8) and ‘communicate test plan and make available’
(TP9) shall be applied in accordance with ISO/IEC/IEEE 29119-2.

© ISO/IEC 2026, © IEEE 2026 – All rights reserved
The test plan documentation defined in ISO/IEC/IEEE 29119-3 applies to MBT. This clause described the
extensions to the documentation by MBT in detail.
7.2 Additional outcomes
In addition to the outcomes defined in ISO/IEC/IEEE 29119-2 7.2.3, the MBT strategy shall be identified by
extended TP5 activity.
7.3 Implementation of the design test strategy activity (TP5) for the MBT strategy
This activity consists of the following tasks:
a) A test strategy shall be designed that considers the test basis, risks, organizational, project, and product
constraints.
NOTE 1 This takes into consideration the results of the risk assessment to prioritise the test activities and
determine the resources needed to perform actions (e.g. time, costs, skills, tool support and environment needs)
while meeting organizational, project and product constraints, such as:
— regulatory standards;
— the requirements of the organizational test policy and organizational test practices;
— higher-level test plans and strategies for the project;
— contractual requirements;
— availability of appropriately skilled testers;
— availability of tools and environments.
Where it is not possible to design a test strategy that implements all the requirements of the organizational test
practices and the recommendations for treating all identified risks while still meeting the project and product
constraints, then a judgement is made to arrive at a test strategy that best meets these conflicting requirements.
How this compromise is achieved varies depending on the project and organization. It can require the constraints
to be relaxed and the identification of risk treatment approaches activity (TP4). This task shall be repeated until
an acceptable test strategy is achieved. Where it is decided to deviate from the organizational test practices, this
should be recorded in the test strategy.
NOTE 2 The format of a test strategy is defined in ISO/IEC/IEEE 29119-3. It includes decisions on test levels,
test types, aspects to be tested, test design techniques, test completion criteria, and suspension and resumption
criteria.
NOTE 3 A test strategy typically addresses static testing (e.g. reviews, inspections, static analysis) and
dynamic testing.
b) An MBT strategy shall be designed when MBT is planned and applicable that considers the MBT scope,
test completion criteria, modelling language, abstraction level and the MBT style guide
NOTE 4 This new task has been added to the original activity defined in ISO/IEC/IEEE 29119-2 to guide MBT
activities in dynamic test processes.
c) Activities required to implement the test strategy shall be identified.
d) Metrics for Test Monitoring and Control (see activities TMC1 to TMC4) shall be identified.
NOTE 5 MBT metrics are identified in task d) also. Refer to Annex B for an example of MBT metrics.
e) Test data requirements shall be identified.
EXAMPLE Factors to consider when identifying test data requirements include regulations on data
confidentiality (it can require data masking or encryption), volume of data required and data clean-up upon
completion.
© ISO/IEC 2026, © IEEE 2026 – All rights reserved
f) Test environment requirements and test tool requirements shall be identified. The MBT online or offline
mode for test case generation and execution shall be chosen. (refer to Clause A.3 for an example of MBT
mode)
NOTE 6 This modified task has been added to the original activity defined in ISO/IEC/IEEE 29119-2 to define
the MBT test case generation and execution mode.
g) Test deliverables shall be identified, and their degree of formality and frequency of communication
should be recorded.
h) An initial estimate of the required resources to perform the complete set of activities required to
implement the test strategy shall be produced.
NOTE 7 The initial test estimate produced in this step is finalised in the record test plan activity (TP7).
i) The test strategy shall be recorded.
NOTE 8 The test strategy is typically a section of the test plan, but in some cases, it can be recorded as a
separate document.
j) The stakeholders shall obtain approval for the test strategy.
NOTE 9 This can require repeating earlier tasks in this activity.
7.4 MBT strategy documentation
7.4.1 Overview
MBT shall be documented in accordance with the requirements defined in ISO/IEC/IEEE 29119-3 and
described in Annex G. In addition to extending ISO/IEC/IEEE 29119-2 test processes, the test strategy
documentation defined in ISO/IEC/IEEE 29119-3:2021, 7.2.7 is extended to support MBT.
7.4.2 MBT strategy
7.4.2.1 MBT scope
For a project test plan or a test plan for a
...

Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
ISO/IEC JTC 1/SC 7/WG 26
Style Definition
...
Style Definition
...
Date: 2026-03-09
Style Definition
...
Secretariat: BIS
Style Definition
...
Style Definition
Date: 2026-04-22 .
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Software and systems engineering — Software testing — —
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Part 8:
Style Definition
...
Model-based testing
Style Definition
...
Ingénierie du logiciel et des systèmes — Essais du logiciel — Partie 8: Model-based testing
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, French (France)
Formatted: HeaderCentered
© ISO/IEC 2026
Formatted: Default Paragraph Font
© /IEEE 2026
Formatted: Adjust space between Latin and Asian text,
Adjust space between Asian text and numbers
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication
may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying,
Formatted: Default Paragraph Font
or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO
Formatted: Default Paragraph Font
at the address below or ISO'sISO’s member body in the country of the requester.
Formatted: Right: 1.5 cm, Bottom: 1 cm, Gutter: 0 cm,
ISO Copyright Officecopyright office Header distance from edge: 1.27 cm, Footer distance
CP 401 • Ch. de Blandonnet 8 from edge: 0.5 cm
CH-1214 Vernier, Geneva
Formatted: zzCopyright address, Adjust space between
Phone: + 41 22 749 01 11
Latin and Asian text, Adjust space between Asian text
and numbers
Email: [e-mail]
Formatted: French (Switzerland)
E-mail: [e-mail]
Website: www.iso.orgwww.iso.org
Formatted: zzCopyright address, Adjust space between
Latin and Asian text, Adjust space between Asian text
Published in Switzerland.
and numbers
Formatted: Font: 10 pt
Formatted: Font: 10 pt
Formatted: Font: 10 pt
Formatted: Font: 11 pt
Formatted: FooterPageRomanNumber, Space After: 0
pt, Line spacing: single
ii © ISO/IEC 2025, © /IEEE 2025 2026 – All rights reserved
ii
Formatted: Font: 11 pt, Bold, French (France)
Formatted: Font: Bold, French (France)
Formatted: HeaderCentered, Left
Contents
Formatted: Adjust space between Latin and Asian text,
Adjust space between Asian text and numbers, Tab
Foreword . vii
stops: Not at 8.6 cm
Introduction . viii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
3.1 Defined terms . 2
3.2 Abbreviated terms . 7
4 Conformance . 8
4.1 Intended usage . 8
4.2 Full conformance . 8
4.3 Tailored conformance . 8
5 Introduction to MBT . 8
5.1 MBT concepts . 8
5.2 MBT modes in test case generation and execution . 9
6 Implementing ISO/IEC/IEEE 29119-2 for MBT . 13
7 MBT modifications of the ‘test strategy and planning’ process . 15
7.1 Overview . 15
7.2 Additional outcomes . 15
7.3 Implementation of the design test strategy activity (TP5) for the MBT strategy . 15
7.4 MBT strategy documentation . 17
8 MBT modifications of the ‘test design and implementation’ process . 17
8.1 Overview . 17
8.2 Implementation of the create test model (TD1) activity for MBT model creation . 18
Annex A (informative) MBT deployment with automated test execution . 20
Annex B (informative) Additional considerations for MBT . 30
Annex C (informative) Automated test case generation in MBT . 44
Annex D (informative) Examples of MBT . 49
Annex E (informative) Formal MBT . 69
Annex F (informative) Roles and responsibilities for the MBT tasks . 74
Annex G (Normative) Mapping of MBT activities to ISO/IEC/IEEE 29119-2, ISO/IEC/IEEE 29119-
3 and ISO/IEC/IEEE 29119-4 . 75
Bibliography . 79

Foreword . vii
Formatted: Font: 10 pt
Introduction . viii
Formatted: Font: 10 pt
1 Scope . 1
Formatted: Font: 10 pt
2 Normative references . 1
Formatted: FooterCentered, Left, Space Before: 0 pt,
3 Terms and definitions . 1
Tab stops: Not at 17.2 cm
Formatted: Font: 11 pt
4 Conformance . 6
4.1 Intended usage . 6
Formatted: FooterPageRomanNumber, Left, Space
4.2 Full conformance . 6
After: 0 pt, Tab stops: Not at 17.2 cm
© ISO /IEC/IEEE 2026 – All rights reserved
iii
Formatted: Font: Bold, French (France)
Formatted: HeaderCentered
4.3 Tailored conformance . 6
5 Introduction to MBT . 7
5.1 MBT concepts . 7
5.2 MBT modes in test case generation and execution . 7
6 Implementing ISO/IEC/IEEE 29119-2 for MBT . 9
7 MBT modifications of the ‘test strategy and planning’ process . 10
7.1 Overview . 10
7.2 Additional outcomes . 10
7.3 Implementation of the design test strategy activity (TP5) for the MBT strategy . 11
7.4 MBT strategy documentation . 12
7.4.1 Overview . 12
7.4.2 MBT strategy . 12
8 MBT modifications of the ‘test design and implementation’ process . 13
8.1 Overview . 13
8.2 Implementation of the create test model (TD1) activity for MBT model creation . 13
Annex A (Informative) MBT deployment with automated test execution. 15
A.1 Scope . 15
A.2 MBT test environment overview . 15
A.3 Example of an MBT test environment . 15
A.3.1 Overview . 15
A.3.2 External interfaces . 17
A.3.2.1 Introduction . 17
A.3.2.2 Requirements management interface . 17
A.3.2.3 Test management and reporting interface . 17
A.3.2.4 Continuous integration interface . 17
A.3.2.5 Automation execution interface . 17
A.3.3 Internal data representation . 18
A.3.3.1 Introduction . 18
A.3.3.2 Model internal representation. 18
A.3.3.3 Testware internal representation . 19
A.3.4 MBT test environment variant . 19
A.4 MBT adaptation module design . 20
Annex B (Informative) Additional considerations for MBT . 22
B.1 Overview . 22
B.2 MBT tool selection . 22
B.3 Abstraction level . 23
Formatted: Font: 10 pt
B.4 Traceability . 26
Formatted: Font: 10 pt
B.5 Model fidelity . 27
Formatted: Font: 10 pt
B.6 Style guide . 27
Formatted: Font: 11 pt
B.6.1 Example MBT style guide . 27
Formatted: FooterPageRomanNumber, Space After: 0
pt, Line spacing: single
iv © ISO/IEC 2025, © /IEEE 2025 2026 – All rights reserved
iv
Formatted: Font: 11 pt, Bold, French (France)
Formatted: Font: Bold, French (France)
Formatted: HeaderCentered, Left
B.6.2 Example MBT style guide template . 29
B.6.3 Contents of MBT style guide . 29
B.6.3.1 Domain structures . 29
B.6.3.2 Convention for different modelling languages. 29
B.6.3.3 Naming rules . 30
B.6.3.4 Information cascade rules . 30
B.6.3.5 Abstraction rules . 30
B.6.3.6 Comment rules . 30
B.6.3.7 Automation execution commands . 30
B.6.3.8 Traceability rules . 30
B.6.3.9 Default semantics of the model element . 30
B.6.3.10 Model appearance rules . 30
B.7 MBT metrics . 31
B.7.1 Overview . 31
B.7.2 MBT-specific metrics . 31
Annex C (Informative) Automated test case generation in MBT . 33
C.1 Overview . 33
C.2 Example of test case generation used in MBT . 33
C.3 Common algorithms for test case generation . 34
C.4 Minimal capability of an MBT generator . 35
C.5 The optional capability of an MBT generator . 35
C.6 Advanced capability of an MBT generator . 35
C.7 Post-process capability of an MBT generator . 36
Annex D (Informative) Examples of MBT . 37
D.1 Examples overview . 37
D.2 MBT in an interactive system . 37
D.2.1 Test item and test objectives . 37
D.2.2 MBT scope . 38
D.2.3 Modelling and case generation for functional testing . 38
D.2.4 Discussion and conclusion for camera preview example . 41
D.3 MBT in business process system . 41
Formatted: Font: 10 pt
D.3.1 Introduction . 41
Formatted: Font: 10 pt
D.3.2 Test item and test objectives . 41
Formatted: Font: 10 pt
D.3.3 MBT scope . 41
Formatted: FooterCentered, Left, Space Before: 0 pt,
D.3.4 General test objectives . 42
Tab stops: Not at 17.2 cm
D.3.5 Characteristics of the MBT approach . 42
Formatted: Font: 11 pt
D.3.6 Modelling for end-to-end testing . 43
Formatted: FooterPageRomanNumber, Left, Space
After: 0 pt, Tab stops: Not at 17.2 cm
© ISO /IEC/IEEE 2026 – All rights reserved
v
Formatted: Font: Bold, French (France)
Formatted: HeaderCentered
D.3.6.1 Requirements and business process . 43
D.3.6.2 Test data . 45
D.3.6.3 Decision tables for business rules . 45
D.3.6.4 Test steps . 47
D.3.7 Test case generation . 47
D.3.8 Test execution . 49
D.3.9 Discussion and conclusion for OrangeHRM example . 49
Annex E (Informative) Formal MBT . 50
E.1 Introduction . 50
E.2 Formal MBT in formal language-based testing . 50
E.3 Application example . 51
E.3.1 The test item . 51
E.3.2 The specification language . 51
E.3.3 The formal model . 52
E.4 Closure . 53
Annex F (Informative) Roles and responsibilities for the MBT tasks . 54
F.1 Roles and responsibilities . 54
Annex G (Informative) Mapping of MBT activities to ISO/IEC/IEEE 29119 standards . 55
G.1 General . 55
Bibliography . 58
Formatted: Font: 10 pt
Formatted: Font: 10 pt
Formatted: Font: 10 pt
Formatted: Font: 11 pt
Formatted: FooterPageRomanNumber, Space After: 0
pt, Line spacing: single
vi © ISO/IEC 2025, © /IEEE 2025 2026 – All rights reserved
vi
Formatted: Font: 11 pt, Bold, French (France)
Formatted: Font: Bold, French (France)
Formatted: HeaderCentered, Left
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
ISO/IEC documents should be noted. This document was drafted in accordance with the rules given in the
ISO/IEC Directives, Part 2 (see www.iso.org/directives or
www.iec.ch/members_experts/refdocswww.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 involved in technical
working groups 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.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: Foreword Text, Adjust space between Latin
and Asian text, Adjust space between Asian text and
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions numbers, Tab stops: Not at 0.7 cm + 1.4 cm + 2.1 cm
related to conformity assessment, as well as information about ISO's adherence to the World Trade + 2.8 cm + 3.5 cm + 4.2 cm + 4.9 cm + 5.6 cm + 6.3
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see cm + 7 cm
www.iso.org/iso/foreword.htmlwww.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-
Formatted: Default Paragraph Font
standardswww.iec.ch/understanding-standards.
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
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
Formatted: Adjust space between Latin and Asian text,
Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards Development
Adjust space between Asian text and numbers
Organization cooperation agreement between ISO and IEEE.
Formatted: Font: 10 pt
Formatted: Font: 10 pt
A list of all parts in the ISO/IEC/IEEE 29119 series can be found on the ISO and IEC websites.
Formatted: Font: 10 pt
Any feedback or questions on this document should be directed to the user’s national standards body. A
Formatted: FooterCentered, Left, Space Before: 0 pt,
complete listing of these bodies can be found at www.iso.org/members.htmlwww.iso.org/members.html and
Tab stops: Not at 17.2 cm
www.iec.ch/national-committeeswww.iec.ch/national-committees.
Formatted: Font: 11 pt
Formatted: FooterPageRomanNumber, Left, Space
After: 0 pt, Tab stops: Not at 17.2 cm
© ISO /IEC/IEEE 2026 – All rights reserved
vii
Formatted
...
Formatted
...
Formatted
...
Introduction
Formatted
...
The purpose of the ISO/IEC/IEEE 29119 series is to define an internationally agreed set of standards for
Formatted
...
software testing that can be used by any organization when performing any form of software testing and using
Formatted
...
any life cycle. This document explains how the ISO/IEC/IEEE 29119 series can be adopted to support model-
Formatted
based testing (MBT). .
Formatted
...
Models can form an abstract or a complete description of a system from a particular perspective, for example,
Formatted
...
software behaviour and design. Software testers can use this document to understand how models of expected
Formatted
behaviour can be used in test design and implementation to derive test cases, including test inputs and .
expected results.
Formatted
...
Formatted
...
The concepts relating to software testing defined in ISO/IEC/IEEE 29119-1 are also applicable to this
document. Formatted
...
Formatted
...
The test process model on which MBT is based is defined in ISO/IEC/IEEE 29119-2. It comprises test process
Formatted
descriptions that define the software testing processes at the organizational level, test management level and .
dynamic test level. Supporting diagrams describing the processes are also provided in ISO/IEC/IEEE 29119-
Formatted
...
2. The processes defined in ISO/IEC/IEEE 29119-2 are extended to support MBT.
Formatted
...
Formatted
The templates and examples of test documentation defined in ISO/IEC/IEEE 29119-3 also apply to this
...
document.
Formatted
...
Formatted
...
Software test design techniques that can be used during test design are defined in ISO/IEC/IEEE 29119-4.
Each test design technique defines a test model with syntax, semantics of the model and the way to derive the Formatted
...
test case from the test model in ISO/IEC/IEEE 29119-4. MBT models and the associated MBT tools can be used
Formatted
...
to produce a test case that, in part or as a whole, satisfies the test techniques of ISO/IEC/IEEE 29119-4.
Formatted
...
ISO/IEC/IEEE 29119-5 addresses using keywords to support testing. A MBT approach can generate keyword
Formatted
...
test cases as defined in ISO/IEC/IEEE 29119-5.
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
Formatted
...
viii © ISO/IEC 2025, © /IEEE 2025 2026 – All rights reserved
viii
FINAL DRAFT International Standard ISO/IEC/IEEE FDIS 29119-8:2025(en)

Formatted: English (United Kingdom)
Software and systems engineering — Software testing — Part 8:
Formatted: Right: 1.5 cm, Bottom: 1 cm, Gutter: 0 cm,
Header distance from edge: 1.27 cm, Footer distance
Model-based testing —
from edge: 0.5 cm
Formatted: Adjust space between Latin and Asian text,
Part 8:
Adjust space between Asian text and numbers
Model-based testing
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
1 Scope
Formatted: Default Paragraph Font
This document provides requirements and guidelines on applying model-based testing (MBT) following the
Formatted
...
test processes defined in ISO/IEC/IEEE 29119-2. This document covers the following areas:
Formatted: Default Paragraph Font
a) a) definitions for MBT;
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
b) b) implementing ISO/IEC/IEEE 29119-2 for MBT;
Formatted: Default Paragraph Font
c) c) implementing ISO/IEC/IEEE 29119-3 for MBT.
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
Using MBT, the generation of a test case is systemized and automated. This document assumes that test
execution is also automated. The implementation of the generation algorithm is tool-dependent and, therefore,
Formatted
...
is outside the scope of this document. MBT tool selection is also outside the scope of this document.
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
The test models and the information generated by the supporting MBT tools can be used, in part or whole, to
satisfy the documentation requirements of ISO/IEC/IEEE 29119-3. Many MBT tools implement one or more
Formatted: Default Paragraph Font
test techniques and associated measures defined in ISO/IEC/IEEE 29119-4. These techniques are associated
Formatted: Default Paragraph Font
with individual tool implementation and are outside the scope of this document.
Formatted: Default Paragraph Font
This document applies to MBT in all development lifecycle models.
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
2 Normative references
Formatted: Default Paragraph Font
The following documents are referred to in the text in such a way that some or all of their content constitutes
Formatted: Default Paragraph Font
the requirements of this document. For dated references, only the edition cited applies. The latest edition of
Formatted: Default Paragraph Font
the referenced documents (including any amendments) applies for undated references.
Formatted
...
ISO/IEC/IEEE 29119--2, Software and systems engineering — Software testing — Part 2: Test processes
Formatted: Default Paragraph Font
ISO/IEC/IEEE 29119--3, Software and systems engineering — Software testing — Part 3: Test documentation Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
ISO/IEC/IEEE 29119--4, Software and systems engineering — Software testing — Part 4: Test techniques
Formatted: Default Paragraph Font
3 Terms and definitions Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
For the purposes of this document, the following terms and definitions apply.
Formatted: Default Paragraph Font
ISO, IEC and IEEE maintain terminological databases for use in standardization at the following addresses:
Formatted: Default Paragraph Font
Formatted
...
— — ISO Online browsing platform: available at https://www.iso.org/obphttps://www.iso.org/obp
Formatted
...
— — IEC Electropedia: available at https://www.electropedia.org/https://www.electropedia.org/
Formatted
...
Formatted: Font: Bold, French (France)
Formatted: HeaderCentered
— — IEEE Standards Dictionary Online: available at
https://ieeexplore.ieee.org/xpls/dictionary.jsphttps://ieeexplore.ieee.org/xpls/dictionary.jsp
NOTE For additional terms and definitions in the field of systems and software engineering, see
[3][3]
ISO/IEC/IEEE 24765, , which is published periodically as a snapshot of the SEVOCAB (Systems and software
Formatted: Default Paragraph Font
engineering vocabulary) database and is publicly accessible at
Formatted: Default Paragraph Font
https://www.computer.org/sevocabhttps://www.computer.org/sevocab.
Formatted: TermNum3, Adjust space between Latin
3.1 Defined terms
and Asian text, Adjust space between Asian text and
numbers
3.1.1 3.1.1
actual results Formatted: Adjust space between Latin and Asian text,
set of behaviours or conditions of a test item (3.1.25),(3.1.25), or set of conditions of associated data or the test Adjust space between Asian text and numbers, Tab
stops: Not at 0.7 cm + 1.4 cm + 2.1 cm + 2.8 cm +
environment (3.1.23),(3.1.23), observed as a result of test execution (3.1.24)(3.1.24)
3.5 cm + 4.2 cm + 4.9 cm + 5.6 cm + 6.3 cm + 7 cm
EXAMPLE: Outputs to screen, outputs to hardware, changes to data, reports and communication messages sent.
Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.1]
Formatted: Default Paragraph Font
3.1.2 3.1.2
Formatted: Default Paragraph Font
expected results
Formatted: Default Paragraph Font
observable predicted behaviour of the test item (3.1.25)(3.1.25) under specified conditions based on its
specification or another source
Formatted: Adjust space between Latin and Asian text,
Adjust space between Asian text and numbers
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.4]
Formatted: Default Paragraph Font
3.1.3 3.1.3
Formatted: Default Paragraph Font
formal language-based testing
Formatted: Default Paragraph Font
formal testing
Formatted: Default Paragraph Font
testing (3.1.32)(3.1.32) based on the integrated use of two or more formal languages
Formatted: Default Paragraph Font
EXAMPLE: Integrated use of a formal specification and a programming language for test case (3.1.19)(3.1.19)
Formatted: Regular, Font: Bold
generation.
Formatted: Adjust space between Latin and Asian text,
3.1.4 3.1.4
Adjust space between Asian text and numbers, Tab
formal MBT
stops: Not at 0.7 cm + 1.4 cm + 2.1 cm + 2.8 cm +
MBT (3.1.10),(3.1.10), in which the models are represented in a formal specification language (3.1.5)(3.1.5)
3.5 cm + 4.2 cm + 4.9 cm + 5.6 cm + 6.3 cm + 7 cm
Formatted: TermNum3, Adjust space between Latin
3.1.5 3.1.5
and Asian text, Adjust space between Asian text and
formal specification language
numbers
precise, mathematically based language used to describe the behaviour and requirements of a system
Formatted: Adjust space between Latin and Asian text,
[1] [1]
Adjust space between Asian text and numbers, Tab
EXAMPLE: B, VDM, Z . .
stops: Not at 0.7 cm + 1.4 cm + 2.1 cm + 2.8 cm +
3.1.6 3.1.6 3.5 cm + 4.2 cm + 4.9 cm + 5.6 cm + 6.3 cm + 7 cm
generation parameters
Formatted: TermNum3, Adjust space between Latin
test selection criteria
and Asian text, Adjust space between Asian text and
parameters used by an MBT tool (3.1.9)(3.1.9) to control the generation of test cases (3.1.19)(3.1.19)
numbers
Formatted: Regular, Font: Bold
3.1.7 3.1.7
MBT model Formatted: Font: 10 pt
test model (3.1.27)(3.1.27) used in MBT (3.1.10)(3.1.10)
Formatted: Font: 10 pt
Formatted: Font: 10 pt
3.1.8 3.1.8
MBT test environment
Formatted: Font: 11 pt
test environment (3.1.23)(3.1.23) that includes MBT tools (3.1.9)(3.1.9)
Formatted: FooterPageNumber, Space After: 0 pt, Line
spacing: single
2 © ISO/IEC 2025, © /IEEE 2025 2026 – All rights reserved
Formatted: Font: 11 pt, Bold, French (France)
Formatted: Font: Bold, French (France)
Formatted: HeaderCentered, Left
3.1.9 3.1.9
MBT tool
software tool used to support MBT (3.1.10)(3.1.10) activities
EXAMPLE 1 A software tool that supports modelling can be used for MBT model creation.
Formatted: Adjust space between Latin and Asian text,
Adjust space between Asian text and numbers, Tab
EXAMPLE 2 A software tool that supports test case (3.1.19)(3.1.19) generation from the MBT model.
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
3.1.10 3.1.10
Formatted: TermNum3, Adjust space between Latin
model-based testing
and Asian text, Adjust space between Asian text and
MBT
numbers
model-driven testing
Formatted: Regular, Font: Bold
MDT
methodology to automatically generate and execute test cases (3.1.19)(3.1.19) from models of expected
Formatted: Font: Bold
behaviour
Formatted: Regular, Font: Bold
3.1.11 3.1.11
model element
Formatted: Adjust space between Latin and Asian text,
identifiable part of a model
Adjust space between Asian text and numbers, Tab
EXAMPLE: A single state in a state diagram. 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
3.1.12 3.1.12
Formatted: TermNum3, Adjust space between Latin
model fidelity
and Asian text, Adjust space between Asian text and
degree to which the MBT (3.1.10)(3.1.10) model matches the precondition, the input and the expected
numbers
behaviour of the test item (3.1.25)(3.1.25)
Formatted: Adjust space between Latin and Asian text,
Adjust space between Asian text and numbers, Tab
3.1.13 3.1.13
stops: Not at 0.7 cm + 1.4 cm + 2.1 cm + 2.8 cm +
modelling language
3.5 cm + 4.2 cm + 4.9 cm + 5.6 cm + 6.3 cm + 7 cm
notations and structures to describe models that have an explicit definition of the syntax
Formatted: TermNum3, Adjust space between Latin
and Asian text, Adjust space between Asian text and
Note 1 to entry: Some modelling languages also have a definition of semantics.
numbers
3.1.14 3.1.14
Formatted: Default Paragraph Font
offline MBT mode
Formatted: Default Paragraph Font
MBT (3.1.10)(3.1.10) approach in which test cases (3.1.19)(3.1.19) are generated and stored in a repository
or the MBT tool (3.1.9)(3.1.9) for execution later Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
3.1.15 3.1.15
Formatted: Default Paragraph Font
online MBT mode
MBT (3.1.10)(3.1.10) approach in which test cases (3.1.19)(3.1.19) are created and immediately executed
Formatted: Default Paragraph Font
before the next test case is generated
Formatted: Default Paragraph Font
3.1.16 3.1.16
Formatted: Default Paragraph Font
performance testing
Formatted: Default Paragraph Font
type of testing (3.1.32)(3.1.32) conducted to evaluate the degree to which a test item (3.1.25)(3.1.25)
Formatted: Default Paragraph Font
accomplishes its designated functions within given constraints of time and other resources
Formatted: Font: 10 pt
[SOURCE: ISO/IEC/IEEE 29119-2:2021, 3.11]
Formatted: Font: 10 pt
3.1
...