Pointers, Lists and Vectors attribute names necessary in the UML diagram? -


i have short question:
should name attributes of types list, arrays, vectors or pointers objects (not primitive type) in uml diagram or association/aggregation/composition arrows enough?

example: of these diagrams correct?

enter image description here

or

enter image description here

in uml, second diagram correct if wrote property names @ far ends of associations. while uml properties allowed unnamed, not practice. use association ends indicate why relationship exists. more 1 association must exist between 1 pair of classes, different reasons. how tell them apart?

the first diagram shows 2 properties of each type. 1 named , (at end of each association) unnamed. incorrect.


Comments

Popular posts from this blog

c++ - llvm function pass ReplaceInstWithInst malloc -

java.lang.NoClassDefFoundError When Creating New Android Project -

Decoding a Python 2 `tempfile` with python-future -