2009
DOI: 10.1007/978-3-642-02571-6_11
|View full text |Cite
|
Sign up to set email alerts
|

Guaranteeing Syntactic Correctness for All Product Line Variants: A Language-Independent Approach

Abstract: Abstract. A software product line (SPL) is a family of related program variants in a well-defined domain, generated from a set of features. A fundamental difference from classical application development is that engineers develop not a single program but a whole family with hundreds to millions of variants. This makes it infeasible to separately check every distinct variant for errors. Still engineers want guarantees on the entire SPL. A further challenge is that an SPL may contain artifacts in different langu… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
44
0

Year Published

2009
2009
2016
2016

Publication Types

Select...
5
4

Relationship

3
6

Authors

Journals

citations
Cited by 53 publications
(44 citation statements)
references
References 30 publications
0
44
0
Order By: Relevance
“…Whereas many concern-location tools (such as Suade [52] and Cerberus [22]) use rather lightweight models and cover only entire methods and fields, we need fine granularity at intraprocedural level, as argued above. For Java, we model compilation units, types, fields, methods, statements, local variables, parameters, and import declarations (we discussed suitable granularity for product lines in prior work [29], [40]; in languages other than Java, we could chose similar structures [32]). Technically, we automatically extract elements from abstract syntax trees provided by Eclipse.…”
Section: Underlying Modelmentioning
confidence: 99%
“…Whereas many concern-location tools (such as Suade [52] and Cerberus [22]) use rather lightweight models and cover only entire methods and fields, we need fine granularity at intraprocedural level, as argued above. For Java, we model compilation units, types, fields, methods, statements, local variables, parameters, and import declarations (we discussed suitable granularity for product lines in prior work [29], [40]; in languages other than Java, we could chose similar structures [32]). Technically, we automatically extract elements from abstract syntax trees provided by Eclipse.…”
Section: Underlying Modelmentioning
confidence: 99%
“…A different line of research aims at the language-independent reasoning about features [15,48,10,43]. The calculus gDeep is most closely related to FFJ since it provides a type system for feature-oriented languages that is language-independent [5,4].…”
Section: Feature-oriented Programsmentioning
confidence: 99%
“…Language independent frameworks [16,125] operate at the product line level for reference checking-checking which dependencies are present and satisfied-and for checking syntactic correctness.…”
Section: Type Systems and Static Analysismentioning
confidence: 99%