ISO/IEC 26559:2017

Software and systems engineering - Methods and tools for variability traceability in software and systems product line

ISO/IEC 26559:2017, within the context of the tools and methods of variability traceability for software and system product lines: - provides the terms and definitions specific to variability traceability for software and systems product lines; - defines process groups and their processes for establishing and managing variability traceability at product line lifecycle processes. Those processes are described in terms of purpose, inputs, tasks, and outcomes; - defines method capabilities to support the defined tasks of each process; - defines tool capabilities to automate/semi-automate tasks or defined method capabilities. ISO/IEC 26559:2017 does not concern processes and capabilities of tools and methods for a single system but rather deals with those for a family of products.

Ingénierie des systèmes et du logiciel — Méthodes et outils pour modéliser la traçabilité dans les gammes de produits des logiciels et systèmes

General Information

• Status: Published
• Publication Date: 09-Aug-2017
• 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 4 - Tools and environment
• Current Stage: 9093 - International Standard confirmed
• Start Date: 21-Dec-2022
• Completion Date: 30-Oct-2025

Overview

ISO/IEC 26559:2017 - "Software and systems engineering - Methods and tools for variability traceability in software and systems product line" defines a framework for establishing and managing variability traceability across a software and systems product line lifecycle. The standard provides domain-specific terms and definitions, a reference model, and structured process groups (planning, enabling, managing) described in terms of purpose, inputs, tasks and outcomes. It also specifies method capabilities and tool capabilities to support or automate variability tracing activities. ISO/IEC 26559:2017 applies to families of products (product lines), not to single-system traceability.

Key technical topics and requirements

• Reference model for variability traceability: conceptual structure to relate variability models and artefacts across domain and application engineering.
• Process groups and processes: defined processes for variability tracing management, including planning, enabling and managing activities with documented inputs, tasks and expected outcomes.
• Traceability types and trace links: establishing trace links between
  • domain variability model ↔ domain artefacts,
  • application variability model ↔ application artefacts,
  • domain ↔ application variability models,
  • artefacts within the same stage and across adjacent lifecycle stages.
• Method capabilities: functional capabilities methods must provide to perform tracing tasks (identification of relations, definition and instantiation of trace links).
• Tool capabilities: automation/semi‑automation support for tasks and method capabilities (trace creation, maintenance, conflict detection, instantiation based on binding results).
• Variability tracing support: guidance on harmonizing traceability with product line traceability, detecting conflicts, quality assurance of tracing activities and artefacts.
• Traceability algorithms and performance: identifying, evaluating and optimizing algorithms that implement variability tracing; measuring algorithm performance.
• Terminology and attributes: consistent terms, traceability dimensions, relation types and attributes (informative annexes).

Practical applications

• Selecting and evaluating tools and methods for variability modelling and traceability in product-line engineering.
• Designing a variability traceability strategy and plan as part of product line lifecycle governance.
• Implementing automated or semi-automated trace link management between variability models and engineering artefacts (requirements, designs, implementations, tests).
• Performing quality assurance of traceability (reviews, metrics, conflict resolution) to support compliance and maintenance.
• Enabling traceability-driven activities during domain engineering, application engineering and product customization.

Who should use this standard

• Product line architects, systems and software engineers managing variability
• Tool vendors and method providers implementing variability traceability capabilities
• Technical managers, configuration managers, and QA teams in organizations adopting Software and Systems Product Line (SSPL) engineering

Related standards

