Duration: 21:56

109 views

1

Our Automotive Eclipse tooling for electronic control units enables realisation of various functionalities for different vehicles. The central part of our IDE is a single holistic EMF model. This model had and still has benefits, but over the years standards evolved and so this core part of our software became bigger and bigger with constantly increasing technical debt.
Because of the generic nature, our model was not easy to be combined with other existing EMF projects ‘out-of-the-box’. On top in automotive industry it is always necessary to deal with extremely large amounts of data, which also slows down multiple basic EMF functionalities.
Finally we decided to search for a better approach, which should enable domain specific models with only required content and which is kept in sync with the main model.
We achieved this by creating an m2m framework with automated domain model import and export functionalities, which are triggered via listening to the main model or other foreign content. Internally it uses EMF to store the model instances, of the domain specific meta-models, and EMF Compare to deal with the imported data and to find differences in the ‘to be exported’ data.
This solution, which is presented in this talk, helped us to use ‘state-of-the-art’ EMF projects, which enables faster development of our Automotive Eclipse tooling, while we achieve a higher scalability, robustness and performance.

Johannes Jeising