1.

INDRODUCTION

At present students make their payment to college office cell or in banks. At the
time exam fees notification every student went to their nearby bank and wants to make
their exam fees payment. But lack of time and long waiting queue, student may not provide
their payment within their planned day. To overcome this issue the college management is
looking for alternate methods. The main objective of this project is to update every single
student’s fees details, semester fees and other miscellaneous fees in online and reach them
immediately. So that he student can make their payment to college as soon as possible via
online, from their place without waiting for queues in bank and college premises.

1
 2. ABSTRACT

The project entitled “ONLINE STUDENTS FEES PAYMENT” will be

developed to implement for academic institution. The main objective of this project is to
automate student exam fees payment system via online. Any new student can register in
online and confirm their payments in online itself.
Presently institution payment system is carried out in direct campus and in banks.
But this previous system has limitations with student whom living in long distance and met
problem in last minute hazardous in payments. For exam fees payments student has to go
approved banks, fill up the cheallans and remit the amount with bank officials. Sometimes
missing in arrear subject payment lead to them write a particular papers in next semester.
To overcome this limitation and assist management with payment system this
project will be developed. This system has the facility to view student’s exam fees in
online. The registered student can make their payment from anywhere. They will get
confirmation from institution staff members once their payment credited to college funds.
Facilities in this project are, student can view the fees to be paid by them for the
selected semester as well as they can check and make payment for arrear papers. This
project will be developed using PHP as front-end, and back-end for this project will be My
SQL.

2
 3. SYSTEM STUDY

3.1 EXISTING SYSTEM

In order to elicit the requirement of the system and to identify the elements,
inputs, subsystem, and procedure, the existing system was to be examined and analyzed in
detail. In the existing system, it is not computerized. If a student wants to make payment
for the institution, he must buy application form. The requisition form for the application
will be manually done, when application form receive, they should go to concerned bank
and make their payment in the bank. In case of absence in said dates or missed payment
due to distance factor the student will be penalized or can’t attend their exam.

3.1.1 LIMITATIONS OF EXISTING SYSTEM

To get complete course details, it may take hours the entire details are spread
across multiple files and computers at multiple locations.
o Lack of data security
o Chance of occurring errors in the manual system is comparatively high
o Possibility of information ambiguity
o Lack of user satisfaction
o In single day students need to pay in particular bank with huge crowd
o Present days technology deserve to make payments on the go from their mobile or
laptop but previous system annoys students when numbers increased

3.2 PROPOSED SYSTEM

The concern has to analyses the existing system whether any difficulties in
handling the data or student information. After finding the problem has addressed and
found solution to overcome. The college has understands the existing problem with
different types of alternative.
All the drawbacks and limitation are restricted by the proposed system. Since this
project is done module-by-module, error rectification and detection becomes Very easy.
Easy module can be selected from the main menu. By integrating online fees payment
student can make their payments from their home, either they can make the payment or
their parents can make the payment using their bank wallet.

3
3.2.1 ADVANTAGES OF THE PROPOSED SYSTEM:
o The proposed system is developed to work in online
o The admin, staff and student can work on this system from anywhere, because this
application is running in web server
o Student’s can have the facility to know about their semester wise exam fees, arrear
paper fees in online
o Minimizes the workload of management and they could keep in touch with students
and payment details by sending notifications

4
 4. SYSTEM SPECIFICATION

4.1 HARDWARE REQUIREMENTS

Processor : Core i3
Speed : 2.4 GHZ
RAM capacity : 4 GB
Hard Disk : 500 GB
CD-ROM drive : 52x speed
Keyboard : 104 keys (normal)
Mouse : Logitech (3 button mouse)
Ethernet card : 10/100 Mbps
Monitor : 15” LG Color Monitor

4.1 SOFTWARE REQUIREMENTS

Operating system : Windows 7

Front End : PHP
Back End : MY SQL
Web Server : APACHE

4.1 ABOUT THE SOFTWARE

4.1.1 HTTP AUTHENTICATION WITH PHP