ISO/IEC 26550 family (covers product line processes and tools), including ISO/IEC 26551–26563 (requirements, design, realization, testing, management, variability mechanisms, product management, etc.). These related standards complement ISO/IEC 26559 by covering other lifecycle aspects of SSPL engineering.

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 26559
First edition
2017-07
Software and systems engineering —
Methods and tools for variability
traceability in software and systems
product line
Ingénierie des systèmes et du logiciel — Méthodes et outils pour
modéliser la traçabilité dans les gammes de produits des logiciels et
systèmes
Reference number
©
ISO/IEC 2017
© ISO/IEC 2017, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. [phone]
Fax [phone]
[e-mail]
www.iso.org
ii © ISO/IEC 2017 – All rights reserved

Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Reference model for variability traceability in software and systems product line .2
5.1 Overview . 2
5.2 Reference model for variability traceability in software and systems product line . 4
6 Variability tracing management . 7
6.1 General . 7
6.2 Variability tracing planning . 7
6.2.1 Purpose of variability tracing planning . 7
6.2.2 Design variability tracing strategy . 8
6.2.3 Define quality assurance measures for variability tracing . 8
6.2.4 Assign responsibility for variability tracing . 9
6.2.5 Record variability tracing plan . 9
6.3 Variability tracing enabling .10
6.3.1 Purpose of variability tracing enabling .10
6.3.2 Provide guidance for variability tracing .10
6.3.3 Mobilize roles and responsibilities for variability tracing .11
6.3.4 Enable variability tracing management .11
6.3.5 Enable variability tracing operations.11
6.3.6 Enable quality assurance measurement for variability tracing .12
6.4 Variability tracing managing .12
6.4.1 Purpose of variability tracing managing .12
6.4.2 Review the plan versus actual result of variability tracing .13
6.4.3 Control issues on domain/application variability tracing .13
6.4.4 Control issues on variability traceability management .13
6.4.5 Control issues on variability tracing support .14
6.4.6 Support corrective actions for variability tracing .14
6.4.7 Make improvement actions for variability tracing .15
7 Variability tracing .15
7.1 General .15
7.2 Traceability between domain variability model and domain artefacts .15
7.2.1 Purpose of traceability between domain variability model and
domain artefacts .15
7.2.2 Identify relations between variation point and domain artefact .16
7.2.3 Identify relations between variant and domain artefact .16
7.2.4 Define the trace links between domain variability model and domain artefacts .17
7.3 Traceability between application variability model and application artefacts .17
7.3.1 Purpose of traceability between application variability model and
application artefacts .17
7.3.2 Identify relations between variation point and application artefact .18
7.3.3 Identify relations between variant and application artefact .18
7.3.4 Define the trace links between application variability model and
application artefacts .19
7.4 Traceability between domain and application variability model .19
7.4.1 Purpose of traceability between domain and application variability model .19
7.4.2 Identify relations between domain and application variability model .20
7.4.3 Define trace links in accordance with binding results .20
7.5 Traceability among variability related artefacts within a stage .20
© ISO/IEC 2017 – All rights reserved iii

7.5.1 Purpose of traceability between variability related artefacts within a stage .20
7.5.2 Identify relations among domain artefacts within the same stage .21
7.5.3 Define trace links among domain artefacts within the same stage .21
7.5.4 Instantiate trace links in line with binding results.22
7.6 Traceability between variability related artefacts in adjacent stages .22
7.6.1 Purpose of traceability between variability related artefacts in different
adjacent stages .22
7.6.2 Identify relations between domain artefacts in adjacent stages .23
7.6.3 Define trace links between domain artefacts in adjacent stages .23
7.6.4 Instantiate trace links in line with binding results.24
8 Variability tracing support.24
8.1 General .24
8.2 Relating tracing to variability model.24
8.2.1 Purpose of relating tracing to variability model . .24
8.2.2 Identify variability tracing conflicts .25
8.2.3 Harmonize variability traceability with product line traceability .25
8.3 Quality assurance for variability tracing .26
8.3.1 Purpose of quality assurance for variability tracing .26
8.3.2 Objectively evaluate variability tracing activities .26
8.3.3 Objectively evaluate variability tracing work products .27
8.3.4 Communicate and resolve noncompliance issues.27
8.3.5 Establish records of tracing quality assurance activities .28
8.4 Variability tracing algorithm .28
8.4.1 Purpose of variability tracing algorithm .28
8.4.2 Identify algorithms for variability tracing .29
8.4.3 Evaluate defined variability tracing algorithms .29
8.4.4 Measure the performance of algorithms .30
8.4.5 Optimize traceability algorithms .30
Annex A (informative) Variability traceability dimension .31
Annex B (informative) Types of variability traceability relations .32
Annex C (informative) Variability traceability attributes.34
Bibliography .35
iv © ISO/IEC 2017 – All rights reserved

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. In the field of information technology, ISO and IEC have established a joint technical committee,
ISO/IEC JTC 1.
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).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www .iso .org/ patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on 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 the following
URL: w w w . i s o .org/ iso/ foreword .html.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 7, Software and systems engineering.
© ISO/IEC 2017 – All rights reserved v

