| [documentation] why are diagrams not done with EMF? [message #609800] |
Tue, 25 September 2007 06:56 |
 Philipp Kutter
Messages: 306
Registered: July 2009 |
Senior Member |
|
|
Hi, everybody of EMFT.
I started to go through validation, ocl and other EMF documentation.
What strikes me is that the documentation gives UML diagrams of the
getters and setters, rather than the real conceptual models you get when
using EMF.
For instance, under "Overview of Constraints" there is a diagram, with
IModelConstraint having a getter "getDescriptor)()" and then there is
a <<use>> relation to IConstraintDescriptor.
By adding a few line of EMF tags to the corresponding interfaces,
extracting the EMF model from it, and then exporting it to UML,
we would get the same diagram, but with a reference "description" from
IModelConstraint to IConstraintDescriptor.
Why is this not done?
Are people not eating their own dog food?
I know the 100 arguments why not to do what I propose, most of them
around the topic "it does not make me faster while programming".
If someone provides me with the UML tool you use to make the screenshot,
I volonteer to annotate the corresponding classes and interfaces with
EMF tags. I do not think it is a lot of work, it is just a last step of
bootstrapping... and it would be the basis to motivate other non-EMF
projects to use EMF in documenting their code in the EMF way.
Would it not be a great step forward, if all the classes developed in
the various Eclipse projects are correctly tagged with EMF info, and if
the resulting diagrams would be a basis for documentation all EMF plugins?
Best, Philipp
|
|
|
Powered by
FUDForum. Page generated in 0.03577 seconds
] 
Search
Help
Register
Login
Home
