actor [English]

Syndetic Relationships

InterPARES Definition

n. ~ PaaST (Actor) · An entity that interacts with a preservation environment using any capabilities defined in the PaaST requirements.

General Notes

An actor may be a person or a system. There are four predefined ways an actor may participate in activities that implement PaaST requirements. 1. Performer: an entity actively involved in executing one or more preservation capabilities – 2. Authorizer: an entity whose approval is needed for an action to be executed in specified circumstances. – 3. Problem resolver: an entity responsible for resolving a problem that occurs in preservation activities. – 4. Approver: an entity who determines if the outcome of an action, including resolution of any problems, is acceptable. Other roles might be defined to satisfy particular circumstances.

Other Definitions

Citations

  • OMG UML 2.5 (†861 ): An Actor models a type of role played by an entity that interacts with the subjects of its associated UseCases (e.g., by exchanging signals and data). Actors may represent roles played by human users, external hardware, or other systems. ¶·NOTE. An Actor does not necessarily represent a specific physical entity but instead a particular role of some entity that is relevant to the specification of its associated UseCases. Thus, a single physical instance may play the role of several different Actors and, conversely, a given Actor may be played by multiple different instances. (†2483)
  • PaaST (0.11) 2016 (†778 p. 9): Role type: An enumeration that lists the possible roles an Actor may have in execution of a Preservation Action or PreservationRule. (†2479)
  • PaaST (0.11) 2016 (†778 p. 12): An Actor is a role played by an entity that interacts with a Preservation Environment using any capabilities defined in the PaaST requirements. An Actor will often be a person but could be an external system. A person acting in one or more of the capacities defined in section 3.1, may perform actions that would qualify them as Actors, but many actions entailed by these capabilities are external to the Preservation Environment. Such actions include defining, implementing, managing, overseeing and evaluating preservation, rather than carrying it out. In contrast, Actor is a class in the PaaST data model and is specifically referenced in the requirements. (†2480)
  • PaaST (0.11) 2016 (†778 p. 12): There are four predefined ways an Actor may participate in activities that implement PaaST requirements. · Performer: an entity actively involved in executing one or more preservation capabilities, · Authorizer: an entity whose approval is needed for an action to be executed in specified circumstances. · Problem Resolver: an entity responsible for resolving a problem that occurs in preservation activities, and · Approver: an entity who determines if the outcome of an action, including resolution of any problems, is acceptable. Other roles might be defined to satisfy particular circumstances, in accordance with the AttributableClass (†2481)
  • PaaST (0.11) 2016 (†778 p. 14): An Actor is a person or an external system that participates in one or more actions; however, a PreservationAction does not necessarily involve any Actor. Some actions may be executed automatically. Actor is associated with PreservationAction by the association class, Participation, which 17 specifies how the Actor participates in the action. (†2482)
  • PaaST (1.0) 2017 (†860 p. 12): Following the description of Actor in UML Use Cases, an Actor is a role played by an entity that interacts with a Preservation Environment using any capabilities defined in the PaaST requirements. An Actor will often be a person but could be an external system. A person acting in one or more of the capacities defined in [PaaST], may perform actions that would qualify them as Actors, but many actions entailed by these capabilities are external to the Preservation Environment. Such actions include defining, implementing, managing, overseeing and evaluating preservation, rather than carrying it out. In contrast, Actor is a class in the PaaST data model and is specifically referenced in the requirements. (†2438)
  • PaaST (1.0) 2017 (†860 p. 12): There are four predefined ways an Actor may participate in activities that implement PaaST requirements. · Performer: an entity actively involved in executing one or more preservation capabilities, · Authorizer: an entity whose approval is needed for an action to be executed in specified circumstances. · Problem Resolver: an entity responsible for resolving a problem that occurs in preservation activities, and · Approver: an entity who determines if the outcome of an action, including resolution of any problems, is acceptable. ¶ Other roles might be defined to satisfy particular circumstances, in accordance with the AttributableClass concept described in section above. (†2440)