Introduction
Software and Systems Product Line (SSPL) engineering and management creates, exploits and manages
a common platform to develop a family of products (e.g. software products, systems architectures) at
lower cost, reduced time to market and with better quality. As a result, it has gained increasing global
attention since the 1990s.
Variability, which differentiates a member product from other products within a product line, plays an
important role in SSPL; and hundreds of variabilities are introduced throughout the whole SSPL domain
engineering stages. Those variabilities are defined, refined, newly added as domain engineering stages
go forward. Variabilities thus are modelled carefully so as to manage and control them in a systematic
way. This document deals with methods and tools capability for supporting variability modelling using
consistent notations and for managing and/or utilizing variability models in domain and application
engineering lifecycle processes.
This document can be used in the following modes:
— by the users of this document: to benefit people who want to adopt SSPL for producing their products
by guiding how to model variabilities among member products;
— by a product line organization: to provide guidance in the evaluation and selection for methods and
tools for variability modelling;
— by providers of tools and methods: to provide guidance in implementing or developing methods and
tools by providing a comprehensive set of methods and tools capabilities for supporting variability
modelling.
The ISO/IEC 26550 family of standards addresses both engineering and management processes and
capabilities of methods and tools in terms of the key characteristics of product line development. This
document provides processes and capabilities of methods and tools for variability modelling in product
lines. Other ISO/IEC 26550 family of standards are as follows:
— processes and capabilities of methods and tools for domain requirements engineering and
application requirements engineering are provided in ISO/IEC 26551;
— processes and capabilities of methods and tools for domain design and application design are
provided in ISO/IEC 26552;
— processes and capabilities of methods and tools for domain realization and application realization
are provided in ISO/IEC 26553;
— processes and capabilities of methods and tools for domain testing and application testing are
provided in ISO/IEC 26554;
— processes and capabilities of methods and tools for technical management are provided in
ISO/IEC 26555;
— processes and capabilities of methods and tools for organizational management are provided in
ISO/IEC 26556;
— processes and capabilities of methods and tools for variability mechanisms are provided in
ISO/IEC 26557;
— processes and capabilities of methods and tools for variability traceability are provided in
ISO/IEC 26559;
— processes and capabilities of methods and tools for product management are provided in
ISO/IEC 26560;
— processes and capabilities of methods and tools for technical probe are provided in ISO/IEC 26561;
vi © ISO/IEC 2017 – All rights reserved

— processes and capabilities of methods and tools for transition management are provided in
ISO/IEC 26562;
— processes and capabilities of methods and tools for configuration management of asset are provided
in ISO/IEC 26563;
— others (ISO/IEC 26564 to ISO/IEC 26599): to be developed.
ISO/IEC 26550, ISO/IEC 26551 and ISO/IEC 26555 are published. ISO/IEC 26557 and ISO/IEC 26559
are to be published. ISO/IEC 26552, ISO/IEC 26553, ISO/IEC 26554, ISO/IEC 26556, ISO/IEC 26560,
ISO/IEC 26561, ISO/IEC 26562, ISO/IEC 26563 are planned International Standards.
© ISO/IEC 2017 – All rights reserved vii

INTERNATIONAL STANDARD ISO/IEC 26559:2017(E)
Software and systems engineering — Methods and tools for
variability traceability in software and systems product line
1 Scope
This document, within the context of the tools and methods of variability traceability for software and
system product lines:
— provides the terms and definitions specific to variability traceability for software and systems
product lines;
— defines process groups and their processes for establishing and managing variability traceability at
product line lifecycle processes. Those processes are described in terms of purpose, inputs, tasks,
and outcomes;
— defines method capabilities to support the defined tasks of each process;
— defines tool capabilities to automate/semi-automate tasks or defined method capabilities.
This document does not concern processes and capabilities of tools and methods for a single system but
rather deals with those for a family of products.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at http:// www .electropedia .org/
— ISO Online browsing platform: available at http:// www .iso .org/ obp
3.1
aspect
special consideration within product line engineering process groups and tasks to which we can
associate specialized methods and tools
3.2
instantiated trace link
trace link (3.6) derived by applying binding in a member product
3.3
texture
architectural texture
collection of common development rules and constraints for realising the applications of a product line
3.4
traceability
discernible association among two or more logical entities, such as requirements, system elements,
verifications, or tasks
© ISO/IEC 2017 – All rights reserved 1

