Bottom-up adoption of software product lines

Martínez, Jabier; Ziadi, Tewfik; Bissyandé, Tegawendé F.; Klein, Jacques; Traon, Yves Le

doi:10.1145/2791060.2791086

Cited by 101 publications

(78 citation statements)

References 42 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This becomes specially challenging when final users need to combine some specifications to define hybrid formalisms. While several approaches have been proposed to reverse engineering software product lines from existing product variants [25,26,27], in this article we propose techniques to reverse engineering language product lines from existing DSL variants. In that sense, our work can be compared with approaches such as the ones presented by Kühn et al [15] and by Vacchi et al [28,29].…”

Section: Motivating Scenariomentioning

confidence: 99%

Reverse engineering language product lines from existing DSL variants

Méndez-Acuña

Galindo

Combemale

et al. 2017

Journal of Systems and Software

View full text Add to dashboard Cite

The use of domain-specific languages (DSLs) has become a successful technique to develop complex systems. In this context, an emerging phenomenon is the existence of DSL variants, which are different versions of a DSL adapted to specific purposes but that still share commonalities. In such a case, the challenge for language designers is to reuse, as much as possible, previously defined language constructs to narrow implementation from scratch. To overcome this challenge, recent research in software languages engineering introduced the the notion of language product lines. Similarly to software product lines, language product lines are often built from a set of existing DSL variants.In this article, we propose a reverse-engineering technique to ease-off such a development scenario. Our approach receives a set of DSL variants which are used to automatically recover a language modular design and to synthesize the corresponding variability models. The validation is performed in a project involving industrial partners that required three different variants of a DSL for finite state machines. This validation shows that our approach is able to correctly identify commonalities and variability.

show abstract

Section: Motivating Scenariomentioning

confidence: 99%

Reverse engineering language product lines from existing DSL variants

Méndez-Acuña

Galindo

Combemale

et al. 2017

Journal of Systems and Software

View full text Add to dashboard Cite

show abstract

“…Bottom-up approaches for SPL adoption are mainly composed of the following processes: Feature identification, feature location and re-engineering [21]. While feature identification is the process that takes as input a set of product variants and analyses them to discover and identify features, the feature location is the process of mapping features to their concrete implementation in the product variants.…”

Section: Feature Locationmentioning

confidence: 99%

“…Once the benchmark is constructed, the bottom part of Figure 4 illustrates how it can be used through BUT4Reuse [21] where feature location techniques can be integrated. The Eclipse adapter, which is responsible for the variants abstraction phase, will be followed by the launch of the targeted feature location techniques.…”

Section: Eclipse Feature Location Benchmarking Frameworkmentioning

confidence: 99%

“…We will refer to the identification of this initial set as block identification [21]. FCA groups elements that share common attributes.…”

Section: Background Algorithmsmentioning

confidence: 99%

“…We propose a standard and a realistic case study for feature location and an integrated benchmark using the packages of Eclipse releases, their features and their associated plugins. We also propose a full implementation to support benchmarking within Bottom-Up Technologies for Reuse (BUT4Reuse) [21] that is an opensource, generic and extensible framework for bottom-up approaches which allows a quick integration of feature location techniques.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Feature Location Benchmark for Software Families Using Eclipse Community Releases

Martínez¹,

Ziadi²,

Papadakis³

et al. 2016

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. It is common belief that high impact research in software reuse requires assessment in realistic, non-trivial, comparable, and reproducible settings. However, real software artefacts and common representations are usually unavailable. Also, establishing a representative ground truth is a challenging and debatable subject. Feature location in the context of software families is a research field that is becoming more mature with a high proliferation of techniques. We present EFLBench, a benchmark and a framework to provide a common ground for this field. EFLBench leverages the efforts made by the Eclipse Community which provides real feature-based family artefacts and their implementations. Eclipse is an active and non-trivial project and thus, it establishes an unbiased ground truth. EFLBench is publicly available and supports all tasks for feature location techniques integration, benchmark construction and benchmark usage. We demonstrate its usage and its simplicity and reproducibility by comparing four techniques.

show abstract

PAxSPL: A feature retrieval process for software product line reengineering

et al. 2019

View full text Add to dashboard Cite

Software product lines (SPLs) are a well-known solution to systematically create reusable software products. Among the approaches to create an SPL, the extractive approach is usually used when the organization already has a set of similar systems. These systems are analyzed to extract, categorize, and group their common and variant features throughout the SPL reengineering process. As there are different scenario variables, such as available artifacts and team experience, the activities and techniques used to perform these tasks may change. This may increase the effort and decrease the quality of retrieved features when users with low experience in SPL reengineering perform such tasks. However, there is a lack of a process supporting these tasks considering different scenarios. Therefore, we specify the Prepare, Assemble, and Execute Process for SPL Reengineering (PAxSPL), a process that provides support to prepare, assemble, and execute feature retrieval throughout the analysis of documentation and team experience. To initially evaluate PAxSPL, we conducted and reported an exploratory case study in a real development environment. The results indicated that our proposal helps in the assembly of a feature retrieval process according to user needs. Results were important to identify points for improvement in PAxSPL. We also could use the information gathered to improve the guidelines and provide this information to be used as basis of comparison for future users. KEYWORDS feature model, feature retrieval, software product line, software product line reengineering, software reengineering, software reuse 1278

show abstract

Bottom-up adoption of software product lines

Cited by 101 publications

References 42 publications

Reverse engineering language product lines from existing DSL variants

Reverse engineering language product lines from existing DSL variants

Feature Location Benchmark for Software Families Using Eclipse Community Releases

PAxSPL: A feature retrieval process for software product line reengineering

Contact Info

Product

Resources

About