ELECTRICITY BILLING SYSTEM

A minor project report submitted in partial fulfilment of the requirements for the
award of the Degree of Bachelor of Technology
In

COMPUTER SCIENCE & ENGINEERING

Submitted by
Ashis Mohanty(1601292038)
Pabitra Kumar Sahoo(1601292070)
Kunal Kar(1601292379)

Under the Guidance of

Prof. Soumya Das GEC,
Bhubaneswar.

Dept. of Computer Science & Engineering

Gandhi Engineering College, Bhubaneswar

 Certificate
This is to certify that the Project entitled “Electricity Billing
System”, being submitted by Ashis Mohanty,Kunal Kar,
Pabitra Kumar Sahoo bearing Regd.No,1601292038,1601292379,
1601292070 for the award of degree of Bachelor of Technology in
Computer Science & Engineering, is a record of bona fide Project
work carried out by him under my supervision. The matter embodied
in this project have not been submitted for the award of any other
degree anywhere.

(Prof. Mohini P. Mishra) (Prof. Soumya Das)

HOD CSE Project Guide
 Acknowledgement
Our sincere thanks to Mohini .P. Mishra, Professor and Head of
Department of Computer Science and Engineering, Gandhi Engineering
College, Bhubaneswar for his encouragement and valuable suggestions
during the period of our Project work.

No words would suffice to express my regards and gratitude

to Prof. Soumya Das, Department of Computer Science and
Engineering, for his inspiring guidance and constant
encouragement, immense support and help during the project
work.

Date:- Ashis Mohanty(1601292038)

Place:- GEC,BBSR Kunal Kar (1601292379)

Pabitra Kumar Sahoo(1601292070)
 Content

Sl.No Description Page No.

Certificate
Acknowledgement
Abstract
1. Introduction 1

2. Objective of the Project 1

3. Feasibility Analysis 2

4. System Requirement Specification 4

5. Design 5

6. Database Specification 11

7. Data flow diagram 14

8. E-R Diagram 15

9. Coding 16

10. Testing 19

11. Sample Output 21

12. Conclusion 24

13. Future Scope 25

