Online bill payments

1. INTRODUCTION

1.1 PROJECT SCOPE

Projects main aim is to build a Information based web based system for the
public to pay their bill with accurate planning method. In software website handling a
project and completing the work in time is most important factor. So there need to be
puzzled in certain process where entire details should be secured which includes bill
number, customer details, transaction Id.

1.2 PROJECT PURPOSE

This has been developed to override the problems prevailing in the practicing
manual system. This system addresses the concern of public in paying their bills.
Moreover this system is designed for the particular purpose of paying and tracking
bills without standing in a line and wasting one’s time. This website works in smooth
and effective manner. The operations which are performed in manual system takes
more time as they depend on more paper work. We need to develop an automated
system where administrator can maintain whole bills information and he can update as
fast as possible. As we can complete the work in a systematic proper plan using
automated scheme and in correct time which can perform operations in a smooth and
purposeful manner which gives an effective outlook.

1.3 PROJECT FEATURES

The main features of this project are this system deals with the problems on
managing a bill payment without going to the concerned departments or stand in long
queues. This helps in forward looking and futuristic approach. It helps in reducing
efforts and risks which need to be faced later. It helps in proper time administration. It
helps in maintaining an individual payment details by administrator. It also reduces
mental effort.

CMRTC 1
 Online bill payments

2. SYSTEM ANALYSIS

System Analysis is the important phase in the system development process.

The System is studied to the minute details and analyzed. The system analyst plays an
important role of an interrogator and dwells deep into the working of the present
system. In analysis, a detailed study of these operations performed by the system and
their relationships within and outside the system is done. A key question considered
here is, “what must be done to solve the problem?” The system is viewed as a whole
and the inputs to the system are identified. Once analysis is completed the analyst has
a firm understanding of what is to be done.

2.1 PROBLEM DEFINITION

The main problem in the project is time administration and manual work
flow. To reduce the hardships that is arising during developing a project. The manual
system is creating lot of massive work, threat of loss of files, tedious report generation
and redundancy in information storage. The administrator can’t analyze who is right
person in particular. In order to solve all these issues we have been developing a new
technique which is automated. This will be directly storing the results of each and
every student by an administrator is to be done properly.

2.2 EXISTING SYSTEM

The system addresses the concern of public in paying their bills. In the present
scenario the individual has to go to the concerned office or department for the bill
payment. Another alternative is using the e-seva centers to pay the bills. Although the
E-seva centers have reduced the congestion it is a one way traffic system. It allows
only the government staff to accept payments and issue bills. The public cannot get
anything from the website. For eg:- The individual cannot keep track of his earlier
payments, settled and unsettled bills. He has to have the originals or run around for
duplicates. This is a lot of work around for the individual. Another scenario would be
in the case of companies who pay huge bills and take credit facility and the dues are
carried forward as ACCT DUE and accumulate in the next bill. It is difficult for the
individuals and companies to keep track of previous records and tally it with the
future records.

CMRTC 2
 Online bill payments

2.2.1 LIMITATIONS OF EXISTING SYSTEM

• It is very time consuming.

• It takes too much cost to perform procedure.

• This process involves more man power

• It is difficult to store the data.

• The current system is not user friendly.

2.3 PROPOSED SYSTEM

The proposed system is to develop a single website that allows the customer to
pay the bills from any place without having to go to the concerned departments or
stand in long queues. . It is through this system the customer can pay his bills without
having to visit the concerned department or e-seva centers with cash or cheques.
Whenever the bill is due the money in full is transferred by the customer to the social
welfare account.The individual can access the site to get his Electricity, gas or water
bills. The individual now need not wait for the receipt of bills by post or courier’s.
The bills can be viewed online indicating the details along with due date and ACCT
DUE if any. The payments can be made from account to account transfer and
monitored by both the individual and the social welfare officer.

2.3.1 ADVANTAGES OF THE PROPOSED SYSTEM

• Increase the Performance speed.

• Less Time consuming Process

• Reduce cost of files and writing materials.

• It helps to pay bills any time and from anywhere.

• Spend less office space for example reduction on use of many files and paper
work.

• Retrieve the required information easily and quickly .

CMRTC 3
 Online bill payments

2.4 FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase. Three key considerations
involved in the feasibility analysis are
● Economic Feasibility
● Technical Feasibility
● Operational Feasibility

2.4.1 ECONOMIC FEASIBILITY