The HTTP Authentication hooks in PHP are only available when it is running as an
Apache module and is hence not available in the CGI version. In an Apache module PHP
script, it is possible to use the header() function to send an "Authentication Required"
message to the client browser causing it to pop up a Username/Password input window.
Once the user has filled in a username and a password, the URL containing the PHP script
will be called again with the predefined variables PHP_AUTH_USER, PHP_AUTH_PW,
and AUTH_TYPE set to the user name, password and authentication type respectively.
These predefined variables are found in the $_SERVER and $HTTP_SERVER_VARS
arrays. Both "Basic" and "Digest" (since PHP 5.1.0) authentication methods are supported.

5
See the header() function for more information. Instead of simply printing out
PHP_AUTH_USER and PHP_AUTH_PW, as done in the above example, you may want
to check the username and password for validity. Perhaps by sending a query to a database,
or by looking up the user in a dbm file.

4.1.1 COOKIES

PHP transparently supports HTTP cookies. Cookies are a mechanism for storing
data in the remote browser and thus tracking or identifying return users. You can set
cookies using the setcookie() or setrawcookie() function. Cookies are part of the HTTP
header, so setcookie() must be called before any output is sent to the browser. This is the
same limitation that header() has. You can use the output buffering functions to delay the
script output until you have decided whether or not to set any cookies or send any headers.

4.1.1 SESSION

Session support in PHP consists of a way to preserve certain data across subsequent
accesses. This enables you to build more customized applications and increase the appeal
of your web site. A visitor accessing your web site is assigned a unique id, the so-called
session id. This is either stored in a cookie on the user side or is propagated in the URL.
The session support allows you to register arbitrary numbers of variables to be
preserved across requests. When a visitor accesses your site, PHP will check automatically
(if session.auto_start is set to 1) or on your request (explicitly through session_start() or
implicitly through session_register()) whether a specific session id has been sent with the
request. If this is the case, the prior saved environment is recreated.

4.1.1 USING REMOTE FILES

As long as allow_url_fopen is enabled in php.ini, you can use HTTP and FTP
URLs with most of the functions that take a filename as a parameter. In addition, URLs can
be used with the include(), include_once(), require() and require_once() statements (since
PHP 5.2.0, allow_url_include must be enabled for these). See Supported Protocols and
Wrappers for more information about the protocols supported by PHP.

6
4.3.5 GARBAGE COLLECTION

4.3.5.1 REFERENCE COUNTING BASICS

A PHP variable is stored in a container called a "zval". A zval container contains,

besides the variable's type and value, two additional bits of information. The first is called
"is_ref" and is a boolean value indicating whether or not the variable is part of a "reference
set". With this bit, PHP's engine knows how to differentiate between normal variables and
references. Since PHP allows user-land references, as created by the & operator, a zval
container also has an internal reference counting mechanism to optimize memory usage.
This second piece of additional information, called "refcount", contains how many variable
names (also called symbols) point to this one zval container. All symbols are stored in a
symbol table, of which there is one per scope. There is a scope for the main script (i.e., the
one requested through the browser), as well as one for every function or method.

4.3.5.2 COLLECTING CYCLES

Traditionally, reference counting memory mechanisms, such as that used
previously by PHP, fail to address circular reference memory leaks. As of 5.3.0 PHP
however implements the synchronous algorithm from the » Concurrent Cycle Collection in
Reference Counted Systems paper which addresses that issue.
A full explanation of how the algorithm works would be slightly beyond the
scope of this section, but the basics are explained here. First of all, we have to establish a
few ground rules. If a refcount is increased, it's still in use and therefore, not garbage. If the
refcount is decreased and hits zero, the zval can be freed. This means that garbage cycles
can only be created when a refcount argument is decreased to a non-zero value. Secondly,
in a garbage cycle, it is possible to discover which parts are garbage by checking whether it
is possible to decrease their refcount by one, and then checking which of the zvals have a
refcount of zero.

4.3.5.3 PERFORMANCE CONSIDERATIONS

We have already mentioned in the previous section that simply collecting the
possible roots had a very tiny performance impact, but this is when you compare PHP 5.2
against PHP 5.3. Although the recording of possible roots compared to not recording them

7
at all, like in PHP 5.2, is slower, other changes to the PHP runtime in PHP 5.3 prevented
this particular performance loss from even showing.
There are two major areas in which performance is affected. The first area is
reduced memory usage, and the second area is run-time delay when the garbage collection
mechanism performs its memory cleanups. We will look at both of those issues.

