1 Introduction
Our project is Online Billing System for Lahore Electric Supply Company in which residents can
pay bills, sign for complaint and administrator can view, upload the bills and can edit
information of residents as well. Administrator will register the bill credentials and manage the
accounts of residents.
1.1 Use case Description
<UC_01>Use case Name: Login by Administrator
Primary Actor: Administrator
Brief Description:
This use case allows administrator to make login in order to perform the desired and available
operations in the website. It checks and authenticates the administrator information; provided
at the time of registration. This use case also defines the limitation and access area of the
administrator.
Pre-Condition:
● Administrator must be registered and have an ID and password
Basic Flow:
1. Administrator enters the ID and password in the fields on the web page
2. System verifies the administrator
3. System displays the relevant page
Alternate Flow:
1a. Administrator does not enter the email ID or password
1. System displays the error message
2a. Administrator enters incorrect email ID and password
1. System displays the error message
Post Condition:
1. Administrator must be granted access
<UC_02>Use case Name: User Registration
Primary Actor: Resident
Brief Description:
This use case allows residents to log in to their account on the system.
Pre-Condition:
The resident has access to the internet and a valid email address.
Basic Flow:
1. The resident clicks on the "Login" button.
2. The system displays the login form.
3. The resident enters their email address and password.
4. The resident submits the login form.
5. The system verifies the information and logs in the resident.
6. The system displays the resident's account dashboard.
Alternate Flow:
4a. If the email address or password is incorrect, the system displays an error message and
prompts the resident to enter the correct information.
Post Condition:
1. The resident is logged in to their account on the system.
2. System makes the changes in database
<UC_03>Use case Name: Edit Account Information
Primary Actor: Resident
Brief Description:
This use case allows residents to edit their personal information on the system.
Pre-Condition:
The resident is logged in to their account on the system.
Basic Flow:
1. The resident clicks on the "Edit Account" button.
2. The system displays the account edit form.
3. The resident makes changes to their personal information.
4. The resident submits the account edit form.
5. The system verifies the information and updates the resident's account.
Alternate Flow:
3a. If the information is incomplete or incorrect, the system displays an error message and
prompts the resident to correct the information.
Post Condition:
1. The resident's personal information is updated on the system.
<UC_04>Use case Name: Manage user
Primary Actor: Administrator
Brief Description:
It allows administrator to delete and manage the user’s account
Pre-Condition:
1. Administrator is log in
Basic Flow:
1. Administrator search the user
2. System displays the user’s profile
3. Administrator deletes the user’s account
Alternate Flow:
1. User does not exist
2. System displays the error message
Post Condition:
1. Administrator receives a success message from the system
2. System makes the changes in database
<UC_05>Use case Name: Upload Bill Credentials
Primary Actor: Administrator
Brief Description:
This use case allows administrator to upload their bill credentials required for the billing process
on the system.
Pre-Condition:
The administrator is logged in to their account on the system.
Basic Flow:
1. The administrator clicks on the "Upload Bill" button.
2. The system displays the bill credentials upload form.
3. The administrator uploads the bill credentials required for the billing process.
4. The administrator submits the bill credentials upload form.
5. The system verifies the information and updates the administrator’s account.
Alternate Flow:
3a. If the bill credentials are incomplete or incorrect, the system displays an error
message and prompts the resident to correct the information.
Post Condition:
The administrator’s bill credentials are uploaded on the system.
<UC_06>Use case Name: Pay Bill
Primary Actor: Resident
Brief Description:
This use case allows the resident to pay their electricity bill online using the system.
Pre-Condition:
The resident must have an account on the system with a bill due for payment.
Basic Flow:
1. The resident logs into their account on the system.
2. The system displays the resident's current bill.
3. The resident selects the payment option (Mobile Wallet/Bank Transfer) and confirms the
payment.
4. The system processes the payment and updates the resident's account with the payment
information.
5. The system sends a confirmation email to the resident with the payment details.
Alternate Flow:
If the payment fails, the system displays an error message and prompts the resident to try
again with a different payment option.
Post Condition:
If the payment fails, the system displays an error message and prompts the resident to try again
with a different payment option.
<UC_07>Use case Name: View Bill
Primary Actor: Job Seeker
Brief Description:
This use case allows the resident to view their electricity bill online using the system.
Pre-Condition:
The resident must have an account on the system with at least one bill available for viewing.
Basic Flow:
1. The resident logs into their account on the system.
2. The system displays the resident's current bill.
3. The resident can view the bill details, such as billing period, usage, and charges.
Alternate Flow:
If there are no bills available for the resident, the system displays a message indicating
that no bills are available.
Post Condition:
The resident has successfully viewed their electricity bill online using the system
<UC-08>Use case Name: Tariff and Tax Management
Primary Actor: Employee
Brief Description:
This use case allows the employee to manage the tariff rates and taxes that apply to electricity
bills.
Pre-Condition:
1. The employee must have an account on the system with appropriate permissions to
manage the tariff rates and taxes.
2. There must be at least one resident with an outstanding electricity bill.
Basic Flow:
1. The employee logs into their account on the system.
2. The system displays the current tariff rates and taxes.
3. The employee can update the tariff rates and taxes as needed.
4. If the tariff rates or taxes are updated, the system recalculates the bills for all residents
based on the new rates.
5. The system sends a notification to residents of the change in rates.
Alternate Flow:
If the employee tries to update the tariff rates or taxes with invalid values, the system displays
an error message and prompts the employee to try again with valid values.
Post Condition:
1. The tariff rates and taxes are updated in the system.
2. The bills for all residents are recalculated based on the new rates.
3. Residents receive a notification of the updated rates.
<UC_09>Use case Name: Increment in Bill
Primary Actor: System
Brief Description:
This use case allows the system to calculate the electricity bill for a resident, including any
applicable tariff rates and taxes.
Pre-Condition:
1. The resident must have a meter connected to the electricity supply and the meter reading
must be available in the system.
Basic Flow:
2. The system retrieves the resident's meter reading from the electricity meter.
3. The system calculates the resident's electricity usage based on the meter reading.
4. The system applies the appropriate tariff rates and taxes to the electricity usage to
determine the bill amount.
5. The system displays the bill amount to the resident.
6. The resident can choose to pay the bill online or in person.
Alternate Flow:
If the resident's meter reading is not available, the system displays a message indicating that the
bill cannot be calculated.
Post Condition:
1. The resident has successfully viewed their electricity bill online using the system.
2. If the resident chooses to pay online, the system processes the payment and updates the
resident's account with the payment information.
