link between two atributes (PleaseHelp)

[futuros]

Hi,

it is possible to create link between two attributes of two different classes ? (Something ling association link between two classes)

thank you very very much

[thomaskilian]

You could use a Dependency <<trace>> between the classes and name the ends accordingly. But there is no way to draw direct relations between ops/attrs.

[futuros]

thanks,

so it seems that EA is not propriate analysis tool for DWH. Maybe in future will

[Bruno.Cossi]

Hi,

not sure if this is quite what you want, but here goes: draw an association between the two classes, then go to the association's properties and look at the tabs Source Role and Target Role. In the dropdwon for role, there is list of the classes' attributes, just select the ones you want.

Hope this helps!
Bruno

Hi,

it is possible to create link between two attributes of two different classes ? (Something ling association link between two classes)

thank you very very much

[robH]

Darn it - you beat me to it Bruno.

And just to add that this is the way that the other UML tools (RSA, Artisan, Tau etc) achieve this result....so don't give up on EA yet...it really is a most fantastic tool - in fact its a fun tool too and its not often you can say that....and for what you pay it's unheard of value for money (even better than ASDA)

p.s. ASDA is a UK supermarket that brands itself on value for money for those of you that didn't know ;-)

[Bruno.Cossi]

For those on the other side of the big pond, ASDA = WalMart :-) But feature-wise, EA is more like.... Harrods, maybe :-)

Darn it - you beat me to it Bruno.

And just to add that this is the way that the other UML tools (RSA, Artisan, Tau etc) achieve this result....so don't give up on EA yet...it really is a most fantastic tool - in fact its a fun tool too and its not often you can say that....and for what you pay it's unheard of value for money (even better than ASDA)

p.s. ASDA is a UK supermarket that brands itself on value for money for those of you that didn't know ;-)

[brazem]

I was looking for a solution for this problem.  But I think I found a bug in EA:

I would expect that in the drop-down for role, I would see attribute names for the appropriate classes.  Both tab drop-downs ("Target / Source") always show the same role names (which come from the source table).

We were hoping to use this to relate attributes between logical / physical models for a legacy COBOL-LIKE application reverse engineering exercise.

Although we can type in column names manually, it is majorly inconvenient to do so.  

Is this a bug?  Will there be a fix coming soon?  

[Bruno.Cossi]

Hi,

just to make sure I understand it properly: you have two tables, you draw an association between them and on the association's properties in both the Source and Target tabs the Role dropdown includes list of something (what?) from one of the tables, the source one. Neither Source or Target tabs lists anything (list of attributes or keys/operations) from the Target table.

Is this correct?

Bruno

I was looking for a solution for this problem.  But I think I found a bug in EA:

I would expect that in the drop-down for role, I would see attribute names for the appropriate classes.  Both tab drop-downs ("Target / Source") always show the same role names (which come from the source table).

We were hoping to use this to relate attributes between logical / physical models for a legacy COBOL-LIKE application reverse engineering exercise.

Although we can type in column names manually, it is majorly inconvenient to do so.  

Is this a bug?  Will there be a fix coming soon?  

[brazem]

The Role DropDown includes list of attributes from Source Class.  I would expect for Role DropDown on Source Tab to list Attributes from Source Class and for Role DropDown on Target Tab to list Attributes from Target Class (or vice versa).

Of course, this implies that source & target class have different attributes.

I would not expect, however for role dropdown to contain the same attributes on both tabs.

[Eve]

The role dropdown works correctly for me.

The target role is filled with all the source attributes (Because the target role represents an attribute in the source class) and vice versa.

[brazem]

OK... had to figure out why it did not work for me.

It works fine if both entities are classes.  However, If I pick the "TABLE" construct for one entity, and the class construct for the other, then I can replicate the behavior.

[Weedman]

Can anyone tell me how to link GUI Elements in the user interface view to attributes of a class (ie boundary class)?

Thanks

[thomaskilian]

Try using a named association.