ELECTRICITYBILLING SYSTEM

Submitted in partial fulfilment of the requirements for the award of

Bachelor of Science Degree in Computer Science
By
INBHA K (Reg No. 38290026)
KARTHIKA J (Reg No. 38290033)

DEPARTMENT OF COMPUTER SCIENCE

SCHOOL OF COMPUTING

SATHYABAMA
INSTITUTE OF SCIENCE AND TECHNOLOGY
JEPPIAAR NAGAR, RAJIV GANDHI SALAI,
CHENNAI – 600119, TAMILNADU

APRIL 2021

1
 SATHYABAMA
INSTITUTE OF SCIENCE AND
TECHNOLOGY (DEEMED TO BE
UNIVERSITY)
Accredited with Grade “A” by NAAC
(Established under Section 3 of UGC Act, 1956)
JEPPIAAR NAGAR, RAJIV GANDHI SALAI, CHENNAI– 600119
www.sathyabama.ac.in

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

BONAFIDE CERTIFICATE

This is to certify that this Project Report is the bonafide work of INBHA.K
(Reg. No. 38290026) and KARTHIKA.J (Reg. No. 38290033) who carried
out the project entitled “ELECTRICITY BILLING SYSTEM “under my
supervision from November 2020 to April 2021.

Internal Guide
Ms. J.REFONAA M.E., Ph.D.,

Head of the Department

Submitted for Viva voce Examination held on

Internal Examiner External Examiner

2
 DECLARATION

I, INBHA K (Reg. No. 38290026) hereby declare that the Project

Report entitled “ELECTRICITY BILLING SYSTEM” done by me
under the guidance of Ms. J.REFONAA M.E., Ph.D., is submitted in
partial fulfillment of the requirements for the Award of Bachelor of
Science Degree in Computer Science.

DATE:
PLACE: CHENNAI SIGNATURE OF THE
CANDIDATE

3
 ACKNOWLEDGEMENT

I am pleased to acknowledge my sincere thanks to Board of Management of

SATHYABAMA for their kind encouragement in doing this project and for
completing it successfully. I am grateful to them.

I convey my thanks to Dr. T.SASIKALA,M.E.,Ph.D., Dean, School of

Computing andDr.S.VIGNESHWARI,M.E.,Ph.D.,and
Dr.L.LAKSHMANAN, M.E., Ph.D., Head of the Department, Department of
Computer Science and Engineering for providing me necessary support and
details at the right time during the progressive reviews.

I would like to express my sincere and deep sense of gratitude to my Project

GuideMs. J.REFONAA for her valuable guidance, suggestions and constant
encouragement paved way for the successful completion of my project work.

I wish to express my thanks to all Teaching and Non-teaching staff members of

the Department of Computer Science and Engineering who were helpful in
many ways For the Completion of the project.

4
 ABSTRACT

Electricity consumers are often faced with the problem of inaccuracy

and delay in monthly billing due to some drawbacks. Thus, it is essential to
have an efficient system for such purposes via electronic platform with
consideration to proximity. The proposed system automates the conventional
process of paying electricity bill by visiting the Electricity Board which is
tiresome and time consuming. It is also designed to automate the electricity
bill calculation and payment for user convenience. The system is developed
with JSP SERVLET as the base programming language which can be used to
develop websites, web applications and web services. The MYSQL is a
relational database management system based on Structured Query Language
(SQL) which is used for the purpose of web database. The system would be
having two logins: the administrative and user login. Theadministrator can
view the user's account details and can add the customer's information of
consuming units of energy of the current month in their account. The Admin
must feed the system with the electricity usage data into respective user’s
account. The system then calculates the electricity bill for every user and
updates the information into their account every month. Users can then view
their electricity bill and pay before the month end.

5
 TABLE OF CONTENTS

CHAPTER NO. TITLE PAGE NO.

ABSTRACT
LIST OF FIGURES

Introduction 10
1.1Preamble 10
1. 11
1.2Problem statement
1.3Proposed solution 11

Analysis and system

