ELECTRICITY BILL

MANAGEMENT SYSTEM
INTRODUCTION OF ELECTRICITY BILL
MANAGEMENT SYSTEM
Are you looking for an Electricity bill management system for your
final year project? We are here to help you. You can contact us
This system is named as Electricity Bill Management System. This
system is made to keep the records about the bills of the
customers.The admin can manage all the accounts and the registered
users like employees and customers can only manage their own
accounts. This system helps in maintaining the bills and the payments.

A different module is there for employees to check the customer’s

details if their job requires. Admin, employees, and customers all have
a different interface and different privileges according to their need.

Like a customer can only manage his account and cannot see any
details of other customers, employees can see the details of all the
customer’s accounts and admin can manage all the accounts including
the customers and employees account.
This system also has the option for customers to pay their electricity
bills by online mode. Either through internet banking or by debit card.

This system also has the feature to add and delete customer and
employee’s accounts in case a customer wants to cut the connection or
an employee wants to leave the job.

All the employees are divided into different departments according to

their job profile and the customers are divided according to their
wards. The rest of the modules are explained in the further sections
with the detailed explanation.

check eCommerce Project in PHP for your final Year

MODULES OF ELECTRICITY BILL MANAGEMENT
SYSTEM
Our system has only two main interfaces. One is for the admin and the
other one is for the user, the here user can be a customer or an
employee. Along with these, we have other interfaces which can be
discussed as below:

Login:
After registration, one can log in the system as the end user of the
system on the behalf of user. The user will get only those privileges
which are given to the user for which one has registered.

For example, if a user has registered as a customer then the user only
has the privileges to view the data and cannot make any changes to the
data that is shown.

User:
The user can be anyone either a customer or an employee. If the user
is an employee then he can make changes to the data like adding units
in the bill, used by a customer.

If the user is a customer then he can only see the details of his account,
not of any other account. The customer can see the monthly usage of
electricity and can pay the bill but cannot make any changes to the
data.

Admin:
This module can only have one account and this account has all the
privileges which a user account might not have. First of all, admin
account is created and then if the admin verifies a registering user
then his account will be created otherwise not.

Queries:
In this module, the customer can ask any query he has and his
question with his details will be sent to the person who is managing
queries and then he or she can reply the query of a customer.

Admin can also see any query made by the customer and can also
reply to the customer.

Department:
In this section, all the employee’s details can be seen by the privileged
user. All the employees are divided into different sections according to
their job profile. Employees working in multiple sections might get
repeated into the different departments.

Only admin has the privilege to make any change into any employees
account.

Meters:
In this, new customers can be added, monthly bills can be sent to
customers account, any particular customer can be found using unique
meter id and the remaining balance of a customer can be checked.

Other Features:
There are other various features that are provided in this attendance
management system like updating result and checking result by the
students. Paying fees either by online mode or by the offline mode.
Check Bus Management System Project for your final year.
SYSTEM DESIGN OF ELECTRICITY BILL
MANAGEMENT SYSTEM:
Now this prison management system is designed in such a way that it
takes fewer resources to work properly. It has its own sort of minimum
requirements that we need to take care of :

The system needs a minimum of 2 GB of ram to run all the features

smooth and sudden.

It needs a minimum 1.3 GHz processor to run smooth as less than that
may create problems.

The system needs to be operated by some authorized person as wrong

hands can make it irresponsible.

Rest is all up to the user’s usage will care for hardware

For security Antivirus is recommended.

The system is made properly and all the testing is done as per the
requirements. So, the rest of the things depend on the user and no one
can harm the data or the software if the proper care is done. All the
attributes are working perfectly and if any error is found then it can be
removed easily.

Check online Food ordering System Project for Final Year

ER DIAGRAM OF ELECTRICITY BILL MANAGEMENT
SYSTEM:
If you need only database of electricity bill Management System,
Check Database Homework Help
Entity User:
Every User detail need to be stored in a proper manner with very
needed attributed. As all the other tasks can be performed only if the
user is authenticated.

