Model Superimposition in Software Product Lines

Apel, Sven; Janda, Florian; Trujillo, Salvador; Kästner, Christian

doi:10.1007/978-3-642-02408-5_2

Cited by 81 publications

(58 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Variant annotations, e.g., using UML stereotypes [31,9], presence conditions [6], or separate variability representations, such as orthogonal variability models [23], define which parts of the model have to be removed to derive the model of a concrete product. Second, compositional approaches [2,30,21,1] associate product fragments with product features which are composed for particular feature configurations. Third, transformational approaches, such as [14], represent variability by rules determining how modelling elements of a base model have to be replaced for a particular product model.…”

Section: Related Workmentioning

confidence: 99%

Compositional Algorithmic Verification of Software Product Lines

Schaefer

Gurov

Soleimanifard

2011

Formal Methods for Components and Objects

View full text Add to dashboard Cite

Abstract. Software product line engineering allows large software systems to be developed and adapted for varying customer needs. The products of a software product line can be described by means of a hierarchical variability model specifying the commonalities and variabilities between the artifacts of the individual products. The number of products generated by a hierarchical model is exponential in its size, which poses a serious challenge to software product line analysis and verification. For an analysis technique to scale, the effort has to be linear in the size of the model rather than linear in the number of products it generates. Hence, efficient product line verification is only possible if compositional verification techniques are applied that allow the analysis of products to be relativized on the properties of their variation points. In this paper, we propose simple hierarchical variability models (SHVM) with explicit variation points as a novel way to describe a set of products consisting of sets of methods. SHVMs provide a trade-off between expressiveness and a clean and simple model suitable for compositional verification. We generalize a previously developed compositional technique and tool set for the automatic verification of control-flow based temporal safety properties to product lines defined by SHVMs, and prove soundness of the generalization. The desired property relativization is achieved by introducing variation point specifications. We evaluate the proposed technique on a number of test cases.

show abstract

Section: Related Workmentioning

confidence: 99%

Compositional Algorithmic Verification of Software Product Lines

Schaefer

Gurov

Soleimanifard

2011

Formal Methods for Components and Objects

View full text Add to dashboard Cite

show abstract

“…In this case, a special marker @ is added to the fields in question because we cannot guarantee that a reference to this field is safe in the given context. 6 It is up to the type system to decide, based on the marker, whether this situation may provoke an error (e.g., the type system ignores the marker when looking for duplicate fields but reports an error when type checking object creations). 5.…”

Section: Field Lookupmentioning

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

“…For a particular feature configuration, the respective feature modules are composed by adding and refining elements following the principles of stepwise refinement [27]. Apel et al [12] apply model superposition to compose model fragments which is similar to FOMDD [218] without the explicit refinement statements. Model superimposition considers models with a hierarchical structure that is preserved when models are composed.…”

Section: Solution Space Variabilitymentioning

confidence: 99%

Software diversity: state of the art and perspectives

Schaefer

Rabiser²,

Clarke

et al. 2012

Int J Softw Tools Technol Transfer

Self Cite

136

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

Model Superimposition in Software Product Lines

Cited by 81 publications

References 18 publications

Compositional Algorithmic Verification of Software Product Lines

Compositional Algorithmic Verification of Software Product Lines

Type safety for feature-oriented product lines

Software diversity: state of the art and perspectives

Contact Info

Product

Resources

About