Use case template
The following is a requirements template developed by Alistair Cockburn. This template may or may not have all or more fields related to the requirements itself.
Recommended reading:
| USE CASE #N | <The name of the goal as a short active verb phrase> |
|---|---|
| Goal in context | <A longer statement of the goal in context if needed> |
| Scope | <What system is being considered back box under design> |
| Level | <one of: Summary, Primary task, Subfunction> |
| Preconditions | <what we expect is already the state of the world> |
| Success end condition | <the state of the world upon successful completion> |
| Failed end condition | <the state of the world if goal abandoned> |
| Primary actor | <a role name for the primary actor, or description> |
| Trigger | <the action upon the system that starts the use case, may be time event> |
| Priority | <how critical to your system/organization> |
| Frequency | <how often it is expected to happen> |
Usage example:
User profile#
| USE CASE #1 | Create user account |
|---|---|
| Goal in context | Client expects to create and account |
| Scope | User account system |
| Level | Primary task |
| Preconditions | User model exists and ready to save new users |
| Success end condition | User gets account created and receives a notification upon creation |
| Failed end condition | Unable to create user |
| Primary actor | User |
| Trigger | Invocation of user creation |
| Priority | Top priority |
| Frequency | Common, users create new account from time to time |