After the admin has registered and is verified by the admin then the
user can perform all the tasks on it. Some of the features of the user
are as follows:

Primary key User id:

The user id is system generated and unique, which can be referenced
in any other entity.This mostly for recognizing it in the unique way
anywhere in the program.

User name:
User name is taken from the user and fed into this it is properly
validated so that no mistake happens.

Number:
The phone number is taken here to keep the member updated and for
the confirmation of the event is also managed through this method.

Email:
Email is taken to make member aware of new offers new events and
for future references, it is also relevant.

Address:
Address of the user is required at the time the user is registering itself
on the system

Password:
The password is required to login into the system and the password
must contain a special character, a numeric character, and an upper-
case letter. Password must contain at least six characters.

One must keep the password difficult so that no one can get into your
account and make any changes.

Entity Customer:
The customer is the entity which requires it to get updated about their
monthly usage of electricity and to pay their monthly bill in online
mode if they want to.

If any customer has any query then there is also an option to put your
query and it will be answered by your service provider. Some of the
features of the customer entity are explained below :

Ward number:
Each customer is divided into a ward as it is easy to manage a bunch of
people in a branch. Each branch can have multiple wards but the
number of customers in a ward is always limited. So, a ward number is
always given to a customer.

Address:
The address is required because the meter is put into the home and
the service provider has to go to customer’s home every month to read
the units used by the customer.

After knowing the units used, only then it can be updated on this
system. So, the address of the customer is required.

Entity payment:
This module is present in both the interfaces but the options that are
provided are different. In the customer’s interface, there is an option
to pay the electricity bill using their debit card or by net banking.

The customer can also pay the bill by cash by going to the particular
branch. Customers can also see their payment status after paying their
bill. In the employee’s module, there is no option to pay the bill, they
can only see the monthly salary status after deducting their leaves.

One thing that employees can do is that they can cut the connection to
a customer that has not paid their bill in the given time period. Admin
cannot see any details they can only help the user in registration by
verifying the user. Some features of payment entity are explained
further :

Number:
The phone number is taken here to keep the member updated and for
the confirmation of the event is also managed through this method.

Address:
The address is required because the meter is put into the home and
the service provider has to go to customer’s home every month to read
the units used by the customer.
After knowing the units used, only then it can be updated on this
system. So, the address of the customer is required.

Entity Billing Cycle:

In this entity, there are the monthly cycles of bills are shown. In
employee’s module, it is present to add the bill to the customer’s
monthly billing cycle and in the customer’s interface, it is provided to
pay the bill and to check the old bills if required.

Other attributes of this entity are as follows:

Name:
The user must know the names of the courses which he or she has
chosen either to teach or to study. who are on duty in the same prison.

Phone number:
The phone number is taken here to keep the member updated and for
the confirmation of the event is also managed through this method.

Check online Bus Booking System in PHP for final year.

USE CASE DIAGRAM OF ELECTRICITY BILL
MANAGEMENT SYSTEM:
In this use case as you can see we have our system as box and the users
who use our system are of the kind of outside the box but related to
the system. There are two kinds of user one is admin and the other is
user type.

Users:
There are two users that are present here in this system. One is admin
but the other is a user. This user has all the privileges but it cannot
register itself on this system as the admin needs to verify the
registering user.
After the admin verifies the user only then he is eligible to use the
system and after that, it has all the privileges.Attributes given to the
user are:

Adding user:
Admin can add a new user and can save it. The details of the user can
be seen only by the valid users.

Adding staff:
In this attribute or column, the user can add the details about the staff
members.

Adding customers: this entity is about the details of the customers who
are using the service from the company and all other details of them.

Admin panel :
There can be only one account of admin. Admin can add the users.
When a user tries to register on prison management system then the
request goes to admin and if the admin verifies only the user can
register itself on it.

