Artifact: Business Actor


	A business actor represents a role played in relation to the business by someone or something in the business environment.
Other Relationships:	Part Of Business Use Case Model
Role:	Business Designer
Optionality/Occurrence:	Can be excluded.
Templates and Reports:	- Report: Business Actor Report -
Examples:
UML Representation:	Actor, stereotyped as <<business actor>>.
More Information:	- Guideline: Business Actor - Checklist: Business Actor - Report: Business Actor Report -


Input to Activities: - Detail a Business Use Case - Structure the Business Use-Case Model	Output from Activities: - Find Business Actors and Use Cases - Structure the Business Use-Case Model

Purpose

The following people use the business actors:

business-system analysts, when defining the boundaries of the organization;
business designers, when describing business use cases and their interaction with business actors;
user-interface designers, as input to capturing characteristics on human [system] actors;
system analysts, as input to finding [system] actors;

Properties

Property Name	Brief Description	UML Representation
Name	The name of the business actor.	The attribute “Name” on model element.
Brief Description	A brief description of the business actor’s sphere of responsibility and what the business actor needs the organization for.	Tagged value, of type “short text”.
Characteristics	Used primarily for human business actors, who will act as customers or vendors to the organization: The physical environment of the business actor, the number of individuals the business actor represents, the business actor’s level of domain knowledge, the business actor’s level of computer experience, other applications the business actor is using, and other general characteristics such as gender, age, cultural background, etc.	Tagged value, of type “formatted text”.
Relationships	The relationships, such as actor-generalizations, and communicates-associations, in which the actor participates.	Owned by an enclosing package, via the aggregation “owns”.
Diagrams	Any diagrams local to the business actor, such as use-case diagrams depicting the business actor’s communicates-associations with business use cases.	Owned by an enclosing package, via the aggregation “owns”

Timing

Business actors are found and related to business use cases early in the inception phase, when the business engineering effort is scoped.

Responsibility

A business-process analyst is responsible for the integrity of business actors, ensuring that:

Each (human) business actor captures the necessary characteristics.
Each business actor has the correct communicates-associations with the business use cases it participates with.
Each business actor is part of the correct generalization relationships.
Each business actor defines a cohesive role, and is independent of other business actors.
The local use-case diagrams describing the business actor are readable and consistent with the other properties.

Tailoring

Decide which properties to use and how to use them. In particular you need to decide at which level of detail the “Characteristics” property should be described.