Source: Personal ( Thomas Owens)
It is very confusing to understand that an Actor may be a generalization of another Actor on a Use Case model of a system. An example of this is not provided in Section 18. To understand this, you need to trace up and back down the document and understand Actor, BehavioredClassifier, Classifier, Generalization, DirectedRelationship, Relationship, Association to see that a Generalization is not an Association.
In section 220.127.116.11, the UML specification states: "An Actor can only have Associations to UseCases, Components, and Classes. Furthermore these Associations
must be binary."
In Section 18.104.22.168, the same document states that an Actor is a BehavioredClassifier. A BehavioredClassifier is also a Classifier.
Section 22.214.171.124 defines the association ends for a Classifier. One of these relationships is Generalization.
Section 9.9.7 defines the Generalization relationship. The generalization of a Generalization is a DirectedRelationship.
Section 7.8.5 defines DirectedRelationship. The generalization of a DirectedRelationship is a Relationship.
Section 7.8.15 defines the Relationship abstract class. The specializations of Relationship are DirectedRelationship and Association.
Reported: UML 2.5 — Wed, 28 Dec 2016 16:58 GMT
Updated: Thu, 29 Dec 2016 16:32 GMT