ISO/IEC 26561:2019

Software and systems engineering — Methods and tools for product line technical probe

This document, within the context of methods and tools for supporting the diagnosis of the organization's capability to adopt or improve software and systems product line engineering: — defines processes for product line technical probe; those processes are described in terms of purpose, inputs, tasks and outcomes; — defines method capabilities to support the defined tasks of each process; and — defines tool capabilities that automate or semi-automate tasks and methods. 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.

Ingénierie du logiciel et des systèmes — Méthodes et outils destinés à la vérification technique des gammes de produits

General Information

• Status: Published
• Publication Date: 27-Nov-2019
• 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: 9060 - Close of review
• Completion Date: 04-Jun-2030

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 26561
First edition
2019-11
Software and systems engineering —
Methods and tools for product line
technical probe
Ingénierie du logiciel et des systèmes — Méthodes et outils destinés à
la vérification technique des gammes de produits
Reference number
©
ISO/IEC 2019
© ISO/IEC 2019
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, 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
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Fax: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2019 – 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 product line technical probe . 2
5.1 Overview . 2
5.2 Reference model for product line technical probe . 3
6 Product line technical probe management . 6
6.1 General . 6
6.2 Technical probe planning . 6
6.2.1 Principal constituents . 6
6.2.2 Establish technical probe goals . 7
6.2.3 Define key procedures for technical probe . 7
6.2.4 Formulate schedules and required resources for technical probe . 7
6.2.5 Specify how to monitor, measure, and control the effectiveness of
technical probe . 8
6.2.6 Document the product line technical probe plan . 8
6.3 Technical probe enabling . 9
6.3.1 Principal constituents . 9
6.3.2 Establish governance policy for technical probe .10
6.3.3 Mobilize qualified human resources for technical probe .10
6.3.4 Identify infrastructure and resource needs for technical probe
operationalization and support .10
6.3.5 Enable quality assurance measurement for technical probe .11
6.3.6 Improve technical probe process continuously .11
6.4 Technical probe managing .12
6.4.1 Principal constituents .12
6.4.2 Tailor and allocate governance policy, R & R, and resources to relevant
sub functions of technical probe .13
6.4.3 Collect data from SSPL technical probe sub functions .13
6.4.4 Monitor, measure, and control technical probe operation and support .13
6.4.5 Manage actual operation and support of technical probe .14
6.4.6 Provide feedback to planning and enabling functions of technical probe .14
7 Product line technical probe operationalization .15
7.1 General .15
7.2 Technical probe preparation .15
7.2.1 Principal constituents .15
7.2.2 Review and refine the context of technical probe .16
7.2.3 Specify the phases of technical probe .16
7.2.4 Identify the organization’s SSPL stakeholders .17
7.2.5 Analyse the organization’s level of process maturity .17
7.2.6 Distribute and gather preliminary phase questionnaire .18
7.2.7 Analyse and document preliminary phase findings .18
7.3 Technical probe operation .19
7.3.1 Principal constituents .19
7.3.2 Perform technical probe interview with organization’s SSPL stakeholders .19
7.3.3 Capture relevant data from the interview .20
7.3.4 Document the findings, strengths and weaknesses.20
7.3.5 Assess gaps between to-be and as-is .20
7.3.6 Provide recommendations .20
© ISO/IEC 2019 – All rights reserved iii

