Task: Detail Requirements
Detail the requirements for the system to be.
Discipline:  Requirements
Purpose

The Use Case is described in sufficient detail -- to the understanding and satisfaction of the actor representative or customer -- in order to enable software development to begin.

Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory: Optional:
  • None
Outputs
Steps
Detail Use Cases and scenarios

Some requirements, like Artifact: Use Case and Scenarios may need to be described in more details. Separate documents coexist with the Artifact: Work Items List; this list has a simplified description of the Artifact: Use Case or Scenario, and optionally a pointer to the actual document describing these. See Guideline: Detail Use Cases and Scenarios for more information.

Detail Supporting Requirements
Some requirements may need to be described in more detail. The Artifact: Supporting Requirements may coexist with the Artifact: Work Items List.  The latter provides a simplified description of the requirements, and optionally a pointer to the Artifact: Supporting Requirements.
Detail glossary terms
Review the use case flow of events. If information is exchanged, be specific about what is passed back and forth and make sure that this information is defined in the Glossary. If necessary refine applicable attributes for domain terms or elementary data items.
Achieve concurrence
A review of the requirements (Artifact: Use Case and Artifact: Supporting Requirements) is conducted with relevant Stakeholders to ensure agreement, assess quality, and/or identify changes required.  See Guideline: Effective Requirement Reviews for more information.
More Information