ADVANT IMS - ONLINE FEES MANAGEMENT SYSTEM

A 6th Semester project report submitted in

partial fulfilment of the requirements for the award of degree in

MASTER OF COMPUTER APPLICATIONS

Bangalore University
2016 -17

Submitted by

SAYAN DIRGHANGI
REG. NO. 14SKSAC019

Under the guidance of

Dr. JAYASHREE NAIR

Professor
Department of IT - MCA

AIMS INSTITUTE OF HIGHER EDUCATION

1 Stage 1st Cross Peenya Industrial Estate, Bangalore-560058
st

NAAC Accredited with ‘A’ Grade

 AIMS INSTITUTE OF HIGHER EDUCATION
NAAC Accredited with ‘A’ Grade

Department of IT - MCA

CERTIFICATE

This is to certify that SAYAN DIRGHANGI with Register No.

14SKSAC019 has satisfactorily completed the Sixth Semester MAIN
Project – titled “ADVANT IMS - ONLINE FEES MANAGEMENT
SYSTEM”, as a part of fulfilment of the partial requirements for the award of
the Degree in Masters of Computer Applications, Bangalore University,
during the Academic year 2016-17.

Guide: Program Manager:

Dr. JAYASHREE NAIR Dr. HEMMANTH K.S

Program Manager

Signature of the Examiners

1.

2.
 DECLARATION

I declare that the 6th Semester Project Work entitled ADVANT IMS-ONLINE
FEES MANAGEMENT SYSTEM has been carried out by me under the
guidance of Sudha T Team Leader Advant TechService India private limited
and Dr. Jayashree Nair, AIMS Institutes. The work has not been submitted
earlier, in full or in part, for the award of Diploma or Degree in this or any
other University.

DATE: SIGNATURE

PLACE: Bangalore

SAYAN DIRGHANGI
Dept. of IT – MCA
AIMS INSTITUTE
 ABSTRACT

ADVANT IMS - Online Fees Management is an ERP based web application

to automate the fee collection process in an education institution. Maintaining
hand written records or manually entering them into the system is time
consuming and also has tendency for errors. The main objective behind
Online Fees Management system is to overcome the manual burden of work
involved in fee management of students in any educational institutions.

Through this system, the staff can easily view enrolled students, their fee
details and details of students who have defaulted on their fees payment. The
system can be searched for specific details based on certain criteria.

This application has 6 major modules and can be used and accessed by

 Management staff

 Students

 Parents

Management staff manage the fee structure, fee due date, fee sponsor details,
etc.

Student can pay their fees online or can check their due date and also can print
fees paid receipt.

Parents can check fees paid and due status of their ward, the last date for
payment with fine and without fine.

If any student has not paid their fees within the due date then the fine amount
is automatically added to their main fees along with an appropriate
explanation. All the students and their parents will get a mobile alert one day
prior to the due date for payment of fees.

i
 ACKNOWLEDGEMENT

I take this opportunity to pass on my deep sense of gratitude

to my Institution, AIMS Institutes, Peenya, Bangalore, and the
Department of IT - MCA, which has given me the opportunity and
exposure to the extensive knowledge, thereby enabling me to attain
my goal of becoming a worthy student.

I am thankful to Dr. Kerron G Reddy, Principal, AIMS Institutes,

for her kind support and encouragement to carry out the project
work in the Institution.

I avail this opportunity to acknowledge my indebtedness and sincere

gratitude to Dr. Jayashree Nair, Professor, Department of IT for her
guidance in the successful completion of the project work.

I thank Dr. Hemmanth K.S, Program Manager, Department of MCA – IT and

Prof. Anantha Rama Krishnan, Director, Department of IT - MCA for their
valuable inspiration and guidance during the course of this project.

I also like to thank all the faculty members, lab assistants, my friends
and last but not the least, my parents for their support during the course
of my project.

Place: Bangalore

Date: SAYAN DIRGHANGI

ii
 INDEX
ABSTRACT...................................................................................................................................................................................................I
FIGURES USED........................................................................................................................................................................................IV
TABLES USED............................................................................................................................................................................................V
ABBREVIATIONS....................................................................................................................................................................................VI
INTRODUCTION........................................................................................................................................................................................2
COMPANY PROFILE.................................................................................................................................................................................4
SOFTWARE REQUIREMENT SPECIFICATION (SRS)......................................................................................................................6
3.1 PROBLEM STATEMENT................................................................................................................................................................6
3.1.1 Existing System........................................................................................................................................................................7
3.2 HARDWARE AND SOFTWARE REQUIREMENTS.....................................................................................................................8
3.2.1 Hardware requirement (Development)....................................................................................................................................8
3.2.2 Software requirement (Development)......................................................................................................................................8
3.2.3 Hardware requirement (Deployment)......................................................................................................................................8
3.2.4 Software requirement (Deployment)........................................................................................................................................8
3.3 FUNCTIONAL REQUIREMENTS..................................................................................................................................................9
3.4 NON FUNCTIONAL REQUIREMENTS.......................................................................................................................................11

