Product Line Implementation using Aspect-Oriented and Model-Driven Software Development

Voelter, Markus; Groher, Iris

doi:10.1109/spline.2007.4339272

Cited by 27 publications

(21 citation statements)

References 10 publications

(14 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [50] Voelter presents an approach that addresses variability implementation, management and tracing by integrating model-driven and aspect-oriented software development. Features are separated in models and composed by aspect-oriented composition techniques at the model level.…”

Section: Related Work and Discussionmentioning

confidence: 99%

Weaving variability into domain metamodels

et al. 2010

View full text Add to dashboard Cite

Domain-specific modeling languages (DSMLs) are the essence of MDE. A DSML describes the concepts of a particular domain in a metamodel, as well as their relationships. Using a DSML, it is possible to describe a wide range of different models that often share a common base and vary on some parts. On the one hand, some current approaches tend to distinguish the variability language from the DSMLs themselves, implying greater learning curve for DSMLs stakeholders and a significant overhead in product line engineering. On the other hand, approaches integrating variability in DSMLs lack generality and tool support.We argue that aspect-oriented modeling techniques enabling flexible metamodel composition and results obtained by the software product line community to manage and resolve variability form the pillars for a solution for integrating variability into DSMLs. In this article, we consider variability as an independent and generic aspect to be woven into the DSML. In particular, we detail how variability is woven and how to perform product line derivation. We validate our approach through the weaving of variability into two different metamodels: Ecore-widely used for DSML definition-and SmartAdapters, our aspect model weaver. These results emphasize how new abilities of the language can be provided by this means.

show abstract

Section: Related Work and Discussionmentioning

confidence: 99%

Weaving variability into domain metamodels

et al. 2010

View full text Add to dashboard Cite

show abstract

“…In [50] Völter and Groher present an approach to support software product line engineering based on domain-specific languages and model-driven development. They propose the usage of staged SPLs or in other words meta-product lines.…”

Section: Dsl-based Approachesmentioning

confidence: 99%

“…In the solution domain (which comprises a componentbased architecture), a combination of manually written code and models are used to represent the components. Modelto-model transformations are used to instantiate, wire and deploy those library components based upon the problem domain model [50].…”

Section: Dsl-based Approachesmentioning

confidence: 99%

“…The approach presented in [50] uses lots of different techniques to realize this goal: both positive and negative variability is used, resulting in construction DSLs and configuration DSLs which are used on different stages of the development process. Furthermore, library components and target code variability are used.…”

Section: Dsl-based Approachesmentioning

confidence: 99%

“…The most significant difference is the usage of staged SPLs in [50]. Furthermore, both positive and negative variability approaches are used.…”

Section: Dsl-based Approachesmentioning

confidence: 99%

See 2 more Smart Citations

Mapping feature models onto domain models: ensuring consistency of configured domain models

Buchmann

Westfechtel

2012

Softw Syst Model

View full text Add to dashboard Cite

We present an approach to model-driven software product line engineering which is based on feature models and domain models. A feature model describes both common and varying properties of the instances of a software product line. The domain model is composed of a structural model (package and class diagrams) and a behavioral model (story diagrams). Features are mapped onto the domain model by annotating elements of the domain model with features. An element of a domain model is specific to the features included in its feature annotation. An instance of the product line is defined by a set of selected features (a feature configuration). A configuration of the domain model is built by excluding all elements whose feature set is not included in the feature configuration. To ensure consistency of the configured domain model, we define constraints on the annotations of inter-dependent domain model elements. These constraints guarantee that a model element may be selected only when the model elements are also included on which it depends. Violations of dependency constraints may be removed automatically with the help of an error repair tool which propagates features to dependent model elements.Keywords Model-driven software product line engineering · Feature models · Domain models · Feature mappings · Dependency constraints Communicated by Prof. Alfonso Pierantonio.

show abstract

Bibliography

2012

Model‐Driven and Software Product Line Engineering

View full text Add to dashboard Cite

Product Line Implementation using Aspect-Oriented and Model-Driven Software Development

Cited by 27 publications

References 10 publications

Weaving variability into domain metamodels

Weaving variability into domain metamodels

Mapping feature models onto domain models: ensuring consistency of configured domain models

Bibliography

Contact Info

Product

Resources

About