Use Case Description of Hajj Umrah Management System Project
Let’s see the Use Case Description of the Hajj Umrah Management System Project. If you are interested to read the case study and SRS of the project in detail, then click here.
| Use Case | Sign in |
| Actor | Administrator |
| Description | The use case begins when the actor indicates the intent to sign in to the system. It ends when the actor is signed in or cancels sign in. |
| Pre-Condition | The sign in exists |
| Post-Condition | The actor signs in successfully |
| Use Case | Enter the Client’s Details |
| Actor | Administrator |
| Description | The use case begins when the actor indicates the intent to enter the details of the customers, It ends when the actor submit details or closes the client’s info form. |
| Pre-Condition | The customer has given their proper details for the booking |
| Post-Condition | The Client’s details are stored in the database |
| Use Case | Enter Package Information |
| Actor | Administrator |
| Description | The use case begins when the actor indicates the intent to enter the values of the customer’s Package Requirements. It ends when the actor submits details or closes the Package form. |
| Pre-Condition | 1-Customer having a valid Passport 2-Actor having details of the customer’s requirements. |
| Post-Condition | The user’s record is added or updated. |
| Use Case | Enter Payment Details |
| Actor | Administrator |
| Description | The use case begins when the actor indicates the intent to enter the values of the customers’ Payment Method. It ends when the actor submits details or closes the payment form. |
| Pre-Condition | 1-At least 50% Amount Paid |
| Post-Condition | The amount of details are stored in the database. |
| Use Case | Manage Client’s Data |
| Actor | Administrator |
| Description | The use case begins when the actor indicates the intent to add, update, delete or edit the Customer’s record. It ends when the actor closes the Records form. |
| Pre-Condition | 1-The customer’s record exists for editing/view.
2-The actor is logged in. |
| Post-Condition | The customer’s record is added or updated. |
| Use Case | Manage Package Details |
| Actor | Administrator |
| Description | The use case begins when the actor indicates the intent to add, update, delete or edit the Customer’s Package. It ends when the actor closes the Package form. |
| Pre-Condition | 1-The customer’s record exists for editing/view.
2-The actor is logged in. |
| Post-Condition | The customer’s record is added or updated. |
| Use Case | Manage Package Details |
| Actor | Administrator/Customer |
| Description | The use case begins when the actor indicates the intent to add, update, delete or edit the Packages. It ends when the actor closes the Records form. |
| Pre-Condition | 1-The customer’s package record exists for editing/view.
2-The actor is logged in. |
| Post-Condition | The customer’s record is added or updated. |
| Use Case | Invoice |
| Actor | Administrator/Customer |
| Description | The use case begins when the actor indicates the intent to generate a print out of the invoice. |
| Pre-Condition | 1-All the payment is paid.
2-Record exists in the database in order to generate a printout |
| Post-Condition | The print out of the invoice is generated successfully and can be viewed by the admin and the customer. |
Hajj Umrah Management System Project SRS Download
If you are interested to read the case study and SRS of the project in detail, then click here.