4.3.5.4 REDUCED MEMORY USAGE

First of all, the whole reason for implementing the garbage collection mechanism is
to reduce memory usage by cleaning up circular-referenced variables as soon as the
prerequisites are fulfilled. In PHP's implementation, this happens as soon as the root-buffer
is full, or when the function gc_collect_cycles() is called. In the graph below, we display
the memory usage of the script below, in both PHP 5.2 and PHP 5.3, excluding the base
memory that PHP itself uses when starting up.

8
 5. LIST OF MODULES

5.1 Subject Master

5.2 Admin Add Exam Fees Details
5.3 Student Semester Fees
5.4 Student Registration
5.5 Student View/Check Fees & Exam Fees Payment
5.6 Payment Notification & Student Queries and Reply

5.1 SUBJECT MASTER

Admin user will create new subjects and update details with database. Subjects will
be created for academic year, and for the particular department and the subject name,
subject code will be added to database.

5.2 ADMIN ADD EXAM FEES DETAILS

Admin will add semester wise student exam fees after login to this web application.
At any time they can modify the fees details according to their institution requirement. As
well as arrear paper fees can also updated. Fees details include department, semester,
theory paper fees, and practical paper fees along with overall amount to be paid.

5.3 STUDENT SEMESTER FEES

Student’s semester fees and miscellaneous fees details can be added by the admin
for every department. This fees detail will be viewed by students after login to this
application.

5.4 STUDENT REGISTRATION

Every student details will be registered by admin user along with their register
number in order to make fees payment to college. Registration includes their name, register
number, department and contact number and the details will be permanently stored in
college server.

9
5.5 STUDENT VIEW/CHECK FEES & EXAM FEES PAYMENT

After login the student able to view the semester fees. To view exam fees the
student should first select their department, followed with academic year and semester then
the page will display their exam fees. Exam fee includes their current semester theory and
practicals.
Student after get to know about their exam fees payment as well as their arrear papers (if
any) and their fees details they will give number of arrear papers in the given list and it will
show them the amount to be paid. By giving their bank card details (credit/debit card)
along the security credentials the system allows them to transfer desired amount to
institution’s bank account.

5.6 PAYMENT NOTIFICATION & STUDENT QUERIES AND ADMIN REPLY

After exam fees payment and student’s semester fees payment the detail will be
updated in admin area. The admin can see list of students made payment for various
activities. As well as admin have facility to send notification to selected student via Mail or
SMS.
Students have queries regarding payments and account details can post query to the
concerned department in-charge. The post query will be viewed and replied by the
concerned department staff members.

10
 6. SYSTEM DESIGN

6.1 INPUT DESIGN

Input design is the process of connecting the user-originated inputs into a

computer to used format. The goal of the input design is to make the data entry logical &
free from errors.
This application is being developed in a user-friendly manner. The forms are
being designed in such a way that during the processing the cursor is placed in the position
where the data must be entered. An option of selecting an appropriate input from the values
of validation is made for each of every data entered. Help managers are also provided
whenever the user entry to a new field to that he/she can understand what is to be entered.
Whenever the user enter an error data, the spry validation will displays an error, without
correcting the error the form cannot be submitted to the database.

6.2 OUTPUT DESIGN

The output form of the project is either by screen or by hard copies. Output
design aims at communicating the results of the processing of the users. The reports are
generated to suit the needs of the users. The reports have to be generated with appropriate
levels.
In this project the output will be displayed in table format. The reports include
product display in online, customer orders, product stock at present and users registered in
online. These details will be more helpful for verification of student fees payment and
student registration details.

11
6.3 DATA FLOW DIAGRAM:

Level 0:

Fees Details
Online View Fees
Student Fees Payment
Administrator Student

View Payments
Payments

12
 Level 1:

Subject Details
Login
Admin

tblsubject

Sem / Exam Fees Details

View Payment & Query

Student Registration
tblFees

tblStu_query

Post Query tblStud_deta

ils

Semester, Exam, Other Fees

View Fees Details

Login
Student

Fees Payment

tblFees_pay

13
ER-Diagram:

SEM Type
SEM

