Some Use Cases and scenarios may need to be described in more detail to validate our understanding of the requirement and to permit software development to begin. This does not imply that all use cases and scenarios will be detailed prior to commencing implementation. Collaborate with stakeholders to detail only those that are prioritized for implementation in the next iteration or two (see Artifact: Iteration Plan), or those that are deemed architecturally significant (see Concept: Architecturally Significant Requirements).

The level of detail captured will vary depending upon the needs of the project and the complexity of the use case. For a discussion of the different levels of detail that may be applicable see Guideline: Use Case Formats.

Capture the use-case details in Artifact: Use Case. For additional information on detailing use cases and scenarios, see Guideline: Detail Use Cases and Scenarios. For assistance in assessing the quality of the use cases see Checklist: Use Case.

Some Supporting Requirements Specification may need to be clarified or described in more detail, new requirements may have been discovered as we detailed the use cases and scenarios, and new requirements may have been submitted as Change Requests. Collaborate with stakeholders to capture, refine and validate those requirements that will have an impact on near term work (see Artifact: Iteration Plan) or are deemed architecturally significant (see Concept: Architecturally Significant Requirements).

Capture these requirements in the Artifact: Supporting Requirements Specification.  For additional guidance on detailing supporting requirements see Guideline: Supporting Requirements. For assistance in assessing the quality of your supporting requirements see Checklist: Supporting Requirements.