ISO/IEC 26580:2021 ソフトウェアおよびシステムエンジニアリング—ソフトウェアおよびシステム製品ラインエンジニアリングへの機能ベースのアプローチのための方法およびツール | ページ 6

3.1

bill-of-features

specification for a member product (3.8) in the product line (3.16) , rendered in terms of the specific features (3.4) from the feature catalogue (3.5) that are chosen for that member product

3.2

bill-of-features portfolio

collection comprising the bill-of-features (3.1) for each member product (3.8) in a product line (3.16)

3.3

domain supersets

collection comprising the feature catalogue (3.5) and shared asset supersets (3.18)

3.4

feature

characteristic of a member product (3.8) in a product line (3.16) that distinguishes it from other member products in the product line

Note 1 to entry: Features can a) express the customer-visible or end-user-visible variability among the member products in a product line, or b) distinguish implementation variability not directly visible to a customer or end user except through non-functional differences such as price, performance, noise, weight, energy and more.

Note 2 to entry: In feature-based PLE, features express differences among member products. A capability or other characteristic common to all member products in the product line is not modelled as a feature.

Note 3 to entry: See Annex A for the definition of this term in ISO/IEC 26550.

3.5

feature catalogue

model of the collection of all the feature (3.4) options and feature constraints (3.6) available across the entire product line (3.16)

3.6

feature constraint

formal relationship between two or more features (3.4) that is necessarily satisfied for all member products (3.8)

3.7

feature language

syntax and semantics for the formal representation, structural taxonomy, and relationships among the concepts and constructs in the feature catalogue (3.5) , bill-of-features portfolio (3.2) , and shared asset superset (3.18) variation points (3.20)

3.8

member product

product belonging to the product line (3.16)

[SOURCE: ISO/IEC 26550:2015, 3.15, modified — The preferred term"application" has been removed.]

3.9

mutually exclusive

alternatives from which at most one is selected

3.10

mutually inclusive

alternatives from which zero or more are selected

3.11

PLE factory

technological, organizational, and business infrastructure and processes to support a PLE factory configurator (3.12) producing product asset instances (3.14) from shared asset supersets (3.18) based on a bill-of-features (3.1) for a member product (3.8)

3.12

PLE factory configurator

automated mechanism that produces assets for a specific member product (3.8) by processing the bill-of-features (3.1) for that member product, and exercising the shared assets’ (3.17) variation points (3.20) in light of the feature (3.4) selections made in that bill-of-features

3.13

PLE factory development environment

toolset for creating, organizing, assembling, and maintaining a collection of elements in a feature catalogue (3.5) , bill-of-features portfolio (3.2) , shared asset supersets (3.18) , and a hierarchy of a product line (3.16) of product lines

3.14

product asset instance

instantiation of a shared asset (3.17) specific to a member product (3.8) , automatically produced by the PLE factory configurator (3.12) , corresponding to a bill-of-features (3.1) for that member product

Note 1 to entry: A product asset instance is analogous to an application asset (ISO/IEC 26550) with the proviso that it is produced by the PLE factory configurator.

3.15

product instances

collection comprising the bill-of-features portfolio (3.2) and product asset instances (3.14)

3.16

product line

family of similar products with variations in features (3.4)

Note 1 to entry: See Annex A for the definition of this term in ISO/IEC 26550.

3.17

shared asset

software and systems engineering lifecycle digital artefacts that compose a part of a delivered member product (3.8) or support the engineering process to create and maintain a member product

Note 1 to entry: A shared asset is analogous to a domain asset (ISO/IEC 26550).

Note 2 to entry: Typical shared assets are requirements, design specifications or models for mechanical, electrical, and software, source code, build files or scripts, test plans and test cases, user documentation, repair manuals and installation guides, project budgets, schedules, and work plans, product calibration and configuration files, mechanical bills-of-materials, electrical circuit board and wiring harness designs, engineering management plans, engineering drawings, training plans and training materials, skill set requirements, manufacturing plans and instructions, and shipping manifests.

3.18

shared asset superset

representation of a shared asset (3.17) that includes all content needed by any of the member products (3.8)

3.19

variant

alternative that can be used to realize a particular variation point (3.20)

[SOURCE: ISO/IEC 26550:2015, 3.28, modified — the word"one" at the beginning of the definition has been removed;"may" has been changed to"can";"particular variation points" has been changed to"a particular variation point"; note 1 to entry has been removed.]

3.20

variation point

identification of a specific piece of shared asset superset (3.18) content and a mapping from feature (3.4) selection(s) to the form of that content that appears in a product asset instance (3.14)

Note 1 to entry: In this document, all features express characteristics that differ among member products (3.8) , which according to ISO/IEC 26550 would also make every feature a variation point. To avoid this redundancy, this document does not call out features as variation points.

Note 2 to entry: See Annex A for the definition of this term in ISO/IEC 26550. The definition in this document is more specific to feature-based PLE and the PLE factory configurator (3.12) approach of producing product asset instances from shared asset supersets.