7.4 Product line value estimation .21
7.4.1 Principal constituents .21
7.4.2 Determine potential member products .21
7.4.3 Measure potential reusability and opportunity .22
7.4.4 Analyse the costs and benefits of a product line .22
7.4.5 Perform go/no-go decision to a product line basis .23
7.4.6 Hand over product line value estimation results to scoping .23
7.5 Product line adoption scenarios structuring .23
7.5.1 Principal constituents .23
7.5.2 Coordinate the adoption strategy with the technical probe results .24
7.5.3 Structure product line adoption scenarios .24
7.5.4 Document a draft CONOPS .25
8 Product line technical probe support .25
8.1 General .25
8.2 Quality assurance for technical probe .25
8.2.1 Principal constituents .25
8.2.2 Objectively evaluate technical probe process .26
8.2.3 Objectively evaluate technical probe work products .27
8.2.4 Communicate and resolve noncompliance issues.27
8.2.5 Establish records of technical probe quality assurance activities .27
8.3 Decision support for technical probe .28
8.3.1 Principal constituents .28
8.3.2 Establish decision support policy for technical probe .29
8.3.3 Tailor decision procedure for technical probe .29
8.3.4 Guide the decision execution for technical probe .30
8.3.5 Document the rationale for decisions concerning technical probe .30
8.3.6 Learn from decision results of technical probe .31
8.4 Risk management for technical probe .31
8.4.1 Principal constituents .31
8.4.2 Identify risks related to the success of technical probe .32
8.4.3 Develop mitigation plans for the identified risks .33
8.4.4 Monitor the execution of the mitigation plan .33
8.4.5 Learn from actual results of risk management for technical probe .34
Annex A (informative) Exemplar multi-criteria decision mechanism for technical probe .35
Annex B (informative) Exemplar adoption scenario .37
Annex C (informative) Exemplar frameworks of maturity and questionnaire .38
Bibliography .39
iv © ISO/IEC 2019 – 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.
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) or the IEC
list of patent declarations received (see http:// patents .iec .ch).
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.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 7, Software and systems engineering.
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.
© ISO/IEC 2019 – 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, with reduced time to market and better quality. As a result, it has gained increasing global
attention since the 1990s.
Product line technical probe diagnoses an organization’s ability necessary to successfully adopt product
line engineering and management. Product line engineering and management require abilities to deal
with markets, competitors, costs, benefits, two different and closely related domain and application
engineering processes, and the distribution of different domain and application engineering over
organizations. Before transitioning to product line engineering, an organization should assess its
ability from these aspects and decide whether or not to switch to product line engineering. Based on
the results of product line technical probe, an organization can establish plans to continuously improve
its abilities.
This document can be used in the following modes:
— by organizations that want to adopt SSPL for producing their products – to provide guidance on how
to probe the organization’s capabilities necessary to adopt or improve product line engineering;
— by a product line organization – to provide guidance on the evaluation and selection for methods
and tools for product line technical probe; and
— by providers of methods and/or tools – to provide guidance on implementing or developing methods
and/or tools by specifying a comprehensive set of methods and tools capabilities for supporting
product line technical probe.
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 standards in the ISO/IEC 26550 family are as follows:
ISO/IEC 26550, ISO/IEC 26551, ISO/IEC 26552, ISO/IEC 26553, ISO/IEC 26554, ISO/IEC 26555,
ISO/IEC 26556, ISO/IEC 26557, ISO/IEC 26558, ISO/IEC 26559 and ISO/IEC 26560 are published.
ISO/IEC 26562 is to be published. ISO/IEC 26563 and ISO/IEC 26564 are planned International
Standards.
— 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 modelling are provided in
ISO/IEC 26558;
vi © ISO/IEC 2019 – All rights reserved

— 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 product line transition management are provided
in ISO/IEC 26562 (International Standard under development);
— Processes and capabilities of methods and tools for configuration management of asset are provided
in ISO/IEC 26563 (planned International Standard);
— Processes and capabilities of methods and tools for product line measurement are provided in
ISO/IEC 26564 (planned International Standard);
— Others (ISO/IEC 26564 to ISO/IEC 26599): To be developed.
© ISO/IEC 2019 – All rights reserved vii

INTERNATIONAL STANDARD ISO/IEC 26561:2019(E)
Software and systems engineering — Methods and tools for
product line technical probe
1 Scope
This document, within the context of methods and tools for supporting the diagnosis of the
organization’s capability to adopt or improve software and systems product line engineering:
— defines processes for product line technical probe; those processes are described in terms of
purpose, inputs, tasks and outcomes;
— defines method capabilities to support the defined tasks of each process; and
— defines tool capabilities that automate or semi-automate tasks and methods.
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:
— ISO Online browsing platform: available at http:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
3.1
aspect
special consideration within product line (3.9) engineering process groups and tasks to which one can
associate specialized methods and tools
3.2
main probe
phase to perform repetitive cycle for gathering and analysing data for finding strengths and challenges
of an organization
3.3
post-probe
optional phase to prepare action plans for addressing challenges
3.4
pre-probe
phase to understand an organization’s basic context such as current structure, terminology, product
maturity level, implementation and documentation
3.5
product line adoption plan
plan that describes the changes in process, organization structure, and product building methods to get
from the current to product line (3.9) engineering
© ISO/IEC 2019 – All rights reserved 1

3.6
product line adoption scenario
scenario that gives concrete sequence of actions related to product line (3.9) adoption
3.7
product line technical probe
technical probe
probe
diagnostic process for investigating the organization’s readiness to adopt, or ability to succeed with,
product line (3.9) engineering and management
3.8
product line transition
transition
switching to product line (3.9) engineering through the right procedures, so as to achieve business
objectives that lead an organization to product line engineering
3.9
software and systems product line
SSPL
product line
paradigm for the creation, exploitation, and management of a common platform for a family of products
Note 1 to entry: Typical goals of product lines are to lower costs, reduce time to market, and improve quality.
4 Abbreviated terms
CONOPS concept of operations
MCDM multiple condition decision method
5 Reference model for product line technical probe
5.1 Overview
A product line technical probe diagnoses an organization’s readiness to adopt product line engineering.
The technical probe includes whether an organization has abilities to succeed with product line
engineering. When an organization considers the adoption of product line engineering, a product line
technical probe informs an organization whether the organization has essential capabilities necessary
to adopt product line engineering and at which maturity level the organization is based on the essential
organizational, technical and software engineering framework. A product line technical probe provides
overall pictures about an organization’s current capability level compared with essential capabilities
necessary to successfully provide products that conform to market and customer needs.
In accordance with the results of a product line technical probe, an organization can make a go/no-
go decision about product line adoption; or in the case that an organization determines product
line adoption, it establishes and implements action plans for resolving weaknesses found, so an
organization can shift to product line engineering after it has the essential capabilities. During product
line engineering and management, a product line technical probe supports continuous improvements
of an organization’s product line capability.
Software and systems product line requires mature capability level in both system and software
engineering. In adopting a product line engineering approach, an organization extends the portfolio
management process of ISO/IEC/IEEE 15288 and applies specializations of its product development,
technical management, and infrastructure processes. Thus, a product line technical probe should
diagnose an organization’s ability from architecture and organizational management viewpoints as
well as process capability. For successful product line adoption, an organization should continuously
diagnose and improve its process, architecture, business, and organizational management capabilities.
2 © ISO/IEC 2019 – All rights reserved

5.2 Reference model for product line technical probe
The reference model specifies the structure of supporting processes and subprocesses for a product
line technical probe. As shown in Figure 1, a product line technical probe can be structured into three
processes: technical probe management, technical probe operationalization and technical probe
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;
— the inputs to produce the outcomes;
— the tasks to achieve the outcomes; and
— the outcomes of the subprocess.
Figure 1 — Reference model for the product line technical probe
The product line technical probe management process provides managerial supports for planning
technical probe (e.g. resource estimation, responsibility allocation, success measures), supports
for providing necessary resources, tools and infrastructures for realizing technical probe plans and
supports for analysing the plan versus actual status of technical probing. The product line technical
probe management shall do the following:
— technical probe planning establishes plans for initiating, operationalizing and supporting product
line technical probe;
— technical probe enabling defines, maintains and assures the availability of environments, guidance,
and measurement necessary to performing product line technical probe; and
© ISO/IEC 2019 – All rights reserved 3

— technical probe managing provides integrated management for the technical probe operationalization;
this subprocess reviews the technical probe operationalization’s actual status against plans,
controls issues and takes corrective actions if necessary.
The product line technical probe operationalization process performs operations for analysing an
organization’s readiness for adopting product line engineering and finding improvements required
for successful and suitable product line adoption. This process deals from the organization’s readiness
for technical probe to producing product line adoption scenarios. The product line technical probe
operationalization shall do the following:
— technical probe preparation initiates the product line technical probe by mobilizing participants and
resources; this subprocess performs preliminary technical probe for coordinating participants and
resources;
— technical probe operation performs the product line technical probe in accordance with the technical
probe plans;
— product line value estimating determines returns on investments in order to decide whether an
organization initiates product line transition or quits product line adoption; and
— product line adoption scenario structuring establishes the product line adoption strategy based on
the findings delivered in technical probe operation.
The product line technical probe support process provides supports required for producing correct
technical probe findings and product line adoption scenarios so as to achieve the organization’s values
through product line engineering. To achieve these, the product line technical probe support shall do
the following:
— quality assurance for technical probe objectively evaluates the activities and artefacts of the
implemented product line technical probe;
— decision support for technical probe supports decision making for producing findings and
recommendations of the product line technical probe and structuring product line adoption plan
and scenarios; and
— risk management for technical probe identifies and mitigates risks related to product line
technical probe.
The identification and analysis of the key differentiators between single-system engineering and
management and product line engineering and management can help the 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 category
of the key aspects.
Table 1 — Key aspects for identifying product line technical probe tasks
Category Aspects
application engineering, domain assets, domain engineering, product management,
Reuse management
platform, reusability
Variability
binding, variability
management
Complexity collaboration, configuration, enabling technology support, reference architecture,
management texture, traceability
Quality management measurement and tracking, cross functional verification and validation
The following is the description for each aspect concerning product line technical probe. The product
line technical probe processes and tasks shall be identified on the basis of these aspects. The concerns
4 © ISO/IEC 2019 – All rights reserved

for the product line technical probe will enable the organization to understand technical probe
processes, subprocesses, tasks, methods and tools’ capabilities.
— Application engineering: A technical probe diagnoses the organization’s capability from the essential
application engineering practices,
— Binding: A product line organization should be able to deal with a complete range of variability
binding times, so a product line technical probe diagnoses this ability.
— Collaboration: Participants of a technical probe should closely collaborate with the probe team
because a technical probe uses a series of interviews and reviews for data analysis as in software
capability assessment.
— Configuration: Because member products are configured during the application engineering based
on domain assets, a product line organization should have the capabilities required for configuring
member products.
— Domain asset: A product line technical probe investigates an organization’s ability for developing and
maintaining all domain assets that will be commonly used by member products of a product line.
— Domain engineering: A product line technical probe diagnoses an organization’s capability from the
essential domain engineering practices.
— Enabling technology support: Technical probe-enabling supports provide resources and
infrastructure necessary to initiate, support and control technical probe tasks.
— Measurement and tracking: Measurement and tracking have two aspects in a technical probe. One
is the organization’s capability to measure and control its product line processes, and another is its
capability to measure and trace the status of action plans defined to adopt or improve product line
engineering.
— Platform: A product line technical probe diagnoses the organization’s capability to design and
realize platforms that will be used by member products of a product line.
— Product management: The results of a product line technical probe are used when the product
management process takes the direction of a product line evolution.
— Reference architecture: Product line engineering relies on a reference architecture, and the
reference architecture is a key success factor of a product line. Thus, a product line technical probe
investigates an organization’s architecture capability.
— Reusability: Reusability that will be expected through the product line is initially estimated.
— Texture: For developing a family of products by using common assets, it is important to define rules
and constraints for implementing architecture and evolving it over time. A product line technical
probe investigates an organization’s ability to select and define texture.
— Traceability: Product line technical probe assures a product line organization’s ability to relate the
assets of the different development roles, such as domain engineering, application engineering, and
each of their different development stages.
— Cross functional validation and verification: Artefacts, processes, and tasks related to product line
technical probe should be validated and verified when the needs arise.
— Variability: Variations among member products of initial product line portfolio defined for
conducting product line pilot are analysed to use as an input for go/no-go decision.
© ISO/IEC 2019 – All rights reserved 5

6 Product line technical probe management
6.1 General
The product line technical probe management supports the following:
— technical probe planning;
— technical probe enabling; and
— technical probe managing.
6.2 Technical probe planning
6.2.1 Principal constituents
6.2.1.1 Purpose
The purpose of this subprocess is to create plans for product line technical probe applied to diagnose
an organization’s strengths and challenges in each of the selected product line frameworks.
6.2.1.2 Inputs
The following inputs should be available to perform the technical probe planning process:
— initial information that provides an overview of the organizational context;
— objectives of the product line;
— description of the organizational structure;
— organization’s process maturity level; and
— outcomes of decision support for technical probe process.
6.2.1.3 Outcomes
The following outcome shall be available as a result of the successful implementation of the technical
probe planning process:
— Product line technical probe plan including goals, key procedures, schedules, required resources,
monitoring and control plan) is established and documented.
6.2.1.4 Tasks
The organization shall implement the following tasks with respect to the technical probe planning
process:
— Establish technical probe goals: Define the technical probe goals and strategies that should be
achieved through the product line technical probe and applied to achieve the goals.
— Define key procedures for technical probe: Determine or tailor procedures used for examining an
organization’s readiness to adopt a product line approach or to assess the current capability of
product line practices.
— Formulate schedules and required resources for technical probe: Schedule the product line technical
probe including time, activities, and key participants with required resources.
6 © ISO/IEC 2019 – All rights reserved