3.5
traceability with different abstraction level
level of detail for established traceability (3.4)
EXAMPLE The finer level of detail, the more general level.
3.6
trace link
association between two trace artefacts or between an element of variability model and a development
artefact
3.7
trace link semantics
purpose or meaning of the trace link (3.6), specified in the trace link types
EXAMPLE ‘Implements’, ‘refines’, ‘requires’ and ‘excludes’.
3.8
variability traceability
traceability (3.4) among variability definition, variability implementation in domain engineering and
application engineering, and thereafter tracing impacts due to variability changes
3.9
variant
instance or value of a variation point (3.10)
3.10
variation point
indication of product differentiation based on particular variable characteristics of products, domain
assets, and application assets in the context of a product line
4 Abbreviated terms
CRUD create, read, update, delete
OVM orthogonal variability model
SSPL software and systems product line
5 Reference model for variability traceability in software and systems
product line
5.1 Overview
Variability is a key differentiator between single-system engineering and management and product
line engineering and management. Product line engineering and management has to take explicitly
into account the variations within and between multiple products. The product line variabilities are
introduced and defined during product management, domain engineering and application engineering
processes defined in ISO/IEC 26550. Explicitly defined variability is represented or implemented
by different development artifacts, and it should be traced for the proper management. Variability
traceability enables tracing variabilities defined in variability models from their introduction stage to
binding stage. Variability tracing should be able to trace variability with all of relevant development
artefacts of domain engineering and application engineering processes of ISO/IEC 26550.
SSPL traceability provides a set of linkages of artefacts in a product line. Compared to the traceability
of single product development, SSPL traceability is more complex because SSPL has two separate
but intimately related development processes, i.e. domain engineering and application engineering.
SSPL traceability includes trace links between artefacts within the same stages, trace links between
2 © ISO/IEC 2017 – All rights reserved

artefacts produced in different stages, trace links between domain and application artefacts, and trace
links among variability-related artefacts. This document deals with trace links among variability-
related artefacts, i.e. variability traceability.
Variability traceability enables the establishment and maintenance of trace links among variabilities
described in the various forms of domain assets, application assets, and variability models.
Variability traceability is important for the consistent maintenance and evolution of variabilities
implemented/described in those various forms. Trace links can be simple relationships between
different variability-related artefacts or they can be comprehensive and sophisticated trace information
including trace link semantics. Because having too much (comprehensive) or too little (simple)
traceability is costly or insufficient, an economic analysis for the abstraction level of traceability should
be conducted in order to make decision on the appropriate level of details for traceability establishment
and management.
The variability of a product line is spread all over development artefacts, so it is difficult to trace
variability, for example, between the sources of variability and the corresponding artefacts. An
orthogonal variability model (OVM), a separated model defining the variability of a product line, provides
a cross-sectional view of the variability across all development artefacts. It relates the elements of a
variability defined to different development artefacts such as feature models, requirements artefacts,
architecture, detailed designs, codes, test artefacts, and after compile time artefacts (e.g. makefile).
Thus, the variability of different development artefacts can be traced through an OVM. Figure 1
illustrates the concept of OVM-based variability traceability in domain engineering.
Figure 1 — OVM-based variability tracing in domain engineering
Variability relating to several domain development artefacts can be traced through the OVM. As shown
in Figure 1, a variation point or variant can relate to different development artefacts of different stages.
They can relate to a use case, corresponding sub-systems, and corresponding components. Therefore,
relations among artefacts corresponding to the same variability either located in the same stage or
different stages can be traced through the links from the elements of the OVM. Because the trace links
from the OVM to development artefacts include links from a variation point to its representing artefacts
© ISO/IEC 2017 – All rights reserved 3

