Work Product Descriptor (Artifact): Business Actor
Business Actors are high-level conceptualizations of the Actors with the system; further analysis is required to fully understand and define required actors.
Relationships
Container Artifact
Main Description

A Business Actor can be equated to the external people or systems that interact with the system under study. Actors are not necessarily external to the business; they may also represent internal “user” interactions with the system. Business Actors are high-level conceptualizations of the Actors with the system; further analysis is required to fully understand and define required actors. Note that actors are not individuals nor are they necessarily equivalent to job titles; instead, they describe the behavior in the enterprise and the responsibilities of the associated “user”.

Properties
Optional
Planned
Key Considerations

Actors are a categorization, based upon required interactions, of external interactions with the system. At the business level they represent the external entities that interact with the system, be they users or other systems. 

In addition to IT Architects, the following people are interested in actors:

  • Business analysts, when defining the boundaries of the organization and required processes;
  • Business designers, when describing business processes and their interaction with external entities;
  • User-interface designers, as input to capturing characteristics on human [system] actors;
  • System analysts, as input to finding [system] actors;
Tailoring
Representation Options

Business Actors are high-level conceptualizations of the Actors with the system; further analysis is required to fully understand and define required actors.

UML Representation: «stereotype» BPL_Actor

Extends: «metaclass» Actor

It has the following properties:

  • id: string - This attribute is used to uniquely identify elements.
  • name: string - A descriptive name for the Actor.
  • characteristics: string - A business level description of the actor and what it represents. Specifics in terms of people, jobs or systems should be avoided at this point—keep it technical. 
Constraints
  • Must be named;
  • Can only have associations to Business Roles. Furthermore these associations must be binary;
  • Shall aggregate at least one associated Business Role;
  • Allowed to have (derived) associations with Business Entities (through associated business roles);
  • Allowed to have (derived) associations with Business Activities (through associated business roles).
More Information