Tribhuvan University

Faculty of Humanities and Social Sciences

Online Food Ordering System

A PROJECT REPORT

Submitted to
Department of Computer Application
Shaheed Smarak College
Sharadanagar, Chitwan

In partial fulfillment of the requirements for the Bachelors in Computer

Application

Submitted by

Sukhad Thapa Magar

BCA 6th Semester
University SN: 6-2-502-11-2019
Symbol No.:
2080/03/27

Under the Supervision of

Mr. Sunil Kumar

Shaheed Smarak collage

 Tribhuvan University
Faculty of Humanities and Social Sciences
Shaheed Smarak College
Sharadanagar, Chitwan

Bachelor in Computer Applications (BCA)

SUPERVISOR’S RECOMMENDATION

I hereby recommend that this project prepared under my supervision by Sukhad

Thapa Magar entitled “Electricity Billing System” in the Partial Fulfillment of
requirement for the degree of Bachelor in Computer Application is recommended
for that final evaluation.

______________
Mr. Sunil Kumar
Project Supervisor
BCA Department
Shaheed Smarak College

Shaheed Smarak collage

 Tribhuvan University
Faculty of Humanities and Social Sciences
Shaheed Smarak College
Sharadanagar, Chitwan

Bachelor in Computer Applications (BCA)

LETTER OF APPROVAL

This is to certify that this project prepared by Sukhad Thapa Magar entitled
“Electricity Billing System” in partial fulfillment of the requirements for the
degree of Bachelor in Computer Application has been evaluated. In our opinion
it is satisfactory in the scope and quality as a project for the required degree.

______________ ______________

Mr. Sunil Kumar Mr. Raju Poudel

Supervisor Program coordinate

BCA Department Shaheed Smarak College

Sharadanagar, Chitwan Sharadanagar, Chitwan

______________
______________
Mr. Sunil Kumar
Internal Examiner
External Examiner

Shaheed Smarak collage

 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 Java swings as the base programming language which can be used to
develop websites, web applications and web services.

The Microsoft Structured Query Language (SQL) server is also used for creating back-
end database. The system would be having two logins: the administrative and user login.
The administrator 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.

Shaheed Smarak collage

 i

Shaheed Smarak collage

 ACKNOWLEDGEMENT

A project is a job of great enormity and it can't be accomplished by an individual all by them.
Eventually, we are grateful to several individuals whose professional guidance, assistance and
encouragement have made it a pleasant to undertake this project.

With immense pleasure we are presenting “Electricity Billing System” Project report as part of the
curriculum of ‘Bachelor of Computer Application’. We wish to thank all the people who gave us
unending support.

I express my profound thanks to our project guide and project in charge Prof. “Mr. Sunil Kumar”
and all those who have indirectly guided and helped us in preparation of this project.

Furthermore, we would also like to acknowledge with much appreciation the crucial role of
coordinator, who gave the permission to use all required equipment and the necessary materials to
complete our project.

Last but not the least, many thanks go to our teachers, friends, guardians who directly or indirectly
helped us in achieving the goal.

I am highly indebted to Shaheed Smarak College for their guidance and constant supervision as
well as for providing necessary information regarding the Project and support in the completion.

We would like to appreciate all the guidance which has improved our presentation skills thanks to
their comment and advices.

In the end, we would also like to thank Tribhuvan University for giving us this opportunity via the
course of Computer Application to help us understand the project ethics at this early stage and
helped us to evaluate my knowledge and expand it a little more.

Yours sincerely,
Sukhad Thapa Magar

ii

Shaheed Smarak collage

 TABLEOFCONTENTS
Abstract i
Aknowledgment ii
Table of contents iii
List of figures iv
1. Introduction
1.1 Preamble 1-2
1.2 Problem statement 2
1.3 Proposed solution 2
2. Analysis and System Requirements
2.1 Existing and Proposed System 3
2.2 Software& Hardware Requirements 3
3. System Design and Modelling
3.1 Preliminary Design
3.1.1 Entity-Relationship Diagram 4-6
3.1.2 Schema Diagram 7-8
3.2 Normalization
3.2.1 First normal form(1NF) 9
3.2.2 Second normal form(2NF) 9
3.2.3 Third normal form(3NF) 9
4. Implementation
4.1 Implementation of operations 10
4.2 Implementation of SQL statements 10-11
4.3 Algorithm or pseudo code of implementation 12-15
5. Testing
5.1 Testing process 16
5.2 Testing objectives 16
5.3 Levels of Testing
5.3.1 Unit Testing 16-18
5.3.2 Integration testing 18-19
5.3.3 System testing 19-20
6. Discussion and Snapshots
6.1 Tables 21-23
6.2 Screenshots 23-33

