UML25 — Redefinition does not allow for overloading

Feature redefinitions may either be explicitly notated with the use of a

property string on the Feature or implicitly by having a Feature with the same name as another Feature in one of the owning Classifier’s more general Classifiers. In both cases, the redefined Feature shall conform to the compatibility constraint on the redefinitions.

By allowing reuse of the name to cause redefinition, you prevent overloading. A class should be allowed to more than one operation with the same name with different argument lists.

We should be more precise and require a compatible signature as well as the same name