Less (or none) transformation between models will surely save time during code generation. This will save a lot of time for developers of huge projects. But concerning thos PSMs, if you really model the PIM, I would think that you should never actualle *see* one of those PSMs as UML. They will be generated during code generation and when generation is finished they just disappear.
I don't know what you mean with "disappear". Yes, the diagrams of intermediate models don't have to be shown for every generated application. However, you do need to store the models (PIM, intermediate models and PSM) in a repository, together with all traceability links. Otherwise, your tool could not maintain consistency when the PIM or the code evolves.
I agree with that when we are talking about some kind of round trip tool. I was thinking of the "model in, code out" generator at this time.
You are obviously right, that you need to store the models to if you want to track changes - you should not need to store them if you can separate the generated code from the code that is manually changed... or am I missing something?
Cheers Harald
I'm also investigating how changes to the transformations (M2M or M2T) affect applications that were generated with the old version of the transformations.
------------------- snip -------------
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