Conclusion 34
Bibliography 35

iii

Shaheed Smarak collage

 LIST OF FIGURES

FIG3.1.1: Schema diagram of Electricity Billing System 6

FIG3.1.2: ER diagram of Electricity Billing System 8
FIG6.1: Screenshot of List of tables 21
FIG6.2: Screenshot login table description 21
FIG6.3: Screenshot of customer table description 22
FIG6.4: Screenshot of tax table description 22
FIG6.5: Screenshot of rent table description 22
FIG6.6: Screenshot of bill table description 22
FIG6.7: Snapshot of meter info table description 23
FIG6.8: Snapshot of Splash page 23
FIG6.9: Snapshot of Login page 24
FIG6.10: Screenshot of Sign up page 24
FIG6.11: Screenshot of Forgot Password page 25
FIG6.12: Screenshot of Admin homepage 25
FIG6.13: Screenshot of New Customer page 26
FIG6.14: Screenshot of Meter Info page 26
FIG6.15: Screenshot of Customer Details page 27
FIG6.16: Screenshot of Tax Details page 27
FIG6.17: Screenshot of Calculate Bill page 28
FIG6.18: Screenshot of Delete Customer page 28
FIG6.19: Screenshot of Customer Homepage 29
FIG6.20: Screenshot of Update Customer Details page 29
FIG6.21: Screenshot of View Customer Details page 30
FIG6.22: Screenshot of View Customer Details page 30
FIG6.23: Screenshot of Pay Bill page 31
FIG6.24: Screenshot of Esewa/Visacard/Paytm page 31
FIG6.25: Screenshot of Bill Details page 32
FIG6.26: Screenshot of Generate Bill page 32
FIG6.27: Screenshot of Deposit Bill page 33
FIG6.28: Screenshot of About page 33

Shaheed Smarak collage

 LIST OF TABLES

Table5.1: Negative test case for phone number insertion

17
Table5.2: Positive test case for phone number insertion 17
Table5.3: Negative test case for email insertion 17
Table5.4: Positive test case for email insertion 17
Table5.5: Negative test case for customer name insertion 18
Table5.6: Positive test case for customer name insertion 18
Table5.7: Test case on basis of generation of bill 18
Table5.8: Test case on basis of Deposit Details 19
Table5.9: Test cases for the project 19-20

iv

Shaheed Smarak collage

 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 a manual track of the users and 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.

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 consuming unit energy of current

month.

 To keep the information of Customer.

Page|10
Shaheed Smarak Collage
  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.

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

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

Page|11
Shaheed Smarak Collage
 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 Software & Hardware Requirements

Hardware Requirements:

➢ Hardware Specification :- Processor Intel Pentium V or higher

➢ Clock Speed :- 1.7 GHz or more
➢ System Bus :- 64bits
➢ RAM :- 16GB
➢ HDD :- 2TB
➢ Monitor :- LCD Monitor
➢ Keyboard :- Standard keyboard
➢ Mouse :- Compatible mouse

Shaheed Smarak Collage Page|12

 Software Requirements:

➢ Operating System :- Windows10

➢ Software :- Microsoft SQL Server
➢ Front End :- Java core/swings (Net Beans)
➢ Back End :- MySQL

Shaheed Smarak Collage Page|13

 CHAPTER 3

SYSTEM DESIGN AND MODELLING

3.1 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.1.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.
Therearetworeasonstocreateadatabasediagram.You’reeitherdesigninganew schema or you
need to document our existing structure.
If you have an existing data base 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.
 Aweakentityisanentitythatmustdefinedbyaforeignkeyrelationshipwithanotherentityasitcan
notbeuniquelyidentifiedbyitsownattributesalone.

Shaheed Smarak Collage Page|14

  Actions, which are represented by diamond shapes, show how two entities share
