2014 IEEE International Conference on Software Maintenance and Evolution 2014
DOI: 10.1109/icsme.2014.67
|View full text |Cite
|
Sign up to set email alerts
|

Recovering Feature-to-Code Mappings in Mixed-Variability Software Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

2015
2015
2024
2024

Publication Types

Select...
5
2
1

Relationship

5
3

Authors

Journals

citations
Cited by 20 publications
(9 citation statements)
references
References 10 publications
0
9
0
Order By: Relevance
“…ECCO provides hints, for instance, to indicate that the implementation of some new modules cannot be fully automated [12,13,25]. Based on the input received manually, ECCO updates and refines its traces.…”
Section: The Human In the Loopmentioning
confidence: 99%
See 1 more Smart Citation
“…ECCO provides hints, for instance, to indicate that the implementation of some new modules cannot be fully automated [12,13,25]. Based on the input received manually, ECCO updates and refines its traces.…”
Section: The Human In the Loopmentioning
confidence: 99%
“…We now describe this form of sensitivity analysis based on our traceability work [27], which is part of our Extraction and Composition for Clone-and-Own (ECCO) approach [12,13,25]. ECCO works under two simple premises.…”
Section: Feature-level Functional Sensitivity Analysismentioning
confidence: 99%
“…Other employed terminology is less generic and they specifically refers to the concrete artefact types that they are dealing with. Linsbauer et al [62] and Salman et al [34] refer to blocks as potential feature-to-code mappings or traces. AL-msie'deen et al call them object-oriented building elements sets [63] and atomic blocks [64].…”
Section: Related Workmentioning
confidence: 99%
“…Our previous work presented a framework and workflow that combines extraction and composition support for clone-andown [15]. Also, we have applied our extraction work to a mixed-variability system from industry [24]. In this type of system, variability is realized in multiple artifact types and with several variability techniques, for example at compile time using custom configuration tools or preprocessors, or during runtime via configuration files.…”
Section: Related Workmentioning
confidence: 99%
“…Unfortunately, while every SPL has inherent variability, the information about it is often not explicitly available as many SPLs are the result of ad hoc development. Variability information can be spread out across several places and implemented using various different techniques like preprocessors, configuration files, runtime constructs, and hidden in custom product line configuration tools [24].…”
Section: Introductionmentioning
confidence: 99%