Sparx Systems Forum
Enterprise Architect => Suggestions and Requests => Topic started by: bmoelk on August 14, 2003, 12:15:11 pm
-
I really like the reverse engineering features you have built into EA. It really rocks.
The one thing that I don't like is that it is filename dependent. This means if you move the source file to a different directory or a class from one file to another, you must go through each class individually in your model to set the proper filename.
If don't fix up the filename's EA will add duplicate classes into your model.
I would like EA to look at the class name and if the filename doesn't match, prompt the user to ask if this is indeed the same class or not.
Regards,
Brian Moelk
-
I agree, with the previous comment, but I would also like to add the following comments about enhancements that would be very useful to me - these are probably biased towards java code generation but here goes anyway:
1.] Could we set a default directory for each namespace root, so that newly generated files are saved to the appropriate (sub)directory by default.
2.] Could the default directory of the namespace root be configurable per user - allowing for different directory structures on the user's local machine
3.] With a default directory for the namespace root configured, could the synchronise option prompt the user about additional java files found on disk (i.e. do you want to import) or java files that have been removed (i.e. do you wish to delete the associated classes).
With these three things, synchronisation between a java code base (that may evolve outside the control of EA) and the model could be achieved more easily.
On another note, it seems that reverse engineering existing model classes takes a very long time - admittedly I have quite a large project, but this time factor could eventually dissuade people from keeping the model and codebase in sync.
On the whole EA seems to be a great tool, I just have some concerns around java code generation
Mikey