information in the database.
 In some cases, entities can be self-linked. For example, employees can super vise other
employees.
 Attributes, which are represented by ovals. A key attribute is the unique, distinguishing
characteristic of the entity.
 A multi valued attribute can have more than one value. For example, an employee entity
can have multiples kill 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 entities in
the diagram.
 Cardinality specifies of many instances of an entity relate to one instance of another
entity. Ordinality is also closely linked to cardinality.

Figure 3.1.1 describes the ER diagram of Electricity Billing System. It has 5entities
namely login, customer, tax, bill, and meter_info. The entities have attributes which are primary
and foreign and attributes. The primary attributes are underlined.

Shaheed Smarak Collage Page|15

 service_charge

3.1.1 ERDiagram cost_per_unit

meter_rent

1
rent
gst

1 service_tax

tax
swacch_bharat_cess

total_bill
N
pays
bill month

meter_no status
units

meter_no
meter_no

name meter_location

city N N
manages
days
address

state phase_code
bill_type

email
has
meter_type
N
phone

login

meter_no username

question password
user

answer

FIG3.1.1: Schema diagram of Electricity Billing System

Shaheed Smarak Collage Page|16

3.1.2 Schema Diagram
Database schema is described as database connections and constraints. It contains attributes.
Every database has a state instances represent current set of databases with values. There are
different types of keys in a database schema.

A primary key is a table column that can be used to uniquely identify every row of the table.
Any column that has this property, these columns are called candidate key. A composite
primary key is a primary key consisting of more than one column. A foreign is a column or
combination of columns that contains values that are found in the primary key of some table.

All the attributes of each table are interconnected by foreign key which is primary key in
another column and composite key. Primary key cannot be null. The fact that many foreign key
values repeat simply reflects the fact that its one- to-many relationship. In one-to-many
relationship, the primary key has the one value and foreign key has many values.

Figure 3.1.2 is a Schema diagram of Electricity Billing System which has six tables i.e., login,
customer, tax, rent, bill, and meter_info where each table contain attributes some with primary
key, foreign key. In the login table there are 6 attributes "meter_no”, "username”, “password”,
"user”, "question”, "answer”. The customer table has 7 attributes "name”, "meter_no"(primary
key), "address”, "city”, "state”, “email”, "phone”. The rent table has 3 attributes
"cost_per_unit"(primary key), " meter_rent”, "service_charge". The tax table has 3 attributes "
service_tax”, "swacch_bharat_cess”, "gst”. The bill table has 5 attributes "meter_no"(foreign
key that references the primary key of the customer table meter_no), "month”,
"units”,"total_bill”, "status”. The meter_info table has 6 attributes "meter_no"(foreign key that
references the primary key of the customer table meter_no), "meter_location”, "meter_type”,
"phase_code”, " bill_type”, "days".

Shaheed Smarak Collage Page|17

3.1.2 Schema
DiagramLogin
meter_no Username password user question Answer

customer
Name meter_no Address City state Email phone

rent
cost_per_unit meter_rent service_rent

tax
service_tax swacch_bharat_cess gst

bill
meter_no Month units total_bill Status

meter_info
meter_no meter_location meter_type phase_code bill_type Days

FIG3.1.2: Schema diagram of Electricity Billing System

3.2 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.

Shaheed Smarak Collage Page|18

 3.2.1 First normal form (1NF)
As per the rule of first normal form,
 All rows must be unique (no duplicate rows).
 Each Cell must only contain a single value (not a list).
 Each value should be non-divisible (can’t be split down further).

Customer

3.2.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.2.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 determinable by the primary/composite
key, not by other keys.

Shaheed Smarak Collage Page|19

 CHAPTER 4
IMPLIMENTATION

4.1 Implementation of operations

❖
Adding Customer: Here admin can add new customer to the 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.
❖
Adding Tax: Here admin can add tax details.
❖
Updating Customer: Here customer can update his/her 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 atable.
• 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 acondition.
• 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”.

Shaheed Smarak Collage Page|20

 Delete statement:
• The DELETE statement is used to delete existing records in atable.
• The DELETE syntax would be as follows: DELETE FROM
table_name WHEREcondition.
• The following SQL statement delete's a record in the “customer” table: delete
from customer wheremeter_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 thetable.

