Task: Find and Outline Requirements
This task describes how to capture the requirements for the system.
Disciplines:  Requirements
Purpose
The purpose of this task is to understand stakeholder needs and communicate these needs to the development team.
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory: Optional:
  • None
Outputs
Steps
Gather information

Various techniques can be used to facilitate requirements gathering as described in Guideline: Requirements Gathering Techniques.

Identify and capture domain terms
Make sure that ambiguous, or domain-specific terms have a clear definition in the  Glossary and that these terms are used consistently.
Capture requirements
Identify the types of requirements relevant to your system. (see Concept: Requirements).

Capture the actors and use cases.  See Guideline: Find and Outline Actors and Use Cases for more information.

Capture the other types of requirements relevant to your system.  See Guideline: Supporting Requirements for more information.

Capture Use Case and Actors in a Use-Case Model

While capturing requirements, it may be useful to identify and capture Use Case and Actor in a Use-Case Model, helping to better understand proposed system functionality and its surroundings. See Guideline: Find and Outline Actors and Use Cases for more details.

Achieve concurrence
A review of the requirements is conducted with relevant Stakeholders to ensure agreement, assess quality, and/or identify changes required.  See  Guideline: Effective Requirement Reviews for more information.
Update the work items list
Capture references to the requirements in the Artifact: Work Items List, so work can be prioritized.
More Information