The Model Driven Software Network

Raise your level of abstraction

EMF Profiles - An annotation mechanism for EMF Models

There are many situations in which you would like to extend or annotate a model with additional information but most times the last thing you’d like to do is to change its metamodel to be able to include this new information. As a solution, we propose to reuse the concept of UML profiles and adapt it for arbitrary EMF models.


Read more about our new EMFProfiles initiative here

Views: 560

Add a Comment

You need to be a member of The Model Driven Software Network to add comments!

Join The Model Driven Software Network

Comment by Konrad Wieland on March 31, 2011 at 12:17

Dear Andreas Leue,

the effect would be that the extended classes include additional properties defined as tagged values in a stereotype. A stereotype, defined as an EClass, may contain also EAttributes and EReferences which are reused to represent tagged values.


I hope this has answered your question.



Konrad Wieland

Comment by Andreas Leue on March 31, 2011 at 8:46

Hi Jordi,


this is interesting. What would be the effect of applying a profile stereotype to an EMF class? Does this include stereotype specific properties/slots/tagged values etc. to be added? And what types can these properties have?


UML profiles e.g. allow Instances as property/slot types, but you cannot edit them graphically, you have to use the EMF tree view - which is rather unusable to customers.


BTW, speaking of model extensions, I wonder what model editors others do use, because the current situation with the eclipse/EMF tool chain and the various releases is so utterly hairy and painful. We do support EMF/UML modelling, but even in our own projects we prefer to use dia (the oss visio clone). It's theoretical background is not as sophisticated as EMF/ECore, but it simply works and is extensible totally easy (xml shape definitions and python scripts), it's UI is stable (read: it neither hangs nor crashes) and it is available on all platforms. We would prefer the eclipse way, but at present it seems it is only usable in single projects (if at all), but by far not as a MDx product frontend.



© 2019   Created by Mark Dalgarno.   Powered by

Badges  |  Report an Issue  |  Terms of Service