Programming language criteria for model transformation evaluation

Samimi-Dehkordi, Leila; Khalilian, Alireza; Zamani, Bahman

doi:10.1109/iccke.2014.6993469

Cited by 6 publications

(1 citation statement)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Different methods have been proposed to investigate transformation languages and their characteristics from different aspects [8]- [11]. In [18] authors have proposed a method in which programming language (PL) evaluation criteria have been used for the assessment of MTLs [12] and applied three major criteria and nine sub-criteria for MTL evaluation. Criteria is based on some PL evaluation criteria [13] and some bidirectional features [14].…”

Section: Literature Reviewmentioning

confidence: 99%

Model Transformation of Declarative User Interface from Platform Specific Model to Platform Independent Model using Graphical Notation.

Agarwal*¹,

Aggarwal²,

Dixit³

2019

IJITEE

View full text Add to dashboard Cite

The approach of model-based user interface development (MBUID) paradigm is for building user interfaces using a set of models that take into account the various facets of a user interface at a semantic level. In this work model transformation of user interface has been explored from source model to target model using relational mapping and graphical notation. A framework based on mathematical graphical notation is presented and relational mapping to re-engineer declarative user interface model transformation through a platform independent model (PIM) is presented. For re-engineering user interface three steps; namely source code to platform specific source model (Extraction), platform specific source model to platform specific target model (Transformation) and platform specific target model to platform specific target code (Development) are followed. For achieving independence with respect to platform and language, user interface elements are addressed at the semantic level. A layer of abstraction of PIM has been added for defining few common basic user interface elements along with their attributes in semantic terms using mathematical graphical notation. Transformation has been defined between the source and target model and generic rules are applied for every new element extracted from source model and placed in the target model. By adding a new layer in the re-engineering process efforts required to port the user interface from one platform specific source model to one or more platform specific model are reduced. By defining the user interface elements semantically in graphical notation, diversity in the programming languages has been reduced. Bi-directionality has been achieved between the source model and the target model by defining the relational mapping between the two

show abstract

Section: Literature Reviewmentioning

confidence: 99%