Taming Multi-Variability of Software Product Line Transformations

Strüber, Daniel; Peldzsus, Sven; Jürjens, Jan

doi:10.1007/978-3-319-89363-1_19

Cited by 11 publications

(4 citation statements)

References 35 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A VB rule could compactly represent the set of induced rules of an effect-oriented rule, albeit in a more complicated way, by explicitly defining a list of features and using them to annotate variable parts. An execution semantics of VB rules has been defined for single graphs [31] and sets of variants of graphs [30]. However, for VB rules, the concept of driving the instance selection by the availability of a match with certain properties has not been developed.…”

Section: Relations To Other Graph Transformation Approachesmentioning

confidence: 99%

Finding the Right Way to Rome: Effect-Oriented Graph Transformation

Kosiol

Strüber

Taentzer

et al. 2023

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Many applications of graph transformation require rules that change a graph without introducing new consistency violations. When designing such rules, it is natural to think about the desired outcome state, i.e., the desired effect, rather than the specific steps required to achieve it; these steps may vary depending on the specific rule-application context. Existing graph-transformation approaches either require a separate rule to be written for every possible application context or lack the ability to constrain the maximal change that a rule will create. We introduce effect-oriented graph transformation, shifting the semantics of a rule from specifying actions to representing the desired effect. A single effectoriented rule can encode a large number of induced classic rules. Which of the potential actions is executed depends on the application context; ultimately, all ways lead to Rome. If a graph element to be deleted (created) by a potential action is already absent (present), this action need not be performed because the desired outcome is already present. We formally define effect-oriented graph transformation, show how matches can be computed without explicitly enumerating all induced classic rules, and report on a prototypical implementation of effect-oriented graph transformation in Henshin.

show abstract

Section: Relations To Other Graph Transformation Approachesmentioning

confidence: 99%

Finding the Right Way to Rome: Effect-Oriented Graph Transformation

Kosiol

Strüber

Taentzer

et al. 2023

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…One example is support for the safe evolution of product line platforms [83], which could be extended to support systems in our intermediate governance levels. specifying our operators in the framework of software product line transformations [84], [85], [86] would make them amenable to conflict and dependency analysis [87], a versatile formal analysis with applications in the coordination of evolution processes. Many of the virtual platform's operators (e.g., those related to change propagation) lead to non-trivial changes of the codebase.…”

Section: Co N C L U S I O Nmentioning

confidence: 99%

Seamless Variability Management with the Virtual Platform

Mahmood

Strüber

Berger

et al. 2021

2021 IEEE/ACM 43rd International Conference on Software Engineering (ICSE)

View full text Add to dashboard Cite

Customization is a general trend in software engineering, demanding systems that support variable stakeholder requirements. Two opposing strategies are commonly used to create variants: software clone&own and software configuration with an integrated platform. Organizations often start with the former, which is cheap, agile, and supports quick innovation, but does not scale. The latter scales by establishing an integrated platform that shares software assets between variants, but requires high up-front investments or risky migration processes. So, could we have a method that allows an easy transition or even combine the benefits of both strategies? We propose a method and tool that supports a truly incremental development of variantrich systems, exploiting a spectrum between both opposing strategies. We design, formalize, and prototype the variabilitymanagement framework virtual platform. It bridges clone&own and platform-oriented development. Relying on programminglanguage-independent conceptual structures representing software assets, it offers operators for engineering and evolving a system, comprising: traditional, asset-oriented operators and novel, feature-oriented operators for incrementally adopting concepts of an integrated platform. The operators record meta-data that is exploited by other operators to support the transition. Among others, they eliminate expensive feature-location effort or the need to trace clones. Our evaluation simulates the evolution of a real-world, clone-based system, measuring its costs and benefits.

show abstract

“…Within model-driven software product line engineering [CAK + 05], some researchers have analysed techniques to manage variability across multiple models and artefacts [GW21,SPJ18]. In [GW21] the authors compare how different tools and approaches deal with the propagation of PCs across different models.…”

Section: Software Product Linesmentioning

confidence: 99%

Language Family Engineering with Product Lines of Multi-level Models

Lara

Guerra

2021

Form. Asp. Comput.

View full text Add to dashboard Cite

Modelling is an essential activity in software engineering. It typically involves two meta-levels: one includes meta-models that describe modelling languages, and the other contains models built by instantiating those meta-models. Multi-level modelling generalizes this approach by allowing models to span an arbitrary number of meta-levels. A scenario that profits from multi-level modelling is the definition of language families that can be specialized (e.g., for different domains) by successive refinements at subsequent meta-levels, hence promoting language reuse. This enables an open set of variability options given by all possible specializations of the language family. However, multi-level modelling lacks the ability to express closed variability regarding the availability of language primitives or the possibility to opt between alternative primitive realizations. This limits the reuse opportunities of a language family. To improve this situation, we propose a novel combination of product lines with multi-level modelling to cover both open and closed variability. Our proposal is backed by a formal theory that guarantees correctness, enables top-down and bottom-up language variability design, and is implemented atop the MetaDepth multi-level modelling tool.

show abstract

Taming Multi-Variability of Software Product Line Transformations

Cited by 11 publications

References 35 publications

Finding the Right Way to Rome: Effect-Oriented Graph Transformation

Finding the Right Way to Rome: Effect-Oriented Graph Transformation

Seamless Variability Management with the Virtual Platform

Language Family Engineering with Product Lines of Multi-level Models

Contact Info

Product

Resources

About