A calculus for uniform feature composition

Apel, Sven; Hutchins, DeLesley

doi:10.1145/1745312.1745316

Cited by 36 publications

(38 citation statements)

References 69 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…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]. The idea is that the recursive process of merging software artifacts, when composing hierarchically structured features, is very similar for different host languages (e.g., for Java, C#, and XML).…”

Section: Feature-oriented Programsmentioning

confidence: 99%

Type safety for feature-oriented product lines

et al. 2010

Self Cite

View full text Add to dashboard Cite

A feature-oriented product line is a family of programs that share a common set of features. A feature implements a stakeholder's requirement and represents a design decision or configuration option. When added to a program, a feature involves the introduction of new structures, such as classes and methods, and the refinement of existing ones, such as extending methods. A feature-oriented decomposition enables a generator to create an executable program by composing feature code solely on the basis of the feature selection of a user -no other information needed. A key challenge of product line engineering is to guarantee that only well-typed programs are generated. As the number of valid feature combinations grows combinatorially with the number of features, it is not feasible to type check all programs individually. The only feasible approach is to have a type system check the entire code base of the feature-oriented product line. We have developed such a type system on the basis of a formal model of a feature-oriented Java-like language. The type system guaranties type safety for feature-oriented product lines. That is, it ensures that every valid program of a well-typed product line is well-typed. Our formal model including type system is sound and complete.

show abstract

Section: Feature-oriented Programsmentioning

confidence: 99%

Type safety for feature-oriented product lines

et al. 2010

Self Cite

View full text Add to dashboard Cite

show abstract

“…Whether these plug-ins can be generated automatically (e.g., from attribute grammars) is an open research question. Regarding inter-language typing, further research is needed to find the right abstractions (e.g., [Apel and Hutchins 2010]) or a suitable polylingual type system (e.g., [Grechanik et al 2004]). From a tool perspective, recent advances in inter-language refactorings in Eclipse can be used as possible starting point [Fuhrer et al 2007].…”

Section: Beyond Featherweight Java (Implementation)mentioning

confidence: 99%

Type checking annotation-based product lines

Kästner

Apel

Thüm

et al. 2012

ACM Trans. Softw. Eng. Methodol.

Self Cite

151

133

View full text Add to dashboard Cite

Software-product-line engineering is an efficient means to generate a family of program variants for a domain from a single code base. However, because of the potentially high number of possible program variants, it is difficult to test them all and ensure properties like type safety for the entire product line. We present a product-line-aware type system that can type check an entire software product line without generating each variant in isolation. Specifically, we extend the Featherweight Java calculus with feature annotations for product-line development and prove formally that all program variants generated from a well-typed product line are well-typed. Furthermore, we present a solution to the problem of typing mutually exclusive features. We discuss how results from our formalization helped implementing our own product-line tool CIDE for full Java and report of experience with detecting type errors in four existing software-product-line implementations.

show abstract

“…In such a feature-product-based verification, features are verified as far as possible in isolation, and all remaining verification tasks are done for each product. A feature-product-based strategy has been proposed for type checking [2], model checking [9], and theorem proving [17].…”

Section: State Of the Artmentioning

confidence: 99%

Product-line verification with feature-oriented contracts

Thüm

2013

Proceedings of the 2013 International Symposium on Software Testing and Analysis

View full text Add to dashboard Cite

Software product lines allow programmers to reuse code across similar software products. Software products are decomposed into separate modules representing user-visible features. Based on a selection of desired features, a customized software product can be generated automatically. However, these reuse mechanisms challenge existing techniques for specification and verification of software. Specifying and verifying each product involves redundant steps, and is often infeasible. We discuss how method contracts (i.e., preconditions and postconditions) can be used to efficiently specify and verify product lines.

show abstract

A calculus for uniform feature composition

Cited by 36 publications

References 69 publications

Type safety for feature-oriented product lines

Type safety for feature-oriented product lines

Type checking annotation-based product lines

Product-line verification with feature-oriented contracts

Contact Info

Product

Resources

About