ISO/IEC 26555:2015
(Main)Software and systems engineering — Tools and methods for product line technical management
Software and systems engineering — Tools and methods for product line technical management
ISO/IEC 26555:2015 deals with the tools and methods of technical management for software products, software services, software-intensive systems (including System Architecture and excluding hardware) within a product line. The scope of this International Standard is as follows: ? Enable the users of this standard to holistically understand, adopt, and enact the processes, tools, and methods for product line technical management. In addition, this International Standard helps the users evaluate and select relevant tools and methods based on business and user-related criteria. ? Help product line engineers, developers, and tool vendors become informed about capabilities of tools and methods that are required for supporting product line implementation from technical aspects. ? Provide product line-specific processes and capabilities of tools and methods in technical management. ISO/IEC 26555:2015 does not concern processes and capabilities of tools and methods for technical management for a one-of-a-kind system but rather deals with those belonging to a family of systems. NOTE: System Architecture is a set of logical and physical principles used to achieve a mission within a given environment. From System Architecture are derived components that can be subsystems, software products, human-based products like crew or operators or hardware product like mechanical structures, electronic boards, chemicals, etc. The scope of the International Standard spans from the system, to sub-systems, and software products. Other types of components and especially those related to human beings and to hardware parts are not within the scope of this International Standard.
Ingénierie du logiciel et des systèmes — Outils et méthodes pour le management technique des gammes de produits
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 26555
Second edition
2015-12-01
Software and systems engineering —
Tools and methods for product line
technical management
Ingénierie du logiciel et des systèmes — Outils et méthodes pour le
management technique des gammes de produits
Reference number
ISO/IEC 26555:2015(E)
©
ISO/IEC 2015
---------------------- Page: 1 ----------------------
ISO/IEC 26555:2015(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2015, 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. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2015 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 26555:2015(E)
Contents Page
Foreword .vi
Introduction .vii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Reference model for product line technical management . 2
5 Process management . 6
5.1 Applying process enabling processes for product lines . 7
5.1.1 Establish process management group . 7
5.1.2 Align resources for process definition and improvements . 8
5.1.3 Govern process definition and improvement . 9
5.1.4 Prepare process management and improvement . 9
5.2 Domain engineering process definition .10
5.2.1 Define domain engineering processes .10
5.2.2 Validate domain engineering processes .11
5.2.3 Deploy the domain engineering processes .11
5.3 Application engineering process definition .12
5.3.1 Define application engineering processes .12
5.3.2 Validate the conformance of application engineering processes with
domain engineering processes .13
5.3.3 Deploy the application engineering processes .14
5.4 Applying process monitoring and control for product lines .14
5.4.1 Plan for process monitoring and control .15
5.4.2 Define process performance measures .15
5.4.3 Measure and manage process performance .16
5.4.4 Coordinate processes for improving reusability .16
5.5 Applying process improvement for product lines .17
5.5.1 Assess processes .17
5.5.2 Estimate the impact of changes on processes .18
5.5.3 Plan process improvement .18
5.5.4 Implement process improvements .19
5.5.5 Evaluate process improvement .19
6 Variability management .20
6.1 Variability modelling .21
6.1.1 Establish variability modeling policy .21
6.1.2 Collect variability information .22
6.1.3 Verify variability models .23
6.1.4 Share and maintain variability models .23
6.2 Variability mechanism .23
6.2.1 Establish variability mechanism management policy .24
6.2.2 Operate variability mechanisms.24
6.2.3 Support variability mechanisms operation .25
6.3 Variability documentation .25
6.3.1 Establish policies for variability documentation .26
6.3.2 Collect annotations of variability models .26
6.3.3 Validate the variability documentation .26
6.4 Variability binding.27
6.4.1 Establish binding policy .27
6.4.2 Guide trade-offs analysis among alternatives of binding time .27
6.4.3 Guide binding time decision .28
6.4.4 Maintain binding information .28
6.5 Variability tracing .29
© ISO/IEC 2015 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 26555:2015(E)
6.5.1 Establish policies for traceability management of variability models .29
6.5.2 Define links between variability model and domain assets .30
6.5.3 Manage the changes of the defined trace links .30
6.6 Variability control and evolution.30
6.6.1 Identify and analyse the evolution needs of variants .31
6.6.2 Add or remove variants.31
6.6.3 Add or remove dependencies and constraints .32
6.6.4 Change binding time .32
6.6.5 Maintain the affected traceabilities .33
6.6.6 Provide feedback for variabilities and the variability evolution process .33
7 Asset Management .33
7.1 Asset identification .34
7.1.1 Set up and maintain organizational policies for managing assets .35
7.1.2 Identity asset candidates .35
7.1.3 Estimate efforts necessary to create, reuse, and update domain assets .35
7.1.4 Determine assets .36
7.1.5 Elicit information necessary to reuse assets .36
7.2 Asset base implementation .37
7.2.1 Establish the mining (retrieval) mechanism for assets .37
7.2.2 Define and implement the CRUD method for assets .38
7.2.3 Establish asset base .38
7.2.4 Evaluate asset base .39
7.3 Asset validation .39
7.3.1 Review the selected assets .40
7.3.2 Review asset configurations .40
7.3.3 Create and release baselines of assets .40
7.4 Asset evolution (including change management) .41
7.4.1 Manage asset changes .41
7.4.2 Maintain traceability of assets .42
7.4.3 Manage feedback and take appropriate evolution actions .42
7.4.4 Transform the existing assets into assets to rehabilitate asset base .43
7.4.5 Dispose assets from asset base .43
8 Support management .43
8.1 Technical quality management .44
8.1.1 Establish technical quality management policy .45
8.1.2 Establish and maintain criteria for quality assurance .45
8.1.3 Perform quality assurance according to criteria .45
8.1.4 Communicate and ensure resolution of noncompliance issues .46
8.2 Configuration management .46
8.2.1 Identify configurations of member products .47
8.2.2 Establish configuration tree for a product line .48
8.2.3 Manage configuration of variability in space .49
8.3 Decision management .49
8.3.1 Establish decision management policy .50
8.3.2 Tailor decision procedure .51
8.3.3 Guide the decision execution .51
8.3.4 Learn from execution results .51
8.4 Technical risk management .52
8.4.1 Identify technical risks .52
8.4.2 Assess technical risks .52
8.4.3 Develop technical risk mitigation plans.53
8.4.4 Activate the mitigation plan .53
8.5 Tool management .54
8.5.1 Identify needs for tool management.54
8.5.2 Select and adapt tools .55
8.5.3 Set up and maintain tools .55
Annex A (informative) Technical management and technical readiness levels (TRL) .56
iv © ISO/IEC 2015 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 26555:2015(E)
Annex B (informative) Relationship with ISO/IEC 12207 processes .57
Annex C (informative) Construct for process, method, tool, and aspect .60
Bibliography .61
© ISO/IEC 2015 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC 26555:2015(E)
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 meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical
Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/IEC JTC 1, Information technology, Subcommittee
SC 7, Systems and software engineering.
This second edition cancels and replaces the first edition (ISO/IEC 26555:2013), of which it constitutes
a minor revision.
vi © ISO/IEC 2015 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 26555:2015(E)
Introduction
The major purpose of this International Standard is to deal with the capabilities of tools and methods of
software and systems product line (SSPL) Technical Management. This International Standard defines
how the tools and methods can support for the software and systems product line-specific technical
management processes. Since product lines deal with multiple products that have similarities,
product lines have an unprecedented level of technical management complexities. This arises from the
following sources:
— There are inherent differences in technical considerations because there are parallel development
processes, domain and application engineering, in a product line and the two processes are tightly
related with each other around assets.
— The close relationships among domain engineering, application engineering, and assets require the
highly matured managerial capabilities for addressing relationships among them.
— There are lack of tools and methods to support the product line-specific technical management.
Technical management provides management support for a timely and proper deployment of product
line in balance with pre-defined product line objectives such as reusability, reducing cost, improving
quality, etc., as well as its planned cost, schedule, and resources. Technical management addresses
actual means used to support, monitor, and control the activities of both domain engineering and
application engineering of a product line.
There are needs for defining product line-specific technical management processes that integrate the
involved product line disciplines with those for a single product. Furthermore, support of tools and
methods are required so that a product line organization can perform technical management under
the systematic control of complexities. This International Standard addresses the product line-specific
processes in technical management by dividing those into process management, variability management,
asset management, and support management areas with the guidance of a set of tools and methods
capabilities for supporting tasks for product line technical management.
This International Standard is intended to benefit people who acquire, supply, develop, operate, and
maintain tools and methods for product line technical management. This International Standard can be
used in one or more of the following modes:
— By an organization intended to implement product lines—to understand, adopt, and enact the
processes, tools, and methods for product line technical management. This also helps the organization
to evaluate and select relevant tools and methods based on business and user-related criteria.
— By a tool vendor who facilitates or leverages product line engineering practices—to provide a set of
tool capabilities that should be embodied in a tool for supporting product line technical management.
ISO/IEC 26550 addresses both engineering and management processes and covers the key
characteristics of product line development. ISO/IEC 26550 provides an overview of the consecutive
international standards (i.e. ISO/IEC 26551 to ISO/IEC 26556), as well as the structure of the model:
— Processes and capabilities of methods and tools for product line scoping, domain requirements
engineering, and application requirements engineering are provided as ISO/IEC 26551.
— Processes and capabilities of methods and tools for domain design and application design are
provided as ISO/IEC 26552.
— Processes and capabilities of methods and tools for domain realization and application realization
are provided as ISO/IEC 26553.
— Processes and capabilities of methods and tools for domain verification and validation and
application verification and validation are provided in ISO/IEC 26554.
— Processes and capabilities of methods and tools for technical management are provided in this
International Standard.
© ISO/IEC 2015 – All rights reserved vii
---------------------- Page: 7 ----------------------
ISO/IEC 26555:2015(E)
— Processes and capabilities of methods and tools for organizational management are provided in this
International Standard.
viii © ISO/IEC 2015 – All rights reserved
---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARD ISO/IEC 26555:2015(E)
Software and systems engineering — Tools and methods
for product line technical management
1 Scope
This International Standard deals with the tools and methods of technical management for software
products, software services, software-intensive systems (including System Architecture and excluding
hardware) within a product line. The scope of this International Standard is as follows:
— Enable the users of this standard to holistically understand, adopt, and enact the processes, tools,
and methods for product line technical management. In addition, this International Standard helps
the users evaluate and select relevant tools and methods based on business and user-related criteria.
— Help product line engineers, developers, and tool vendors become informed about capabilities of tools
and methods that are required for supporting product line implementation from technical aspects.
— Provide product line-specific processes and capabilities of tools and methods in technical management.
This International Standard does not concern processes and capabilities of tools and methods for technical
management for a one-of-a-kind system but rather deals with those belonging to a family of systems.
NOTE System Architecture is a set of logical and physical principles used to achieve a mission within a given
environment. From System Architecture are derived components that can be subsystems, software products,
human-based products like crew or operators or hardware product like mechanical structures, electronic
boards, chemicals, etc. The scope of the International Standard spans from the system, to sub-systems, and
software products. Other types of components and especially those related to human beings and to hardware
parts are not within the scope of this International Standard.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
There are no normative references cited in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
application engineering process
processes for developing a member product in a product line
3.2
attached process
process definitions how each asset will be used in application
Note 1 to entry: The set of attached processes are those for orchestrating the assets together into a coherent
whole application.
3.3
binding time
moment of variability resolution
© ISO/IEC 2015 – All rights reserved 1
---------------------- Page: 9 ----------------------
ISO/IEC 26555:2015(E)
3.4
external variability
variability that is visible to customers
3.5
domain engineering process
processes for domain asset development
3.6
internal variability
variability defined from an engineer’s perspective and is not visible to customers
3.7
variability binding
act of determining the variant of the variation point defined in the variability model
3.8
variability documentation
detailed description of variability models for being used across the member products within a product
line
3.9
variability in space
variation that occurs at the same time with different shape
3.10
variability in time
variation that occurs at different times
3.11
variability mechanism
variability implementation methods in a product line for supporting assembly of domain assets
3.12
variability traceability
trace links established for a variability model both with domain assets and with application assets
where variants are bound.
4 Reference model for product line technical management
The technical management provides processes for addressing technical issues that arise during
implementation of a product line, deployment of processes, and development of assets and products
within a product line in balance with accomplishing the objectives of a product line, the given costs,
schedule, and so forth. Technical
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.