14. Bibliography 26
 ` Abstract
A new software system to modernize the electricity billing procedure is required. This electricity billing system would
replace the traditional and analog type of electricity billing system ensuring security, ease and comfort in billing. it meets
the current user demands and new features can be easily integrated into the system in future as per user requirements. The
application has high speed of performance with accuracy and efficiency. The software provides facility of data sharing. It
does not require staff as in the conventional system. It has the provision of security restriction. It require small storage for
installation and functioning. There is a provision for debugging if any problem is encountered in the systemThe purpose of
the electricity billing system is to automate the existing manual system by the help of
computerized equipments and full fledged computer
A new software system to modernize the electricity billing procedure is required.
This electricity billing system would replace the traditional and analog type of electricity billing system ensuring security,
ease and comfort in billing.
it meets the current user demands and new features can be easily integrated into the system in future as per user
requirements
. The application has high speed of performance with accuracy and efficiency. The software provides facility of data
sharing. It does not require staff as in the conventional system
. It has the provision of security restriction
. It require small storage for installation and functioning.
There is a provision for debugging if any problem is encountered in the system.
1.Introduction about the project
The Project Electricity billing system is system is made to keep the records about the bills of the customer
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.

Existing System:

In the existing system only we can see the details of particular information about the police stations in our state,
the existing system has more workload for the authorized person, but in the case of Proposed System, the user can
registered in our site and send the crime report and complaint about a particular city or person.

Drawbacks of Existing System

 More man power.

 Time consuming.
 Consumes large volume of pare work.
 Needs manual calculations.
 No direct role for the higher officials.
 Damage of machines due to lack of attention.
To avoid all these limitations and make the working more accurately the system needs to be computerized.

2. OBJECTIVE OF THE PROJECT

The Primary aim of this software is to provide an improved design methodology, which envisages the future
Expansion, and modification. This necessitates the design to be expandable and modifiable and so a popular approach is
used in developing a software. Anybody who is an meter holder in this bank can become a member of online electricity
system. He has to fill the form with his personal details and meter number.
 All transaction are carried out online by transferring from accounts in the customer name. This software is
meant to overcome the drawback of the manual system. The software has been developed using the most powerful and
secure backend ORACLE SQL. and the most widely accepted web oriented as well as application oriented
programming language java.

Electrcity billing System can help to meet and overcome the problem of manual processing. Electricity billing
System offer flexible client-server technology based on a scalable system. It’s Centralized and customer centric design
offers a complete set of integral retails banking modules sharing a user-friendly interface. This project includes the entire
upgraded feature required for the computerization electricity system. This system is very easy to use, so that any user
can use without getting pre-knowledge about this.
This system is completely GUI based and can be use by mouse and as well as keyboard. This system is melded
in such a way that has got all features to upgrade without making much change in existing components .

Proposed System:
The aim of proposed system is to develop a system of improved facilities. The proposed system can overcome all
the limitations of the existing system. The system provides proper security and reduces the manual work. The existing
system has several disadvantages and many more difficulties to work well. The proposed system tries to eliminate or
reduce these difficulties up to some extent. The proposed system will help the user to reduce the workload and mental
conflict. The proposed system helps the user to work user friendly and he can easily do his jobs without time lagging.

3. Feasibility Analysis:-
Depending on the results of the initial investigation, the survey is expanded to a more detailed feasibility study.
A feasibility study is a test of a system proposal. According to its workability, impact on the organization, ability to
meet user’s needs and effective use of the resources its main task done during the feasibility study are:-

1. Evaluation of existing system and procedures. Our group went to various electricity Professionals
to gather information about the software system. They are using and evaluating those system and
the procedures invoked in it during the period of feasibility study.

2. Analysis of alternative candidate systems after studying the various systems we derived various
alternatives through which we develop our project and evaluated the alternative. The most appropriate
is selected.

FEASIBILITY STUDY
The only tangible benefit provided by the proposed system is that the paper work is reduced to the minimum
and hence the reduction in cost incurred on Stationary and its storage.
The system provides many benefits that can’t be measured in terms of Money for e.g. user’s friendliness, more
user response being more efficient.
TECHNICAL FEASIBILITY:-
The proposed system is technically feasible as it can be developed easily with the help of available technology. The
proposed system requires Sublime Text Editor using JAVA as a Interface for Programming & back-end as ORACLE
SQL for storing/maintaining database.
 OPERATIONAL FEASIBILITY:-
Automation makes our life easy. The proposed system is highly user friendly and is much easily able to interact with the
system. Therefore the users will readily accept the system as data entry and making queries can be easily done.

SDLC (Software Development Life Cycle)

The systems development life cycle (SDLC), or software development process in systems
engineering, information systems and software engineering, is a process of creating or altering information systems, and
the models and methodologies that people use to develop these systems. In software engineering, the SDLC concept
underpins many kinds of software development methodologies. These methodologies form the framework for planning
and controlling the creation of an information system: the software development process.

A Systems Development Life Cycle (SDLC) adheres to important phases that are essential for developers, such
as planning, analysis, design, and implementation, and are explained in the section below.It include evaluation of present
system, information gathering, feasibility study and request approval. A number of system development life cycle (SDLC)
models have been created: waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, and synchronize and
stabilize. The oldest of these, and the best known, is the waterfall model: a sequence of stages in which the output of each
stage becomes the input for the next. These stages can be characterized and divided up in different ways, including the
following:
 Systems analysis, requirements definition: Defines project goals into defined functions and operation of the
intended application. Analyzes end-user information needs.
 Systems design: Describes desired features and operations in detail, including screen layouts, business rules,
process diagrams, pseudo code and other documentation.
 Development: The real code is written here.
 Integration and testing: Brings all the pieces together into a special testing environment, then checks for errors,
bugs and interoperability.
 Acceptance, installation, deployment: The final stage of initial development, where the software is put into
production and runs actual business.
 Maintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a
different computing platform and more. This is often the longest of the stages.

4. System Requirement Specification

Hardware Specification:-
Processor : Intel i3 5th Generation
RAM : 8 GB
Hard disk : 1 TB
Monitor : 14 inch
Mouse : 3 Button scroll

Software Specification:-
Operating System : Windows 10
Languages : java
Platform : Netbeans
Web Servers : Wampserver
Backend : Oracle11g
Browser Program : Google Chrome
5. Design:-

Language (JAVA) :-

Java is a small, simple, safe, object oriented,architectural,multithreaded programming language

with a strongly typed exception-handling for writing distributed and dynamically extensible programs.

Java a supports this application and the follow features make it one of the best programming languages.
 It is simple and object oriented
 It helps to create user friendly interfaces.
 It is very dynamic.
 It supports multithreading.
 It is platform independent
 It is highly secure and robust.
 It supports internet programming
Java applications are typically compiled to byte code which can run on any Java virtual machine (JVM)
regardless of computer architecture.
Different "editions" of the platform are available, including:

 Java ME (Micro Edition): Specifies several different sets of libraries (known as profiles)
for devices which are sufficiently limited that supplying the full set of Java libraries would
take up unacceptably large amounts of storage.
 Java SE (Standard Edition): For general purpose use on desktop PCs, servers and similar
devices.
 Java EE (Enterprise Edition): Java SE plus various APIs useful for multi-tier client-server
enterprise applications.

 Java Virtual Machine:-

The heart of the Java Platform is the concept of a "virtual machine" that executes Java bytecode
programs. This bytecode is the same no matter what hardware or operating system the program is running
under. There is a JIT compiler within the Java Virtual Machine, or JVM. The JIT compiler translates the
Java bytecode into native processor instructions at run-time and caches the native code in memory during
execution.

Platform independence:-
One characteristic, platform independence, means that programs written in the Java language
must run similarly on any supported hardware/operating-system platform. One should be able to write a
program once, compile it once, and run it anywhere. And JAVA is platform Independent.

Automatic Memory Management:-

In Java, memory management is the process of allocation and de-allocation of objects,
called Memory management. Java does memory management automatically. Java uses an automatic
memory management system called a garbage collector. Thus, we are not required to implement memory
management logic in our application.
OOPs Concept:-
As the name suggests, Object-Oriented Programming or OOPs refers to languages that uses objects in programming.
Object-oriented programming aims to implement real-world entities like inheritance, hiding, polymorphism etc in
programming The main aim of OOP is to bind together the data and the functions that operate on them so that no other part
of the code can access this data except that function.
 Polymorphism
 Inheritance
 Abstraction
 Encapsulation
 Class
 Object
Java is not purely OOP language cause It support pre-defined datatypes.

 Java 2 Enterprise Edition(J2EE):

The J2EE platform uses a multitier distributed application model. Application logic is divided
into components according to function, and the various application components that make up a J2EE
application are installed on different machines depending on the tier in the multitier J2EE environment to
which the application component belongs. Figure shows two multitier J2EE applications divided into the
tiers described in the following list. The J2EE application parts shown in Figure are presented in J2EE
Components.

 Client-tier components run on the client machine.

 Web-tier components run on the J2EE server.
 Business-tier components run on the J2EE server.
 Enterprise information system (EIS)-tier software runs on the EIS server.

Although a J2EE application can consist of the three or four tiers shown in Figure J2EE multitier
applications are generally considered to be three-tiered applications because they are distributed over
three different locations: client machines, the J2EE server machine, and the database or legacy machines
at the back end. Three-tiered applications that run in this way extend the standard two-tiered client and
server model by placing a multithreaded application server between the client application and back-end
storage.
J2EE Clients
A J2EE client can be a Web client or an application client.

Web Clients :
A Web client consists of two parts: dynamic Web pages containing various types of markup
language (HTML, XML, and so on), which are generated by Web components running in the Web tier,
and a Web browser, which renders the pages received from the server.
A Web client is sometimes called a thin client. Thin clients usually do not do things like query
databases, execute complex business rules, or connect to legacy applications. When you use a thin
client, heavyweight operations like these are off-loaded to enterprise beans executing on the J2EE
server where they can leverage the security, speed, services, and reliability of J2EE server-side
technologies.

Application Clients :
A J2EE application client runs on a client machine and provides a way for users to handle tasks
that require a richer user interface than can be provided by a markup language. It typically has a
graphical user interface (GUI) created from Swing or Abstract Window Toolkit (AWT) APIs, but a
command-line interface is certainly possible.
Application clients directly access enterprise beans running in the business tier. However, if
application requirements warrant it, a J2EE application client can open an HTTP connection to establish
communication with a servlet running in the Web tier.
 JavaBeans Component Architecture:
The server and client tiers might also include components based on the JavaBeans component
architecture (JavaBeans component) to manage the data flow between an application client or applet
and components running on the J2EE server or between server components and a database. JavaBeans
components are not considered J2EE components by the J2EE specification.
JavaBeans components have instance variables and get and set methods for accessing the data
in the instance variables. JavaBeans components used in this way are typically simple in design and
implementation, but should conform to the naming and design conventions outlined in the JavaBeans
component architecture.

J2EE Server Communications :

The client communicates with the business tier running on the J2EE server either directly or, as
in the case of a client running in a browser, by going through JSP pages or servlets running in the Web
tier.J2EE application uses a thin browser-based client or thick application client. In deciding which one
to use, you should be aware of the trade-offs between keeping functionality on the client and close to
the user (thick client) and off-loading as much functionality as possible to the server (thin client). The
more functionality you off-load to the server, the easier it is to distribute, deploy, and manage the
application; however, keeping more functionality on the client can make for a better perceived user
experience.
Web Components:-
J2EE Web components can be either servlets or JSP pages. Servlets are Java programming
language classes that dynamically process requests and construct responses. JSP pages are text-based
documents that execute as servlets but allow a more natural approach to creating static content. Static
HTML pages and applets are bundled with Web components during application assembly, but are not
considered Web components by the J2EE specification. Server-side utility classes can also be bundled
with Web components and, like HTML pages, are not considered Web components. Like the client tier
and as shown in Figure , the Web tier might include a JavaBeans component to manage the user input
and send that input to enterprise beans running in the business tier for processing

 Business Components :-
Business code, which is logic that solves or meets the needs of a particular business domain
such as banking, retail, or finance, is handled by enterprise beans running in the business tier. An
enterprise bean also retrieves data from storage, processes it (if necessary), and sends it back to the
client program
  Java Server Pages (JSP):

Java Server Pages technology is the Java platform technology for building applications
containing dynamic Web content such as HTML, DHTML and XML. The Java Server Pages technology
enables the authoring of Web pages that create dynamic content easily but with maximum power and
flexibility.

 Write Once, Run Anywhere properties:

The Java Server Pages technology is platform independent, both in its dynamic Web pages, its
Web servers, and its underlying server components.

 Reuse of components and tag libraries:-

The Java Server Pages technology emphasizes the use of reusable components such as:
JavaBeans components, Enterprise JavaBeans components and tag libraries.
 Separation of dynamic and static content:-
The Java Server Pages technology enables the separation of static content from
Dynamic content that is inserted into the static template. This greatly simplifies the creation of
content. This separation is supported by beans specifically designed for the interaction with server-side
objects.
 Support for scripting and actions:-
The Java Server Pages technology supports scripting elements as well as actions.
Actions permit the encapsulation of useful functionality in a convenient form that
Can also be manipulated by tools; scripts provide a mechanism to glue together this
Functionality in a per-page manner.
 Wampserver

Wampserver is a servlet container and Java Server Pages implementation it may be used stand
alone, or in conjunction with several popular web servers.
Wampserver is a security update release. This release closes a whole that potentially allowed access to
resources protected by a <security constraint > in web.xml.

6. Database Specification:-
A database is an organized mechanism that has the capability of storing information through which a user can
retrieve stored information in an effective and efficient manner. The data is the purpose of any database and must be
protected.
The database design is a two level process. In the first step, user requirements are gathered together and a database
is designed which will meet these requirements as clearly as possible. This step is called Information Level Design and it
is taken independent of any individual DBMS.
In the second step, this Information level design is transferred into a design for the specific DBMS that will be
used to implement the system in question. This step is called Physical Level Design, concerned with the characteristics of
the specific DBMS that will be used. A database design runs parallel with the system design. The organization of the data
in the database is aimed to achieve the following two major objectives.
o Data Integrity
o Data independence
Normalization is the process of decomposing the attributes in an application, which results in a set of tables with
very simple structure. The purpose of normalization is to make tables as simple as possible. Normalization is carried out
in this system for the following reasons.
 To structure the data so that there is no repetition of data , this helps in
Saving.
 To permit simple retrieval of data in response to query and report request.
 To simplify the maintenance of the data through updates, insertions,
Deletions.
 To reduce the data need to restrict which new application requirements arise.
Introduction to SQL: -

SQL is a standard computer language for accessing and manipulating databases.

SQL stands for Structured Query Language.

SQL allows you to access a database.

SQL is an ANSI standard computer language.

SQL can execute queries against a database.

SQL can retrieve data from a database.

SQL can insert new records in a database.

SQL can delete records from a database.

SQL can update records in a database. SQL is easy to learn

SQL Data Query Language

 This is used to fetch record from table.

 SELECT - extracts data from a database table
SQL Data Manipulation Language (DML)
 SQL (Structured Query Language) is syntax for executing queries. But the SQL language also includes syntax
to update, insert, and delete records.
 These query and update commands together form the Data Manipulation Language (DML) part of SQL: -
 SELECT - extracts data from a database table

 UPDATE - updates data in a database table

 DELETE - deletes data from a database table

 INSERT – insert data into a database table

SQL Data Definition Language (DDL)

 The Data Definition Language (DDL) part of SQL permits database tables to be created or deleted. We can also
define indexes (keys), specify links between tables, and impose constraints between database tables.

 The most important DDL statements in SQL are: -

CREATE TABLE - creates a new database table
ALTER TABLE - alters (changes) a database table
DROP TABLE - deletes a database table
 TRUNCATE – delete records permanently
 SQL Transaction Control Language
 To save or discard the Transaction, SQL provides 3 statements.
 Commit - commits a Transaction.
 Rollback- rollbacks a transaction in case of any error occurs.
 Savepoint- sets a savepoint within a transaction.

SQL Data Control Language

 Grant :- To assign the permission to the User.
 Revoke :- To remove permission from the User.

Table Structure:- User

Field name Data type Length Key
Meter_Number Number 15 Primary key
meter_Code Number 6 -
meter_Type Varchar2 20 -
Connection Varchar2 20 -
Date_of_Issue Varchar2 20 -
Customer_Name Varchar2 50 -
Cust_Father_Name Varchar2 50 -
Cust_Mother_Name Varchar2 50 -
Cust_DOB Varchar2 20 -
Gender Varchar2 15 -
Nationality Varchar2 20 -
Marital_status Varchar2 15 -
PAN_Number Varchar2 10 Unique
Aadhaar Number 12 Unique
Email Varchar2 50 Not null
Mobile Number 15 not null
Permanent_Address Varchar2 100
Permanent_City Varchar2 20
Permanent_State Varchar2 20
Permanent_Area_Pin Number 6
Communication_Address Varchar2 100
Communication_City Varchar2 20
Communication_State Varchar2 20
Communication_Area_Pin Number 6
 Religion Varchar2 20
Category Varchar2 20
Qualification Varchar2 20
Occupation Varchar2 20
Password Varchar2 50
Photo Varchar2 50
Debit_Card Number 1
Internet_Banking Number 1

7. DATA FLOW DIAGRAM:-

The data flow diagram is also known as “bubble chart” has the purpose of clarifying system requirements and
identifying major transformations that will become programs in system design so it is the starting point of specification
down to the lowest level of detail. A DFDs consists of a series if bubbles joined by lines. The bubbles represent data
transformation and the lines represent the data flow in the system.

 DFD SYMBOLS:
 A system defined a source or destination of data.
 An arrow identifies data flow, data in motion.
 A circle represents the process that transforms incoming data flow to outgoing data flow.
 An open rectangular is data store-data at rest or a temporary repository of data.
Diagram Below :-

Connection Meter no
8. E-R DIAGRAM:-
ER-modeling is a data modeling technique used in software engineering to produce a conceptual data model of a
information system. Diagrams created using this ER-modeling technique are called Entity-Relationship Diagrams, or
ER diagrams or ERDs. So you can say that Entity Relationship Diagrams illustrate the logical structure of databases.
The original notation for ER-Diagrams uses rectangles to represent entities, and diamonds to represent
relationships.
There are three basic elements in ER-Diagrams:
 Entities are the "things" for which we want to store information. An entity is a person, place, thing or event.
 Attributes are the data we want to collect for an entity.
 Relationships describe the relations between the entities.

The Diagram in below :-

 9. Coding:-

1-package electricity.billing.system;

import java.sql.*;

public class conn{

Connection c;
Statement s;
public conn(){
try{
Class.forName("com.mysql.jdbc.Driver");
c =DriverManager.getConnection("jdbc:mysql:///project","root","");
s =c.createStatement();

}catch(Exception e){
System.out.println(e);
}
}
}

2- package electricity.billing.system;
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;

public class splash {

public static void main(String[] args){
fframe f1 = new fframe();
f1.setVisible(true);
int i;
int x=1;
for(i=2; i<=600; i+=4, x+=1){
f1.setLocation(800 - ((i+x)/2), 500 - (i/2));
f1.setSize(i+x,i);
try{
Thread.sleep(10);
}catch(Exception e){}
}

}
}
class fframe extends JFrame implements Runnable{
Thread t1;
fframe(){
super("Electricity Billing System");
setLayout(new FlowLayout());
ImageIcon c1 = new ImageIcon(ClassLoader.getSystemResource("icon/elect.jpg"));
Image i1 = c1.getImage().getScaledInstance(730, 550,Image.SCALE_DEFAULT);
ImageIcon i2 = new ImageIcon(i1);
 JLabel l1 = new JLabel(i2);
add(l1);
t1 = new Thread(this);
t1.start();
}
public void run(){
try{
Thread.sleep(7000);
this.setVisible(false);

Login l = new Login();

l.setVisible(true);
}catch(Exception e){
e.printStackTrace();
}
}
}

3- package electricity.billing.system;
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
import java.sql.*;

public class Login extends JFrame implements ActionListener{

JLabel l1,l2,l3;
JTextField tf1;
JPasswordField pf2;
JButton b1,b2;
JPanel p1,p2,p3,p4;
Login(){
super("Login Page");

l1 = new JLabel("Username");
l2 = new JLabel("Password");
tf1 = new JTextField(15);
pf2 = new JPasswordField(15);

ImageIcon ic1 = new ImageIcon(ClassLoader.getSystemResource("icon/login.png"));

Image i1 = ic1.getImage().getScaledInstance(16, 16,Image.SCALE_DEFAULT);
b1 = new JButton("Login", new ImageIcon(i1));

ImageIcon ic2 = new ImageIcon(ClassLoader.getSystemResource("icon/cancel.jpg"));

Image i2 = ic2.getImage().getScaledInstance(16, 16,Image.SCALE_DEFAULT);
b2 = new JButton("Cancel",new ImageIcon(i2));

b1.addActionListener(this);
b2.addActionListener(this);

ImageIcon ic3 = new ImageIcon(ClassLoader.getSystemResource("icon/pop.png"));

Image i3 = ic3.getImage().getScaledInstance(128, 128,Image.SCALE_DEFAULT);
ImageIcon icc3 = new ImageIcon(i3);
 l3 = new JLabel(icc3);

setLayout(new BorderLayout());

p1 = new JPanel();
p2 = new JPanel();
p3 = new JPanel();
p4 = new JPanel();

add(l3,BorderLayout.WEST);
p2.add(l1);
p2.add(tf1);
p2.add(l2);
p2.add(pf2);
add(p2,BorderLayout.CENTER);

p4.add(b1);
p4.add(b2);
add(p4,BorderLayout.SOUTH);

p2.setBackground(Color.WHITE);
p4.setBackground(Color.WHITE);
setSize(440,250);
setLocation(600,400);
setVisible(true);

}
public void actionPerformed(ActionEvent ae){

try{
conn c1 = new conn();
String a = tf1.getText();
String b = pf2.getText();
String q = "select * from login where username = '"+a+"' and password = '"+b+"'";
ResultSet rs = c1.s.executeQuery(q);
if(rs.next()){
new Project().setVisible(true);
this.setVisible(false);

}else{
JOptionPane.showMessageDialog(null, "Invalid login");
setVisible(false);
}
}catch(Exception e){
e.printStackTrace();
System.out.println("error: "+e);
}
}

public static void main(String[] args){

new Login().setVisible(true);
}
}
10. Testing:-
Software Testing is the process of executing software in a controlled manner, in order to answer the
question - Does the software behave as specified?. Software testing is often used in association with the
terms verification and validation. Validation is the checking or testing of items, includes software, for
conformance and consistency with an associated specification. Software testing is just one kind of
verification, which also uses techniques such as reviews, analysis, inspections, and walkthroughs. Validation
is the process of checking that what has been specified is what the user actually wanted.
Validation : Are we doing the right job?
Verification : Are we doing the job right?
Software testing should not be confused with debugging. Debugging is the process of analyzing and
localizing bugs when software does not behave as expected. Although the identification of some bugs will be
obvious from playing with the software, a methodical approach to software testing is a much more thorough
means for identifying bugs. Debugging is therefore an activity which supports testing, but cannot replace
testing.
Testing is a set of activity that can be planned in advanced and conducted systematically. Testing
begins at the module level and work towards the integration of entire computers based system. Nothing is
complete without testing, as it vital success of the system testing objectives, there are several rules that can
serve as testing objectives. They are

 Testing is a process of executing a program with the intend of finding an error.

 A good test case is one that has high possibility of finding an undiscovered error.

 A successful test is one that uncovers an undiscovered error.

If a testing is conducted successfully according to the objectives as stated above, it would uncovered errors in
the software also testing demonstrate that the software function appear to be working according to the specification,
that performance requirement appear to have been met.There are three ways to test program.
 For correctness
 For implementation efficiency
 For computational complexity
TEST PLAN
A test plan implies a series of desired course of action to be followed in accomplishing various testing
methods. The Test Plan acts as a blue print for the action that is to be followed. The software engineers create a
computer program, its documentation and related data structures. The software developers is always responsible
for testing the individual units of the programs, ensuring that each performs the function for which it was
designed. There is an independent test group (ITG) which is to remove the inherent problems associated with
letting the builder to test the thing that has been built. The specific objectives of testing should be stated in
measurable terms. So that the mean time to failure, the cost to find and fix the defects, remaining defect density
or frequency of occurrence and test work-hours per regression test all should be stated within the test plan.
 The levels of testing include:
Unit testing
Integration Testing
Data validation Testing
Output Testing
1. UNIT TESTING
Unit testing focuses verification effort on the smallest unit of software design – the software component or module.
Using the component level design description as a guide, important control paths are tested to uncover errors within the
boundary of the module. The relative complexity of tests and uncovered scope established for unit testing. The unit
testing is white-box oriented, and step can be conducted in parallel for multiple components. The modular interface is
tested to ensure that information properly flows into and out of the program unit under test. The local data structure is
examined to ensure that data stored temporarily maintains its integrity during all steps in an algorithm’s execution.
Boundary conditions are tested to ensure that all statements in a module have been executed at least once. Finally, all
error handling paths are tested.
2. INTEGRATION TESTING

Integration testing is systematic technique for constructing the program structure while at the same time conducting
tests to uncover errors associated with interfacing. The objective is to take unit tested components and build a program
structure that has been dictated by design. The entire program is tested as whole. Correction is difficult because isolation
of causes is complicated by vast expanse of entire program. Once these errors are corrected, new ones appear and the
process continues in a seemingly endless loop.

After unit testing in Sell-Soft System all the modules were integrated to test for any inconsistencies in the interfaces.
Moreover differences in program structures were removed and a unique program structure was evolved.

3. VALIDATION TESTING OR SYSTEM TESTING

This is the final step in testing. In this the entire system was tested as a whole with all forms, code, modules and class
modules. This form of testing is popularly known as Black Box testing or System tests.
Black Box testing method focuses on the functional requirements of the software. That is, Black Box testing enables
the software engineer to derive sets of input conditions that will fully exercise all functional requirements for a program.
Black Box testing attempts to find errors in the following categories; incorrect or missing functions, interface errors,
errors in data structures or external data access, performance errors and initialization errors and termination errors.
4. OUTPUT TESTING OR USER ACCEPTANCE TESTING
 The system considered is tested for user acceptance; here it should satisfy the firm’s need. The software should keep
in touch with perspective system; user at the time of developing and making changes whenever required. This done
with respect to the following points.
1. Input Screen Designs,
2. Output Screen Designs,
3. Online message to guide the user and the like.
The above testing is done taking various kinds of test data. Preparation of test data plays a vital role in the
system testing. After preparing the test data, the system under study is tested using that test data. While testing the
system by which test data errors are again uncovered and corrected by using above testing steps and corrections are also
noted for future use.

11. Sample Output :-

10001----------------------1
Home ----------------------- 2
Public ---------------------- 4
Manish Pande ---------------------- 5
1996-02-07----------------------6
Male ---------------------- 7
Biswa Behera-----------------------8
Indian ---------------------- 9
Rani Behera ---------------------- 10
Married ---------------------- 11
9874579612----------------------12
655232219663----------------------13
securebank.service@gmail.com ---------------------- 14
9853632148----------------------15
AT/po -ctc ---------------------- 16
AT/po -ctc ---------------------- 17
cuttack ---------------------- 18
cuttack ---------------------- 19
Odisha ---------------------- 20
Odisha ---------------------- 21
782369----------------------22
782369----------------------23
Hinduism ---------------------- 24
SC ---------------------- 25
Under Graduation ---------------------- 26
Business -------------------------
Screenshots:-
12-Conclusion
The project titled as “Electricity billing system” is a web based application. This software provides facility
for, create, and update a person’s banking account with help of Internet. The customer can access the bank website
for viewing their account details and perform the transaction.
13-FUTURE SCOPE OF THE PROJECT
This project can be handled in future by doing various modifications like: -

1. We can go further for Online Banking.

2. We can establish and start various Branches and available help centers for Account Holder’s Queries.

3. We can also deal through internet by creating web pages and a banking website for internet dealing.

4. To attract Account Holder’s we can offer various offers during festivals months.

5. We can also deal in various types of Banking Transactions.

6. To have more and more customer satisfaction we will emphasize more and more on our dealings.
14-Bibliography:-
BOOKS:

 Rajeev mall ‘Software engineering’

 Elmasri Navathe ‘Fundamentals of database systems’

Sudarshan, Korth: Database System Concepts, 6th edition, McGraw-Hill Education

Advanced Java Programming, Uttar K. Roy, Oxford University Press.

Java 2: The Complete Reference by Herbert Scheldt, Fifth Edition Paperback

ONLINE REFERENCE:
www.geeksforgeeks.com
www.w3schools.com
www.wikipedia.com
WWW.TECHNOBUZZ.COM