TY - GEN
T1 - On quantitative requirements for product lines
AU - Legay, Axel
AU - Perrouin, Gilles
N1 - Publisher Copyright:
© 2017 ACM.
Copyright:
Copyright 2017 Elsevier B.V., All rights reserved.
PY - 2017/2/1
Y1 - 2017/2/1
N2 - Software Product Line Engineering (SPLE) aims at developing a large number of software systems that share a common and managed set of features [5]. In the past years, it has been an active area in both research and industry. SPLE aims at improving productivity and reducing the time, effort, and cost required to develop a family of products (also called variants). The key point to achieve this goal is to manage the variability among various products of a Software Product Line (SPL). Variability is commonly expressed in terms of features, i.e., units of difference between software products. A product can thus be viewed as a set of features. Dependencies between features are typically represented in a Feature Model (FM) [11], whose ultimate purpose is to define which combinations of features (that is, which products) are valid [16]. Behavior of both the features and the core behavior (i.e., the behavior shared by all products in the line) may be represented by (variants of) state machines [3, 13].
AB - Software Product Line Engineering (SPLE) aims at developing a large number of software systems that share a common and managed set of features [5]. In the past years, it has been an active area in both research and industry. SPLE aims at improving productivity and reducing the time, effort, and cost required to develop a family of products (also called variants). The key point to achieve this goal is to manage the variability among various products of a Software Product Line (SPL). Variability is commonly expressed in terms of features, i.e., units of difference between software products. A product can thus be viewed as a set of features. Dependencies between features are typically represented in a Feature Model (FM) [11], whose ultimate purpose is to define which combinations of features (that is, which products) are valid [16]. Behavior of both the features and the core behavior (i.e., the behavior shared by all products in the line) may be represented by (variants of) state machines [3, 13].
UR - http://dl.acm.org/citation.cfm?id=3023970
UR - http://www.scopus.com/inward/record.url?scp=85014907062&partnerID=8YFLogxK
U2 - 10.1145/3023956.3023970
DO - 10.1145/3023956.3023970
M3 - Conference contribution
SN - 978-1-4503-2138-9
T3 - ACM International Conference Proceeding Series
SP - 2
EP - 4
BT - Proceedings - VaMoS 2017
A2 - Schaefer, Ina
A2 - ter Beek, Maurice H.
A2 - Siegmund, Norbert
PB - ACM Press
CY - Eindhoven
ER -