The UML as a formal modeling notation
Computer Standards & Interfaces - Special issue on semantics in specifications
Domain-specific languages: an annotated bibliography
ACM SIGPLAN Notices
MDA Explained: The Model Driven Architecture: Practice and Promise
MDA Explained: The Model Driven Architecture: Practice and Promise
Eclipse Modeling Framework
The Pragmatics of Model-Driven Development
IEEE Software
Generation of visual editors as eclipse plug-ins
Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering
A Landscape of Bidirectional Model Transformations
Generative and Transformational Techniques in Software Engineering II
Eclipse Modeling Project: A Domain-Specific Language (DSL) Toolkit
Eclipse Modeling Project: A Domain-Specific Language (DSL) Toolkit
Isabelle/HOL: a proof assistant for higher-order logic
Isabelle/HOL: a proof assistant for higher-order logic
Model driven engineering: an emerging technical space
GTTSE'05 Proceedings of the 2005 international conference on Generative and Transformational Techniques in Software Engineering
From UML to alloy and back again
MODELS'09 Proceedings of the 2009 international conference on Models in Software Engineering
UML2Alloy: a challenging model transformation
MODELS'07 Proceedings of the 10th international conference on Model Driven Engineering Languages and Systems
Hi-index | 0.00 |
Formal methods (such as interactive provers) are increasingly used in software engineering. They offer a formal frame that guarantees the correctness of developments. Nevertheless, they use complex notations that might be difficult to understand for unaccustomed users. On the contrary, visual specification languages use intuitive notations and allow to specify and understand software systems. Moreover, they permit to easily generate graphical interfaces or editors for Domain Specific Languages (DSLs) starting from a meta-model. However, they suffer from a lack of precise semantics. We are interested in combining these two complementary technologies by mapping the elements of the one into the other. In this paper, we present a generic transformation process from functional data structures, commonly used in proof assistants, to Ecore models and vice-versa. This translation method is based on Model-Driven Engineering and defined by a set of bidirectional transformation rules. These rules are presented with an illustrating example, along with an implementation in the Eclipse environment.