DESIGN......................................................................................................................................................................................................13
4.1 SYSTEM PERSPECTIVE...............................................................................................................................................................13
4.1.1 Architectural design...............................................................................................................................................................13
4.2 DETAILED DESIGN......................................................................................................................................................................14
4.2.1. USE CASE DIAGRAM..........................................................................................................................................................14
4.2.2. SEQUENCE DIAGRAM.......................................................................................................................................................16
4.2.3. ACTIVITY DIAGRAM...........................................................................................................................................................17
4.2.4. DFD......................................................................................................................................................................................18
4.2.5. ER DIAGRAM.......................................................................................................................................................................19
4.2.6. PRPCESS FLOW DIAGRAM...............................................................................................................................................20
4.3 DATABASE TABLES.....................................................................................................................................................................21

SYSTEM IMPLEMENTATION...............................................................................................................................................................24
TESTING....................................................................................................................................................................................................26
6.1 INTRODUCTION...........................................................................................................................................................................26
6.2 STEPS IN TESTING.............................................................................................................................................................................27

SCREEN SHORTS.....................................................................................................................................................................................57
7.1 LOGIN PAGE.....................................................................................................................................................................................57
7.2 HOME PAGE......................................................................................................................................................................................58
7.3 FEE HEAD.........................................................................................................................................................................................59
7.4 FEE STRUCTURE...............................................................................................................................................................................60
7.5 FEE COLLECTION..............................................................................................................................................................................61
7.6 FEES DUE STATEMENT.....................................................................................................................................................................62
7.7 FEES STRUCTURE BULK ENTRY.......................................................................................................................................................63
7.8 COLLECT SPONSOR MONEY.............................................................................................................................................................64

CONCLUSION, AND FUTURE ENHANCEMENTS............................................................................................................................69

8.1 CONCLUSION................................................................................................................................................................................69
8.2 FUTURE ENHANCEMENT..........................................................................................................................................................69

REFERENCES...........................................................................................................................................................................................72

iii
Visual Studio...............................................................................................................................................................................................74

iv
 FIGURES USED

FIG NO TITLE PAGE NO

Fig 4.1 Database Architectural 14
Fig 4.2 Use case Diagram 15

Fig 4.4 Sequence Diagram 16

Fig 4.5 Activity Diagram 17
Fig 4.6 DFD 18
Fig 4.7 Level 0 DFD 18
Fig 4.8 Level 1 DFD 19
Fig 4.9 ER Diagram 20

Fig 4.10 Process Flow Diagram 20

Fig 7.1 Log In 57
Fig 7.2 Home Page 58
Fig 7.3 Fee head 59
Fig 7.4 Fee Structure 60
Fig 7.5 Fee Collection 61
Fig 7.6 Miscellaneous Fee Collection 62
Fig 7.7 Fee Due Statement 62
Fig 7.8 Fee Due Report 63
Fig 7.9 Fee Structure Bulk Entry 64
Fig 7.10 Collect Sponsor Money 65
Fig 7.11 Fee Collection Report 66
Fig 7.12 Miscellaneous Fee Collection Report 66
Fig 7.13 Collect Sponsor Money Report 67

v
 TABLES USED

TABLE NO TITLE PAGE NO

Table 4.1 Fee Head 21
Table 4.2 Fees Structure 21
Table 4.3 Academic dashboard 22
Table 4.4 Sponsor details 22
Table 6.3 Test Cases 28-55

vi
 ABBREVIATIONS

ERP Enterprise Resource Planning.

SRS Software Requirement Specification.

ER-Diagram Entity Relationship Diagram.

SQL Structure Query Language.

DFD Data Flow Diagram.

ECS Electronic Clearing Service.

VB Visual Basic.

SMS Short Message Service.

HTTP Hyper Text Transfer Protocol.

vii
CHAPTER 1
INTRODUCTION

1
 CHAPTER 1

INTRODUCTION

Traditionally fee records are maintained on paper. It becomes very

inconvenient to modify the data. Here is a possibility that the same data in
different registers may have different values which means the entries for the
same data do not match. This inconsistent state does not supply the concrete
information which poses a problem in the case information related to
particular record is searched.