Other privileges that admin has been explained below :

He can Login through his id and password. The password is made very
secure so that no person can guess and make it difficult for hackers to
crack.

He has access to the profile of his own and he can search detail of
other Users and can see the detail of him.

This admin is responsible for creating and uploading the Menu card to
every User in the Interface. Admin can also delete the cards according
to the requirement.

He can add a user to that account and give access to for handling the
prison on their own.
He can manipulate the data of any user.In this, we are showing here
the interaction of the users with our system through our use case
diagram.

Check Case Management System Project for Final year

FUNCTIONAL AND NON-FUNCTIONAL OF
ELECTRICITY BILL MANAGEMENT SYSTEM
The functional requirement of the electricity bill management system
is that it does what it is meant for. A functional requirement describes
what a software system should do, while non-functional requirements
place constraints on how the system will do so.

Functional requirements specify a function that a system or system

component must be able to perform. It can be documented in various
ways. The most common ones are written descriptions in documents
and use cases.

Few of its functional requirements are as given below:-

User data should be fed into the system:

this system is doing that properly in user entity. After fetching the data
of the customer, the bill can be made and sent to the customer.

Admin can add the users:

Admin can verify and add the user, which is they are doing with this
system. He can also delete the users if required.

Non-Functional of electricity bill management system:-

Non-functional necessities square measure the other demand than
practical necessities. This square measure the necessities that specify
criteria which will be wouldn’t to choose the operation of a system,
instead of specific behaviors.
Non-functional necessities square measure within the style of “system
shall be “, associate degree overall property of the system as a full or of
a specific facet and not a particular operation.

The system’s overall properties remarkably mark the distinction

between whether or not the event project has succeeded or
unsuccessful.

Non-functional necessities – are often divided into 2 main categories:

Execution qualities, like security and usefulness, that square measure

evident at the run time.

Evolution qualities, like liabilities, maintainability, flexibility and

quantifiable, that square measure embodied within the static structure
of the code.

Non-functional necessities place restrictions on the merchandise being

developed, the event method, and specify external constraints that the
merchandise should meet

Our project qualifies all the criteria of functional and non-functional

accordingly and the system is up to mark performance vise.Here we
need to take care of few more things before heading towards the
system.

The most important feature of electricity bill management system

application world is that application’s ease of usage .application will
easy to use if made while keeping in mind that user need not think
twice about searching any feature.

Everything should be made distinctive by using the color combination

such that everything needed most frequently highlighted with focus
colors. We can use simple layouts like the card and grid layout etc.

By varying color and other UI combination, many good intuitive

interfaces can be made. Which ultimately makes interface easy to use
for a long time.
Unlike ancient style wherever the goal is to form the thing or
application physically enticing, the goal of interface style is to form the
user’s interaction expertise as straightforward and intuitive as
attainable – what’s typically known as user-centered style.

Where smart graphic/industrial style is daring and eye catching, smart

interface style is commonly delicate and invisible.

Keep things simple and consistent:-

Simple and Harmonic way making UI is very intuitive and needs to
follow.

Make good use of typography:-

The typography is taken care very strictly as the need of the system.

Use color and contrast properly:-

Color combo of lite and dark is good way emphasise and done well in
this system

Consider feedback messages:-

the feedback form is a very good way taking feedback of forms and
improving the system.

Simplified forms:-
the form is made simple to fill with the clean user interface.

ELECTRICITY BILLING MANAGEMENT SYSTEM

PROJECT
CONCLUSION OF ELECTRICITY BILL
MANAGEMENT SYSTEM
After all the hard work is done for electricity bill management system
is here. It is a software which helps the user to work with the billing
cycles, paying bills, managing different departments under which
employees are working etc.
This software reduces the amount of manual data entry and gives
greater efficiency. The User Interface of it is very friendly and can be
easily used by anyone.

It also decreases the amount of time taken to write details and other
modules.