13
2. requirements 13
2.1 Existing and proposed system.
13
2.2 Feasibility study
2.3 System Development
14
& environment 14
2.3.1 Hardware requirements
15
2.3.2 Software requirements

System design and modelling 16

3.1 System Architecture 16
3. 3.2 Preliminary Design 17
3.2.1 Entity relationship diagram 17
3.3 Normalization 20
3.3.1 First normal form 20
3.3.2 Second normal form 20
3.3.3 Third normal form 20

6
 21
Implementation 21
4. 4.1 Implementation of operations
21
4.2 Implementation of sql statement
22
4.3 Algorithm of Implementation
22
4.3.1 Algorithm of admin 26
4.3.2 Algorithm of
27
customer
4.4 DFD (Data Flow
Diagram)
30
Testing 30
5.1 Testing process 30
5.
5.2 Testing objectives 30
5.3 Level of testing 30
5.3.1 Unit testing 32
5.3.2 Integration testing 33
5.3.3 System testing

Conclusion 35
6.1 Conclusion 35
6. 6.2 Future Analysis 35
6.3 References 35

Appendix 37
Source code

7
 LIST OF FIGURES

Figure No: Figure Name Page No

1.1.1 Block Diagram 11

3.1.1 System Architecture of 16

system
3.2.1 ER diagram 19

4.3.1 Flow chart of 25

Administrator
4.3.2 Flow chart of Consumer 27

4.4.1 Zero level DFD 28

4.4.2 First Level DFD 29

4.4.3 Second Level DFD 30

8
 LIST OF TABLES

TABLE NO: TABLE NAME PAGE NO

5.1 Negative test case for 31

phone number insertion
5.2 Positive test case for 31
phone number insertion
5.3 Negative test case for 31
email insertion
5.4 Positive test case for 31
email insertion
5.5 Negative test case for 32
customer name insertion
5.6 Positive test case for 32
customer name insertion
5.7 Test case on basis of 32
generating of bill
5.8 Test cases 33

9
 Chapter 1
INTRODUCTION

Electricity Billing System is a software-based application.

i. This project aims at serving the department of electricity

by computerizing the billing system.
ii. It mainly focuses on the calculation of units consumed during the
specified time and the money to be charged by the electricity
offices.
iii. This computerized system will make the overall billing system
easy, accessible, comfortable, and effective for consumers.

To design the billing system more service oriented and simple, the following
features have been implemented in the project. The application has high speed
of performance with accuracy and efficiency.
The software provides facility of data sharing, it does not require any staff as
in the conventional system. Once it is installed on the system only the meter
readings are to be given by the admin where customer can view all details, it
has the provision of security restriction.
The electricity billing software calculates the units consumed by the customer
and makes bills, it requires small storage for installation and functioning. There
is provision for debugging if any problem is encountered in the system.
The system excludes the need of maintaining paper electricity bill,
administrator does not have to keep amanual track of the users, users can pay
the amount without visiting the office. Thus, it saves human efforts and
resources.

1.1 Preamble
We, the owners of our project, respect all customers and make them happy
with our service.

The main aim of our project is to satisfy customer by saving their time by
payment process, maintaining records, and allowing the customer to view
his/her records and permitting them to update their details.
10
 The firm handles all the work manually, which is very tedious and
mismatched.
The objectives of our project are as follows:
 To keep the information of customer.
 To keep the information of consuming unit energy of current month.
 To keep the information of consuming unit energy of previous month.
 To calculate the units consumed every month regularly.
 To generate the bills adding penalty and rent.
 To save the time by implementing payment process online.

Electricity online billing Homepage

electr

Consumer user Interface Administrative user Interface

Fig 1.1.1: Block diagram showing the proposed online Electricity billing
system.

1.2 Problem Statement

The manual system is suffering from a series of drawbacks. Since whole

of the bills is to be maintained with hands the process of keeping and
maintaining the information is very tedious and lengthy to customer. It is very
time consuming and laborious process because, staff need to be visited the
customers place every month to give the bills and to receive the payments. For
this reason, we have provided features Present system is partially
automated(computerized), existing system is quite laborious as one must enter
same information at different places.

