Integrated revision and variation control for evolving model-driven software product lines

Schwägerl, Felix; Westfechtel, Bernhard

doi:10.1007/s10270-019-00722-3

Cited by 20 publications

(7 citation statements)

References 45 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Superimposition of Models (SuperMod) (Schwȧgerl and Westfechtel 2016) is a tool for evolving model and implementation of SPLs in a conceptual framework for integrating revision and variation control of model-driven software projects (Schwägerl and Westfechtel 2019). Similar to VCSs, SuperMod is based on a workspace repository, where the user can store and edit the files of source code and modeling of all revisions and variants of an SPL.…”

Section: Related Workmentioning

confidence: 99%

Evolving software system families in space and time with feature revisions

et al. 2022

View full text Add to dashboard Cite

Software companies commonly develop and maintain variants of systems, with different feature combinations for different customers. Thus, they must cope with variability in space. Software companies further must cope with variability in time, when updating system variants by revising existing software features. Inevitably, variants evolve orthogonally along these two dimensions, resulting in challenges for software maintenance. Our work addresses this challenge with ECSEST (Extraction and Composition for Systems Evolving in Space and Time), an approach for locating feature revisions and composing variants with different feature revisions. We evaluated ECSEST using feature revisions and variants from six highly configurable open source systems. To assess the correctness of our approach, we compared the artifacts of input variants with the artifacts from the corresponding composed variants based on the implementation of the extracted features. The extracted traces allowed composing variants with 99-100% precision, as well as with 97-99% average recall. Regarding the composition of variants with new configurations, our approach can combine different feature revisions with 99% precision and recall on average. Additionally, our approach retrieves hints when composing new configurations, which are useful to find artifacts that may have to be added or removed for completing a product. The hints help to understand possible feature interactions or dependencies. The average time to locate feature revisions ranged from 25 to 250 seconds, whereas the average time for composing a variant was 18 seconds. Therefore, our experiments demonstrate that ECSEST is feasible and effective.

show abstract

Section: Related Workmentioning

confidence: 99%

Evolving software system families in space and time with feature revisions

et al. 2022

View full text Add to dashboard Cite

show abstract

“…Variation control systems such as ECCO (Linsbauer et al, 2017a(Linsbauer et al, , 2021 or SuperMod (Schwägerl & Westfechtel, 2019) address this problem by providing capabilities to uniformly handle revisions and variants. In particular, they allow to decompose a software system into finer-grained variable entities, i.e., features, to manage variability.…”

Section: Version Control Systemsmentioning

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

“…SPL evolution is a widely investigated area [9,23,32] with work on modeling and performing evolutionary modifications to an FM [22,40,54,59], its associated realization artifacts [28,50] or both [27,56,60]. A range of tools tackles selected areas of SPL evolution, e.g., DeltaEcore [62], ECCO [14], SuperMod [57,58], VaVe [4], SiPL [49], EvoFM [10,11], EvoPL [9,55] or DarwinSPL [41]. Recently, there have also been first attempts to harmonize modeling of SPL evolution by integrating [17] or abstracting from [3] various of the different underlying notations.…”

Section: Related Workmentioning

confidence: 99%

Consistency-preserving evolution planning on feature models

Hoff

Nieke

Seidl

et al. 2020

Proceedings of the 24th ACM Conference on Systems and Software Product Line: Volume a - Volume A

View full text Add to dashboard Cite

A software product line (SPL) enables large-scale reuse in a family of related software systems through configurable features. SPLs represent a long-term investment so that their ongoing evolution becomes paramount and requires careful planning. While existing approaches enable to create an evolution plan for an SPL on feature-model (FM) level, they assume the plan to be rigid and do not support retroactive changes. In this paper, we present a method that enables to create and retroactively adapt an FM evolution plan while preventing undesired impacts on its structural and logical consistency. This method is founded in structural operational semantics and linear temporal logic. We implement our method using rewriting logic, integrate it within an FM tool suite and perform an evaluation using a collection of existing FM evolution scenarios. CCS CONCEPTS• Software and its engineering → Software product lines; Software evolution; Software notations and tools.

show abstract

Integrated revision and variation control for evolving model-driven software product lines

Cited by 20 publications

References 45 publications

Evolving software system families in space and time with feature revisions

Evolving software system families in space and time with feature revisions

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

Consistency-preserving evolution planning on feature models

Contact Info

Product

Resources

About