• Keine Ergebnisse gefunden

Analysis Strategies for Software Product Lines: A Classification and Survey

N/A
N/A
Protected

Academic year: 2022

Aktie "Analysis Strategies for Software Product Lines: A Classification and Survey"

Copied!
1
0
0

Wird geladen.... (Jetzt Volltext ansehen)

Volltext

(1)

Analysis Strategies for Software Product Lines:

A Classification and Survey

Thomas Th¨um,1Sven Apel,2Christian K¨astner,3Ina Schaefer,4and Gunter Saake1

1University of Magdeburg, Germany

2University of Passau, Germany

3Carnegie Mellon University, USA

4Technische Universit¨at Braunschweig, Germany

Abstract: Software-product-line engineering enables the efficient development of similar software products. Instead of developing each product from scratch, products are generated from common artifacts. However, the product generation is a challenge for the analysis of correctness properties. Applying traditional analysis techniques, such as type checking and model checking, to each product involves redundant effort and is often not feasible to the combinatorial explosion of products. Approaches to scale analysis techniques to product lines have been presented in unrelated research areas with a different terminology each. We propose a classification of analysis strate- gies and classify a corpus of more than 100 approaches. Based on our insights, we develop a research agenda to guide research on product-line analyses.

This talk is based on our recent ACM Computing Surveys article [TAK+14].

References

[TAK+14] Thomas Th¨um, Sven Apel, Christian K¨astner, Ina Schaefer, and Gunter Saake. A Classi- fication and Survey of Analysis Strategies for Software Product Lines.ACM Computing Surveys, 47(1):6:1–6:45, June 2014.

Referenzen

ÄHNLICHE DOKUMENTE

Software product lines, tool support, sampling, testing, type checking, static analysis, model checking, theorem proving, non-functional properties, code

Our empirical results point out to the fact that (a) the backtracking algorithm running from preprocessed instances was always faster than the same algorithm running from the

We identify challenges when developing multi product lines and propose interfaces for different levels of abstraction ranging from variability modeling to functional and

An analysis of a software product line is called feature-based, if it (a) operates only on domain artifacts and (b) software artifacts belonging to a feature are analyzed in

The underlying assumption of this survey is that every software analysis known from single-system engineering, such as type check- ing, static analysis, model checking, and

Given our tool support in FeatureIDE it is possible to implement feature modules, specify feature-oriented con- tracts, and verify them using theorem proving and model checking by

The basic problem: the system state can quickly get huge, and the basic complexity of the problem is horrendous, leading to so-called state explosion. But the use of abstraction

Example projects would be a Java application, that consists of a tree of classes, one of which is the main class of the executable; or a feature project, which is a project