and links from the variants to their realizing artefacts, impacts on the corresponding artefacts due to
the variability changes or evolution can be completely and easily analysed.
The OVM, namely the domain variability model, relates with the application variability model in
accordance with binding decisions and the corresponding trace links are also instantiated along with
binding. Member product specific variability is defined through the application variability model and
it relates to the corresponding application artefacts. From introduction time through binding time,
variability traceability is achieved through the instantiated trace links, trace links between the OVM
and application variability model, and member product specifically established trace links. Figure 2
illustrates OVM based variability tracing in a product line.
Domain artefact Application artefact
Figure 2 — OVM based variability tracing within a product line
The thick broken line means instantiated trace links in accordance with binding decisions in application
engineering. There exists a newly added variability (e.g. CfgDisplay in Figure 2) and its trace link with
application artefacts is defined.
5.2 Reference model for variability traceability in software and systems product line
The reference model specifies the structure of supporting processes and subprocesses for variability
traceability in product line. As shown in Figure 3, variability traceability in product line can be
structured into three processes: variability tracing management, variability tracing and variability
tracing support. In the rest of this document, tasks, methods and tools are described in terms of
processes and subprocesses defined in the reference model.
Each process is divided into subprocesses and each subprocess is described in terms of the following
attributes:
— the title of the subprocess;
— the purpose of the subprocess;
4 © ISO/IEC 2017 – All rights reserved

— the inputs to produce the outcomes;
— the tasks to achieve the outcomes;
— the outcomes of the subprocess;
— the capabilities of tools and methods are a list of the required support of tools and methods for
performing the tasks properly.
Figure 3 — Variability traceability in SSPL
The variability tracing management process supports for establishing plans for establishing
and maintaining variability traceability with the different levels of detail, for providing enabling
environments for realizing the planned variability traceability, and for managing plans versus actual
variability traceability status. The variability tracing management process provides required principles
and foundations such as the level of abstraction of traceability, traceability notation, and traceability
algorithm for establishing and maintaining variability traceability. Variability tracing management
shall do the following:
— variability tracing planning;
— variability tracing enabling;
— variability tracing managing.
The variability tracing process supports establishing and maintaining variability traceability in domain
engineering and application engineering. Variability tracing shall do the following:
— traceability between domain variability model and domain artefacts;
— traceability between application variability model and application artefacts;
— traceability between domain and application variability model;
© ISO/IEC 2017 – All rights reserved 5

— traceability between variability related artefacts within a stage;
— traceability between variability related artefacts in different adjacent stages.
The variability tracing support process provides required support for establishing and maintaining the
required variability traceability including traceability algorism, validation and verification supports
for established variability traceability, and traceability with variability models. Variability tracing
support shall do the following:
— relating traceability to variability model;
— quality assurance for variability tracing;
— traceability algorism.
The identification and analysis of the key differentiators between single-system engineering and
management and product line engineering and management can help organizations to understand the
product line and to formulate a strategy for successful implementation of product line engineering and
management. The key aspects have been defined in ISO/IEC 26550 and Table 1 shows the categories of
the key aspects.
Table 1 — Key aspects for identifying product line-specific variability traceability tasks
Category Aspects
Reuse management Application engineering, domain assets, domain engineering, product management,
platform, reusability
Variability manage- Binding, variability
ment
Complexity manage- Collaboration, configuration, enabling technology support, reference architecture,
ment texture, traceability
Quality management Measurement and tracking, cross functional verification and validation
The following are the descriptions for each aspect concerning variability traceability for product lines.
The variability tracing relevant processes and tasks shall be identified on the basis of these aspects. The
concerns specific to variability traceability for product lines will enable an organization to understand
the variability tracing relevant processes, subprocesses, tasks, methods and tools’ capabilities.
— Application engineering: Variabilities-bound and newly-added application specific variabilities
during application engineering should be traced. Application variability model plays a key role for
maintaining those traceabilities.
— Binding: Binding results (i.e. variants decision) in a member product should be properly traced so
as to manage them with variability changes and evolutions.
— Collaboration: Variability traceability enables collaboration among domain and application
engineers.
— Configuration: Bound variability of a configuration should be traced and its version should be
properly managed.
— Domain asset: Variabilities implemented through domain assets should be traced. Variability model
is used to trace them.
— Domain engineering: Variability defined and implemented during domain engineering should be
traced. Trace links for a variability implemented in different domain assets and trace links for a
variability implemented throughout the different domain engineering stages should be established
and maintained. Domain variability model can be used to trace a variability implemented throughout
the different domain engineering stages.
— Enabling technology support: Technologies for establishing and maintaining trace links for
variabilities should be supported.
6 © ISO/IEC 2017 – All rights reserved

