2013
DOI: 10.1016/j.infsof.2012.11.004
|View full text |Cite
|
Sign up to set email alerts
|

Applying MDE to the (semi-)automatic development of model transformations

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
18
0

Year Published

2014
2014
2021
2021

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 40 publications
(18 citation statements)
references
References 48 publications
0
18
0
Order By: Relevance
“…AToMPM [53] MATA [60] MeTAGeM [15] MoTif [51] MoTMoT [56] PICS [9] QVT-R [36] Schmidt [39] transML [22] VMTL Syntax transparency is exhibited by MATA [60], PICS [9] and the MTL proposed by Schmidt [39], all of which deliberately shun expressive control flow in favor of avoiding conformance breaking augmentations to the host metamodel. However, none of these approaches also address both environment and execution transparency.…”
Section: St Ent Extmentioning
confidence: 99%
See 1 more Smart Citation
“…AToMPM [53] MATA [60] MeTAGeM [15] MoTif [51] MoTMoT [56] PICS [9] QVT-R [36] Schmidt [39] transML [22] VMTL Syntax transparency is exhibited by MATA [60], PICS [9] and the MTL proposed by Schmidt [39], all of which deliberately shun expressive control flow in favor of avoiding conformance breaking augmentations to the host metamodel. However, none of these approaches also address both environment and execution transparency.…”
Section: St Ent Extmentioning
confidence: 99%
“…The recent emergence of transformation primitive libraries such as T-Core [52], along with their usage for implementing existing MTLs such as MoTif [51], indicates that this implementation style is viable. Execution transparency is also addressed in the context of the systematic development of model transformations by the transML [22] and MeTAGeM [15] tools.…”
Section: St Ent Extmentioning
confidence: 99%
“…However, the proposed diagrams use a UML heavy extension and new notations that make it difficult to integrate with the existing UML tools which are usually adopted. MeTaGen [2] proposes metamodels for transformation design and tools generate code automatically or semi automatically. The main difference between this work and ours is that it focuses on design, not considering the requirement specification level and it uses textual language for transformation specification whereas we use a profile that is a visual language.…”
Section: Related Workmentioning
confidence: 99%
“…In addition to the areas of knowledge already mentioned, the implementation of the proposed methodology for the regeneration of the user interfaces at runtime in an evolutionary way will make use of others such as cloud computing [18], big data [2] or model transformation [1]. Continued access to distributed systems and the data generated by that connection justify the use of cloud computing and big data [16].…”
Section: Introductionmentioning
confidence: 99%