Use Case Descriptions of SHOPPING MALL MANAGEMENT SYSTEM Project
If you are interested to read the SRS of the project, then click here for the details case study.
| Use Case | Register |
| Actor | Customer |
| Description | The use case begins when the actor indicates the intent to login to the system. It ends when the actor is logged in or cancels login. |
| Pre-Condition | The login exists. |
| Post-Condition | The actor logs in successfully. |
| Use Case | Login |
| Actor | Administrator/User |
| Description | The use case begins when the actor indicates the intent to login to the system. It ends when the actor is logged in or cancels login. |
| Pre-Condition | The login exists |
| Post-Condition | The actor logs in successfully. |
| Use Case | View Shops |
| Actor | Customer/User |
| Description | The use case begins when the actor indicates the intent to view Shops record. It ends when the actor closes the Shops form. |
| Pre-Condition | 1-The Shops record exists for view.
2-The actor is logged in |
| Post-Condition | The Shops record is Viewed. |
| Use Case | Booking for Shops |
| Actor | Customer/User |
| Description | The use case begins when the actor indicates the intent to Book the shops. It ends when the actor closes the Shops Apply form. |
| Pre-Condition | 1-The Shops record exists for Booking. 2-The actor is logged in |
| Post-Condition | The actor easily books shops. |
| Use Case | Payments details |
| Actor | Customer/User |
| Description | The use case begins when the actor indicates the intent to add payment details for shops. It ends when the actor closes payment form. |
| Pre-Condition | 1-The shops record exists for booking.
2-The actor is logged in. |
| Post-Condition | The actor easily gives information related to accounts. |
| Use Case | Receives Payments Receipts |
| Actor | Customer/User |
| Description | The use case begins when the actor indicates the intent to get payment receipts details for shops. It ends when the actor closes the payment form. |
| Pre-Condition | 1-The shop’s record exists for booking.
2-The actor is logged in. |
| Post-Condition | The actor easily gets receipts related to accounts. |
| Use Case | View shops Records |
| Actor | Administrator |
| Description | The use case begins when the actor indicates the intent to view or edit Monthly record. It ends when the actor closes the form. |
| Pre-Condition | 1-The shops record exists for editing/view.
2-The actor is logged in. |
| Post-Condition | The Record viewed successfully. |
| Use Case | Add shops Records |
| Actor | Administrator |
| Description | The use case begins when the actor indicates the intent to add or edit record. It ends when the actor closes the add form. |
| Pre-Condition | 1-The shops record exists for editing/Adding. 2-The actor is logged in. |
| Post-Condition | The Record added successfully. |
| Use Case | Delete shops Records |
| Actor | Administrator |
| Description | The use case begins when the actor indicates the intent to Delete or edit a record. It ends when the actor closes the delete form. |
| Pre-Condition | 1-The shop’s record exists for editing/Deleting.
2-The actor is logged in. |
| Post-Condition | The Record Deleted successfully. |
| Use Case | Update shops Records |
| Actor | Administrator |
| Description | The use case begins when the actor indicates the intent to update or edit the record. It ends when the actor closes the update form. |
| Pre-Condition | 1-The shops record exists for editing/updating.
2-The actor is logged in. |
| Post-Condition | The Record updated successfully. |
| Use Case | View accounts records |
| Actor | Administrator |
| Description | The use case begins when the actor indicates the intent to view the Transaction’s record. It ends when the actor closes the Ledgers form. |
| Pre-Condition | 1-The Transaction record exists for view.
2-The actor is logged in. |
| Post-Condition | The account record is viewed successfully. |
| Use Case | View Clients records |
| Actor | Administrator |
| Description | The use case begins when the actor indicates the intent to view the clients’ record. It ends when the actor closes the Clients form. |
| Pre-Condition | 1-The clients’ record exists for view.
2-The actor is logged in. |
| Post-Condition | The client record is viewed successfully. |
| Use Case | View Clients records |
| Actor | Administrator |
| Description | The use case begins when the actor indicates the intent to delete the clients’ record. It ends when the actor closes the Clients form. |
| Pre-Condition | 1-The clients’ record exists for delete.
2-The actor is logged in. |
| Post-Condition | The client record is deleted successfully. |
If you are interested to read the SRS of the project, then click here for the details case study.
