Safe Evolution Patterns for Software Product Lines

Nicolas Dintzner*

*Corresponding author for this work

Research output: Chapter in Book/Conference proceedings/Edited volumeConference contributionScientificpeer-review

1 Citation (Scopus)

Abstract

Despite a global recognition of the problem, and massive investment from researchers and practitioners, the evolution of complex software systems is still a major challenge for today's architects and developers. In the context of product lines, or highly configurable systems, variability in the implementation and design makes many of the pre-existing challenges even more difficult to tackle.Many approaches and tools have been designed, but developers still miss the tools and methods enabling safe evolution of complex, variable systems.In this paper, we present our research plans toward this goal: making the evolution of software product lines safer.We show, by use of two concrete examples of changes that occurred in Linux, that simple heuristics can be applied to facilitate change comprehension and avoid common mistakes, without relying on heavy tooling.Based on those observations, we present the steps we intend to take to build a framework to regroup and classify changes, run simple checks, and eventually increase the quality of code deliveries affecting the variability model, mapping and implementation of software product lines.

Original languageEnglish
Title of host publicationProceedings - 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering, ICSE 2015
PublisherIEEE
Pages875-878
Number of pages4
Volume2
ISBN (Electronic)978-1-4799-1934-5
DOIs
Publication statusPublished - 2015
EventICSE 2015: 37th IEEE/ACM International Conference on Software Engineering - Florence, Italy
Duration: 16 May 201524 May 2015
Conference number: 37

Conference

ConferenceICSE 2015
Country/TerritoryItaly
CityFlorence
Period16/05/1524/05/15

Keywords

  • Evolution
  • Product line
  • Variability

Fingerprint

Dive into the research topics of 'Safe Evolution Patterns for Software Product Lines'. Together they form a unique fingerprint.

Cite this