UML standar for class diagram

Hi Diego,

we do a new object of type attribute for every Class-Attribute. This is not very comfortable but I don't know or see an alternative....

BR Gerald

Hi Gerald

Thanks again for the answer. This is the way I was doing it, but I think there is another way.

Regards

Hi Diego,

take a look at chapter 3.25 of your cited specification. You will notice, that each attribute bears quite a few properties (e.g. visibility, name, type, ordering, initial value). It would be very difficult to realize all that information on the class the attribute belongs to. Of course you could put it all in a string as suggested by the spec, but do you want to maintain that...? And when you want to do anything sensible with the attribute, the parsing starts...

Regards.

Hi Diego,

as Mr. Zschuckelt expressed between his lines: ARIS strictly implements the UML specification and not some proprietary vendor specific notation. Despite the fact there are 100+ so called "UML" tools on the market, I am only aware of 3 other UML tools strictly implementing the UML specification.

The advantage is you get the full expression power of UML. But actio est reactio. Consequently the natural downside of this approach is: you have to deal with the full UML complexity.

Best regards

Carsten

Hi M. Zschuckelt

I want to do something like the representation show in  the page 3-46, when you can see that BurglarAlarm have an attribute call isTripped and it's type. I want to see the attribute inside the class, not as an independent object. That's what I need to do. Thanks for the help and hints.

Regards

Hi Diego,

in the original pst you referenced the UML 1.4 specification. ARIS 9.x is at least UML 2.4.1 compliant, nor sure it fully supports UML 2.5 yet.

But nevertheless something as trivial as the BurglarAlarm example should also work with UML 2.4.1 and 2.5.

Best regards

Carsten

I have also got required information from here.