I would rather get rid of the semantic variational points of UML. A typical example that causes confusion when modeling diagrams is the point of multiple classification semantic change. When modeling generalizations in a class diagram, you can assume that the diagram allows multiple classification (an object can be an instance of two or more classes that are not related by a subtype relation) or not.
Typically, designers with background programming imply that this is not possible, although at a conceptual level, many of us tend to implicitly assume that this is possible. You can submit the result.
source
share