A
MINI PROJECT REPORT
ON
“ENERGY BILLING SYSTEM”
Of
Database Management System Lab
SUBMITTED BY:
1. HARSHAL DALVI.
2. SHUBHAM KASAR.
3. PRIYANKA DEORE.
4. BHAGYASHRI KHAIRNAR.
UNDER THE GUIDANCE OF
Mr. A. R. JAIN.
(LECTURER, PVG COLLEGE OF ENIGNNERING, NASHIK)
Department Of Computer Engineering,
PVG COLLEGE OF ENGINEERING, NASHIK
Academic Year 2018-19
Table of Contents
Page
Sr. No Name Of Topic
No
Introduction
1 01
Scope
2 01
Requirement Analysis
4.1 Functional Requirement 02
3
4.2 Non Functional Requirement
Data Modeling
a. ER Diagram
b. Relational model 03
4
c. Normalization
Software Requirements
a. Front End
b. Back End
5 04
c. Database Connectivity
GUI (Graphical User Interface)
6 05
Source Code
7 08
Testing
8 10
Conclusion
9 12
INTRODUCTION
In today’s world of emerging technology, computers are playing a vital role in
every walk of life. The problems due to the traditional system are overcome with the
help of tasks being online. Maintenance of the data like insertion, deletion and
modification is difficult with manual systems. The basic option of security is itself not
provided which is of major concern. Apart from this, storage of the large amounts of
data is difficult. Moreover the problems of consistency, reliability, integrity also
exists. Since this is a manual system there is always a probability that there is loss of
data, resulting in less durability. As these issues are of major concern, we developed
an application were in all the above factors are achieved.
The application basically starts by asking the user to sign in. Later username and
password of the employee option is provided. Validating the username and password,
the user is directed to the homepage were in he has various options like consumer
management, revenue collection, billing and accounting, generating the report.
Regarding the modification, constraint is provided wherein the access is limited to the
administrator. The statuses of the requests are updated at the earliest. The rectification
information will be again updated for the knowledge of the employee. The employee
can check the status of the requests before accessing the computer, which will speed
up the disposal of the request. Thus, improving the overall efficiency of the
organization.
Scope
This application is basically written as a solution to the drawbacks of existing
system. This application can be used as a real world application and by any
organization. It’s could be used as a general application with few minor
modifications.
Purpose
The purpose of this application is to develop “EBS” (Electronic Billing System),
which is a web application which provides a service to all the customers and
employees to deal with the transactions online.
Page: 1
Requirement Analysis
In software engineering, a functional requirement defines a function of a software
system or its component. A function is described as a set of inputs, the behavior, and
outputs. Functional requirements may be calculations, technical details, data
manipulation and processing and other specific functionality that show how a use case
is to be fulfilled. They are supported by non-functional requirements, which impose
constraints on the design or implementation (such as performance requirements,
security, or reliability).As defined in requirements engineering, functional
requirements specify particular behaviors of a system. This should be contrasted with
non-functional requirements which specify overall characteristics such as cost and
reliability
Functional Requirements-
Bill generated automatically as per reading.
Its work speed is depends upon the processor speed or clock speed of
system.
Customer is able to see Generated Bill by putting Consumer Number and
also customer can take printout of same bill.
Non Functional Requirements –
There are two types of Non-Functional Requirements:-
1.) Software Requirements:
Operating System :- Windows 7/8/10, Ubuntu 14.04/16.04/18.04
Tools :- Mysql , Netbeans IDE 8.2
Languages :- JAVA, RDBMS
2.) Hardware Requirements:
Processor :- Pentium 3 or above
RAM :- 256 MB
Hard Disk :- Min.300 MB working space
Key Board :- 101 Standards
Page: 2
Data Modeling
ER diagram
Relational Modeling
Page: 3
Software Requirements
Front End:-
- jdk-8u181-windows-x64(JAVA)
- NetBeans 8.2 IDE
Back End:-
-MySQL 8.0.12
Database Connectivity:-
-MySQL [Link]
-[Link] connector
Page: 4
GUI (Graphical User Interface)
Front Page
Page: 5
Administrator Login
Customer Login
Page: 6
Help
Page: 7
Source Code
1) Login_Form Code :
package Billing_System;;
import [Link];
import [Link];
import [Link].*;
import [Link].*;
import [Link];
import [Link];
public class Login extends [Link] {
Connection con;
PreparedStatement pst;
ResultSet rs;
String sql;
String uname,passwd;
public Login() throws SQLException {
initComponents();
[Link](null);
} private void loginbtnActionPerformed([Link] evt) {
try {
con =
[Link]("jdbc:mysql://localhost:3306/project","root","nick@123");
sql="Select Uname,Password from Employee where Uname=?";
pst = [Link](sql);
[Link](1, [Link]());
rs = [Link]();
while([Link]())
{
uname=[Link]("Uname");
passwd = [Link]("Password");
}
Page: 8
if ([Link]([Link]()) && [Link]([Link]()))
{
[Link](null,"Login Successful");
close();
MainForm mf = new MainForm();
[Link](true);
}
else
{
[Link](null,"Incorrect UserName or Password...
Please Try again");
[Link]("");
[Link]("");
}
} catch (Exception ex) {
[Link](null,"Incorrect UserName or Password... Please Try
again");
[Link]("");
[Link]("");
}
}
private void registerbtnActionPerformed([Link] evt) {
close();
Register R=new Register();
[Link](true);
}
private void cancelbtnActionPerformed([Link] evt) {
[Link]();
Frontpage F;
F = new Frontpage();
[Link](true);
}
Page: 9
Testing
Test case Expected actual
[Link] Explanation Remarks
Name output output
Username & Username & Username &
1 Authentication Password Password Password is Pass
confirmation will accepted accepted
Username &
Username & Username &
Password
2 Authentication Password Password is Fail
should not
confirmation not matched
matched
Pin code Pin code Pin code
3 Acceptance should be 6 should accept Pass
digit accepted successfully
Pin code Pin code
Pin code not
4 Acceptance should be 6 should not Fail
accepted
digit accepted
Email should Email
Email should
5 Acceptance have correct accepted Pass
accepted
format successfully
Email should
Email should Email not
6 Acceptance have correct Fail
not accepted accepted
format
Consumer
Enter Correct
number Consumer is
7 Authentication consumer Pass
should accepted
number
accepted
Page: 10
Consumer
Enter Correct
number Consumer is
8 Authentication consumer Fail
should not present
number
present
Cannot leave
Field should Field is not
10 Field any field Pass
not empty Empty
empty
Cannot leave
Field should Field is
11 Field any field Fail
empty Empty
empty
Bill Details
Print the Bill Bill Details
12 Print should be Pass
Details are printed
printed
Mobile no.
Mobile No. Mobile no. Is
13 Mobile No Should be of Pass
Is 10 Digit of 10 digit
10 digit
Mobile no.
Mobile No. Should be Mobile no. Is
14 Mobile No Fail
Is 10 Digit not of 10 not 10 digit
digit
Reading Reading
Reading
should be should
15 Update reading updated Pass
enter in updated
successfully
database successfully
Page: 11
Conclusion
We have been given the problem of Billing of Electricity Consumers. Earlier the
Billing process is manually calculated by using the database small tolls and small
scale packages at their desktop. In our project “ENERGY BILLING SYSTEM”
we have automated the entire billing system is Online and centralized with all
offices which they have in the central power distribution company limited.
In Consumer Management, I have tracked all the information of the consumer and
have given the privileged modifications, changes.
As a result of this automation, manual workload is reduced and data retrieval
becomes easy. This project can be helpful for centralization of information.
Page: 12
