• [Technical Specification]

• Use-Case Model

• Analyst

• Analyst

• Detail Use-Case Scenarios

• Detail System-Wide Requirements

• Create Test Cases
• Design the Solution
• Implement Solution
• Outline the Architecture
• Plan Project
• Refine the Architecture

• Assess Results
• Identify and Outline Requirements
• Plan Iteration

• Detail Use-Case Scenarios
• Identify and Outline Requirements

• Implement Solution

A use case typically includes the following information:

• Name: The name of the use case.
• Brief Description: A brief description of the role and purpose of the use case.
• Flow of Events: A textual description of what the system does in regard to a use case scenario (not how specific problems are solved by the system). The description is understandable by the customer.  The flows can include a basic flow, alternative flows, and subflows.
• Key scenarios: A textual description of the most important or frequently discussed scenarios.
• Special Requirements: A textual description that collects all requirements, such as non-functional requirements, on the use case, that are not considered in the use-case model, but that need to be taken care of during design or implementation.  
• Preconditions: A textual description that defines a constraint on the system when the use case may start.    
• Post conditions: A textual description that defines a constraint on the system when the use cases have terminated.   
• Extension points: A list of locations within the flow of events of the use case at which additional behavior can be inserted using the extend-relationship.   

• Use-Case Specification

• Use-Case Specification

The use case can be documented as just a use-case specification document, or can be incorporated in a use-case model.  Use cases, and parts of use cases, can also be captured in a requirements management tool.

• Use Case

• Use Case