— Specify how to monitor, measure, and control the effectiveness of technical probe: Determine key
actions and measures for quantifying and qualifying the effectiveness of the product line technical
probe activities and its results.
— Document the product line technical probe plan: Set plans for performing the product line technical
probe or improve the product line technical plan in accordance with the preliminary technical probe
results.
6.2.2 Establish technical probe goals
The goal of this task is to define the product line technical probe goals and strategies for diagnosing an
organization’s readiness for the successful adoption or improvement of a product line approach.
The method should support establishing technical probe goals with the following capabilities:
— examining product line technical probe context and requirements;
— formulating product line technical probe goals; and
— reviewing established technical probe goals.
A tool should support establishing technical probe goals by allowing the user to do the following:
— access product line technical probe goals; and
— communicate product line technical probe goals with key stakeholders.
6.2.3 Define key procedures for technical probe
The goal of this task is to define and/or tailor key procedures for the preliminary, the technical probe,
and the follow-on phases.
The method should support defining key procedures for the technical probe with the following
capabilities:
— tailoring procedures for the technical probe based on the overall product line process;
— embedding defined technical probe goals into defined key procedures so that measuring of goal
achievement is possible; and
— specifying defined key phases and tasks of the technical probe.
A tool should support defining key procedures for the technical probe by allowing the user to do the
following:
— access the overall product line technical probe process;
— share key procedures with relevant stakeholders;
— make decisions under the supports of decision-making procedures;
— integrate and calibrate procedures; and
— edit/fill out key phases and tasks of the product line technical probe in accordance with the
documentation standard.
6.2.4 Formulate schedules and required resources for technical probe
The goal of this task is to define the day-by-day technical probe schedule and resources required for
activities such as people, devices and space. The typical probe schedule includes activities over time
and participants.
© ISO/IEC 2019 – All rights reserved 7

