2014 Second IEEE Working Conference on Software Visualization 2014
DOI: 10.1109/vissoft.2014.18
|View full text |Cite
|
Sign up to set email alerts
|

Abstract: International audience—Software Product Line Engineering is a mature approach enabling the derivation of product variants by assem-bling reusable assets. In this context, domain experts widely use Feature Models as the most accepted formalism for capturing commonality and variability in terms of features. Feature Models also describe the constraints in feature combinations. In industrial settings, domain experts often deal with Software Product Lines with high numbers of features and constraints. Furthermore, … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
21
0

Year Published

2015
2015
2022
2022

Publication Types

Select...
4
2
2

Relationship

2
6

Authors

Journals

citations
Cited by 28 publications
(21 citation statements)
references
References 26 publications
0
21
0
Order By: Relevance
“…Feature blueprints are feature models where the size of the feature box depends on the number of internal and external constraints found in a feature and use colors to distinguish optional from mandatory features. Feature relation graphs depict features and their relations as colored concentric circles whose color, width, and size depend on the properties of the relations . Feature survival charts display one bar for each feature and use colors to describe its evolution, for example, when a feature is in the scope of a SPL and when it was deprecated .…”
Section: Resultsmentioning
confidence: 99%
See 1 more Smart Citation
“…Feature blueprints are feature models where the size of the feature box depends on the number of internal and external constraints found in a feature and use colors to distinguish optional from mandatory features. Feature relation graphs depict features and their relations as colored concentric circles whose color, width, and size depend on the properties of the relations . Feature survival charts display one bar for each feature and use colors to describe its evolution, for example, when a feature is in the scope of a SPL and when it was deprecated .…”
Section: Resultsmentioning
confidence: 99%
“…Concept lattices, a more specialized form of graphs, were used in 2 primary sources. Concept lattices 76,77 Bar diagrams 81,94 Colored code/model elements 64,65 Feature histograms 83 Tables/matrices 88 Bubble chart 84 Levelized structure map 90 Bubble map 72 Heat map 72 Tree map 72 Grid 72 Feature blueprints 70 Feature relation graphs 73 Component model annotations 97 Flow maps 78 3D cone trees 98 Feature survival chart 68 3D color spheres 100 Logical gates 74 Nested colored circles 66 Bar diagrams and using color to distinguish elements in source code and models had also 2 primary sources. There were also 17 other visualization techniques with just a single primary source.…”
Section: Rq1 Software Product Line Engineering Activitiesmentioning
confidence: 99%
“…Thus, future research is needed in this field to derive products with a higher satisfaction degree for a set of different decision makers. As an example, (Martinez et al, 2014) present a visualisation paradigm called FRoGs (Feature Relations Graphs). This solution supports different decision makers to obtain a better understanding of feature constraints during the product configuration process.…”
Section: Open Challengesmentioning
confidence: 99%
“…Feature Relations Graphs (FRoGs): FRoGs is an interactive visualisation paradigm to help domain experts and stakeholders to manage the challenges in maintaining the constraints among features [9]. The objective is to obtain a better understanding of feature constraints and potentially refine the existing feature model by uncovering and formalizing missing constraints (i.e., feature constraints discovery).…”
Section: Validation Studiesmentioning
confidence: 99%