1.3 Proposed Solution

11
  This project system excludes the need of maintaining paper electricity bill
as all the electricity bill records are managed electronically.
 Administrator doesn’t have to keep a manual track of the users. The
system automatically calculates fine.
 Users don’t have to keep a manual track of the users. The system
automatically calculates fine.
 There is no need of delivery boy for delivery bills to user’s place.
Thus, it saves human efforts and resources.

12
 CHAPTER 2
ANALYSIS AND SYSTEM REQUIREMENT

2.1 Existing and Proposed System

The conventional system of electricity billing is not so effective; one staff
must visit each customer’s house to note the meter readings and collect the data.
Then, another staff must compute the consumed units and calculate the money
to be paid. Again, the bills prepared are to be delivered to customers. Finally,
individual customer must go to electricity office to pay their dues.
Hence, the conventional electricity billing system is uneconomical, requires
many staffs to do simple jobs and is a lengthy process overall. In order to solve
this lengthy process of billing, a web based computerized system is essential.
This proposed electricity billing system project overcomes all these drawbacks
with the features. It is beneficial to both consumers and the company which
provides electricity.
With the new system, there is reduction in the number of staffs to be
employed by the company. The working speed and performance of the software
is faster with high performance which saves time. Furthermore, there is very
little chance of miscalculation and being corrupted by the staffs.

2.2 Feasibility Study:

Feasibility study is the phase in which the analyst checks that the candidate
system is feasible for the organization or not. This entails identification,
description & evaluation of the system. Feasibility study is done to select the
best system that meets the performance requirement.
If the feasibility study is to serve as a decision document, it must answer key
questions.
1. Is there a new and better way to do the job that will benefit the user?
2. What are the costs and savings of the alternatives?
3. What is recommended?
The most successful system projects are not necessarily the biggest or most
visible in the business but rather those truly meet user’s expectations.

13
Feasibility considerations
Three key considerations are involved in the feasibility study. They are as
follows:-
Economic Feasibility:
Economic analysis is the most frequently used method for evaluating the
effectiveness of the candidate system.
We analyse the candidate system (computerized system) is feasible as than the
manual system because it saves the money, time and manpower. It also feasible
according to cost benefits analysis
Technical Feasibility:
Technical feasibility centers around the technology used. It means the candidate
system is technically feasible i.e. it don’t have any technical fault and work
properly in the given environment. Our system is technically feasible; it is
providing us required output.
Behavioral Feasibility:
Behavioral feasibility is the analysis of behavior of the candidate system. In this
we analyse that the candidate system is working properly or not. If working
than it communicating proper with the environment or not. All this matters are
analysed and a good candidate system is prepared. Due to the change of system
what is the change in behaviour of the users, this factors are also analysed.

2.3SYSTEM DEVELOPMENT ENVIRONMENT

System development environment shows the hardware and software
requirement, which is necessary for developing the software. Necessary
software and hardware requirement, which are necessary for making this
software are as follows:
2.3.1 : Hardware Requirements:
 Hardware specification: Intel Pentium Processor
 32 MB RAM or Higher
 1.2 GB Hard Disk or Greater
 Video Display Unit
 Keyboard

14
 Mouse

2.3.2 : Software Requirements:

 Operating System: Windows 10
 Software: Microsoft SQL Server
 Front End: Jsp Servlet
 Back End: Database – Mysql
Business Logic- Java

15
 CHAPTER 3
SYSTEM DESIGN AND MODELLING

3.1 System Architecture

The system architecture gives the overview of the organizational system that
shows the system boundaries, external entities that interact with the system, and
the major information that flows between the entities and the system.
Fig 3.1.1 System Architecture of system

Login page Fill Insert

Consumer
Homepage
(id & registrati regis
Registration
View bill
on details Details
password)
monthwise

Bill calculation
if
Per unit cost Bill payment
Of electricity
View consumer

Feedback

Logout