Today no one prefers to perform calculations on calculator write receipts or

search in bulky ledgers. Everyone wants his/her work to be done by computer
automatically and displaying the result for further manipulations. So this
project is about providing convenience regarding fee management system.
With online fee payment system user no longer are required to check his
register in search of records, as now it can be searched by the software by
choosing some options. The user need not to type in most of the information.
He/she is just required to enter the desired options. On the whole it liberates
the user from keeping lengthy manual records.

This application has 6 major modules and can be used and accessed by

 Management staff

 Students

 Parents

Management staff manage the fee structure, fee due date, fee sponsor details,
etc. Student can pay their fees online or can check their due date and also can
get print fees paid receipt. Parents can check the status of their ward, the last
date for payment with fine and without fine.

2
 CHAPTER 2
COMPANY PROFILE

3
 CHAPTER 2

COMPANY PROFILE

Advant Techservices India Private Limited was formerly known as Advant

Technologies Inc. which was founded in year 2005 in Bangalore. From April
1st, 2013 Advant Technologies Inc. has been upgraded to private limited
status and hence the name change. There has been no change in management
and are providing the same products and services on which we have built our
reputation in the industry. Directors of company are Nanthakumar
Alwarpillai and Amita Pandey.
It is involved in software package business enterprise, consultancy and
provide. Advent began with one simple aim: to provide its client the power
to go above and beyond simple technology.
It is involved in made-to-order software based on orders from specific users,
provide best custom software solution and maintenance of software, web
page design.
Advant also provides some services and those are
 Training
Advant Techservices India Private Limited offers comprehensive
training on its products and solutions.
Advant TechService India Private Limited has several own product and its
being used globally.
Those products are
 ADVANT IMS (Advant Institute Of Management System)
 MyHomeAtMyPrice
 BizCom
 BizComPlus

4
 CHAPTER 3
SOFTWARE REQUIREMENT SPECFICATION

PROBLEM STATEMENT

HARDWARE SOFTWARE REQUIREMENT

FUNCTIONAL REQUIREMENT

NON FUNCTIONAL REQUIREMENT

5
 CHAPTER 3

SOFTWARE REQUIREMENT SPECIFICATION (SRS)

The Software Requirement Specification is a document that describes the

external requirement for any system. The Requirement analyst has to identify
the Requirements by taking to the clients and understanding their needs. The
inputs are to be gathered from different resources, these inputs may be
inconsistent. The Requirement phase translates the ideas in the minds of the
clients into a formal document. Here the user needs are accurately specified.
Requirement must be actionable, measurable and testable related to business
need or opportunities and defined to a level of detail sufficient for system
design.

Advantages of developing the SRS are as follows

 An SRS establishes the basis for the agreement between the client and
the developer on what the software product will do.
 SRS provides a reference for validation of the final product.
 A high-quality SRS is a prerequisite to high-quality software.
 A high-quality SRS reduces the development cost.

3.1 PROBLEM STATEMENT

In educational institution students have the option to pay their fees in multiple
instalments. When the number of students is very large it is difficult to keep
track of fees paid and due statement of each student. The government is also
discouraging cash payments of amount exceeding a certain limit. Retrieving
the particulars of a student or group of students is tedious. Preparing a general
statement of fees due from students is a herculean task.

6
 3.1.1 Existing System

A student or parent will approach the fee collection department of an

educational institute and make payment in the form of cash, cheque or
demand draft. The officer will issue the fee receipt and make an entry in the
day book. At the end of the day he will transfer all the transactions to an excel
sheet or tally software. In case a parent approaches to know the fee due details
a number of ledgers have to be checked or the excel sheet has to be searched.
Every month the institute prepare a list of all students who have outstanding
dues. This is also a highly tedious task.

Limitations of existing system

 Maintaining the record of large amount of data manually is tedious and

time consuming activity.
 Tendency of human error is maximum while maintaining record.
 Time consuming activity for generating fees defaulter list.

3.1.2 Proposed System

In order to overcome the limitation of the existing system, an ERP web
application ADVANT IMS - Online Fees Management system is proposed
which is very convenient to use compared to the existing system.

ADVANT IMS - Online Fees Management manages details related to fee of

the students. Fee structure, fee collection and fee due amount. In ADVANT
IMS - Online Fees Management, fees can be collected from students over
their entire academic career and can print receipt in just one click. The total
fee, balance amount etc., can be viewed Creating fee structure for a course
was never as easy. Advance fee collection, due reports, fine adjustment and
receipt printing options are provided. The features are:

 Define any type of Fees

 Variety of reports on dues and collections
 Reduces the work load of accounts department
 Real time reconciliation of dues