dept. Sub name

dept. amount

Add

subject exam fees

Dept

other fees title

circular

amount
view
dept details
Pay
title Pay

Pay
student_reg payments

reg_no name dept total

dept sem regno

14
 6.4 TABLE DESIGN:

Table Name: circular

Primary Key: circular_id
FIELD NAME DATA TYPE SIZE DESCRIPTION

circular_id Integer 10 Circulatr ID

Date Date 15 Circular Date

Dept Varchar 20 Department

title Varchar 25 Title

Details Varchar 30 Details

Files Varchar 15 Files

Table Name: exam fees

Primary Key: fees_id
FIELD NAME DATA TYPE SIZE DESCRIPTION

fees_id Integer 10 Fees ID

Year Varchar 10 Year

Dept Varchar 10 Department

Semester Varchar 15 Semester

Type Varchar 15 Type

paper_type Varchar 15 Paper Type

fee_amount Varchar 15 Fees Amount

lastdate Date 15 Last Date

fine_date Date 15 Fine Date

fine_amt Varchar 10 Fine Amount

Table Name: other fees

15
Primary Key: fees_id
FIELD NAME DATA TYPE SIZE DESCRIPTION

Fees_id Integer 10 Fees ID

Year Varchar 10 Year

Dept Varchar 20 Department

Semester Varchar 10 Semester

Title Varchar 20 Title

Amount Varchar 10 Amount

Lastdate Date 15 Last Date

Fine_date Date 15 Fine Last Date

Fine_amt Varchar 10 Fine Amount

16
 Table Name: register
Primary Key: reg_id
FIELD NAME DATA TYPE SIZE DESCRIPTION

reg_id Integer 10 Register ID

stu_name Varchar 25 Student Name

reg_no Varchar 15 Register No

DDept Varchar 15 Department

pass Varchar 10 Pass

Table Name: student_reg

Primary Key: stu_id
FIELD NAME DATA TYPE SIZE DESCRIPTION

stu_id Integer 10 Student ID

Year Varchar 10 Year

Dept Varchar 15 Department

reg_no Varchar 15 Register No

roll_no Varchar 15 Roll No

stu_name Varchar 25 Student Name

Mobile Varchar 15 Mobile

Mailed Varchar 15 Mail ID

aadhar_no Varchar 15 Aadhar No

17
Table Name: subject
Primary Key: sub_id
FIELD NAME DATA TYPE SIZE DESCRIPTION

sub_id Integer 10 Subject ID

Year Varchar 10 Year

Dept Varchar 25 Department

Sem Varchar 10 Semester

Type Varchar 10 Type

Code Varchar 10 Subject Code

sub_name Varchar 25 Subject Name

18
Table Name: payment
Primary Key: pay_id
FIELD NAME DATA TYPE SIZE DESCRIPTION

pay_id Integer 10 Payment ID

Date Date 10 Payment Date

Year Varchar 10 Year

Dept Varchar 15 Department

Sem Varchar 10 Semester

reg_no Varchar 10 Register No

Name Varchar 25 Student Name

theo_fees Varchar 10 Theory Fees

no_theo Varchar 10 No of TheoryPapers

tot_theo Varchar 10 Total Theory Amount

prat_fees Varchar 10 Pratical Fees

no_prat Varchar 10 No of particalPapers

tot_prat Varchar 10 Total Pratical Amount

arr_fees Varchar 10 Arrear Fees

no_arr Varchar 10 No of ArrearPapers

tot_arr Varchar 10 Total Arrear Amount

total Varchar 10 Total

Cardno Varchar 20 Card No

card_name Varchar 30 CardHolder Name

Cvv Varchar 5 Cvv

19
 7. SYSTEM TESTING

7.1 SYSTEM TESTING

Testing is an important phase in project development. System testing makes a

logical assumption that if all parts of the system are correct, and the goal will be achieved
successfully. The software must meet the user specification and it must satisfy according to
the needs of the users.
Testing is the process of executing a project within the intend of finding errors.
A good test case is one that has a high probability of finding an undiscovered error.

7.1.1 TESTING METHODOLOGIES

 Unit testing
 Black box testing
 White box testing
 Integration testing
 Acceptance testing
 Validation testing
 Output testing

