2015
DOI: 10.1016/j.infsof.2015.02.002
|View full text |Cite
|
Sign up to set email alerts
|

Supporting distributed product configuration by integrating heterogeneous variability modeling approaches

Abstract: Context: In industrial settings products are developed by more than one organization. Software vendors and suppliers commonly typically maintain their own product lines, which contribute to a larger (multi) product line or software ecosystem. It is unrealistic to assume that the participating organizations will agree on using a specific variability modeling technique-they will rather use different approaches and tools to manage the variability of their systems. Objective: We aim to support product configuratio… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
20
0
1

Year Published

2016
2016
2021
2021

Publication Types

Select...
5
1

Relationship

4
2

Authors

Journals

citations
Cited by 39 publications
(22 citation statements)
references
References 55 publications
1
20
0
1
Order By: Relevance
“…Modelers need to explicitly define dependencies between feature models of different purpose that exist at different levels (requirement 3). This confirms the need for existing approaches for modeling dependencies between different modeling spaces [23, 37], between models of one space [31, 38] or between different levels of abstraction [62, 68]. Finally, our experiences confirm the need for mapping features to code (requirement 4).…”
Section: Exploratory Case Study: Feature Modeling Of Kemotion and Kepsupporting
confidence: 77%
“…Modelers need to explicitly define dependencies between feature models of different purpose that exist at different levels (requirement 3). This confirms the need for existing approaches for modeling dependencies between different modeling spaces [23, 37], between models of one space [31, 38] or between different levels of abstraction [62, 68]. Finally, our experiences confirm the need for mapping features to code (requirement 4).…”
Section: Exploratory Case Study: Feature Modeling Of Kemotion and Kepsupporting
confidence: 77%
“…Nowadays, the variability description of variability-intensive systems is getting more complex. This is done by introducing non-boolean information [145], and by using several variability models [118] in a multi-layer fashion. However, we found no proposals to reverse engineer the existing variability information of variability-intensive systems with more than one variability model or non-boolean information.…”
Section: Research Opportunitiesmentioning
confidence: 99%
“…Product configuration and derivation [35,37,42,46,47,49,50,53,55,56,57,58,59,60,65,66,68,72,74,75,76,77,80,82,83,89,93,95,98,99,100,103,105,106,107,108,109,110,112,114,116,118,119,120,123,125,126,128,133,134,135,136,…”
Section: Variability Contextmentioning
confidence: 99%
See 1 more Smart Citation
“…Galindo et al [10] present an approach to ease the integration of variability models specified using different modeling styles, variability languages, and tools to perform configuration. They introduce the Invar approach to provide the user with a configuration tool that hides the different models, their semantics, and internal representation.…”
Section: Related Workmentioning
confidence: 99%