7
  Reduces manpower, easy to customize
 Net banking and credit card payment options are available on demand
from the institution.
 Fee collection, total summary/fee details can be retrieved.

3.2 HARDWARE AND SOFTWARE REQUIREMENTS

3.2.1 Hardware requirement (Development)

 PC with 1.8 GHz.

 Processor: Intel Core i3.
 RAM: 4 GB or higher recommended.
 500 GB HARD DISK.
 Keyboard and mouse or compatible pointing device.

3.2.2 Software requirement (Development)

 Operating System: Windows 7 and higher version.

 Web Browsers: Any Web Browser.
 Front-end: Microsoft Visual Studio 15 Ultimate with VB language.
 Back-end: SQL Server 2014.

3.2.3 Hardware requirement (Deployment)

 PC with 1.8 GHz.

 Processor: Intel Core i3.
 RAM: 4 GB or higher recommended.
 500 GB HARD DISK.
 Keyboard and mouse or compatible pointing device.

3.2.4 Software requirement (Deployment)

 Operating System: Windows 7 and higher version.

 Web Browser: Any Web Browser.

3.3 FUNCTIONAL REQUIREMENTS

8
Interfaces

 The concerned staff can create new fees head entries (exam fees,
semester fees, tuition fees, etc.) for the student using fees head module.
In addition staff can also edit or view the pervious fees head type.

 Using fees structure module the concerned staff can create or view
record for the students based on their academic calendar, batch,
semester, and course. Also the responsible staff can edit the fee
structure details and provide due date for submission of the fees.

 Using fee collection module, the responsible staff can maintain record
for the fees paid mode (cheque, cash, demand draft) by student for their
corresponding course.

 The responsible staff can also generate receipt for the student details
fees and summary of fees paid in details for the individual student.

 The responsible staff can publish fee due statement using the fee due
statement module for the individual student and send the report to
management and notify the students.

 Using fee structure bulk entry, the responsible staff can enter and
maintain fees for many students at a time.

 Using collect sponsor money module, the responsible staff can collect
and maintain record for funds donated by sponsors and also the
sponsor details are created and maintained.

Process of project

 The staff login to the application using their credentials.

 After successful login the staff can entire add, view or edit fees head,
fee structure, generate receipt for the fees paid depending on the
requirement.

9
  If the new fees head to be created or modified, the staff can add fees
type or can modify the fees record.

 For generating the fees paid, the staff can use fees collection module
and generate the detailed fees receipt mentioning the mode of fees
payment, total fees, and fees paid and balance fee to de paid.

 Using fee due statement, the staff can report or publish default fee to be
paid to the students.

 For maintaining the sponsor fund collection, the staff can use collect
sponsor money module. Contract details of sponsors are also recorded.

Output of Project

 The application is very helpful in maintaining the fees management of

educational institute efficiently and in faster way.

 It reduces the manual activity involved in collection of fees by the staff

and also reduces the human error tendency to minimal extends.

 The generation of fees receipt and fees default list can be published in
very less time. The records are maintained for long time in database.

Developer Responsibility

 The developer is responsible for the proper functionality of the

application. The receipts are to be generated accurately. The records are
to be inserted into database property and fetching of data should take
optimal time.

 If any upgrade is in database happen, the developer should upgrade the

version of database for proper functioning.

 Any changes in user interface from the client should be incorporated

by developer if request arise.

10
 3.4 NON FUNCTIONAL REQUIREMENTS

Maintainability
The item will be utilize for long time, it must be anything but difficult to keep
up and simple to join future changes, the outline if the framework ought to be
module based and changing the configuration of the one module ought not
influence the best possible operation of the other module.

Portability
The framework ought to be convenient to keep running in any web browser
on any stage with almost no or on changes.

Usability
A few framework are exceptionally difficult to handle consequently this
prerequisite especially important. Normally the necessities are appeared in
learning time and same measurements.

Flexibility
Flexibility in proposed system should be there because if any new
requirements come developer will be able to change in that system.

11
 CHAPTER 4
SYSTEM PERSPECTIVE

DETAILED DESIGN

DATABASE TABLES

12
 CHAPTER 4

DESIGN

4.1 SYSTEM PERSPECTIVE

Before implementing the system designing the system is very important stage
where we get the solution of the problems.

Two types of designs are-

 High level design

 Architectural design

High level design

High level design is used to identify that how module will look like and how
those will be operated by the user.

4.1.1 Architectural design

Architectural design is used to combine different components and to show

how they are behaving with each other.

In this project 3 tier architecture is used

The data layer

