Author: (Name)
Email: (Email address)
Team: (Product team)
Contract: (caCORE:Contract number)
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services
Introduction
Use Cases
UC0: Use case name
This use case is the only one that is at a high level and might include stakeholders and criticality (relative priority). This user case provides context for the lower level use cases.
Use Case Description |
Definition of use case |
Primary Actor |
The primary user/role/profile or system which uses the system being built to achieve some specific goal. |
Primary Stakeholder |
Who submitted the use case and how they are involved. |
Other Stakeholders |
Others who have an interest and how they are involved. |
Expected Inputs |
For USE CASE 0, high level description of any activities immediately preceding this use case, only include as much history as relevant. |
Expected Outputs |
For USE CASE 0, high level description of any activities immediately preceding this use case, only include as much history as relevant. |
Pre-conditions |
For USE CASE 0, high level description of any activities immediately preceding this use case, only include as much history as relevant. |
Post-conditions |
Detail any activities immediately following this use case, only include as much history as relevant. |
Exception Conditions |
Detail exceptions that can occur in the Success Scenario; do not include technical implementation exceptions. All use cases are written from the user perspective. |
Related Gforge Trackers |
Links to Gforge trackers, diagrams, or related requirements documents. |
Related JUnits |
Links to Gforge trackers, diagrams, or related requirements documents. |
Related Links |
Links to Gforge trackers, diagrams, or related requirements documents. |
UC1: Use case name
Primary Actor |
The primary user/role/profile or system which uses the feature of this use case to achieve some specific goal. |
Pre-conditions |
Detail any activities immediately preceding this use case; only include as much history as relevant. |
Main Success Scenario |
Describe the main scenario if nothing fails, the "perfect case" scenario; this may contain some actions that are not immediately related to this use case but are necessary to satisfy other stakeholders. |
Post-conditions |
Detail any activities immediately following this use case, only include as much history as relevant. |
Exception Scenarios |
Detail exceptions that can occur in the Success Scenario; do not include technical implementation exceptions. All use cases are written from the user perspective. |
Related Links |
Links to Gforge trackers, diagrams, or related requirements documents. |
UCx: Use case name
Primary Actor |
The primary user/role/profile or system which uses the feature of this use case to achieve some specific goal. |
Pre-conditions |
Detail any activities immediately preceding this use case; only include as much history as relevant. |
Main Success Scenario |
Describe the main scenario if nothing fails, the "perfect case" scenario; this may contain some actions that are not immediately related to this use case but are necessary to satisfy other stakeholders. |
Post-conditions |
Detail any activities immediately following this use case, only include as much history as relevant. |
Exception Scenarios |
Detail exceptions that can occur in the Success Scenario; do not include technical implementation exceptions. All use cases are written from the user perspective. |
Related Links |
Links to Gforge trackers, diagrams, or related requirements documents. |