Morpheus: Variability-Aware Refactoring in the Wild

Liebig, Jörg; Apel, Sven; Janker, Andreas; Garbe, Florian; Oster, Sebastian

doi:10.1109/icse.2015.57

Cited by 17 publications

(7 citation statements)

References 64 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There are some approaches that address such refactorings and aim to ease or partly automate this task. For instance, Liebig et al introduced MORPHEUS , a tool for automated refactorings of C code that can handle annotations. Kästner et al described concepts to automate extractions.…”

Section: Practical Applicationmentioning

confidence: 99%

Composing annotations without regret? Practical experiences using FeatureC

Krüger

Pinnecke

Kenner³

et al. 2017

Softw Pract Exp

View full text Add to dashboard Cite

Software product lines enable developers to derive similar products from a common code base. Existing implementation techniques can be categorized as composition-based and annotation-based approaches, with both approaches promising complementary benefits. However, annotation-based approaches are commonly used in practice despite composition allowing physical separation of features and, thus, improving traceability and maintenance. A main hindrance to migrate annotated systems toward a composition-based product line is the challenging and time-consuming transformation task. For a company, it is difficult to predict the corresponding costs, and a successful outcome is uncertain. To overcome such problems, a solution proposed by the previous work is to use a hybrid approach, utilizing composition and annotation simultaneously. Based on this idea, we introduce a stepwise migration process from annotation-based toward composition-based approaches to lower the adoption barrier of composition. This process itself is independent of used implementation techniques and enables developers to incrementally migrate toward composition. We support our approach with detailed examples by partially migrating a real-world system.In detail, we describe the following: (1) our migration process, (2) its application on a real-world system, and (3) discuss practical challenges we face. We implemented the proposed approach and show that appropriate tool support helps to migrate toward composition-based product lines. Based on the case study, we show that the hybrid product lines work correctly and can compete with the performance of the original annotated system. However, the results also illustrate open issues that have to be solved to apply such migrations in practice.

show abstract

Section: Practical Applicationmentioning

confidence: 99%

Composing annotations without regret? Practical experiences using FeatureC

Krüger

Pinnecke

Kenner³

et al. 2017

Softw Pract Exp

View full text Add to dashboard Cite

show abstract

“…Furthermore, there is a high probability to replace the nesting with guard clauses. This procedure includes a sequential on the non-nested if statement, making it easier to read [8].…”

Section: Discussionmentioning

confidence: 99%

Analysis Refactoring with Tools

Othman¹

2018

Adv. sci. technol. eng. syst. j.

View full text Add to dashboard Cite

The drive for this report is to inaugurate the innumerable techniques espoused by the refactoring tools in coding development. The software product is a very complex and timeconsuming process of development. Difficulty understanding and maintaining poorly designed software systems Software maintenance can take up to 50% of total development costs for software production. As a modus operando, the refactoring tools purpose ultimately to amend the basis codes into an easier and more comprehensible way. Moreover, refactoring succors to check the trifle of the coding procedure. This is apparent through having deliberation on the program catalog, precision and the use of the deconstruct trees. Refactoring tools are convenient for innumerable observes done by the human beings. Software refactoring has a direct impact on reducing the cost of software maintenance by changing the internal structure of the code without changing its external behavior. So the time taken to process as well as doing a critical analysis of complex codes is reduced. This report proposes to have a precarious scrutiny on the various use including the pluses of using refactoring tools.

show abstract

“…Others focus on evolving software platforms. Liebig et al [80] present variability-aware sound refactorings (rename identifier, extract function, inline function) for evolving a platform by preserving the variants. Rabiser et al [81] present an approach for managing clones at product, component, and feature, and define 5 consistency levels to monitor co-evolving clones.…”

Section: Re L a T E D Wo R Kmentioning

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

Morpheus: Variability-Aware Refactoring in the Wild

Cited by 17 publications

References 64 publications

Composing annotations without regret? Practical experiences using FeatureC

Composing annotations without regret? Practical experiences using FeatureC

Analysis Refactoring with Tools

Seamless Variability Management with the Virtual Platform

Contact Info

Product

Resources

About