Towards systematic ensuring well-formedness of software product lines

Heidenreich, Florian

doi:10.1145/1629716.1629730

Cited by 29 publications

(29 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The rules of these type systems contain reachability checks (basically implications) making sure, among others, that every program element is defined in all products where it is referenced. Variability-aware type systems have been developed for composition-based implementation [Thaker et al 2007;Huang et al 2007;Kim et al 2008;Kuhlemann et al 2009;Delaware et al 2009;Apel et al 2010a;Apel et al 2010c;Kolesnikov et al 2013], composition-based design [Alférez et al 2011], annotation-based implementation [Aversano et al 2002;Kim et al 2008;Kenner et al 2010;Teixeira et al 2011;Kästner et al 2012a;Kästner et al 2012b;Liebig et al 2013;Le et al 2013;Chen et al 2014], and annotation-based design [Czarnecki and Pietroszek 2006;Metzger et al 2007;Heidenreich 2009]. For composition-based product lines, type checking ensures safe composition [Thaker et al 2007;Kim et al 2008].…”

Section: Family-based Type Checkingmentioning

confidence: 99%

A Classification and Survey of Analysis Strategies for Software Product Lines

et al. 2014

View full text Add to dashboard Cite

Software-product-line engineering has gained considerable momentum in the recent years, both in industry and in academia. A software product line is a family of software products that share a common set of features. Software product lines challenge traditional analysis techniques, such as type checking, model checking, and theorem proving, in their quest of ensuring correctness and reliability of software. Simply creating and analyzing all products of a product line is usually not feasible, due to the potentially exponential number of valid feature combinations. Recently, researchers began to develop analysis techniques that take the distinguishing properties of software product lines into account, for example, by checking feature-related code in isolation or by exploiting variability information during analysis. The emerging field of product-line analyses is both broad and diverse, so it is difficult for researchers and practitioners to understand their similarities and differences. We propose a classification of product-line analyses to enable systematic research and application. Based on our insights with classifying and comparing a corpus of 123 research articles, we develop a research agenda to guide future research on product-line analyses.

show abstract

Section: Family-based Type Checkingmentioning

confidence: 99%

A Classification and Survey of Analysis Strategies for Software Product Lines

et al. 2014

View full text Add to dashboard Cite

show abstract

“…Heidenreich [105] describes techniques for ensuring the correspondence between solution space models, and problem space models, which is realised in the FeatureMapper tool. In this tool, models are checked for well-formedness against their meta-model.…”

Section: Type Systems and Static Analysismentioning

confidence: 99%

Software diversity: state of the art and perspectives

Schaefer

Rabiser²,

Clarke

et al. 2012

Int J Softw Tools Technol Transfer

137

View full text Add to dashboard Cite

Abstract. Diversity is prevalent in modern software systems to facilitate adapting the software to customer requirements or the execution environment. Diversity has an impact on all phases of the software development process. Appropriate means and organizational structures are required to deal with the additional complexity introduced by software variability. This introductory article to the special section "Software Diversity -Modeling, Analysis and Evolution" provides an overview of the current state of the art in diverse systems development and discusses challenges and potential solutions. The article covers requirements analysis, design, implementation, verification and validation, maintenance and evolution as well as organizational aspects. It also provides an overview of the articles which are part of this special section and address particular issues of diverse systems development.

show abstract

“…Heidenreich [10] describes techniques for ensuring the correspondence between feature models, solution-space models, and problem-space models, which is realised in the FeatureMapper tool. In this tool, models are checked for wellformedness against their meta-model.…”

Section: Related Workmentioning

confidence: 99%

Row types for delta-oriented programming

Lienhardt

Clarke

2012

Proceedings of the Sixth International Workshop on Variability Modeling of Software-Intensive Systems

View full text Add to dashboard Cite

Delta-oriented programming (DOP) provides a technique for implementing Software Product Lines based on modifications (add, remove, modify) to a core program. Unfortunately, such modifications can introduce errors into a program, especially when type signatures of classes are modified in a non-monotonic fashion. To deal with this problem we present a type system for delta-oriented programs based on row polymorphism. This exercise elucidates the close correspondence between delta-oriented programs and row polymorphism. General Terms Theory KeywordsSoftware product line engineering, delta-oriented programming, structural typing

show abstract

Towards systematic ensuring well-formedness of software product lines

Cited by 29 publications

References 15 publications

A Classification and Survey of Analysis Strategies for Software Product Lines

A Classification and Survey of Analysis Strategies for Software Product Lines

Software diversity: state of the art and perspectives

Row types for delta-oriented programming

Contact Info

Product

Resources

About