— Measurement and tracking: The effectiveness and efficiency of traceability established and
maintained should be properly measured and tracked so as to improve variability tracing processes.
— Platform: Variability consisting parts of a platform should be traced.
— Product management: Variability traceability should evolve in accordance with the evolution and
changes of product lines. Variability traceability should be established and maintained towards
ease of supporting the evolution and changes of product lines.
— Reference architecture: Reference architecture has a key role in a product line, so variability
traceability for variability-relevant architectural design decisions, architectural elements, and
textures in the reference architecture should be carefully established and managed.
— Reusability: Variability traceability enables the reusability of variability among member products
under the change and evolution control of variability.
— Texture: Texture related to rules and constraints for variability should be properly traced by
variability traceability.
— Traceability: Traceability among variability expressed/implemented in requirements, architecture,
realization, and variability models should be established and managed.
— Cross functional validation and verification: Validation and verification for established and
maintained variability traceability are performed.
— Variability: Relations among variability in domain engineering, application engineering, and
variability explicitly defined in variability model are managed through the variability trace links.
6 Variability tracing management
6.1 General
Variability tracing plan, enabling environments, and other managerial supports address variability
traceability establishment and maintenance with variability model.
The variability tracing management process includes the following subprocesses:
— variability tracing planning;
— variability tracing enabling;
— variability tracing managing.
6.2 Variability tracing planning
6.2.1 Purpose of variability tracing planning
6.2.1.1 General
The purpose of this subprocess is to establish and maintain plans for defining and maintaining
variability traceabilities in a product line.
6.2.1.2 Inputs
The following inputs should be available to perform the variability tracing planning process:
— variability management plan;
— organization’s process capability;
© ISO/IEC 2017 – All rights reserved 7

— organization’s available resources.
6.2.1.3 Outcomes
The following outcomes shall be available as a result of the successful implementation of the variability
tracing planning process:
— variability tracing management plans are established;
— quality measures for variability tracing are defined;
— responsibilities for variability tracing are assigned.
6.2.1.4 Tasks
The organization shall implement the following tasks with respect to the variability tracing planning
process.
— Design variability tracing strategy: to make a strategy for establishing and maintaining variability
tracing centred on variability model.
— Define quality assurance measures for variability tracing: to define quality assurance measures
to monitor and control quality assurance activities in variability tracing so as to achieve quality
assurance throughout the SSPL stages.
— Assign responsibility for variability tracing: to clarify roles and responsibilities with respect to
variability tracing.
— Record variability tracing plan: to document and get agreement and commitment on variability
tracing plan from the appropriate staffs and managers.
6.2.2 Design variability tracing strategy
The goal of this task is to define the level of maintaining variability traceability, standards and methods
used for establishing and maintaining variability traceability, rules, constraints, and validation related
strategy for established variability traceability.
The method should support designing variability tracing strategy with the following capabilities:
— providing selection guides for variability tracing relevant standards, methods, validation;
— providing templates for informing what is major contents of strategy;
— providing examples for major documentation contents.
A tool should support designing variability tracing strategy by allowing the user to do the following:
— supporting the access of selection guides;
— providing electronic documentation template for strategy;
— allowing immediate reference for the examples of major documentation contents during
documentation.
6.2.3 Define quality assurance measures for variability tracing
The goal of this task is to define quality assurance measures for quantifying the quality of variability
tracing. Quality assurance measures include measures representing the quality level of established
variability traceability, quality level of implemented quality assurance activities, and deviations from
the defined rules and constraints.
8 © ISO/IEC 2017 – All rights reserved

