Seminar 5 Oct 9:00, 2012 in semminar room I7
Bridging GROOVE to the world using an abstracted language model
Currently GROOVE is capable of importing and exporting Ecore models, which can be used by tools such as Eclipse using its underlying modeling framework. This is done using a standalone tool which can transform GROOVE graphs to Ecore models and vice versa. An Ecore model may be imported as a type graph, and Ecore instance models as instance graphs. GROOVE can then be used to transform these instance graphs, which may then be exported back again to Ecore instance models. However, the generated type and instance graphs can sometimes become too complex and unmanageable, where a simpler graph would be sufficient. It is therefore desirable to improve the current import and export facilities, and give the user the option to generate more simple graphs. Ideally, this process would be configurable so different choices can be made on the resulting outcome.
Additionally, it is interesting to add the capability for translating other graph languages to the import and export facilities as well, so as to make GROOVE more interoperable with other tools. This can be approached by defining an abstraction over these languages (including Ecore), which can be formalized into a model that may be used to transform these languages to graphs in GROOVE and vice versa. Adding new languages to the importer/exporter will then be a matter of defining a mapping between the abstraction and the language, with the added benefit that it could be possible to transform languages with the abstraction/GROOVE as an intermediate form.
Currently GROOVE is capable of importing and exporting Ecore models, which can be used by tools such as Eclipse using its underlying modeling framework. This is done using a standalone tool which can transform GROOVE graphs to Ecore models and vice versa. An Ecore model may be imported as a type graph, and Ecore instance models as instance graphs. GROOVE can then be used to transform these instance graphs, which may then be exported back again to Ecore instance models. However, the generated type and instance graphs can sometimes become too complex and unmanageable, where a simpler graph would be sufficient. It is therefore desirable to improve the current import and export facilities, and give the user the option to generate more simple graphs. Ideally, this process would be configurable so different choices can be made on the resulting outcome.
Additionally, it is interesting to add the capability for translating other graph languages to the import and export facilities as well, so as to make GROOVE more interoperable with other tools. This can be approached by defining an abstraction over these languages (including Ecore), which can be formalized into a model that may be used to transform these languages to graphs in GROOVE and vice versa. Adding new languages to the importer/exporter will then be a matter of defining a mapping between the abstraction and the language, with the added benefit that it could be possible to transform languages with the abstraction/GROOVE as an intermediate form.