The method should support formulating schedules and required resources for the technical probe with
the following capabilities:
— understanding difficulties in the technical probe and capabilities of people, materials, and
mechanisms that can be mobilized;
— estimating efforts and resources required; and
— defining the documentation standard for technical probe scheduling.
A tool should support formulating schedules and required resources for the technical probe by allowing
the user to do the following:
— access information to formulate schedules for the technical probe;
— access information to assign the organization’s available resources for the technical probe; and
— specify a schedule for the product line technical probe according to the defined documentation
standard (graphically describe the schedules).
6.2.5 Specify how to monitor, measure, and control the effectiveness of technical probe
The goal of this task is to define ways to collect data that indicate the state of the probe, track, measure,
and analyse relevant attributes of the technical probe process, so as to perform the corrective actions
to obstacles.
The method should support specifying how to monitor, measure, and control the effectiveness of the
product line technical probe with the following capabilities:
— defining observation points to monitor the effectiveness of the technical probe;
— defining pre-conditions for monitoring the effectiveness of the technical probe;
— defining measures and integration functions for evaluating the effectiveness of the technical
probe; and
— defining rules adhered when the product line technical probe is controlled.
A tool should support specifying how to monitor, measure, and control the effectiveness of the technical
probe by allowing the user to do the following:
— access historical data related to monitoring and controlling other processes;
— specify escalation lines for controlling the issues and obtaining feedbacks; and
— specify monitor, measure, and control plan using the documentation standard.
6.2.6 Document the product line technical probe plan
The goal of this task is to put the specified items of product line technical probe plan together and
obtain approvals for implementing the product line technical probe plan.
The method should support documenting the product line technical probe plan with the following
capabilities:
— providing the documentation standard for the product line technical probe plan (the contents of
plan include stakeholder, strategy of technical probe, technical probe tasks and estimates, staffing
including required training); and
— providing examples for each technical probe documentation item.
8 © ISO/IEC 2019 – All rights reserved

