Conference Paper

Domain-Specific Composition of Model Deltas

DOI: 10.1007/978-3-642-13688-7_2 Conference: Theory and Practice of Model Transformations, Third International Conference, ICMT 2010, Malaga, Spain, June 28-July 2, 2010. Proceedings
Source: DBLP


We present a general approach to the incremental development of model-based applications using endogenous transformations,
i.e. transformations whose input and output models conform to the same metamodel. Our work describes these transformations
as model deltas that, when composed, deliver a complete model. We establish a relationship between a metamodel and its corresponding
delta metamodel, show how model deltas can be defined as model changes (additions), explain how deltas can be composed using
domain-specific composition algorithms, and propose metamodel annotations to specify these algorithms. We present different
case studies as proofs of concept.

Download full-text


Available from: Oscar Díaz
  • Source
    • "The problem is that neither RAS nor AMS can represent information about technical solutions for ASE, limiting knowledge about MDE-based processes to descriptive information. On the other hand, approaches to automate MDE-based processes consider important to embed semantics for execution on tasks [9], [2], [3], a lack in the asset specifications. "
    [Show abstract] [Hide abstract]
    ABSTRACT: Model Driven Engineering (MDE) is a software development paradigm that promotes improvements in pro-ductivity through reuse of software model specifications. Although much effort has been dedicated for more than ten years, MDE has not achieved expressive use. In this paper we address the problem of a lack of a knowledge base about MDE-based solutions, a reason that hampers MDE in practice. To surpass it we propose a domain specific language named RAS++ that represents these solutions as reusable assets. Assets are composed by reuse structures and semantics for the execution of technical solutions for Automated Software Engineering, fostering the integration of tasks for MDE in development environments. Facilities are introduced through some supporting tools: one to design reusable assets and other to integrate them in target de-velopment environments. Practical experiences have proven to be promising, suggesting that reusable assets promote some benefits not allowed by other approaches, such as the possibility of a distributed base of knowledge for ASE solutions.
    Full-text · Conference Paper · Aug 2014
  • Source
    • "In this scenario, generation occurs by means of Model Transformations (MTs) that are executed by MDE tools such as FeatureIDE [33] and Andromeda [4]. These tools must be tailored to apply transformations for specific software implementation details. "
    [Show abstract] [Hide abstract]
    ABSTRACT: Model transformation is a central activity in Model Driven Engineering (MDE) as it specifies how models are consumed to generate other models or code. Complex scenarios typically involve the execution of several transformations that, due to variability of solutions to develop software projects, need to be tailored to attempt different implementation technologies, libraries, patterns, etc. Recent proposals to tailor these assets suggested that current Software Product Line (SPL) techniques can be used to promote reuse of model transformation assets. However, in a recent case study, we have found lacks in techniques, including ours, to apply reuse for this domain in particular. Thus, this paper presents this case study and discusses implications and challenges in tailoring these assets with SPL techniques.
    Full-text · Conference Paper · Mar 2014
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: In model-driven engineering of applications, the quality of the software architecture is realized and preserved in the successive stages of its lifecycle through model transformations. However, limited support for reuse in contemporary model transformation techniques forces developers of product line architectures to reinvent transformation rules for every variant of the product line, which can adversely impact developer productivity and in turn degrade the quality of the resulting software architecture for the variant. To overcome these challenges, this paper presents the MTS (Model-transformation Templatization and Specialization generative transformation process, which promotes reuse in model transformations through parameterization and specialization of transformation rules. MTS defines two higher order transformations to capture the variability in transformation rules and to specialize them across product variants. The core idea behind MTS is realized within a graphical model transformation tool in a way that is minimally intrusive to the underlying tool's implementation. The paper uses two product line case studies to evaluate MTS in terms of reduction in efforts to define model transformation rules as new variants are added to the product line, and the overhead in executing the higher order transformations. These metrics provide an indirect measure of how potential degradation in the quality of software architectures of product lines caused due to lack of reuse can be alleviated by MTS.
    Full-text · Conference Paper · Jan 2011
Show more