Data layer is used to be linked with the stored procedure in the database. We
create store procedure in database which are used in data layer to fetch the
data.

Business Layer
Business layer contains the class member and member function. An object for
business layer class is created and object will invoke the methods .

13
Presentation Layer
Presentation Layer is ASP.NET (front end) which invokes the business layer
through button click or page load.

Figure 4.1: Architectural design

4.2 DETAILED DESIGN

4.2.1. USE CASE DIAGRAM

A use case diagram shows that how actor are interacting with the system. It is
used to show which function perform how for which user. Use case diagram
helps us to understand the functional overview of the system.

Use case

In use case diagram use case are used to show the function of the system. It is
represented by ellipse which is horizontal.

Actor
Actors are used who interact with the system and who involve in all system
function

14
 Figure 4.2: Actor view diagram

USE CASE DIAGRAM

Figure 4.3: Use case diagram for fees management

A use case diagram is a graphic depiction of the interaction among the elements of a
system. A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use cases which specific roles are played by the
actors within and around the system. In the above use case diagram there is 3 actors
those are ADMIN, STUDENT, and PARENTS. Where student and parents can pay
fees check for the fees due.

15
4.2.2. SEQUENCE DIAGRAM

Figure 4.4: Sequence diagram for Fee management

A sequence diagram is an interaction diagram that shows how objects operate with
one another and in what order. It is a construct of message sequence chat. A
sequence diagram shows object interactions arranged in time sequence. Sequence
diagrams are sometimes called event diagrams or event scenarios. A sequence
diagram shows, as parallel vertical lines, different process or objects that live
simultaneously, and as horizontal arrows, the message exchanged between them, in
the order in which they occur. This allows the specification of simple runtime
scenarios in a graphical manner. In the above sequence diagram there is 4 types of
processes and those are Users, Login page, Fee system, and database. And it shows
the interactions between those processes.

16
4.2.3. ACTIVITY DIAGRAM

Figure 4.5: User Activity Diagram for fees management

Activity diagram is another important diagram in UML to describe the dynamic

aspect of the system. Activity diagram is basically a flowchart to represent the flow
from one activity to another activity. The activity can be described as an operation of
the system. The basic purpose of activity diagram is if captures the dynamic
behaviour of the system.
In the above activity diagram it shows the process flow for the fees management
staff.

17
 4.2.4. DFD

DFD is the short form of Data Flow Diagram which shows how data is flowing in
the system.

Figure 4.6: DFD for user module

LEVEL 0

Figure 4.7: level 0 DFD

18
LEVEL 1

Figure 4.8: level 1 DFD

4.2.5. ER DIAGRAM

ER Diagram is the short form of Entity Relationship Diagram. It shows the

relationship between kind of entity in the system which represents graphically.

Here Student, Administration, Sponsor, and Fee those are the entity and each
of the entity are connected each other. Relationships are represented by
diamond-shape box. Name of the relationship is written inside the diamond
box. All the entities (rectangles) participating in a relationship, are connected
to it by a line. More than one student can add single sponsor so for that
student to sponsor entity mapping is many to one (N-1).

19
 Figure 4.9: ER diagram for Fees management

4.2.6. PRPCESS FLOW DIAGRAM

Figure 4.10: Overall process flow diagram for fees management

A process flow diagram is a diagram commonly used process engineering to

indicate the general flow of software process and functions. The PFD displays
the relationship between major functions and the facility.

20
4.3 DATABASE TABLES

Column Name Data Type Auto Null

Head_id Int Not Null

Head_type Varchar(50) Not null

Reg_time Date time Not null

Mod_date Date time Not Null

Table 4.1: Fees Head

Column Name Data Type Auto Null

Str_id Int Not Null

Branch Varchar(10) Not Null

Ac_year Int Not Null

Course Varchar(20) Not Null

Semester Varchar(5) Not Null

St_cat Varchar(10) Not Null

Head_type Varchar(50) Not Null

Fe_amt Numeric Not Null

D_date Date time Not Null

Reg_time Date time Not Null

Mod_date Date time Not Null

Table No: 4.2: Fees Structure

Column Name Data Type Auto Null

A_id Int Not Null

Ac_year Numeric Not Null

21
 Branch Varchar(10) Not Null

Stu_id Varchar(10) Not Null

Course Varchar(20) Not Null

Stu_name Varchar(30) Not Null

Mod_date Date time Not Null

Reg_time Date time Not Null

Table No: 4.3: Academic dashboard

Column Name Data Type Auto null

Sponsor_id Int Not Null

Sponsor_name Varchar(20) Not Null

Spon_details Varchar(20) Not Null

Amount Numeric Not Null

