Providing Support for Model Composition in Metamodels

France, Robert; Fleurey, Franck; Reddy, Raghu; Baudry, Benoît; Ghosh, Sudipto

doi:10.1109/edoc.2007.55

Cited by 43 publications

(50 citation statements)

References 10 publications

(5 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Kompose proposes a system of pre-and postdirectives to modify the models before and after the merge. The two models are called base model and aspect model, as in Aspect-Oriented Modeling, which suggests an asymmetric treatment, yet the tool is symmetric [5]. Only the merging process of our framework simulates correctly Kompose.…”

Section: E Validation Using Existing Toolsmentioning

confidence: 99%

“…Kompose: Kompose 3 is a model merging tool [5] implemented in the Kermeta language [9]. It merges two homogeneous models (instances of the same metamodel) by comparing the signatures of their elements.…”

Section: E Validation Using Existing Toolsmentioning

confidence: 99%

“…We also give several properties inspired from [2], [3], that are verified by one or both approaches, and allow further comparison and comprehension of the two kind of operators. Finally, we validate our framework by checking that it correctly identifies three tools from the literature, UML Package Merge [4], Kompose [5] and ADORE [6], as using a merging or a weaving operator.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A categorical model of model merging and weaving

Marchand

Combemale

Baudry

2012

2012 4th International Workshop on Modeling in Software Engineering (MISE)

Self Cite

View full text Add to dashboard Cite

Abstract-Model driven engineering advocates the separation of concerns during the design time of a system, which leads to the creation of several different models, using several different syntaxes. However, to reason on the overall system, we need to compose these models. Unfortunately, composition of models is done in an ad hoc way, preventing comparison, capitalisation and reuse of the composition operators. In order to improve comprehension and allow comparison of merging and weaving operators, we use category theory to propose a unified framework to formally define merging and weaving of models. We successfully use this framework to compare them, both through the way they are transformed in the formalism, and through several properties, such as completeness or nonredundancy. Finally, we validate this framework by checking that it correctly identifies three tools as performing merging or weaving of models.

show abstract

Section: E Validation Using Existing Toolsmentioning

confidence: 99%

Section: E Validation Using Existing Toolsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A categorical model of model merging and weaving

Marchand

Combemale

Baudry

2012

2012 4th International Workshop on Modeling in Software Engineering (MISE)

Self Cite

View full text Add to dashboard Cite

show abstract

“…Aspect-Oriented Architecture Models of France et al [30,31] The symmetric model composition technique proposed by France et al [30,31] supports composition of model elements that present different views of the same concept. This composition technique has been implemented in a tool called Kompose [32,42]. The model elements to be composed must be of the same syntactic type, i.e., they must be instances of the same meta model class.…”

Section: In-depth Comparison To Related Workmentioning

confidence: 99%

Aspect-Oriented Design with Reusable Aspect Models

Kienzle

Abed

Fleurey

et al. 2010

Transactions on Aspect-Oriented Software Development VII

Self Cite

View full text Add to dashboard Cite

Abstract. The idea behind Aspect-Oriented Modeling (AOM) is to apply aspect-oriented techniques to (software) models with the aim of modularizing crosscutting concerns. This can be done within different modeling notations, at different levels of abstraction, and at different moments during the software development process. This paper demonstrates the applicability of AOM during the software design phase by presenting parts of an aspect-oriented design of a crisis management system. The design solution proposed in this paper is based on the Reusable Aspect Models (RAM) approach, which allows a modeler to express the structure and behavior of a complex system using class, state and sequence diagrams encapsulated in several aspect models. The paper describes how the model of the "create mission" functionality of the server backend can be decomposed into 23 inter-dependent aspect models. The presentation of the design is followed by a discussion on the lessons learned from the case study. Next, RAM is compared to 8 other AOM approaches according to 6 criteria: language, concern composition, asymmetric and symmetric composition, maturity, and tool support. To conclude the paper, a discussion section points out the features of RAM that specifically support reuse.

show abstract

“…Kompose [12,13] is an Aspect-Oriented Modeling (AOM) approach based on the systematic merging of matching elements. Initially, AOM comes from the Aspectoriented software development (AOSD) community.…”

Section: Komposementioning

confidence: 99%

Reconciling Automation and Flexibility in Product Derivation

Perrouin

Klein

Guelfi

et al. 2008

2008 12th International Software Product Line Conference

View full text Add to dashboard Cite

Product derivation, i.e. reusing core assets to build products, did not receive sufficient attention from the productline community, yielding a frustrating situation. On the one hand, automated product derivation approaches are inflexible; they do not allow products meeting unforeseen, customer-specific, requirements. On the other hand, approaches that consider this issue do not provide adequate methodological guidelines nor automated support.This paper proposes an integrated product derivation approach reconciling the two views to offer both flexibility and automation. First, we perform a pre-configuration of the product by selecting desired features in a generic feature model and automatically composing their related product-line core assets. Then, we adapt the pre-configured product to its customer-specific requirements via derivation primitives combined by product engineers and controlled by constraints that flexibly set product line boundaries. Our process is supported by the Kermeta metamodeling environment and illustrated through an example.

show abstract

Providing Support for Model Composition in Metamodels

Cited by 43 publications

References 10 publications

A categorical model of model merging and weaving

A categorical model of model merging and weaving

Aspect-Oriented Design with Reusable Aspect Models

Reconciling Automation and Flexibility in Product Derivation

Contact Info

Product

Resources

About