File:Usecase-Parent-Teacher-2 actors 5 usecases.svg
UML use case diagram with two actors (Parent-Teacher and Child) and 5 use cases.

An actor<ref name=OMG>Template:Cite book </ref> in the Unified Modeling Language (UML) "specifies a role played by a user or any other system that interacts with the subject."<ref name=OMG/>

"An Actor models a type of role played by an entity that interacts with the subject (e.g., by exchanging signals and data), but which is external to the subject."<ref name="OMG UML V2.1.2">{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>

"Actors may represent roles played by human users, external hardware, or other subjects. Actors do not necessarily represent specific physical entities but merely particular facets (i.e., “roles”) of some entities that are relevant to the specification of its associated use cases. A single physical instance may play the role of several different actors and a given actor may be played by multiple different instances."<ref name= "OMG UML V2.1.2"/>

UML 2 does not permit associations between Actors.<ref name= "OMG UML V2.1.2"/><ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref> The use of generalization/specialization relationship between actors is useful in modeling overlapping behaviours between actors and does not violate this constraint since a generalization relation is not a type of association.<ref name="UML Specification">{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>

Actors interact with use cases.

ReferencesEdit

Template:Reflist

External linksEdit

Template:UML

Template:Uml-stub