Spon_mode Varchar(20) Not Null

Remarks Varchar(50)

Table No: 4.4: Sponsor Details

22
 CHAPTER 5
SYSTEM IMPLEMENTATION

23
 CHAPTER 5

SYSTEM IMPLEMENTATION

This project is implemented using three tier architecture ASP.NET is used in

the presentation layer, Visual Basic classes are used in the Business logic,
Stored Procedure is used in the data tier and MS SQL server 2014(database) is
used as the backend.
Implementation Stapes
Presentation Layer is ASP.NET (front end) which invokes the business layer
through button click or page load.
Business Layer contains the class member and member function. An object
for Business layer class is created and object will invoke the method.

Data Layer is used to be linked with the stored procedure in the database. We
create store procedure in database which are used in the data layer to fetch the
data.

Store Procedure

Store procedure is set of queries which is user in data layer in the three tire
architecture. In SQL Server we used to create the store procedure which create
table and fetch the data from database design or table design.
For each and every event in the form like add, view, update, delete, we have
to create different store procedure which will be linked through the data layer.

24
CHAPTER 6
INTRODUCTION

STEPS IN TESTING

TEST CASE

25
 CHAPTER 6

TESTING

6.1 INTRODUCTION

Software Testing is a critical element of a software quality assurance and

represents the ultimate review of specification, Design and code generation.

Once the source code has been generated, software must be tested to uncover
as many errors as possible before delivery to your customer. There are various
techniques for testing. These techniques provides guidance for designing test
that-

1. Exercise the internal logic of software components.

2. Exercise the input and output domains of the programs to uncover errors in
program

Function, behaviour and performance.

 Testing strategies and techniques used:

o Windows application like any other engineering product may
subject to failure due to errors in its engineering process.
o Testing is process of executing a program with the intent of
finding an error. It is a process of verification and validation often
used interchangeably. However, they have different meaning-
 “Verification” is the process to fulfill the specification
established during the previous phase. The verification
activities are proving, testing and reviews.
 “Validation” is the process of evaluating the software at the
end of the software development to ensure compliance with
software requirements. Testing is a common method of
validation.
 Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding.

26
  A successful testing is one that uncovers an as yet undiscovered error. If
testing is conducted successfully, it will uncover errors in software. As a
secondary benefit, testing demonstrates that system functions appear to
be working according to specification and that performance requirements
appear to have been met.
 In addition, data collected as testing is conducted provides a good
indication of software reliability but testing can’t show the absence of
defects, it can show that software errors are present.
 During the testing process only failure are observed, by which the
presence of fault is deducted. The actual faults are identified by separate
activities commonly referred as “Debugging”.

6.2 Steps in Testing

Unit Testing
In testing process unit testing comes first and then integration testing. In unit
testing we check each and every small unit of the system that it is giving
output correctly or not. After checking if units behave as expected result we
combine all small in a single unit otherwise units go to be corrected.

Integration Testing
After finishing unit testing we integrate all small components in single system
and check that it is giving required result or not. In the integrated system,
interface will be tested between components.

User Testing
User testing is the last step in testing process where user will check the entire
system. User tests by using system that it is really giving her/him the correct
output or not.

27
CHAPTER 7
SCREEN SHORTS

56
 CHAPTER 7

SCREEN SHORTS

7.1 Login Page

The user will first come to this where they have to login here by giving there
unique userid and password. Here total three types of user can login those are
staff, parent, student.

Figure No 7.1: Login Page

After clicking the login button it will come to this page where the user has to
give there high security password.

57
7.2 Home Page

After entering the high security password it will come to home page.

Figure No 7.2: Home Page

58
7.3 Fee Head

In this form the management user will able to add all the fee head name like
(Admission fee, exam fee, hostel fee, etc.). Only the staff can add fee head.

Figure No 7.3: Fee Head

By clicking the add button it will add the head type in to the database and by
clicking view button it will display all the available head list are already in the
database. It won’t accept any repetition fee head. And also user can edit the
existing fee head.

59
7.4 Fee Structure

This form is used to set the fee details. It means it’s used for set the fee
amount for student. The fee amount can be different for different student
category (like General, SC, ST Etc.) and it also be different for different
academic year and different batches so before set the fee structure amount
academic year, batch name, student category those field values are required.

Figure No 7.4: Fee Structure

By selecting academic year and batch course will come automatically based
on these two fields.

By clicking add button it will add the details to the database and by clicking
view button it will display all the existing fee structure details and the user
also can edit the existing details.

60
7.5 Fee collection

