problem with aggregations and attributes

[NothanUmber]

Hi,

I'm playing around with the trial-version of EA for the first time so perhaps I simply haven't understood the "principle" behind some functions. But something with the code-syncronization-mechanism seems really odd from my point of view. Here's a receipt to reproduce the effect:

* create a new project (based on EABase)
* add a new class ClassOne in the Data Model class diagram
* add a new class ClassTwo in the Data Model class diagram
* add an attribute objTwo: ClassTwo to ClassOne
* add a strong aggregation between ClassOne and ClassTwo and name the TargetRole objTwo
* generate C++-sourcecode for both classes
* rename the attribute to objTwoRenamed in the sourcecode
* synchronize the sourcecode with the diagrams
* now only the attributename becomes changed not the named aggregation. So if you generate sourcecode a second time now, you'll have two attributes objTwo and ObjTwoRenamed in your code.

Couldn't you treat named aggregations internally just like another form of attributes (what they essentially are)? Perhaps with a switch in the "Model Attributes"-Section and while importing source, whitch representation should be choosen (aggregation,attribute or both).

Another annoying detail: If I delete an attribute or method in the model and synchronize with the source, the deleted elements stay in the code in the default settings. There are flags for reverse engineering in the Local Options-Dialog. Is there a similar option for forward engineering?

Greetings,
Ferdinand