Bridging the Gap Between Clone-and-Own and Software Product Lines

Kehrer, Timo; Thüm, Thomas; SchultheiB, Alexander; Bittner, Paul Maximilian

doi:10.1109/icse-nier52604.2021.00013

Cited by 21 publications

(18 citation statements)

References 46 publications

(77 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Clone-and-own research tries to address the challenges of cloneand-own and different approaches have been proposed over the years. The approaches range from the systematic support of cloneand-own development (with the aim of reducing maintenance costs) [8,11,19,24,31,34,48] to techniques that support the migration of a set of variants into an integrated platform (with the aim of eliminating duplicated code) [11,21,39]. To evaluate these approaches, suitable benchmarks are required.…”

Section: Multi-variant Software Systemsmentioning

confidence: 99%

“…Given these practical experiences, a more recent line of research focuses at better supporting clone-and-own [8,11,19,21,24,31,34,37,39,48]. Clone-and-own research focuses on developing methods and tools with the ultimate goal of either migrating a clone-andown project to a software product line, or systematically supporting clone-and-own development through better automation.…”

Section: Introductionmentioning

confidence: 99%

“…variablity extraction) serves as a preparatory step for migration, while tracing features to development artifacts [2,8,19] (aka. feature trace recording) serves as a foundation for automatically synchronizing cloned variants [24].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Simulating the Evolution of Clone-and-Own Projects with VEVOS

Schultheiß

Bittner

El-Sharkawy

et al. 2022

The International Conference on Evaluation and Assessment in Software Engineering 2022

Self Cite

View full text Add to dashboard Cite

In clone-and-own development, new variants of a software system are typically created by manually copying and adapting an existing variant. This approach is flexible but suffers from various challenges such as high maintenance cost in the long term. While researchers started to address the challenges of clone-and-own, there is yet little empirical evidence on the efficiency and effectiveness of clone-andown research. The main reason for this is the lack of appropriate benchmarks, which need to expose a multitude of different data and meta-data serving as input and ground truth for experimental evaluations. We present VEVOS, a benchmark generation framework that picks up these requirements and, given the version history of a software product line, enables the simulation of the evolution of cloned variants, and provides meta-data serving as ground truth. CCS CONCEPTS• Software and its engineering → Software configuration management and version control systems.

show abstract

Section: Multi-variant Software Systemsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Simulating the Evolution of Clone-and-Own Projects with VEVOS

Schultheiß

Bittner

El-Sharkawy

et al. 2022

The International Conference on Evaluation and Assessment in Software Engineering 2022

Self Cite

View full text Add to dashboard Cite

show abstract

“…), and conflicting features (interact?). The Vari-antSync project (Pfofe et al, 2016;Kehrer et al, 2021) intends to keep clones separate instead of consolidating them into a product line. It aims to support the synchronization of clones based on features.…”

Section: Related Workmentioning

confidence: 99%

Feature-oriented clone and pull operations for distributed development and evolution

et al. 2022

View full text Add to dashboard Cite

Software companies frequently customize and extend product lines in multiple projects concurrently to quickly deliver solutions to customers. Engineers use a distributed and feature-oriented development process, commonly supported by version control systems to track implementation-level changes. For instance, feature branches are widely used to add new or modify existing features. However, when merging back features to the product line, the information about feature-to-code mappings is usually lost. Furthermore, the granularity of merging is limited to branches, making it hard to extract and merge selected individual features from one product to another. This paper thus presents feature-oriented clone and pull operations for distributed development, which are implemented in the FORCE2 platform. Our evaluation uses variants of the ArgoUML product line to investigate the correctness and performance of our approach. The results show that the feature-oriented operations work with high precision and recall for different cases of feature interactions, also when feature implementations are scattered across many locations in the source code. The performance measurements demonstrate that the operations can be integrated in the typical workflows of engineers.

show abstract

“…We have extended Feature models in the Feature Oriented Reuse Method with Business Component Semantics (FORM/BCS) [12,13,14,15,16,17]. Each product in the product line is derived from a selection of a valid combination of features [18] -a process known as product configuration [19,20]. .…”

Section: Introductionmentioning

confidence: 99%

Evolution in Software Product Lines: Defining and Modelling for Management

Ngoumou¹,

Ndjodo²

2022

J. Engg. Res. & Sci.

View full text Add to dashboard Cite

Evolution in Software Product Line (SPL) is claimed when there are changes in the requirements, product structure or the technology being used. Currently, many different approaches have been proposed on how to manage SPL assets and some also address how evolution affects these assets. However, the usefulness, effectiveness and applicability of these approaches are unclear, as there is no clear consensus on what an asset is. In this work, we plan to reduce complexity in SPL evolution management. For this goal, the difficulty is defining and modeling SPL evolution and we expect to propose a flexible way to manage it. However, a large variety of artifacts is considered in SPL evolution studies, but feature models are by far the most researched ones. Feature models are widely used to represent SPLs and have been greatly developed in the Feature-Oriented Reuse Method (FORM). Consequently, in our previous works, after observed that this method has a loose structure since it does not provide guidance to reuse and rigorously analyze its assets, we have extended FORM to FORM/BCS (the Feature Oriented Reuse Method with Business Component Semantics) by enveloping its assets among which feature models with business component semantics. The contribution and the novelty of this work is that, by highlighting formally the concept of software asset and revisiting feature business components, to add new information when analyzing a domain, such as clashing actions. conflicts or undesired interactions between existing features in a product line and new features due to evolution of the product line can be manage in a flexible way.

show abstract

Bridging the Gap Between Clone-and-Own and Software Product Lines

Cited by 21 publications

References 46 publications

Simulating the Evolution of Clone-and-Own Projects with VEVOS

Simulating the Evolution of Clone-and-Own Projects with VEVOS

Feature-oriented clone and pull operations for distributed development and evolution

Evolution in Software Product Lines: Defining and Modelling for Management

Contact Info

Product

Resources

About