UNIT TESTING

Unit testing focuses verification efforts on the smallest unit of software design
of the module. This is also known as “module testing”. This testing is carried out during
programming stage itself. In this testing step, each module is found to be working
satisfactorily as regards to the expected output of the modules.

BLACK BOX TESTING

Black box testing design usually described as focusing on testing functions

requirements. Synonyms for black box include behavioral, functional, opaque box and
closed box. Black box test design treat the system as “black box”, so it does not explicitly
use knowledge on the internal structure.

20
WHITE BOX TESTING

White box test allows one to pack inside the box and it focuses specifically on
using internal knowledge of the software to guide the selection of the test date. White box
testing also called “Behavioral” or “Structural” testing.

INTEGRATION TESTING

Data can be lost across an interface, one module can have adverse effect on
another sub function when combined it may not produce the desired major functions.
Integration testing is a systematic testing for constructing test to uncover errors associated
within an interface. The objectives taken from unit tested modules and built a program
structure for integrated testing. All the modules are combining and made the test.
A correction made in this testing is difficult because the vast expenses of the
entire program complicated the isolation of causes. This is the integration testing step, all
the error is corrected for next testing process.

ACCEPTANCE TESTING

Acceptance test has the objectives of convenience the user on the validity and
readability of the system. It verifies that the system procedures operate to system
specifications and the integrity of vital data is maintained. User motivation and knowledge
are critical for the successful performance of the system.

VALIDATION TESTING

All the completion of the integrated testing, software is completely assembled

as a package; interfacing error has been uncovered and corrected and a final series of
software test- Validation begins.
Validation testing can be defined in many ways but a simple definition is that
validation succeeds when the software function in a manner that can be reasonably
expected by the customer. After validation test has been conducted, one of two possible
conditions exists:

21
 The function or performance characteristics conform to specification and are
accepted.
A derivation from specification is uncovered and a deficiency list is created,
proposed system under consideration has been listed by using validation testing and found
to be working satisfactorily.

OUTPUT TESTING

The next process of validation testing, is output testing of the proposed system,
since no system could be if it does not produce the required output in the specified format.
Asking the user about the format required, list the output to be generated or displayed by
the system under considerations.
Output testing is a different test whose primary purpose is to fully exercise the
computer based system although each test has a different purpose all the work should
verify that all system elements have been properly integrated and perform allocated
functions.
The output format on the screen is found to be corrected as the format was designed
in the system design phase according to the user needs for the hard copy also; the output
testing has not resulted in any correction in the system.

22
 8. SYSTEM IMPLEMENTATION

8.1 SYSTEM IMPLEMENTATION

System implementation is the stage of the project that the theoretical design is
turned into a working system. If the implementation stage is not properly planned and
controlled, it can cause error. Thus it can be considered to be the most crucial stage in
achieving a successful new system and in giving the user confidence that the new system
will work and be effective.
Normally this stage involves setting up a coordinating committee, which will
act as a sounding board for ideas; complaints and problem. The first task is implementation
planning; i.e., deciding on the methods and time scale to 1be adopted. Apart from planning
two major task of preparing for implementation are, education taken place much earlier in
the project; at the implementation stage the emphasis must be on training in new skills to
give staff confidence they can use the system. Once staff has been trained, the system can
be tested.
After the implementation phase is completed and the user staff is adjusted to
the changes created by the candidate system, evaluation and maintenance is to bring the
new system to standards. The activities of the implementation phase can be summarized as,
 Implementation planning
 Education planning
 System planning

23
 9. APPENDIX

9.1 SCREEN SHOTS

HOME SCREEN

ADMIN LOGIN

24
STUDENT LOGIN

ADDING SUBJECTS

25
ADDING EXAM FEES DETAILS

ADDING OTHER FEES DETAILS:

26
STUDENTS REGISTRATION

ADDING CIRCULAR INFORMATION

27
ADDING PAYMENT DETAILS

CHANGING PASSWORD

28
STUDENTS WELCOME PAGE

VIEWING EXAM FEES DETAILS

29
VIEWING OTHER FEES

VIEWING CIRCULAR DETAILS

30
STUDENT FEES PAYMENT