• The syntax would be as follows: CREATETABLE table_name

(column1datatype, column2datatype, column3 datatype, column datatype,
PRIMARY KEY (one or morecolumns)).

 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 “tax” table:create table tax
(cost_per_unit int (20) primary key, meter_rent int (20), service_charge int (20),
service_tax int (20), swacch_bharat_cess int (20), gst int (20));

 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));

 The following SQL statement creates a table “meter_info” table: create table
meter_info (meter_no varchar (30), foreign key(meter_no) references
customer(meter_no) on delete cascade, meter_location varchar (10), meter_type
varchar (15), phase_code int (5), bill_type varchar (10), days int (5)

Shaheed Smarak Collage Page|21

 4.3 Algorithm or pseudo code of implementation
Explanation of Algorithm or pseudo code of system:

 Start system
 Enter login name and password
 On clicking the login button
 Connect to data base
 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
Algorithm or pseudo code of admin:

Login:
 This program will allow the admin to enter the user name 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 user name and answer for
security question.
 After successful login the admin will be redirected to admin portal page where he/she can
do following activities.

New Customer:
 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 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 on to next button.
 If we need to cancel the particular that has been entered click onto cancel option
 If we need to submit the particular that has been entered click onto submit option.

Shaheed Smarak Collage Page|22

Customer Details:
 This program will allow the admin to view customer details.
 If we need to print the particular that has been viewed click onto print option.

Deposit Details:
 This program will allow the admin to view bill details. If we need to sort the particulars
based on meter_no and month.
 If we need to search the particular that has been viewed click onto search option.
 If we need to print the particular that has been viewed click onto print option.

Tax Details:
 This program will allow the admin to add tax details. insert
the values into tax else print error
Submit the details of tax that has been entered by clicking onto submit button.
 If we need to cancel the particular that has been entered click onto cancel option.

Calculate Bill:
 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 particular that has been entered click onto cancel option.

Delete Bill:
 This Program will allow the admin to delete the customer info when meter_no is selected.
 If we need to delete the particular that has been saved click onto delete option.
 If we need to cancel the particular that has been entered click onto back option.

Shaheed Smarak Collage Page|23

About:
 This program will allow the admin to view details of the projectin short.
 If we need to exit the particular that has been viewed click onto exit option.

Algorithm or pseudo code 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.

Update Info:
 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 particular that has been updated, click onto back option.

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

Pay Bill:
 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 particular that has been viewed click onto back option.
 If we need to pay the bill amount that has been viewed click onto pay option.

Bill Details:
 This program will allow the customer to view bill details.
 If we need to print the particular that has been viewed click onto print option.

Shaheed Smarak Collage Page|24

Generate Bill:
 This program will allow the customer to generate bill when meter_no and month is
selected.
 Generate the details by clicking on generate bill button.

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

NOTE: Utility (notepad, browser and calculators), query and logout are given to both customer and
admin portals.

Shaheed Smarak Collage Page|25

 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 away 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.

Shaheed Smarak Collage Page|26

 Table5.1: Negative test case for phone number insertion

Function Input Expected Error Resolved

Name Output
Input phone 98977 Phone Length of Consume()
number number is phone
invalid number is not
equal to
10

Input phone 98977agv Phone Alphabets

number number is are being
invalid taken as _
input for
phone
number

Table5.2: Positive test case for phone number insertion

Function Input Expected Error Resolved

Name Output
Input phone 9897778988 Expected
number output is _ _
seen

Table5.3: Negative test case for email insertion

Function Input Expected Error Resolved

Name Output
Input email Sai1.in Email is Email is not in a Consume()
in valid format given

Table5.4: Positive test case for email insertion

Function Input Expected Error Resolved

Name Output
Input email [email protected] Expected
output is seen _ _

Shaheed Smarak Collage Page|27

 Table5.5: Negative test case for customer name insertion

Function Input Expected Error Resolved

Name Output
Input Sana123 Name is Numbers are Consume()
customer in valid being taken as
name input for name

Table5.6: Positive test case for customer name insertion

Function Input Expected Error Resolved

Name Output
Input Gowthu Expected
customer output is seen _ _
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 i
fall the modules can be integrated properly. We have been identified and debugged.

Table5.7:Test case on basis of generation of bill

Function Input Expected Error Resolved

Name Output
Negative 12334 (meter_no) Details seen Output not Consume()
searching of January(month) but not seen
total_bill total_bill
Positive 12334 (meter_no) Must display
searching of January(month) full generated
total_bill bill with _ _
total_bill

Shaheed Smarak Collage Page|28

 Table5.8: Test case on basis of deposits details

Function Input Expected Error Resolved

Name Output
Negative 12334 (meter_no) Details not Output not Consume()
searching of January(month) seen seen
deposited details

Positive 12334 (meter_no) Must display

searching of January(month) deposite details _ _
total_bill

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 meet sits requirements.
Each module and component of ethereal was thoroughly tested to remove bugs through a
system testing strategy. Test cases were generated for all possible input sequences and the
output was verified for its correctness.

Table5.9: Test cases for the project

Steps Action Expected output

Step 1 The screen appears when the A page with different menu’s
choice users run the program. appears.
1.If admin login 1.Admin panel opens
2.If customer login 2.Customer panel opens

Step 2 The screen appears when the A window for adding new
admin logs in and selects any customer, inserting tax,
one of the menus from the calculate bill, view deposit
click of the mouse. details etc

Selection1  New Customer

 Customer Details
 Deposit Details
 Calculate Bill
 Tax Details
 Delete Customer

Shaheed Smarak Collage Page|29

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

Selection 2  Update Details

 View Details
Selection 2a  Generate Bill
Selection 2b  Pay Bill
 Bill Details

Shaheed Smarak Collage Page|30

 CHAPTER 6
DISCUSSION AND SNAPSHOTS
6.1 TABLES:
The given below table is a snapshot of backend view of the local host and the structures
of the tables present in Electricity Billing System. The tables present are login, customer, tax,
bill, meter_info.

 The login is used to store the details of login’s admin and customer with meter_no.
 The customer is used to store details of customer.
 The tax is used to store tax values.
 The rent is used to store rent values.
 The bill is used to store details of bill of meter.
 The meter_info is used to store information of meter placed.

FIG6.1: List of tables

Login Table:

FIG6.2: login table description

Shaheed Smarak Collage Page|31

CustomerTable:

FIG6.3: customer table description

Tax Table:

FIG6.4: tax table description

RentTable:

FIG6.5: rent table description

BillTable:

FIG6.6: Bill table description

Shaheed Smarak Collage Page|32

Meter_InfoTable:

FIG6.7: meter_info table description

6.2 SCREENSHOTS:

FIG6.8: Splash page of Electricity Billing System

Shaheed Smarak Collage Page|33

 FIG6.9: Login page

FIG6.10: Signup page

Shaheed Smarak Collage Page|34

 FIG6.11: Forgot Password page

FIG6.12: Admin homepage

Shaheed Smarak Collage Page|35

 FIG6.13: New customer page

FIG6.14: Meter Info page

Shaheed Smarak Collage Page|36

 FIG6.15: Customer Details page

FIG6.16: Tax Details page

Shaheed Smarak Collage Page|37

 FIG6.17: Calculate Bill page

FIG6.18: Delete Customer page

Shaheed Smarak Collage Page|38

 FIG6.19: Customer Homepage

FIG6.20: Update customer details page

Shaheed Smarak Collage Page|39

 FIG6.21: View Customer Details page

FIG6.22: Query page

Shaheed Smarak Collage Page|40

 FIG6.23: Pay Bill page

FIG6.24: Paytm page

Shaheed Smarak Collage Page|41

 FIG6.25: Bill Details page

FIG6.26: Generate Bill page

Shaheed Smarak Collage Page|42

 FIG6.27: Deposit Details page

FIG6.28: About page

Shaheed Smarak Collage Page|43

 CONCLUSION

After all the hard work is done for electricity bill management system is here. It is
software which helps the user to work with the billing cycles, paying bills, managing different
DETAIL Sunder which 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.

Shaheed Smarak Collage Page|44

 BIBLIOGRAPHY
REFERENCES
Book Reference
Database Management Systems 3rd Edition by Raghu Rama Krishnan
(TEXTBOOK).
Websites
 www.stackoverflow.com
 www.google.com
 http://www.javatpoint.com/

Shaheed Smarak Collage Page|45