You are here


public class: Actor
Author: Jim Salmons
Project: Phase: 1.0; Status: Proposed; Version: 1.0; Complexity: 1
Dates: Created: 8/5/2006 1:13:03 PM; Modified: 8/6/2006 1:34:55 PM;
Flags: Active: false; IsRoot: false; IsLeaf: false;
Extension Points:
UUID: {37341C6C-630E-4c54-B044-2F9134ACD7FF}
An Actor is how we objectify a Person's or Agent's ability/perspective to "act out" a Role. Attributes such as Skill_Level, Certification, Domain_Knowledge_Level, etc. parameterize the Actor's "approach" or profile when performing the Activities of a Role.

By explicitly modeling the Actor of a Role, we provide the flexibilty to provide wide variety to a Person's state of "Being in the World." That is, for example, a Person "Joe" who is a Farmer, may be a skilled Actor of the Customer Role in a Feed Store Business_Process context, but a low skilled Actor when acting as a Customer in a New York City Art Gallery Business_Process context. Farmer "Jane," on the other hand, may be skilled in both domains. Or in another example, Person "Fred" may not be able to be considered in the pool of Actors for a House Sale Business_Process if his associated Realtor Actor does not have an up-to-date license.

The main point here is that by having a Person be an Actor of Roles gives us great flexibility in building specific instances of the LFEGame model. One Person can have a collection of Actors that represent the profile of how that Person can be/perform in the world. This keeps us from having to add loads of attribute and behavior complexity to the Person object. In this sense, the LGEGame metamodel reflects the distinction we make between Being and Doing.

Goto: Custom Properties

See also: Role, Who's In Charge?

Appears in: Logical View

Custom Properties