To merge or not to merge: Managing software product families

0Citations
Citations of this article
5Readers
Mendeley users who have this article in their library.
Get full text

Abstract

A large number of companies, especially in the automotive, electronics, aerospace and defense domains, develop a portfolio of closely related software products designed to satisfy similar, yet not identical, needs of their customers (a.k.a. a software product line). Even though numerous software product line engineering approaches promise to ease the product line development and maintenance effort, in practice, the adoption of such approaches is still limited. Instead, products are often established ad-hoc, e.g., by copying existing variants and modifying them to fit the requirements of a new customer or market segment. In this paper, we discuss reasons leading organizations to employ cloning to realize their product lines. We then present two strategies for efficient management of cloned product variants: (1) the unification of the variants into single-copy representations promoted by product line engineering methods and (2) the construction of a management infrastructure on top of existing cloned variants, to mitigate the shortcomings of cloning while leveraging its benefits. We outline existing work that contributes to the implementation of these two strategies and identify opportunities for future research.

Cite

CITATION STYLE

APA

Rubin, J. (2017). To merge or not to merge: Managing software product families. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 10223 LNCS, pp. 73–97). Springer Verlag. https://doi.org/10.1007/978-3-319-60074-1_4

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free