Use Cases Description of Real Estate Management System Project
This tutorial covers the Use Cases Description of Real Estate Management System Project. If you are interested to read the functional requirement of the given case study, then you can click here.
| Use Case | Register |
| Actor | Admin/User |
| Description | The use case begins when the actor
indicates the intent to register to the system. It ends when the actor is registered or cancels the registration. |
| Pre-Condition | The register exists |
| Post-Condition | The actor registered successfully |
| Use Case | Login |
| Actor | Admin/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 form exists |
| Post-Condition | The actor logs in successfully |
| Use Case | Manage user profile |
| Actor | Seller/buyer |
| Description | The use case begins when the actor
indicates the intent to view, update or delete profile. It ends when the actor closes the user_dashboard form. |
| Pre-Condition | 1-The user_dashboard record exists for
editing/view. 2-The actor is logged in
|
| Post-Condition | The user_dashboard record is added or
updated. |
| Use Case | Manage Property |
| Actor | Seller |
| Description | The use case begins when the actor
indicates the intent to view, update, add or delete his/her own property. It ends when the actor closes Add_Property form. |
| Pre-Condition | 1-The actor record exists for
editing/view. 2-The actor is logged in. |
| Post-Condition | The actor record is updated. |
| Use Case | Add property |
| Actor | Seller |
| Description | The use case begins when the actor
indicates the intent to add property. It ends when the actor added the property or exit the add property form. |
| Pre-Condition | 1-The add property form exists for
adding property. 2-The actor is logged in. |
| Post-Condition | The seller added property successfully. |
| Use Case | Add property |
| Actor | Seller |
| Description | The use case begins when the actor
indicates the intent to add property. It ends when the actor added the property or exit the add property form. |
| Pre-Condition | 1-The add property form exists for
adding property. 2-The actor is logged in. |
| Post-Condition | The seller added property successfully. |
| Use Case | Add property |
| Actor | Seller |
| Description | The use case begins when the actor |
| indicates the intent to add property. It | |
| ends when the actor added the property | |
| or exit the add property form. | |
| Pre-Condition | 1-The add property form exists for |
| adding property. | |
| 2-The actor is logged in. | |
| Post-Condition | The seller added property successfully. |
| Use Case | Bidding |
| Actor | Buyer |
| Description | The use case begins when the actor |
| indicates the intent to bid for the property. | |
| It ends when the actor bid or cancel the | |
| bidding. | |
| Pre-Condition | 1-The bided property exist for bidding. |
| 2-The actor is logged in. | |
| Post-Condition | The bidding is done successfully. |
| Use Case | Ask Question |
| Actor | User/buyer/seller |
| Description | The use case begins when the actor
indicates the intent to ask a question. It ends when the actor closes the query form. |
| Pre-Condition | The query form exists for asking a question. |
| Post-Condition | The question is asked successfully. |
| Use Case | Search Property |
| Actor | User/buyer |
| Description | The use case begins when the actor
indicates the intent to search for the property according to his/her requirement. It ends when the result is shown. |
| Pre-Condition | The searching form exists for searching. |
| Post-Condition | The property searched successfully. |
