Duplication of names for both 'state' and 'method'

[alicecbrown]

   Why, when duplication of names is so dangerous, are we allowed to use the same name for a method as for a state?  And this isn't information hiding at work, since both are public.  Is there a GOOD reason for this?  :-/

[sargasso]

Not that i KNOW of.

UML says nothing about a constraint of this type.  In fact, a diagram, an object, it classifier, its attributes and methods and states can all have the same name.

The uniqueness constraint has been explored in these forums before.  There still remains some unquietness in all camps regarding it.

IMO the "real" UML constraint on uniqueness is that any structural element of type "a" in a model having a name "X" refers to a unique entity in the real world.  Thus in a model with 6 diagrams/packages each containing a classifer "XXX", each of these model items is referring to the SAME real world item.

Any further delineation is handled via UML namespacing.

(Note I have succinctly and deliberately avoided ANY comment on packages v namespaces. NFCWBEI)

regards
bruce

[alicecbrown]

Further analysis of the code emerging from this design is called for, to guard against the confusion of identical names.  Hopefully, the programmer did not carry this PERCEIVED problem into the code.
by the way, we do not use EA to generate code, nor do we use the Requirements feature for traceability since we have entirely too much many to one and one to many relationships between requirements and  design.