STUDENT FEES PAYMENT DETAILS

31
 10.SAMPLE CODING

<?php
session_start();
session_destroy();
session_unset();
?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Fees</title>
<meta name="keywords" content="free website template, CSS templates, Gray Blog
Template, HTML CSS" />
<meta name="description" content="Gray Blog Website - Free CSS Template, Free HTML
CSS Layout" />
<link href="templatemo_style.css" rel="stylesheet" type="text/css" />
<script type="text/javascript" src="js/jquery-3.1.1.min.js"></script>
<script type="text/javascript" src="js/cufon-yui.js"></script>
<script type="text/javascript" src="js/arial.js"></script>
<script type="text/javascript" src="js/cuf_run.js"></script>
<!-- Free CSS Template | Designed by TemplateMo.com -->
<style>
#HDropdown-orange-classic {
margin:0;
padding:0px;
list-style:none;
background:#CCC;
height:35px;
width:99%;
border:solid 1px #CCC;
border-width:1px 1px 1px 0;
}
#HDropdown-orange-classic li {

32
display:inline;
position:relative;
float:left;
}
#HDropdown-orange-classic li a {
display:block;
float:left;
height:29px;
line-height:29px;
padding:0 25px;
text-decoration:none;
color:#CCC;
font-weight:normal;
font-size:12px;
border-left:solid 1px #CCC;
}
#HDropdown-orange-classic li a:hover {
color:#F00;
background:#CCC;
}
#HDropdown-orange-classic li ul {
margin:0;
padding:0 5px;
line-height:none;
position:absolute;
top:45px;
left:0;
border:solid 1px #CCC;
border-width:0px 1px 1px 1px;
width:180px;
display:none;
background:#CCC;
}
#HDropdown-orange-classic li:hover ul {
display:block;

33
}
#HDropdown-orange-classic li:hover a {
color:#F00;
background:#CCC;
}
#HDropdown-orange-classic li ul li {
display:block;
border-bottom:solid 1px #dbdcd9;
width:100%;
background:#CCC no-repeat 3px 12px;
padding:0 0 0 10px;
}
#HDropdown-orange-classic li ul li:last-child {
border-bottom:0px;
}
#HDropdown-orange-classic li ul a {
border-width:0px;
color:#909090;
padding:0 5px 0 0;
background-color:transparent;
}
#HDropdown-orange-classic li:hover ul li a {
color:#FFF;
}
#HDropdown-orange-classic li ul li a:hover {
color:#F00;
}
#apDiv1 {
position:absolute;
width:200px;
height:30px;
z-index:1;
left: 503px;
top: 318px;
}

34
#apDiv2 {
position:absolute;
width:1010px;
height:358px;
z-index:1;
left: -205px;
top: 47px;
}
#slideshow {
margin: 50px auto;
position: relative;
width: 240px;
height: 240px;
padding: 10px;
box-shadow: 0 0 20px rgba(0,0,0,0.4);
}

#slideshow > div {

position: absolute;
top: -44px;
left: -373px;
right: 10px;
bottom: 10px;
width: 637px;
height: 311px;
}
#apDiv3 {
position:absolute;
width:988px;
height:372px;
z-index:1;
left: 96px;
top: 334px;
}
#apDiv4 {

35
position:absolute;
width:451px;
height:312px;
z-index:1;
left: 860px;
top: 339px;
}
</style>
<script>
$("#slideshow > div:gt(0)").hide();

setInterval(function() {
$('#slideshow > div:first')
.fadeOut(1000)
.next()
.fadeIn(1000)
.end()
.appendTo('#slideshow');
}, 3000);
</script>
</head>
<body link="#FF0000">
<div id="templatemo_background_section_top">

<div class="templatemo_container">

<div id="templatemo_header">

</div><!-- end of headder -->

<div id="templatemo_menu_panel">

<div id="templatemo_menu_section">
<ul id="HDropdown-orange-classic">
<li style="width:50px">&nbsp;</li>

36
<li style="width:50px">&nbsp;</li>
<li style="width:50px">&nbsp;</li>
<li style="width:50px"> &nbsp;</li>
<li><a href="index.php">Home</a></li>
<li><a href="adminlogin.php">Admin</a></li>
<li><a href="stu_login.php">Student</a></li>
</ul>

