Repeatable forward process

[nbhatia]

I am a newbie to EA. Can someone tell me what is the smoothest repeatable forward code generation process using EA. I am not interested in reverse engineering.

What I am finding is that when I drop attributes or methods they are still left in the code. It also appears that when I am changing say an attribute from public to private then the code generator does not pick it up. I have also enabled the option "On forward sync, prompt to delete code features not in model". This helps with the delete problem but forces you to answer bunch of questions during regeneration.

In addition to this, I would also like to know what is the smoothest process to generate multiple outputs from the a same PIM. I am primarily interested in generating Java, C#, XSD and hibernate mappings from the same model. Again only interested in forward generation, but output should be totally in sync with model without any pain.

Has anyone tried EA with AndroMDA? Any opinions on this combination?

Thanks.

[Eve]

From EA 5.0 you can create one model and execute transformations to Java, C# and XSD from that one.  (All three transformations are already defined.)

The questions that EA is asking are to protect your source code from accidental deletion. (If the method signature changes.)

The scope problem should be only in C++ and Delphi because of their scope blocks.  As a result, changing the scope actually comes under the category of refactoring.  We are planning to add support though.

I haven't tried AndroMDA, so I can't comment on that.

Simon

[nbhatia]

Is there a step-by-step tutorial that walks through the creation of a PIM from which two or more PSMs are gernerated and finally code being generated from PSMs? Does the PIM have to be defined in a platform neutral types? How are the PSMs kept in sync with the PIM?

[Eve]

Currently there isn't a tutorial.  I can only recommend some experimentation.

Platform neutral types make the job much easier when converting types.

The PSMs are kept in synch by executing the transformation again after a change and the changes will be synchronised into the transformed class.

Simon