| [news.eclipse.modeling] Re: Should UML be used in an Agile Project ? |
Vlad,
Comments below.
Yes, it's another use.Ed,
Dynamic ecore is another use of the technology which is related to MDD.
This is model to model transformation but certainly not agile.No it's not model to model transformation. It can be used to work with instance data exactly the same way as if you'd generated code. It seems one could argue that if round tripping is agile, then eliminating the need to round trip entirely is even more agile. Of course I really don't agree with the assertion nor do I understand your line of reasoning. I'm not sure anyone does.
Agile is composed by all team members architects, modelers and developer and not just architects+modelers.Yes, so what's your point?
A developer will always code and his job should be in the agile iteration.So the assertion is that defining an Ecore model isn't coding even though Ecore is a language, i.e., even though defining an EClass is isomorphic to defining a Java interface, the former is not coding while the latter is. What an odd perspective.
I guess round tripping is simply impossible then because the code must contain the model to be able to recover the model from the code and therefore refactoring will destroy the whole pretty picture. But that's a general sweeping statement to which Omondo's technology is somehow an exception.
If the java code contains the model information then it is impossible to guarantee that refactoring will not erase the model.
This is definitely a bad practice.According to Vlad...
Yet another assertion. Facts and opinions are different things.
I agree with you that Java source code doesn't have enough information and should be extended. The extension should be a Java to UML Ids merge and not an annotated model information in the Java code.
Java Id and UML Id are used together but all the information should be in the model and not in the java code.And of course Java code isn't a model according to you. But that's just an opinion, not a fact.
So no one does any coding in Java ever because that's a bad practice...
When you say "And how did you get your UML IDs in out and out of your Java without getting the Java dirty?" Please not that we don't touch the java code but upload information into the model.
This is the Java to XMI mapping approach which is the only possible modern modeling usage with an agile methodology.This is all such totally circular reasoning with the one and only purpose being to promote your proprietary technology. I doubt you are serving your cause well by making questionable assertions as a starting point, reasoning from those assertions with great leaps of logic, and then drawing conclusions that simply reflect the original assertions. Feel free to keep digging a deeper and deeper hole though, just be careful you don't fall in and have the hole collapse in on you.