2006
DOI: 10.1007/11663430_15
|View full text |Cite
|
Sign up to set email alerts
|

Practical Declarative Model Transformation with Tefkat

Abstract: Abstract. We present Tefkat, an implementation of a language designed specifically for the transformation of MOF models using patterns and rules. The language adopts a declarative paradigm, wherein users may concern themselves solely with the relations between the models rather than needing to deal explicitly with issues such as order of rule execution and pattern searching/traversal of input models. In this paper, we demonstrate the language using a provided example and highlight a number of language features… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
53
0
3

Year Published

2006
2006
2016
2016

Publication Types

Select...
6
4

Relationship

0
10

Authors

Journals

citations
Cited by 91 publications
(56 citation statements)
references
References 5 publications
(7 reference statements)
0
53
0
3
Order By: Relevance
“…From the early years of model transformation, Prolog has been present as a tool to specify simple transformations [10,11,12,13]. Prolog has been also present in early relevant proposals like VIATRA [14].…”
Section: Model Transformation and Prologmentioning
confidence: 99%
“…From the early years of model transformation, Prolog has been present as a tool to specify simple transformations [10,11,12,13]. Prolog has been also present in early relevant proposals like VIATRA [14].…”
Section: Model Transformation and Prologmentioning
confidence: 99%
“…In particular, declarative transformation languages such as QVT Relational [OMG05] and Tefkat [LS06] explicitly establish how target elements relate to source elements, which facilitates rule adaptation. However, the integration of adapter code (written in OCL) will be easier in QVT than in Tefkat because the former uses OCL (i.e., the translation is straightforward) while the latter is based on a logic-based pattern matching language.…”
Section: Templates In Atlmentioning
confidence: 99%
“…Transformation frameworks can address traceability during the design of transformations [12], either by providing dedicated support for traceability (e.g., Tefkat [19], QVT [2]), or by encoding traceability as any other link between the input and output models (e.g., VIATRA [25], GreAT [4]). Traceability links may be encoded manually in the transformation rules (e.g., [19]), or inserted automatically (e.g., [2]). A HOT-based traceability system for ATL is already implemented in [17], where the HOT adds to each original transformation rule the production of a traceability link in an external ad-hoc traceability model (conforming to a small traceability metamodel).…”
Section: Related Workmentioning
confidence: 99%