1
3.2 Preliminary Design
System design is an abstract representation of a system component and
their relationship and which describe the aggregated functionally and
performance of the system. It is also the plan or blueprint for how to obtain
answer to the question being asked. The design specifies various type of
approach.
Database design is one of the most important factors to keep in mind if
you are concerned with application performance management. By designing
your database to be efficient in each call it makes and to effectively create rows
of data in the database, you can reduce the amount of CPU needed by the server
to complete your request, thereby ensuring a faster application.

3.2.1 Entity – Relationship Diagram

An entity relationship diagram (ERD) shows the relationships of entity
sets stored in a database. An entity in this context is an object, a component of
data. An entity set is a collection of similar entities. These entities can have
attributes that define its properties.
There are two reasons to create a database diagram. You’re either designing a
new schema or you need to document our existing structure.
If you have an existing database you need to document, you create a database
diagram using data directly from your database. You can export your data base
structure as a CSV file (there are some scripts on how to do this here), then have
a program generate the ERD automatically.
An ER diagram is a means of visualizing how the information a system
produces is related. There are five main components of an ERD:
 Entities, which are represented by rectangles. An entity is an object or
concept about which you want to store information.
 A weak entity is an entity that must defined by a foreign key relationship
with another entity as it cannot be uniquely identified by its own
attributes alone.
 Actions, which are represented by diamond shapes, show how two entites
share information in the database.
 In some case, entities can be self-linked. For example, employees can
supervise other employees.

1
  Attributes, which are represented by ovals. A key attribute is the unique,
distinguishing characteristic of the entity.
 A multivalued attribute can have more than one vale. For example, an
employee entity can have multiple skill values.
 A derived attribute is based on another attribute. For example, an
employee’s monthly salary is based on the employee’s annual salary.
 Connecting lines, solid lines that connect attributes to show the
relationships of the entities in diagram.
 Cardinality specifies how many instances of an entity relate to one
instance of another entity. Ordinality is also closely linked to cardinality

Figure 3.2.1 describes the ER diagram of Electricity Billing System. It

has 5 entities namely login, customer, bill, and meter info. The entities have
attributes which are primary and foreign and attributes. The primary attributes
are underlined.

1
Fig 3.1.1: ER diagram
Login username
Login id password
User_id

Login
Username Usermobile

user
Has

Useremail

manage
Bill cus
Cus add id
Bill type
Cus id

customer bills
Cus
name

Conc date
Cus mobile connection
Conctyp
Cus email

Conc id
Has

Unit id
units
19
Unit typ
3.3 Normalization

Normalization is a process of organizing the data in database to

avoid data redundancy, insertion anomaly, update anomaly & deletion
anomaly.
Let’s discuss about anomalies first then we will discuss normal forms
with examples. Anomalies in DBMS There are three types of anomalies that
occur when the database is not normalized. These are –Insertion, update and
deletion anomaly.

3.3.1 First normal form(1NF)

As per the rule of first normal form,
 All rows must be unique.
 Each cell must only contain a single value.
 Each value should be non- divisible.

3.3.2 Second normal form(2NF)

As per the rule of second normal form,
 Database must be in first normal form.
 Non partial dependency All non-prime attributes should be fully
functionally dependent on the candidate key.

3.3.3 Third normal form(3NF)

As per the rule of third normal form,
 Database must be in first and second normal form.
 Non transitive dependency All fields must only be determined by the
primary/composite key,not by other keys.

2
 CHAPTER 4
IMPLIMENTATION

4.1 Implementation of operations

 Adding customer:Here admin can add new customer list who started
using electricity bill system.
 Searching deposit details: Here admin can search according to meter
number and month to view deposit details.
 Viewing Details: Here admin and user can view customer details and
about details.
 Updating customer: Here customer can update their details by using
meter no of the customer.
 Delete customer: Here admin can delete details based on meter number.

4.2 Implementation of SQL statements

Insert statement:

• The INSERT INTO statement is used to insert new records in a table.

• The INSERT INTO syntax would be as follows: INSERT INTO
table_name VALUES (value1, value2, value3, ...).