The method should support defining quality assurance measures for variability tracing with the
following capabilities:
— providing characteristic functions for expressing the overall quality level of variability traceability;
— supporting quality measure and metric definition;
— supporting quality measurement activities related to variability tracing.
A tool should support defining quality assurance measures for variability tracing by allowing the user
to do the following:
— supporting calculation of characteristic functions;
— supporting data collection related to measures;
— allowing integration or expansion of quality measures for quality level analysis.
6.2.4 Assign responsibility for variability tracing
The goal of this task is to assign roles and responsibilities for variability tracing. Roles and
responsibilities include identifying sources and targets of trace links, establishing variability trace
links with tools, validating and verifying the established variability tracing, and quality assurance for
variability tracing.
The method should support assigning responsibility for variability tracing with the following
capabilities:
— extracting organization units that are proper to the defined variability tracing roles;
— assuring their capabilities with the roles and responsibilities to be assigned;
— providing a way to define roles and responsibilities concretely, correctly, and consistently for the
right communication.
A tool should support assigning responsibility for variability tracing by allowing the user to do the
following:
— allowing access for the structure of organization units;
— providing documentation for the assignment results;
— sharing the defined roles and responsibilities with relevant participants.
6.2.5 Record variability tracing plan
The goal of this task is to document plans for variability tracing. Plan documentation includes schedules,
defined roles and responsibilities, defined quality assurance measures.
The method should support recording variability tracing plan with the following capabilities:
— supporting variability tracing relevant scheduling (establishment, management);
— supporting integration of the pre-defined roles and responsibilities to variability tracing plan;
— providing documentation template for variability tracing plan.
A tool should support recording variability tracing plan by allowing the user to do electronic plan
documentation.
© ISO/IEC 2017 – All rights reserved 9

6.3 Variability tracing enabling
6.3.1 Purpose of variability tracing enabling
6.3.1.1 General
The purpose of this subprocess is to provide enabling environments for defining and maintaining
variability traceabilities in a product line.
6.3.1.2 Inputs
The following inputs should be available to perform the variability tracing enabling process:
— variability tracing management plans;
— quality measures for variability tracing.
6.3.1.3 Outcomes
The following outcomes shall be available as a result of the successful implementation of the variability
tracing enabling process:
— guidance for variability tracing is defined;
— roles and responsibilities for variability tracing are mobilized;
— variability tracing environments are enabled;
— quality assurance measurement environments for variability tracing are enabled.
6.3.1.4 Tasks
The organization shall implement the following tasks with respect to the variability tracing enabling
process.
— Provide guidance for variability tracing: to define detailed ways to establish and maintain variability
tracing centred on variability model.
— Mobilize roles and responsibilities for variability tracing: to provide resources appropriate for roles
and responsibilities necessary to variability tracing.
— Enable variability tracing management: to provide managerial environments necessary to
establishing and maintaining variability tracing centred on variability model.
— Enable variability tracing operations: to provide enablers necessary to right use of established
variability tracing.
— Enable quality assurance measurement for variability tracing: to provide enablers necessary to
measuring quality assurance activities.
6.3.2 Provide guidance for variability tracing
The goal of this task is to define detailed guides used for variability traceability establishment and
management. The guidance includes detailed procedures, techniques used at the specific steps, detailed
rules and constraints adhered during procedures, and required supports for the successful variability
tracing in SSPL.
The method should support providing guidance for variability tracing with the following capabilities:
— defining the contents of the guidance;
10 © ISO/IEC 2017 – All rights reserved

— providing examples for each content.
A tool should support providing guidance for variability tracing by allowing the user to do the following:
— providing documentation environment for variability tracing guidance;
— allowing easy reference to each contents of guidance.
6.3.3 Mobilize roles and responsibilities for variability tracing
The goal of this task is to make all assigned roles and responsibilities ready for variability tracing.
The method should support mobilizing roles and responsibilities for variability tracing with the
following capabilities:
— providing supports required for completing each role and responsibility’s assignment;
—
...