This system is economically feasible keeping in mind:

● Lesser investment towards training.
● One time investment towards development.
● Minimizing recurring expenditure towards training, facilities offered and
consumables
The system as a whole is economically feasible over a period of time.

2.4.2 TECHNICAL FEASIBILITY

Keeping in mind the existing system network, software and hardware, already
available the audit application generated in .NET provides an executable file that
requires MSIL that provides compatibility from windows98 without having to load
.NET software. No additional hardware or software is required which makes smart
audit technically feasible.

2.4. 3 SOCIAL FEASIBILITY

The application smart audit does not require additional manual involvement or
labor towards maintenance of the system. Cost for training is minimized due to the
user friendliness of the developed application. Recurring expenditures on
consumables and material are minimized.

CMRTC 4
 Online bill payments

2.5 HARDWARE & SOFTWARE REQUIREMENTS

2.5.1 HARDWARE REQUIREMENTS:

Hardware requirements specifies the logical characteristics of each interface

and hardware components of the system. The following are some hardware
requirements.

• Processor : Pentium based system with a minimum of p4

• RAM : 1Gb (Minimum)

• Hard disk : 10Gb or more

.
2.5.2 SOFTWARE REQUIREMENTS:

Software requirements specifies the logical characteristics of each interface

and software components of the system. The following are some Software
requirements.

• Operating System: Windows 2000 or higher

• Language : JAVA(JSP,JDBC)

• IDE : Eclipse Java EE

• Back End : MySQL Server

• Front End : HTML,CSS

CMRTC 5
 Online bill payments

3. ARCHITECTURE

3.1 PROJECT ARCITECTURE

This project architecture describes about how a data will be stored in database.
This describes how a user requests and a admin will generate a response. The detailed
architecture is explained below.

Fig. 3.1 Project Architecture

CMRTC 6
 Online bill payments

3.2 MODULES DESCRIPTION

Modules

● Administrator

● Boards

● Customers

3.2.1 ADMINISTRATOR

Administrator will activate or deactivate boards i.e type of bill payments.

Administrator will keep the track of customer details. He will assign bills to
customers. He can view customer and payment details. He can delete and enter the
records of customers and boards.

3.2.2 CUSTOMER

Customers register in the webpage for payment of bills. They can view the
payment details. They can update their details. They van view the payment details and
due date for paying the bills. They can make the payments by using any online
services.

3.2.3 BOARDS

This module is maintained by the admin. The module is used to enter the
payment details of customers and the appropriate due dates. This module helps to
view different boards and their user ids which would help in further board logins.

3.3 USE CASE DIAGRAM

CMRTC 7
 Online bill payments

In the use case diagram we have basically three actors who are the Customer,
Boards and the administrator. The user has the rights to login, access to resources and
to view the details. Whereas the administrator has the login, access to resources of the
users and also the right to update and remove the details.

Fig. 3.2 Use Case Diagram for online bill payment

3.4 CLASS DIAGRAM

CMRTC 8
 Online bill payments

Class Diagram is a collection of classes and objects.

Fig. 3.3 Class Diagram

CMRTC 9
 Online bill payments

3.5 SEQUENCE DIAGRAM

The user registers to the website for payment of bills and the admin uploads
the bills.

CMRTC 10
 Online bill payments

CMRTC 11
 Online bill payments

CMRTC 12
 Online bill payments

3.6 ACTIVITY DIAGRAM

It describes about flow of activity states.

Fig. 3.5 Activity Diagram for Admin

CMRTC 13
 Online bill payments

Fig. 3.6 Activity Diagram for Board

CMRTC 14
 Online bill payments

Fig. 3.7 Activity Diagram for Customer

CMRTC 15
 Online bill payments

4. IMPLEMENTATION

4.1 SAMPLE CODE

Register.jsp

<html>

<head>

<title>Sign-Up</title>

<style>

</style>

</head>

<body bgcolor="LIGHTBLUE">

<%@ page language='java' import='java.sql.*,java.text.*' %>

<%

Connection cn=null;

Statement stmt=null;

int no=0;

try

Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

cn=DriverManager.getConnection("jdbc:odbc:onlinebills");

stmt=cn.createStatement();

String str="Select max(uid) from customer";

ResultSet rs=stmt.executeQuery(str);

