Actor Candidates

From EUDP
Revision as of 14:33, 10 August 2009 by Ellyk (Talk)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

What

Actor candidates

How

The dish

Actor Candidates

Ingredients

  • Preliminary use cases
  • Use Case Candidates
  • Event Candidates

Process

Consider which actors will be using the system-to-be. There are two types of actors: Users and other systems. The use case candidates might give you an idea of the different users using the system. Other systems may not be that obvious to identify unless the customer clearly expresses them.

Do not assess the candidates now. The gross list with all possible and less possible candidates is useful and is assessed when you write the use cases.

The customer can, with great success, be involved in this process, because it is actually the customer's use of the system we are trying to describe. Consult the customer with the list and get all comments relevant for the candidates. It might helpful later in the development process.

Why

In order to be open-minded and avoid assessing any possible actor candidates before actual analysis and description of the use cases in which they may participate, the developer should produce a candidate list.

By preparing the list of all possible actor candidates without assessing the individual candidate, the developer ends up with a list probably containing at least all possible candidates.

The assessment later in the analysis will eliminate the candidates not suitable for the system-to-be.

Example

House occupier

Service Technician

Production test engineer

Internet user