</div>

</div> <!-- end of menu -->

</div><!-- end of container-->

</div>
<div id="slideshow">
<div><img src="images/79.jpg" width="634" height="398" /></div>
<div><img src="images/80.jpg" width="634" height="398" /></div>
<div><img src="images/81.jpg" width="634" height="398" /></div>
<div><img src="images/82.jpg" width="634" height="398" /></div>
</div>
<div id="apDiv4">
<p align="center" style="color:#000;font-family:Verdana, Geneva, sans-serif;font-
size:24px">Welcome to CIT Sandwich</p>
<p align="center" style="color:#000;font-family:Verdana, Geneva, sans-serif;font-
size:24px"> Polytechnic College</p>
<p style="color:#999;font:Tahoma, Geneva, sans-serif;font-size:12px">CIT Sandwich
Polytechnic College is one of the institutions run by the V. Rangaswamy Naidu
Educational Trust founded in 1955 by Late.Sri. V. Rangaswamy Naidu for the promotion
of Technical Education and Industrial Training in Tamil Nadu. The Polytechnic was started
in the year 1961 and is located near Coimbatore Civil Aerodrome on the outskirts of
Coimbatore on the Avinashi Road. The campus area is 25.30 hectares (both C.I.T. & C.I.T.
Sandwich Polytechnic College).
</p>

37
<p align="center" style="color:#000;font-family:Verdana, Geneva, sans-serif;font-
size:24px">MANDATE</p>
<p style="color:#999;font:Tahoma, Geneva, sans-serif;font-size:12px">CIT Sandwich
Polytechnic College, Coimbatore, a Government aided, co-educational institution,
established and run by V. Rangaswamy Naidu Educational Trust is to offer post-matric
level technical education in Full Time, Part Time and Sandwich modes, leading to the
Diploma from the State Board of Technical Education and Training, Tamilnadu, in
compliance with all Government and AICTE rules and regulations.</p>
</div>
<!-- end of templatemo_background_section_top-->
<!-- end of background middle-->
<!-- end of background bottom--></body>
<!-- Designed by w w w . t e m p l a t e m o . c o m -->
</html>

38
 11. CONCLUSION & FUTURE ENHANCEMENT

To provide faster and efficient methods for data management and to increase the
level of user friendliness we are implementing this Application. All updating are done in a
master database table to keep in generating reports at any time. Use of new software
available and adding new features will definitely improve the functionality of the present
system. Incorporating technological advances is the best way to modify the present system.
Regarding the fees details it provides an efficient displays for college
administration and also the students. This application consists of displaying the fees due
for each student and gives an updates if paid from web admin. Exam arrear fees
management also integrated in this application and student can make payment at their
convenient.

39
 SCOPE FOR FUTURE DEVELOPMENT

The “ONLINE STUDENT FEES PAYMENT” application has made possible for
the accessing of data relating to students. The system has developed in PHP as front end
and MY SQL as back end. The application has been developed to satisfy the needs of the
institute. The entire application is user friendly and interactive. The performance of the
application is provided efficiently.
The newly developed application overcomes all the drawbacks of the existing
system. That is it’s more or less eliminates the manual works to computerized one. In
future this system can be expanded to incorporate student’s attendance system and exam
mark management in this same application. So that by calculating attendance percentage of
individual student the fees payment can be allowed.

40
 12. BIBLIOGRAPHY

REFERENCE BOOKS
1. Jesus Castagnetto, Sascha Schumann,” Proffesional Php Programming”, Addison
wesley Publication, Fifth Edition.
2. Jay Greenspan, Brad Bulgar ,”Mysql/Php Database Applications”,Tata McGraw-Hill
Publishing Company, Third Edition.
3. Rogres Pressman,”Software Engineering And Applications”, Galgotie Publication,
Sixth Edition
4. Richard Fairley,”Software Engineering Concepts”,Tata McGraw-Hill Publishing
Company, Fourth Edition.
5. Ellias M.Award “System Analysis And Design” Tata McGraw-Hill Publishing Company,
Second Edition.

Websites
www.phpbuilder.com
www.apache.org
www.mysql.com
www.php.net
www.w3schools.com

41