Task Descriptor: Find and Outline Requirements
Capture and describe the requirements for the system to be.
Based on Method Task:  Find and Outline Requirements
Relationships
RolesMain: Additional: Assisting:
InputsMandatory: Optional:
  • None
External:
  • None
Outputs
Steps
Gather information

Information is initially gathered when the vision for the system to be is being defined (see Task: Define Vision for more details). Various techniques can be used to facilitate requirements elicitation. For that, consider to conduct a workshop, as described in Guideline: Requirements Gathering Techniques.

Identify and capture domain terms
Make sure that each term used in brief descriptions of actors and use cases has a clear definition in the Glossary and it is used consistently in those descriptions.
Capture requirements

Capture the various types of  requirements (see Concept: Requirements) as part of the Work Items List, so work can be prioritized and assigned to team members:

  • Use Case and Scenarios have their description captured in this list, but may be detailed in a separate document as needed.
  • Supporting Requirements can be captured in this list, but can be detailed or make reference to external supplemental documents as necessary.
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.
Properties
Multiple Occurrences
Event-Driven
Ongoing
Optional
Planned
Repeatable