A tool should support documenting the product line technical probe plan by allowing the user to do the
following:
— edit/fill out technical probe plan using editable and changeable template;
— maintain the version control of the technical probe plan documents; and
— share the product line technical probe plan with the stakeholders.
6.3 Technical probe enabling
6.3.1 Principal constituents
6.3.1.1 Purpose
The purpose of this subprocess is to acquire the required resources and establish environments for
probing an organization’s technical strengths and weaknesses in each of the selected product line
engineering frameworks.
6.3.1.2 Inputs
The following inputs should be available to perform the technical probe enabling process:
— product line technical probe plan;
— document for organizational enabling processes; and
— resources and capabilities of organizational enabling.
6.3.1.3 Outcomes
The following outcomes shall be available as a result of the successful implementation of the technical
probe enabling process:
— Governance policy document for technical probe is clarified.
— Roles and responsibilities for technical probe are structured.
— Technical probe enablers including resources are mobilized.
— Action plan for technical probe process improvement is documented.
— Technical probe processes are continuously improved.
6.3.1.4 Tasks
The organization shall implement the following tasks with respect to the technical probe enabling
process:
— Establish governance policy for technical probe: Define product line technical probe policy including
objectives, process, organization, evaluation, standards, and process improvement approaches for
the product line technical probe.
— Mobilize qualified human resources for technical probe: Organize the probe team and representatives
from the organization’s product line stakeholder groups.
— Identify infrastructure and resource needs for technical probe operationalization and support:
Identify and develop the appropriate supporting tools, set of standards to be followed during the
tec
...