• The following SQL statement insert's a new record in the “customer”

table: Insert into customer VALUES (“sai”,”12345”,” btm”,” Bangalore”,
“Karnataka”, “[email protected]”, “9876543333”).

Update statement:

• An SQL UPDATE statement changes the data of one or more records in a

table. Either all the rows can be updated, or a subset may be chosen using
a condition.

2
 • The UPDATE syntax would be as follows: UPDATE table_name SET
column_name =value, column_name=value... [WHERE condition].

• The following SQL statement update's a new record in the “customer”

table: UPDATE TABLE customer SET email= [email protected] WHERE
meter_no =”12345”.

Delete statement:

• The DELETE statement is used to delete existing records in a table.

• The DELETE syntax would be as follows: DELETE
FROM table_nameWHERE condition.
• The following SQL statement delete's a record in the “customer”
table: delete from customer where meter_no=12345.

Create statement:
• The CREATE TABLE Statement is used to create tables to store data.
Integrity Constraints like primary key, unique key, foreign key can be
defined for the columns while creating the table.

• The syntax would be as follows: CREATETABLE table_name

(column1datatype, column2datatype, column3 datatype, columnN
datatype, PRIMARY KEY (one or more columns)).

➢ The following SQL statement creates a table “customer” table:

create table customer (name varchar (30), meter no varchar (20)
primary key, address varchar (50), city varchar (20), state
varchar (30), email varchar (30), phone varchar (30));
➢ The following SQL statement creates a table “login” table:
create table login (meter no varchar (30), username varchar (30),
password varchar (30), user varchar (30), question varchar (40),
answer varchar (30));

➢ The following SQL statement creates a table “bill” table: create

table bill (meter no varchar (20), foreign key(meter no) references
customer(meter no) on delete cascade, month varchar (20), units
int (20), total bill int (20), status varchar (40));

2
4.3 Algorithm of implementation

Explanation of Algorithm:
✓ Start system
✓ Enter login name and password
✓ On clicking the login button
✓ Connect to database
✓ Query database to know whether user credentials are correct
✓ If not, deny access and return login page with an error message
✓ If correct, check if credentials for administrator
✓ If yes, allow login
✓ Set admin session, re-direct administrator to admin login page
✓ If no, allow login set user session
✓ Re-direct user to user home page

4.3.1 Algorithm of admin:

Login:
 This program will allow the admin to enter the username
and password.
 If the entered credentials are correct, then the login will be
successful otherwise need to be signup.
 If admin forgets password, it can be retrieved by giving
username and answer for security question.
After successful login the admin will be redirected to admin portal
page where he/she can do following activities.

NewCustomer:

▪ This program will allow the admin to enter the customer details
and automatically generates unique meter number.
▪ If customer name, address, city, state, email and phone number
is entered, insert the values into customer

2
 else print
error while
next=true

enter the meter info

details else print meter
info error

Submit the details of customer that has been entered by clicking onto next
button.

▪ If we need to cancel the particulars that has been entered click

onto cancel option.

CustomerDetails:
▪ This program will allow the admin to view customer details.
▪ If we need to print the particulars that has been viewed click onto
print option.

CalculateBill:

▪ This program will allow the admin to calculate total bill when
units consumed are inserted where meter no and month is
selected.
insert the values into
bill else print error

Submit the details of tax that has been entered by clicking onto submit
button.

▪ If we need to cancel the particulars that has been entered click onto
cancel option.

DeleteBill:

▪ This Program will allow the admin to delete the customer info
when meter no is selected.

▪ If we need to delete the particulars that has been saved click onto
delete option.

2
 ▪ If we need to cancel the particulars that has been entered click onto back
option.

About:
▪ This program will allow the admin to view details of the project in short.
▪ If we need to exit the particulars that has been viewed click onto
exit option.

Fig 4.3.1: Activity Flow chart of Administrator

Start

Admin login

if

Main page

View consumer

Bill

Logout

Stop

2
4.3.2 Algorithm or of Customer:

Login:

▪ This program will allow the customer to enter the username and
password. If the entered credentials are correct, then the login will be
successful otherwise need to be signup with the meter_no which is given
by admin.
▪ If customer forgets password, it can be retrieved by giving username and
answer for security question. After successful login the customer will be
redirected to customer portal page where he/she can do following
activities.

UpdateInfo1:

▪ This program will allow the customer to update the customer details.
If customer address, city, state, email and phone number is updated,
update the values into
customer else print error

update the details of customer that has been updated by clicking onto
update button.

▪ If we need to cancel the particulars that has been updated, click onto
back option.

ViewInfo:
▪ This program will allow the customer to view his/her own details.
▪ If we need to go back from the particulars that has been viewed click
onto back option.

PayBill:
▪ This program will allow the customer to view bill details and redirects
to pay
▪ the bill where status will be updated.
▪ If we need to cancel the particulars that has been viewed click onto
back option.
▪ If we need to pay the bill amount that has been viewed click onto
pay option.

2
BillDetails:
▪ This program will allow the customer to view bill details.
▪ If we need to print the particulars that has been viewed click onto
print option.

GenerateBill:
▪ This program will allow the customer to generate bill when meterno and
month is selected.
▪ Generate the details by clicking on generatebill button.

About:
▪ This program will allow the customer to view details of the project
in short.
▪ If we need to exit the particulars that has been viewed click onto
exit option.

NOTE: Utility (notepad, browser, calculator),query and logout is given to both

customer and admin portals.
Fig 4.3.2 Activity Flow chart of consumer

Start

Consumer

If

Main page

View bill

Consummation calculation

Bill payment
2
 4.4 DFD(Data Flow DiLaoggroaumt )
They are the versatile diagramming tools used for structured system analysis.
They are specifically used for process modelling which involves graphically
representing the function or process, which captures, manipulate, store, and
distribute data between a system and its environment and between components
within a system.
Fig 4.4.1 zero level DFD

Bill management

Customer management
Connection management

Electricity billing system

System user management

Payment management

Login management

2
 Fig 4.4.2 First level DFD

ELECTRICITY GENERATE
MANAGEME ELECTRIC
NT REPORT
CUSTOMER GENERATE CUSTOMER
MANAGEME REPORT
NT

CONNECTIO GENERATE
N ELECTRICITY CONNECTION
MANAGEME REPORT
BILLING
SYSTEM

GENERATE BILL
BILL MANAGEMENT REPORT

LOGIN MANAGEMENT CHECK

CUSTOMER
LOGIN DETAILS

GENERATE
SYSTEM SYSTEM USER
USER REPORT
MANAGEME

2
 Fig 4.4.3 Second level DFD

Login to Check roles of access

Admin system Manage electricity details

Manage bill details

Forgot
password Check credentials

Manage customer details

Send email to user Manage

Manage connection
modules details

Manage payment details

Manage paid
record

Manage system admins Manage user permission Manage report

Manage roles of user

3
 CHAPTER 5
TESTING

This chapter gives the outline of all the testing methods that are carried
out to get a bug free application.

5.1 Testing process

Testing is an integral part of software development. Testing process, in a
way certifies, whether the product, that is developed, compiles with the
standards, that it was designed to. Testing process involves building of test
cases, against which, the product has to be tested. In some cases, test cases are
done based on the system requirements specified for the product/software,
which is to be developed.
5.2 Testing objectives
The main objectives of testing process are as follows:
• Testing is a process of executing a program with the intent of finding an error.
• A good test case is one that has high probability of finding an as
yet undiscovered error.
• A successful test is one that uncovers an as yet undiscovered error.

5.3 Levels of Testing

Different levels of testing are used in the testing process; each level of
testing aims to test different aspects of the system. The basic levels are unit
testing, integration testing, system testing and acceptance testing.

5.3.1 Unit Testing

Unit testing focuses verification effort on the smallest unit of
software design the module. The software built, is a collection of
individual modules. In this kind of testing exact flow of control
for each module was verified. With detailed design consideration
used as a guide, important control paths are tested to uncover
errors within the boundary of the module.