This form will used when any student wants to pay fees. It will show how
much due that particular student have by entering that student details (student
ID, academic year, branch). While paying the fees that student can select the
payment method which are available to that particular branch. While this
module is fully based on money transaction and money related all issue so
that staff has be very much focus, and that staff has to provide receipt for each
and every single transaction. And by using this module receipt will be
generate automatically after completing each and every transaction. And here
also a data recovery method has been used so that if any student lost his/her
receipt then also that student can get another receipt from the database so no
question about data losing.

Figure No 7.5: Fee Collection

The student can get their details fee receipt and summary fees receipt.

61
And also those fees which are not structure (any fine, any activity fees etc.).

Figure No 7.6: Miscellaneous Fee Collection

7.6 Fees Due Statement

This form will show the due statement and make a report based on that
statement. The main thing is by using this form we can get more than one
report at a time. Here we can select for a particular year for a particular batch
or we can select for a particular year all batch and it will generate only report
statement.

62
Figure No 7.7: Fee Due Statement
And we get report like this below:

Figure No 7.8: Fee Due Report

63
7.7 Fees Structure Bulk Entry

While we are defining the fee structure, it will take long time to defining fees
structure for each department one by one so to avoid this problem this form is
used. By using this form the management or the staff user can set more than
one fee details at a time, so it will reduce the time effect.

For any particular batch fees can be different for different student category, by
using this form staff or the management people can set all fee details at a time.

Figure No 7.9: Fee Structure Bulk Entry

64
7.8 Collect Sponsor Money

This form will get use when any student get any discount or get any
scholarship then that institute has to keep track of that scholarship sponsor all
details on that time this form will get use. It will save all the details of that
sponsor and then how much money that sponsor is providing and by how all
the details are kept in this form.

65
Figure No 7.10: Collect Sponsor Money

And also it will generate report for each and every transaction.

66
 Fee Collection Report

Figure No 7.11: Fee Collection Report

Miscellaneous Fee Collection Report

Figure No 7.12: Miscellaneous Fee Collection Report

67
Collect Sponsor Money

Figure No 7.13: Collect Sponsor Money Report

68
 CHAPTER 8
CONCLUSION

FUTURE ENHANCEMENTS

69
 CHAPTER 8

CONCLUSION, AND FUTURE ENHANCEMENTS

8.1 CONCLUSION

This application aims to give solution to the problem of fees and dues
management. Maintaining hand written records or manually entering them
into the system is time consuming and also has tendency for errors. The main
objective behind Online Fees Management system is to overcome the manual
burden of work involved in fee management of students in any educational
institutions.

Online fees management application help fee staff person to maintain record
of all fees related transaction and maintain receipt for each of those single
transaction. Admission fees, application fees, exam fees and semester fees are
handled by this application.

Staff can search the record easily and generate fee due statement for defaulter
students. If any student loss his/her fee receipt then that student can get his/her
receipt form the data base. The flexible report generation system can be used
to generate a variety of reports - dues statement of each student, de list for a
course, fees paid statement of each students, fees paid month wise, etc. can be
generated.

8.2 FUTURE ENHANCEMENT

Features that are proposed to be added to this application in future in order to

ensure additional functionality are:

 The application will automatically send mail of fee receipt after each
transaction.

70
 One new payment mode will be added that payment mode is called
ECS.

 The application will generate year wish graphical chart report which
includes all the fees structure for each department, so that the
institution management can make an analysis on based on that report.

71
APPENDIX 1
REFFERENCES

72
 Appendix 1

REFERENCES

https://www.w3schools.com/asp/default.asp

https://docs.microsoft.com/en-us/aspnet/web-pages/overview/getting-
started/introducing-razor-syntax-vb

https://www.tutorialspoint.com/vb.net/vb.net_web_programming.htm

https://code.msdn.microsoft.com/ASPNET-45-Web-Forms-f37f0f63

https://support.microsoft.com/en-us/help/821765/how-to-use-microsoft-
visual-basic-net-to-connect-to-a-microsoft-access-database-and-to-retrieve-
data

http://www.c-sharpcorner.com/UploadFile/abb1a5/connecting-database-using-
ado-net-in-VB-Net/

https://msdn.microsoft.com/en-us/library/ms178411.aspx

https://docs.microsoft.com/en-us/aspnet/mvc/overview/getting-
started/introduction/creating-a-connection-string

73
APPENDIX 2
VISUAL STUDIO

SQL SERVER

74
 Appendix 2

Visual Studio

.NET FRAMWORK

