Example: Login Use Case Specification
Course Registration System
Use-Case Specification
Login Use-Case
Version 2.0
Revision History
| Date | Version | Description | Author |
|---|---|---|---|
| 21/Dec/98 | Draft | Draft Version | S. Gamble |
| 13/Feb/99 | Version 1.0 | Minor corrections based on review | S. Gamble |
| 15/Feb/99 | Version 2.0 | Modify section on use case extends Final cleanup. Revise alternate flows. Resolve outstanding issues. | S. Gamble |
| | | |
| | | |
| | | |
Table of Contents
Login Use Case
- Brief Description
This use case describes how a user logs into the Course Registration System.
The actors starting this use case are Student, Professor, and Registrar.
2. Flow of Events
The use case begins when the actor types his/her name and password on the login form.
2.1 Basic Flow - Login
- The system validates the actor’s password and logs him/her into the system.
- The system displays the Main Form and the use case ends.
2.2 Alternative Flows
- Invalid Name / Password
If in the basic flow the system cannot find the name or the password is invalid, an error message is displayed. The actor can type in a new name or password or choose to cancel the operation, at which point the use case ends.
3. Special Requirements
There are no special requirements associated with this use case.
4. Preconditions
There are no preconditions associated with this use case.
5. Postconditions
There are no postconditions associated with this use case.
6. Extension Points
There are no extension points associated with this use case.