Supporting the Grow-and-Prune Model in Software Product Lines Evolution Using Clone Detection

Mende, Thilo; Beckwermert, Felix; Koschke, Rainer; Meier, G.

doi:10.1109/csmr.2008.4493311

Cited by 56 publications

(35 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Some existing work deals with implementation issues for evolving product lines (Loughran and Rashid, 2004;Deng et al, 2005) using, e.g., aspect-oriented programming. Mende et al (2008) describe tool-support for the evolution of product lines based on the "growand-prune" model, i.e., they support refactoring code that has been created by copy & paste and which can potentially be propagated to product line level. Svahnberg and Bosch (1999) report on experiences regarding the evolution of products, components, and software architecture.…”

Section: Evolution Of Product Linesmentioning

confidence: 99%

Model-driven support for product line evolution on feature level

Pleuss

Botterweck

Dhungana

et al. 2012

Journal of Systems and Software

View full text Add to dashboard Cite

Please cite this article in press as: Pleuss, A., et al., Model-driven support for product line evolution on feature level. J. Syst. Software (2011), doi:10.1016/j.jss.2011.08.008 Software Product Lines (SPL) are an engineering technique to efficiently derive a set of similar products from a set of shared assets. In particular in conjunction with model-driven engineering, SPL engineering promises high productivity benefits. There is however, a lack of support for systematic management of SPL evolution, which is an important success factor as a product line often represents a long term investment. In this article, we present a model-driven approach for managing SPL evolution on feature level. ARTICLE IN PRESSTo reduce complexity we use model fragments to cluster related elements. The relationships between these fragments are specified using feature model concepts itself leading to a specific kind of feature model called EvoFM. A configuration of EvoFM represents an evolution step and can be transformed to a concrete instance of the product line (i.e., a feature model for the corresponding point in time). Similarly, automatic transformations allow the derivation of an EvoFM from a given set of feature models. This enables retrospective analysis of historic evolution and serves as a starting point for introduction of EvoFM, e.g., to plan future evolution steps.

show abstract

Section: Evolution Of Product Linesmentioning

confidence: 99%

Model-driven support for product line evolution on feature level

Pleuss

Botterweck

Dhungana

et al. 2012

Journal of Systems and Software

View full text Add to dashboard Cite

show abstract

“…Several research works [32], [4], [33], [5] indicate the existence of industrial product lines that are realized by cloning instead of using variability management techniques. Faust and Verhoef [4] further describe "Software Mitosis"-the uncontrolled adoption of systems in a global organization, where successful systems are duplicated and modified by local sub-organizations.…”

Section: Related Workmentioning

confidence: 99%

An Exploratory Study of Cloning in Industrial Software Product Lines

Dubinsky

Rubin

Berger

et al. 2013

2013 17th European Conference on Software Maintenance and Reengineering

226

103

View full text Add to dashboard Cite

Abstract-Many companies develop software product linescollections of similar products-by cloning and adapting artifacts of existing product variants. Transforming such cloned product variants into a "single-copy" software product line representation is considered an important software re-engineering activity, as reflected in numerous tools and methodologies available. However, development practices of companies that use cloning to implement product lines have not been systematically studied. This lack of empirical knowledge threatens the validity and applicability of approaches supporting the transformation, and impedes adoption of advanced solutions for systematic software reuse. It also hinders the attempts to improve the solutions themselves.We address this gap with an empirical study conducted to investigate the cloning culture in six industrial software product lines realized via code cloning. Our study investigates the processes, and the perceived advantages and disadvantages of the approach. We observe that cloning, while widely discouraged in literature, is still perceived as a favorable and natural reuse approach by the majority of practitioners in the studied companies. This is mainly due to its benefits such as simplicity, availability and independence of developers. Based on our observations, we outline issues preventing the adoption of systematic software reuse approaches, and identify future research directions.

show abstract

“…It may be used to detect aspects [16,17], reduce the memory footprint of programs for small devices [20], detect plagiarism [82,76,29,69,38,68,36], and to compare versions or variants [86,99,34,35,88,96,97,9,31,73]. I expect that clone detection will make many more contributions in related fields and in turn will learn from these other fields.…”

Section: Discussionmentioning

confidence: 99%