if(rs.next()){

no=Integer.parseInt(rs.getString(1))+1;

CMRTC 16
 Online bill payments

catch(Exception e)

no=11;

session.setAttribute("uid",String.valueOf(no));

%>

<center>

<form action="register1.jsp" method="POST">

<font size="7"><b><u>Register</u></b></font></br></br>

<table border="0" cellspacing="5px" cellpadding="5px"

align="center">

<tr>

<td><b>USER ID:</b></td>

<%

out.println("<td><input type='text' name='t1'

value='"+no+"' disabled style='font-size: 1.2em'></td>");

%>

</tr>

<tr>

<td><b>USER NAME:</b></td>

<td><input type="text" name="uname"

placeholder="username" style="font-size: 1.2em" ></td>

</tr>

<tr>

<td><b>FIRST NAME:</b></td>

CMRTC 17
 Online bill payments

<td><input type="text" name="fname"

style="font-size: 1.2em" ></td>

</tr>

<tr>

<td><b>LAST NAME:</b></td>

<td><input type="text" name="lname"

style="font-size: 1.2em" ></td>

</tr>

<tr>

<td><b>GMAIL:</b></td>

<td><input type="text" name="gmail"

style="font-size: 1.2em" ></td>

</tr>

<tr>

<td><b>CONTACT NO:</b></td>

<td><input type="text" name="mobile"

style="font-size: 1.2em" ></td>

</tr>

<tr>

<td><b>GENDER:</b></td>

<td>MALE:<input type="radio" name="gen"

value="male" style="font-size: 1.2em" >

FEMALE:<input type="radio" name="gen"

value="female" style="font-size: 1.2em" >

OTHERS:<input type="radio" name="gen"

value="female" style="font-size: 1.2em" >

</td>

</tr>

CMRTC 18
 Online bill payments

<tr>

<td><b>ADDRESS:</b></td>

<td><textarea rows="2" cols="20"

name="address" style="font-size: 19px" ></textarea></td>

</tr>

<tr>

<td><b>PASSWORD:</b></td>

<td><input type="text" name="pwd"

style="font-size: 1.2em" placeholder="minimum 6 char"></td>

</tr>

<tr>

<td><b>CONFIRM PASSWORD:</b></td>

<td><input type="text" name="cpwd"

style="font-size: 19px" ></textarea></td>

</tr>

</table></br></br>

<input type="submit" value="SIGN-UP" style="padding:15px;border-radius:

15px;background-color:green">&ensp;&ensp;&ensp;

<span>Already registered ? <a href="login.jsp"><b>Login</b></a></span>

</form>

</body>

</html>

CMRTC 19
 Online bill payments

5. SCREEN SHOTS

5.1 LOGIN PAGE

This is Login Page where admin can log in.

5.1. Screenshot: Login Page

5.2REGISTRATION PAGE

In this screenshot a customer can register to the website. Customer uploads the
information required.

CMRTC 20
 Online bill payments

5.2 Screenshot: Registration

5.3 Registration Successful

5.3 Screenshot: Registration Successful

5.4 MODULES PAGE

This screenshot shows all the modules present in the project

CMRTC 21
 Online bill payments

5.4 Screenshot: About modules

5.5 CREATE BOARDS:

Admin creates the type of boards i.e type of bills to be paid .It
generates a board id and password.

5.5 Screenshot: create board

5.6 GENERATE BILLS:

Bills are generated by the admin in board module .The bills are
created for every user registered.

CMRTC 22
 Online bill payments

5.6 Screenshot :Generate bills

5.7 SUCCESSFUL BILL GENERATION:

5.7 Screenshot :Successful bill generation

5.8 View Bills:

Customer logins into his account and views his bills for payment.

CMRTC 23
 Online bill payments

5.8 Screenshot:View Bills

5.9 Payment of Bills:

Customer views the bills and pays his bills using payment gateway.

5.9 Screenshot: Payment of bills

5.10 PAYMENT SUCCESSFUL

After payment of bills a popup is displayed.

CMRTC 24
 Online bill payments

5.10 Screenshot: Payment Successful

6. TESTING

CMRTC 25
 Online bill payments

6.1 INTRODUCTION TO TESTING

The purpose of testing is to discover errors. Testing is the process of trying to
discover every conceivable fault or weakness in a work product. It provides a way to
check the functionality of components, subassemblies, assemblies and/or a finished
product. It is the process of exercising software with the intent of ensuring that the
Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a
specific testing requirement.

6.2 TYPES OF TESTING

6.2.1 UNIT TESTING
Unit testing involves the design of test cases that validate that the internal
program logic is functioning properly, and that program inputs produce valid outputs.
All decision branches and internal code flow should be validated. It is the testing of
individual software units of the application .it is done after the completion of an
individual unit before integration. This is a structural testing, that relies on knowledge
of its construction and is invasive. Unit tests perform basic tests at component level
and test a specific business process, application, and/or system configuration. Unit
tests ensure that each unique path of a business process performs accurately to the
documented specifications and contains clearly defined inputs and expected results.

6.2.2 INTEGRATION TESTING

Integration tests are designed to test integrated software components to
determine if they actually run as one program. Testing is event driven and is more
concerned with the basic outcome of screens or fields. Integration tests demonstrate
that although the components were individually satisfaction, as shown by successfully
unit testing, the combination of components is correct and consistent. Integration
testing is specifically aimed at exposing the problems that arise from the combination
of components.

6.2.3 FUNCTIONAL TESTING

Functional tests provide systematic demonstrations that functions tested are
available as specified by the business and technical requirements, system

CMRTC 26
 Online bill payments

documentation, and user manuals.

Functional testing is centered on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input : identified classes of invalid input must be rejected.
Functions : identified functions must be exercised.
Output : identified classes of application outputs must be exercised.
Systems/Procedures: interfacing systems or procedures must be invoked.
Organization and preparation of functional tests is focused on requirements,
key functions, or special test cases. In addition, systematic coverage pertaining to
identify Business process flows; data fields, predefined processes.

CMRTC 27
 Online bill payments

6.3 TEST CASES

6.3.1 NEW USER ID CREATION

Test case ID Test case name Purpose Test Case Output

1 New User ID1 Creating a The user gives the input of his User ID1 for the
creation User ID1 personal details including the user has been
for a user desired username and chosen successfully
password Created

2 New User ID2 Creating a The user gives the input of his User ID2 for the
creation User ID2 personal details including the user has been
for a user desired username and chosen successfully
password Created

3 New User ID3 Creating a The user gives the input of his User ID3 for the
creation User ID3 personal details including the user has been
for a user desired username and chosen successfully
password Created

CMRTC 28
 Online bill payments

6.3.2 LOGIN PAGE

Test case ID Test case name Purpose Input Output

1 Login in page To check if the The username1 Client Home

login page and the password Page
performs its of a registered user
task

2 Login in page To check if the Incorrect username The entered

login page and the password username or
performs its of a registered user password is
task invalid

3 Login in page To check if the The username and The entered

login page the password of a username or
performs its unregistered user password is
task invalid

CMRTC 29
 Online bill payments

6.3.3 ADMINISTRATOR LOGIN

Test case ID Test case name Purpose Input Output

1 Administrator To verify the The already Display

Login Administrator allocated admin
Page username1 and control panel
password for
the Admin

2 Administrator To verify the The The entered

Login Administrator misallocated username or
Page username and password is
password for invalid
the Admin

3 Administrator To verify the The already The entered

Login Administrator allocated username or
Page username3 and password is
incorrect invalid
password for
the Admin

CMRTC 30
 Online bill payments

7. CONCLUSION

7.1 PROJECT CONCLUSION

The Administrator is a necessary tool for planning, executing, implementation

and monitoring our project. In our project we ensure you consistently have exactly the
right administrator with the right skills in place, in order to achieve user satisfaction.
At the same time, he must observe all the customer details, payment details and entire
board details. The system can be implemented across various places in the country
enabling a smooth functioning of various departments from one contact point .
Various cumtomers and their payment detils across each department can be generated
instantaneously. This project is thus helpful in solving all types of requests of users.

7.2 FUTURE ENHANCEMENTS

This project can be further implemented on automated system but not in

manual system. Later this project can provide certification facility.These certifications
may include death and birth certificates. Further the automated system will be helpful
in registering for bill payments and certifications from anywhere and anytime. Later
this project can be helpful to all people where they can pay bills from anywhere
anytime.

CMRTC 31
 Online bill payments

8.BIBILOGRAPHY

8.1 References

● World Wide Web

● Database Administration System
● Web Programming, building internet applications Chris bates 2nd Edition,
Wiley dream tech
8.2 Websites

● www.w3schools.com
● www.jsssliders.com
● www.freewebsitetemplates.com
● www.templateworld.com

CMRTC 32