• Use-Case Model

• Requirements Specifier

• System Analyst

• Capture a Common Vocabulary
• Design the User Interface
• Prototype the User-Interface
• Review Requirements

• Find Actors and Use Cases

• Analysis & Design  >  Analyze Behavior  >  Actor
• Analysis & Design  >  Analyze Behavior  >  Actor
• Requirements  >  Analyze the Problem  >  Actor [preliminary] [preliminary]
• Requirements  >  Understand Stakeholder Needs  >  Actor
• Requirements  >  Define the System  >  Actor
• Requirements  >  Manage Changing Requirements  >  Actor

In creating this artifact, you should consider various aspects of the artifact including the following:

• the different interest groups or stakeholders who may have requirements to contribute
• the different requirement types (categories, dimensions) that need to be considered
  

• Actor Report -

The actor may have the following properties:

• Name: The name of the actor.
• Brief Description: A brief description of the actor's sphere of responsibility and what the actor needs the system for. 
• Characteristics: For human actors: The physical environment of the actor, the number of users the actor represents, the actor's level of domain knowledge, the actor's level of computer experience, other applications the actor is using, and other general characteristics such as gender, age, cultural background, and so on. 
• Relationships: The relationships, such as actor-generalizations, and communicates-associations in which the actor participates. 
• Diagrams: Any diagrams local to the actor, such as use-case diagrams depicting the actor's communicates-associations with use cases. 

Decide which properties to use and how to use them. In particular, you need to decide at which level of detail the "Characteristics" property needs to be described.

• Actor

• Requirements
• Types of Requirements

• Actor