Microsoft designed VB from the ground up to take advantage of its new .NET
Framework. The .NET Framework is made up of four parts, the Common
Language Runtime, a set of class libraries, a set of programming languages,
and ASP .NET environment. The .NET Framework was designed with three
goals in mind. First, it was intended to make windows applications much
more reliable, while also providing an application with greater degree of
security. Second, it was intended to simplify the development of web
applications and services that not only work in the traditional sense, but on
mobile devices as well. Lastly, the Framework was designed to provide a
single set of libraries that would work with multiple languages.

What is ASP.NET?
ASP.NET is a programming framework built on the common language
runtime that can be used on a server to build powerful Web applications.
ASP.NET offers several important advantages over previous Web
development models

Enhanced Performance

ASP.NET is compiled common language runtime code running on the server.

Unlike its interpreted predecessors, ASP.NET can take advantage of early
binding, just-in-time compilation, native optimization, and caching services
right out of the box. This amounts to dramatically better performance before
you ever write a line of code.

75
World-Class Tool Support

The ASP.NET framework is complemented by a rich toolbox and designer in

the Visual Studio integrated development environment. WYSIWYG editing,
drag-and-drop server controls, and automatic deployment are just a few of the
features this powerful tool provides.

Power and Flexibility

Because ASP.NET is based on the common language runtime, the power and
flexibility of that entire platform is available to Web application developers.
The .NET Framework class library, Messaging, and Data Access solutions are
all seamlessly accessible from the Web.

Simplicity

ASP.NET makes it easy to perform common tasks, from simple form

submission and client authentication to deployment and site configuration. For
example, the ASP.NET page framework allows you to build user interfaces
that cleanly separate application logic from presentation code and to handle
events in a simple, Visual Basic - like forms processing model.

Additionally, the common language runtime simplifies development, with

managed code services such as automatic reference counting and garbage
collection.

Manageability

ASP.NET employs a text-based, hierarchical configuration system, which

simplifies applying settings to your server environment and Web applications.
Because configuration information is stored as plain text, new settings may be
applied without the aid of local administration tools. This "zero local
administration" philosophy extends to deploying ASP.NET Framework
applications as well. An ASP.NET Framework application is deployed to a

76
server simply by copying the necessary files to the server. No server restart is
required, even to deploy or replace running compiled code.

Scalability and Availability

ASP.NET has been designed with scalability in mind, with features

specifically tailored to improve performance in clustered and multiprocessor
environments. Further, processes are closely monitored and managed by the
ASP.NET runtime, so that if one misbehaves (leaks, deadlocks), a new process
can be created in its place.

Customizability and Extensibility

ASP.NET delivers a well-factored architecture that allows developers to

"plug-in" their code at the appropriate level. In fact, it is possible to extend or
replace any subcomponent of the ASP.NET runtime with your own custom-
written component. Implementing custom authentication or state services has
never been easier.

Security

With built in Windows authentication and per-application configuration, you

can be assured that your applications are secure.

Introduction to SQL Server

SQL Server is a Relational Database Management System (RDBMS) that runs

exclusively under the Windows operating system. One benefit of using
Windows exclusively is that you can send and receive E-mail messages based
on SQL Server "events" and you can also let the operating system handle
login security.

Database Evolution
SQL was invented back in the 1960's by E.F.Cod of IBM. In order to increase
data integrity and reduce repetitive data. RDBMS systems didn't appear until

77
 the late 70's when Sybase and Oracle introduced systems. These systems
existed on mainframes at the time. ANSI-SQL came to be in the 1980's. This
was important because it meant that disparate systems could communicate
through an agreed set of standards. There are different levels of ANSI-SQL
compliance. Almost every major RDBMS today is entry level compliant,
including SQL Server 2008. Every RDBMS has its own flavour of SQL that
complements ANSI-SQL with proprietary elements. SQL Server's flavour of
SQL is known as Transact SQL (T-SQL).

SQL Server was originally a Sybase product. Microsoft bought the product
outright from Sybase and by version 7.0, the version prior to 2008, all the
code had been rewritten by Microsoft's programming gurus.

Features of SQL
 It is simple English like language and uses simple commands such as
SELECT, CREATE, DROP etc.
 It is not having condition loops, variables and most of the commands are
single line commands.
 To implement application logics, SQL has got extension language popularly
called as PL/SQL (Procedural language of SQL).
 One of the key features of SQL server is the XML support. XML has grown to
be standard technology for organizations that share data on the web.

Now with SQL server 2008 XML documents can be retrieved directly from
the database and it provides various ways to retrieve data in XML format.

Security

View are basically used as a part of security, means in many organizations ,the
end user will never be given original tables & all data entry will be done with
the help of views only. But the data base administrator will be able to see
everything because all the operations done by the different users will come to
the same table.

78