Gymnasium Management System Use Cases Description (SRS)
This post is full of use case description of the Gymnasium Management System. If you want to read the case study of the project of Gymnasium Management System, then you can click here.
Use Case | Login |
Actor | Admin |
Description
|
The use case begins when the admin indicates the intent to login to the system. It ends when the actor is login or cancel login. |
Pre-Condition
|
Admin must have an internet connection
Admin is viewing the website. |
Post-Condition | The actor login successfully. |
Use Case | Login |
Actor | User |
Description
|
The use case begins when the User indicates the intent to login to the
system. It ends when the actor is login or cancel login. |
Pre-Condition
|
Users must have an internet connection.
Users must register first. The user is viewing the website. |
Post-Condition | The actor login successfully. |
Use Case | Logout |
Actor | Admin, User |
Description
|
The use case begins when the admin
and user indicate the intent to |
login to the system. It ends when the actor is
login or cancel login. |
|
Pre-Condition | Must log in first. |
Post-Condition | The actor logs out successfully. |
Use Case | Manage Members Records | |
Actor | Admin
|
|
Description
|
The use case begins when the Actor indicates the intent to view, | |
update add or delete Client records. It ends when the actor is close to this form. | ||
Pre-Condition
|
1. | The client Record must exist for view/editing/delete. |
2. | The actor is logged in. | |
Post-Condition | The client record is edited or deleted. |
Use Case | Manage Equipment Records |
Actor | Admin
|
Description
|
The use case begins when the Actor indicates the intent to view, update add or delete equipment records. It ends when the actor is closing this form. |
Pre-Condition
|
1. The Equipment Record exists for view/editing/delete.
2. The actor is logged in. |
Post-Condition | The Equipment record is edited or delete |
Use Case | View Record |
Actor | Admin |
Description | The use case begins when the admin wants to view the record. |
Pre-Condition
|
Login first.
The record exists. |
Post-Condition | The actor view record successfully. |
Use Case | Update Record |
Actor | Admin |
Description | The use case begins when the admin wants to update the record. |
Pre-Condition
|
Login first.
The record exists. |
Post-Condition | The actor updated the record successfully. |
Use Case | View Diet plan |
Actor | User |
Description | The use case begins when the user wants to view the diet plan |
Pre-Condition
|
Login first.
The record exists. |
Post-Condition | The actor viewed the diet plan successfully. |
Use Case | View Workout Videos |
Actor | User |
Description | The use case begins when the user wants to view the Workout video. |
Pre-Condition
|
You must have an internet connection.
Visit website. Videos exist. |
Post-Condition | The actor viewed videos successfully. |
Use Case | View Record |
Actor | User |
Description
|
The use case begins when the user wants to view the record.
|
Pre-Condition
|
Login first.
The record exists. |
Post-Condition | The actor view record successfully. |
Use Case | Update Record |
Actor | User |
Description
|
The use case begins when the user wants to update the record.
|
Pre-Condition
|
Login first.
The record exists. |
Post-Condition | The actor updated the record successfully. |