3
Table 5.1: Negative test case for phone number insertion
Function Input Expected Error Resolved
name error
Input phone 98977 Phone is Length of Consume()
number invalid phone number
is not equal to
10
Input phone 9877avg Phone Alphabets are
number number is being taken as
invalid input for
phone
number

Table 5.2: Positive test case for phone number insertion

Function Input Expected Error Resolved
name error

Input phone 8690345678 Expected

number output is seen

Table 5.3: Negative test case for email insertion

Function Input Expected Error Resolved
name error

Input email Sail.in Email is Email is not Consumer()

invalid in a format
given

Table 5.4: Positive test case for email insertion

Function Input Expected Error Resolved
name error

Input email [email protected] Expected

output is seen

3
Table 5.5: Negative test case for customer name insertion

Function Input Expected Error Resolved

name output

Input Sana123 Name is Number are Consume()

customer invalid being taken as
name input

Table 5.6: Positive test case for customer name insertion

Function Input Expected Error Resolved

name name

Input Pooja Expected

customer output
name

5.3.2 Integration testing

The second level of testing is called integration testing. In this, many class-
tested modules are combined into subsystems, which are then tested. The goal
here is to see if all the modules can be integrated properly. We have been
identified and debugged.
Table 5.7: Test case on basis of generation of bill
Function Input Expected Error Resolved
name error
Negative 1234(meter no) Details seen Output not Consume ()
searchin of January(month) but not total seen
g total bill
bill
Positive 1234(meter no) Must display
searching of January(month) full generated
total bill bill

3
5.3.3 System testing

Here the entire application is tested. The reference document for this process is
the requirement document, and the goal is to see IF the application meets its
requirements. Each module and component of ethereal was thoroughly tested to
remove bugs througha system testing strategy. Test cases were generated for all
possible input sequences and the output was verified for its correctness.
Table 5.8: Test cases for the project

Steps Action Expected error

Step 1 The screen appears when A page with different
Choice the users run the menus appears.
program. 1. Admin panel
1. If admin login opens and
2. If customer login 2. Customer panel
opens.

Step 2 The screen appears when A window for adding

the admin logs in and new customer,
selects any one of the Calculate bill, etc
menus from the click of
the mouse

Selection 1  New customer

 Customer details
 Delete customer
Step 2.1 The screen appears when A window for generating
the customer login and bill, update
selects any one of the Customer details, view
menus from the click of details, generating bill
the mouse

Selection 2  Update details

 View details
Selection 2a  Generate bills
Selection 2b  Pay bills
 Bill details
CHAPTER6
3
 CONCLUSION

Usability testing was part of the post implementation review and

performance evaluation for the Electricity Online Bill Payment System, in order
to ensure that the intended users of the newly developed system can carry out
the intended task effectively using real data so as to ascertain the acceptance of
the system and operational efficiency. It caters for consumers’ bills and also
enables the administrator to generate monthly reports. It is possible for the
administrator to know the consumers have made payment in respect of their
bills for the current month, thereby improving the billing accuracy, reduce the
consumption and workload on the Electricity Board employees or designated
staff., increase the velocity of electricity distribution, connection, tariff
scheduling and eliminates variation in bills based on market demand. The
conceptual framework allows necessary adjustments and enhancement
maintenance to integrate future demands according to the technological or
environmental changes with time. It manages the consumers’ data and validates
their input with immediate notification centralized in Electricity Board offices
across the nation.

6.1 Future Analysis:

We have left all the options open so that if there is any other future requirement
in the system by the user for the enhancement of the system then it is possible to
implement them. We hope that the project will serve its purpose for which it is
develop there by underlining success of process

6.2 REFERENCES
[1]. Arimoro, T. A., Oyetunji, A. K., &Odugboye, O. E. (2019). Analysis of
Electricity Billing System in Corporate Buildings in Lagos, Nigeria. Studies,
1(6), 10-20.
[2]. Panthala, S., Islam, N., & Habib, S. A. (2015). Automated industrial load
measurement system.
[3]. Adegboyega, A., Gabriel, A. A., Ademola, A. J., Victor, A. I., &Nigeri, K.
(2013). Design and Implementation of an Enhanced Power Billing System for
Electricity Consumers in Nigeria. African Journal of Computing & ICT, 6(1).

3
[4]. Antoniou, G., Batten, L., Narayan, S., &Parampalli, U. (2009). A privacy
preserving e-payment scheme. In Intelligent Distributed Computing III (pp.
197-202). Springer, Berlin, Heidelberg
[5]. Rahul K. Sai (2016) Advanced Centralized Electricity Billing System
Using (IOT). International Journal of Advanced Research in Computer Science
and Software Engineering icrosoft Developer Network (MSDN)
[6]. Li, S., Wang, G., Zhou, J., & Chen, K. (2009). Fair and secure mobile
billing systems. Wireless personal communications, 51(1), 81-93.
[7]. Al-Ani, M. S., &Noory, R. (2012). Billing system design based on internet
environment. Editorial Preface, 3(9).
[8]. Barreto, P. S., Amvame-Nze, G., Silva, C.V., Oliveira, J. S. S., de Carvalho,
H. P., Abdalla, H., ... &Puttini, R. (2005, April). A study of billing schemes in
an experimental next generation network. In International Conference on
Networking (pp. 66-74). Springer, Berlin, Heidelberg
[9]. Bo, Y., Dongsu, L., &Yumin, W. (2002).An anonymity-revoking e-
payment system with a smart card. International Journal on Digital Libraries,
3(4), 291-296

3
 Appendix
Source code:
New page:
<!DOCTYPE html>
<html>
<head>
<meta charset="ISO-8859-1">
<title>Electricity Bill</title>

<link type="text/css" href="css/addStyle.css" rel="stylesheet"></link>

</head>
<body>
<div class="container">
<h1 id="nav"> Electricity Billing System </h1>
<div id="bd" >

<form class = "admin" action = "adminlogin.jsp">

<button id="own" >Admin</button>

</form>

<form class = "user" action = "user.jsp">

<button id="ownn" >User </button>

</form>
<img id="oimg"
src="https://previews.123rf.com/images/pikepicture/pikepicture1904/pikepictur
e190400140/120731051-long-queue-in-food-store-vector-banner-concept-
young-and-old-people-waiting-in-queue-line-men-women-.jpg">
<footer>
<a href="zsd">Help</a>
<a href="ds">Support</a>

3
</footer>
</div>

</div>
</body>
</html>
New page:
<!DOCTYPE html>
<html>
<head>
<meta charset="ISO-8859-1">
<title>Insert title here</title>
<link rel="stylesheet"
href="https://stackpath.bootstrapcdn.com/bootstrap/4.3.1/css/bootstrap.min.css "
integrity="sha384-
ggOyR0iXCbMQv3Xipma34MD+dH/1fQ784/j6cY/iJTQUOhcWr7x9JvoRxT2
MZw1T" crossorigin="anonymous">

</head>
<body>

<form action="newpage.html" method="GET" style="border:1px solid #ccc">

<div class="container">
<h1>Sign Up</h1>
<p>Please fill in this form to create an account.</p>
<hr>

<input type="hidden" name="command" value="NewUser">

<label for="name"><b>Enter a Name</b></label>

<input type="text" placeholder="Enter a Name" name="name" required>
<br>
<label for="id"><b>Consumer Number</b></label>
<input type="text" placeholder="Enter Consumer number" name="id"
required>
<br>

3
 <label for="psw"><b>Password</b></label>
<input type="password" placeholder="Enter Password" name="psw"
required>

<br>

<div class="clearfix">
<br>

<button type="submit" class="signupbtn">Sign Up</button>

</div>
</div>
</form>
</body>
</html>
Result page:
<!DOCTYPE html>
<html>
<head>
<meta charset="ISO-8859-1">
<title>Insert title here</title>
</head>
<body>

<h1>Added Sucessfully!</h1>

</body>
</html>

3
4