A

Project Report

On

“ONLINE COLLEGE FEE PAYMENT SYSTEM”

Submitted to

Dr. A. P. J. Abdul Kalam Technical University, Lucknow

In partial fulfilment of requirement of the degree of
Master of Computer Application

Prepared By: Project Supervisor:

Himanshu Singh Dr. Abhishek Singh
MCA 3rd Semester (Associate Professor)
Roll Number: 2300400140039
Enrollment No.: 230040014103359

2024 – 2025

Department of Computer Application

Technical Education & Research Institute
Post Graduate College Ghazipur – 233001 (U.P.)
 CERTIFICATE

This is to certify that Himanshu Singh pursing MCA 3rd Semester from this institute, has
prepared the project report entitled “Online College Fee Payment System” in partial
fulfilment of the requirement of the degree of Master of Computer Application from Dr.
A. P. J. Abdul Kalam Technical University, Lucknow for the session 2024-2025.

This report is based on the project work undertaken by Himanshu Singh at

Technical Education & Research Institute under the supervision of Dr. Abhishek
Singh and fulfils the requirements of regulations relating to the nature and standard of
MCA course of Dr. A. P. J. Abdul Kalam Technical University, Lucknow, Uttar Pradesh.

I recommended that this project may be sent for evaluation.

Dr. Abhishek Singh Dr. Ajit Pratap Singh Gautam

Associate Professor Head, Deptt. Of Computer Application
 DECLARATION

I, Vikas Sahu hereby declare that this project report entitled “Online College Fee
Payment System” has been prepared by me under the supervision of Dr. Abhishek
Singh.

This project report is my bona fide work and has not been submitted in any form to any
University or Institute for award of any degree or diploma prior to the under mentioned
date. I bear the entire responsibility of submission of this project report.

Vikas Sahu

MCA 3rd Semester

Department of Computer Application

Technical Education & Research Institute

Post-Graduate College, Ghazipur

 ACKNOWLEDGEMENT

I would like to convey my sincere regards and gratitude to Dr. Ajit Pratap Singh
Gautam, Head of Department of Computer Application for providing me an opportunity
and support to work on this project.

I would like to express my gratitude to Dr. Abhishek Singh, Associate Professor, for his
guidance and help. His constant inspiration and timely suggestions helped me to collect
information related to my project without any difficulties.
I would also like to say thanks to Mr. Subhash Chandra Gupta who helped me as well
as provided me a better way to develop a better project.
At last, I express my thanks towards all the faculty members, classmates,
seniors who have continuously encouraged and motivated me during the preparation of
this project.

Place: Ghazipur Himanshu Singh

MCA 3rd Semester

Roll Number: 2300400140018

 PREFACE
The project “Online College Fee Payment System” is designed as the project work of
MCA 3rd semester. Problem has been solved manually on the basis of user’s requirement.
Here is a system designed to simplify to get a better platform and make it so easy to do
everything whatever needs by the clients.

The project starts with system analysis. This part focuses on the Requirement
Analysis & Specification. It first describes the present working system. Then the
problems are identified and solved manually. After the complete analysis of present
system, the problem related to old system have been specified and a new system has
proposed, which gives the user a better and efficient way of managing information and
updating his knowledge regarding to the latest development.

After completion of the Requirement and Analysis of Proposed System we move to the
Software Requirement Specification where we specify the basic requirements of the
system such as Functional Requirement, Security Requirement, Hardware and Software
Requirement etc.
Then we move forward to System Design Phase where we go to the various designing
components and Software Process Model, Designing approach and Module Specification.
Then we move to High Level Design where we have designed the Data Flow Diagram,
E-R diagram and Table Schema of our project. At last we described the bibliography and
web references.
 INDEX OF CONTENTS

1. Introduction ------------------------------------------------------ [1-2]

2. Initial requirement ---------------------------------------------- [3-4]
3. System analysis --------------------------------------------------- [5-12]
3.1. Business Need
3.2. Objective
3.3. Existing System Description
3.4. Proposed System
3.5. Feasibility study with report
4. Software Requirement Specification ------------------------ [13-20]
4.1. Objective
4.2. Scope
4.3. Requirement
4.3.1. Functional requirement
4.3.2. Security requirement
4.4. Software requirement
4.5. Hardware requirement
4.6. Module description
5. System design ---------------------------------------------------- [21-24]
5.1. Software process module
 5.2. Designing approach

6. High level design ------------------------------------------------ [25-37]

6.1. Data Flow Diagram
6.2. E-R diagram
6.3. Table Schema
7. Low level design ------------------------------------------------- [38-40]
8. Bibliography & References ----------------------------------- [41-42]
INTRODUCTION

1
 1. INTRODUCTION
We know that the traditional method of fee payment is quite troublesome. There are many students who
use bank payment process, but this is a time-consuming process. Those parents, who live in other
villages or cities, have to travel long distance only for paying the fee of colleges. So, to overcome this
problem we have developed this online fee payment system, in this system we can pay the fees online
without going to the college bank. This process is easy as we can directly transfer the amount from our
account to the college bank account. This student payment system has two modules namely the user and
the admin. Admin has access to manage student’s details, college details, view pending fees and paid
fees. User can view their profile and get updates on pending fees and paid fees details. In this students
can pay their fees in an efficient way.

An “Online College Fee Payment System” is a digital platform that allows students, parents, and
administrators to manage and pay fees for educational institutions.

Benefits:

Online Fee Payment Systems can:

 Simplify and streamline the fee management process.

 Reduce errors and paperwork.
 Improve efficiency and transparency.
 Allow students to pay fees from anywhere using credit or debit cards.

Features:

Online Fee Payment Systems can include:

 Student profile management.

 Fee structure customization.
 Online payment integration.
 A user module for students to view their profile and get updates on fees.
 An admin module for managing students details, college details, and viewing fees.

2
INITIAL REQUIREMEMNT

3
 2. INITIAL REQUIREMENT

Hardware Requirement:

Hard disk - 512GB

RAM - 4GB

Processor - Intel(R) Core(TM) i7-7700HQ CPU

3.8GHZ

System type - 64-bit Operating System

Interface - Keyboard, Mouse, Display devices

Software Requirements:

Operating System - Window 10

Operating System type - 64-bit OS

Web Designing - HTML, CSS, BOOTSTRAP

Client Side Scripting - JavaScript

Server Side Script - PHP (Hypertext Pre-Processor)

Web Server - Apache

Database - MySQL

Control Panel - XAMPP

Web Browser - Google Chrome, Microsoft Edge

4
Editors - Notepad++, Bracket ,VS code

SYSTEM ANALYSIS

5
 3. SYSTEM ANALYSIS

System analysis is the process of gathering and interpreting facts, diagnosing problems and using the
information to recommend improvements on the system. System analysis is a problem solving activity
that requires intensive communication between the system users and system developers. System analysis
or study is an important phase of any system development process.

The system is studied to the minutes detail and analyzed. The system analyst plays the role of an
interrogator and dwells deep into the working of the present system. The system is viewed as a whole
and the inputs to the system are identified.

The outputs from the organization are traced through the various processing that the inputs phase
through in the organization. A detailed study of these processes must be made by various techniques like
Interviews, Questionnaires etc. The data collected by these sources must be scrutinized to arrive to a
conclusion.

The conclusion is an understanding of how the system functions. This system is called the existing
system. Now, the existing system is subjected to close study and the problem areas are identified. The
designer now functions as a problem solver and tries to sort out the difficulties that the enterprise faces.
The solutions are given as a proposal. The proposal is then weighed with the existing system analytically
and the best one is selected.

The proposal is presented to the user for an endorsement by the user. The proposal is reviewed on user
request and suitable changes are made. This loop ends as soon as the user is satisfied with the proposal.

Since this is small project and is developed for academic purpose system analysis is not required.

6
 3.1- Business Need
In the world we are growing for globalization day by day with the development in IT resources and
advancement, by using latest technologies every organization wants to beat its competitors and want to
grow. Enterprise Resourceful Planning is the need of today’s organization. Survival on manual system is
difficult so, that’s why organization of the corporate world wants to computerize their departments. The
modules should be complete database driven and interactive that should provide the proper information
about the Placement and Training Organization. Success of any system depends up to a large extent on
how accurately a problem is defined, thoroughly investigated and properly carried out to the choice of
solution.

Analysis is the only phase in which the requirements for the new system are identified. System analysis
is a detail study of the various operations performed by a system and their relationship within and
outside of the system. The question is: what must be done to solve the problem? One aspect of analysis
is defining the boundaries of the system and determining whether or not a candidate system should
consider other related system.

During analysis data are collected on the available files, decision points and transactions handled by the
parent system. Data flow diagram, interviews, onsite observations, questionnaires are used as a logical
system model and tools to perform the analysis.

3.2- Objective
The objective of an “Online College Fee Payment System” is to automate the process of collecting and
paying fees. This platform aim is to develop an online payment system that allows students securely and
comfortably pay their fee.

Function of System is as follows:

 Flexible payment methods.

 Paperless transactions.

7
  Transparency.
 It saves time.

3.3- Existing System Description

The main problem with the existing system is that the records are maintained manually. All tasks are
required to be handled manually with a lot of time consume and also includes the maintenance of
records or registers that include a lot of paper work. All the information regarding the customer as well
as the project have to be maintained in the registers and if we have to find out any detail about any field
it involves a lot of time and it is too tedious.

 Limitation of Existing System:-

The present needs to be computerized because the present manual system has the following
drawbacks:-

 The biggest problem of existing system is that each time when a  project changes
then all the records have to be updated.
 Handling and maintenance of records are quite tedious.
 Mishandling of records can cause a great deal of problem.

Thus to overcome all these problems the existing manual system is to be computerized on whole. It will
help in manpower planning and will give perfect estimation of packages information. There is almost
need for computerization as to facilitate “Online College Fee Payment System” will help this to
maintain better records. These are the major problems facing the existing system and would be corrected
with the help of the proposed system.

8
 3.4- Proposed System
The proposed system should have the following features. The transactions should take place in a secured
format between various clients in the network. It provides flexibility to the user to transfer the data
through the network very easily by compressing the large amount of file. It should also identify the user
and provide the communication according to the prescribed level of security with transfer of the file
requested and run the required process at the server if necessary. In this system the data will be send
through the network as a audio file. The user who received the file will do the operations like de
embedding, decryption, and decompress in their level of hierarchy etc.

The modern computerized system is developed with the aim to overcome the drawbacks of existing
system. The proposed system has got many advantages. The new system is more personalized. It is maze
in such a manner that all the new users can understand all the options in it very easily. It is made in a
quick and easy referential manner.

Access to all important matters is always locked and can be opened easily at the time of requirement.
The advantages of proposed system are that securities for all important data are maintained
confidentially. Since it is easy to understand and user friendly, quick entries can be made in this system.

It is the purpose of the new proposed system to address all the problems of the present system. This
system will do the analysing and storing of information either automatically or interactively.

9
 3.5- Feasibility Study with Report
When a project is started an initial investigation is carried out. During this phase of study users
need has recognized and other requirements are determined. Once the problem has been defined
a study is carried out to select the best system i.e. a feasible system that meets performance
requirements. So Feasibility is the determination of whether or not a project is worth doing and
the process followed in making this determination is called a Feasibility Study. In order to
conduct the feasibility study we have seven distinct, but inter-related types of feasibility, these are
Technical feasibility, Operational feasibility, Economical feasibility, Social feasibility, Management
feasibility, Legal feasibility and Time feasibility. Out of these seven three are key feasibilities to
consider, these are:
 Technical Feasibility
 Economical Feasibility
 Operational Feasibility

Technical Feasibility:-
This is concerned with specifying equipment (hardware) and software that will successfully satisfy the
user requirement. It considers the following facts:
 The facility to produce outputs in a given time.
 Response time under certain conditions.
 Ability to process a certain volume of transaction at a particular speed.
 Facility to communicate data to distant location.
While examining technical feasibility, huge importance is given to the configuration of the proposed
system. The configuration should give the complete picture about the system’s requirement such that
what kind of hardware is required and how these units are interconnected so that they could operate and
communicate smoothly. The proposed system can be run on currently existing software and hardware.

10
Economical Feasibility:-

Since cost plays quite an important role in deciding the new system, it must be identified and
estimated properly. So economic analysis is the most frequently used technique for evaluating the
effectiveness (economical feasibility) of a proposed system. To determine the economical feasibility
of the system a cost/benefit analysis is to make. This procedure is to determine the benefits and
savings that are expected from a proposed system and compare them with costs. Four facts that
plays an important role in deciding economical feasibility of the proposed system are as follows:
Cost-saving benefits, Cost-avoidance benefits, Improved-performance benefits, Improved-information
benefits.

Since this project is developed for academic purpose, so there is no need of economical stability in
my project.

Operational feasibility:

It is mainly related to human organizational aspects. The points to be considered are:

• What changes will be brought with the system?

• What organizational structures are disturbed?

• What new skills will be required?

Since this project is very small and it is developed for academic purpose operational feasibility is
not required.

11
Feasibility Study Report:-
The end product, i.e. the documentation after feasibility study report document. It contains the following
sections:
1. Covering the reports, which briefly indicates the management about the nature, general findings
and recommendations to be considered.
2. Table of contents.
3. Narrative study, and the explanation of the purpose and scope of the project, the reason for
undertaking feasibility department involved or affected by candidate system.
4. Detail findings outline the methods used in the present system. Effectiveness, efficiency
operating costs, description of objectives and general procedures of the candidate system.
5. Economic justification details point-to-point cost comparisons and preliminary cost estimates for
the development and operation of the candidate system. Return on Investment (ROI) is also
given.
6. Recommendations and conclusion suggest to management the most beneficial and cost effective
system.

12
SOFTWARE REQUIREMENT
SPECIFICATION

13
 4. SOFTWARE REQUIREMENT SPECIFICATION

4.1- Objective
The objective of an “Online College Fee Payment System” is to automate the process of collecting and
paying fees. This platform aim is to develop an online payment system that allows students securely and
comfortably pay their fee.

A software requirement specification is literally the conversation of a specific point. It's difficult in this
instance to avoid the circular reference. A project's specifications consist of the body of information that
should guide the project developers, engineers, and designers through the work of creating the software.
A software requirement specification document describes how something is supposed to be done. A
specifications document may list out all of the possible error states for a certain form, along with all of
the error messages that should be displayed. The specifications may also describe the steps of any
functional interaction, and the order in which they should be followed by the user. A requirements
document, on the other hand, would state that the software must handle error states reasonably and
effectively, and provide explicit feedback to the users.

4.2- Scope
Boundaries of software products are defined by a set of Requirements. The software development team
designs, implements, tests, and delivers these Requirements to you. A Requirement is an atomic unit of a
software product from the viewpoint of the user. As a rule, Requirements are always correct,
unambiguous, verifiable, and traceable. Requirements are numbered and prioritized.

All Functional Requirements are then listed in a requirements attributes spreadsheet, where all necessary
attributes for each Requirement are maintained. Changes to the project scope can be made only by
issuing new Specifications through a process called Change Requests. Each Change Request implies that
changes will be made to the Budget, Schedule, and Risks.

14
 4.3- Requirements
A requirements specification for a software system – is a complete description of the behaviour of a
system to be developed. It includes a set of used cases that describe all the interactions the users will
have with the software. In addition to use cases, the SRS also contains non-functional (or
supplementary) requirements. Non-functional requirements are requirements which impose constraints
on the design or implementation (such as performance engineering requirements, quality standards, or
design constraints).

Requirement documentation is very important activity after the requirements elicitation and
analysis. This is the way to represent the requirements in a consistent format. Requirement document is
called Software Requirement Specification (SRS).

The software requirement specification is produced at the culmination of the

analysis task. This is the way to represent requirements in a consistent format. It is a
specification for a particular software product , program or a set of programs that
performs certain functions in a specific environment .The function and allocated to software
as part of system engineering are refined by establishing a complete information description, a
detailed functional and behavioral description, an indication of performance requirements and
design constraints, appropriate validation criteria, and other data pertinent to requirements.

Software product, program or set of programs that perform certain functions in a specific
environment. There are two important cases regarding SRS: First one, SRS is used to define
the needs and expectations of the users. The second one, SRS is written for different purpose
and serve as a contract document between customer and developer. This produces the
probability of the customer being disappointment with the final product.

IEEE defines a requirement as:

 A condition of capability needed by a user to solve a problem or achieve an

objective.
 A condition or capability that must be met or processed by a system to satisfy a
contract, standard, specification, or other formally imposed document.

15
Generally, the SRS is a document that completely describes what the proposed software should
do without describing how the software will do it. The basic goal of the requirements phase
is to produce the SRS, which describe the complete external behaviour of the proposed
software.

Organization of an SRS:

The most general organization of an SRS is as follow

Introduction
 Purpose
 Scope
 Definitions
 System Overview

Overall Description

 Product Perspective
 Product Functions
 User Characteristics
 Constraints, Assumptions and Dependencies

Specific Requirements

 External interfaces
 Functions
 Performance requirements
 Logical database requirement
 Design constraints

An SRS must consist of the following features:-

 Consistent
 Complete
 Unambiguous
 Modifiable
 Verifiable

16
  Traceable

Need for SRS:

The SRS is needed for the following reasons:

 An SRS establishes the basis for agreement between client and developer.
 An 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.

Platform:

Windows is very powerful scalable Operating System that provides basic file and prints
services as well as robust platform for server applications. Main features are as follows:-

 More extensive network management features.

 Improved Network Performance.

 Enhanced communication features.

4.3.1- Functional Requirement

Functional requirements specify which output should be produced from the given input. They describe
the relationship between the input and output of the system. For each functional requirement, a detail
description of all the data inputs and their sources, the units of measure, and the range of valid inputs
must be specified.

All the operations to be performed on the input data to obtain the output should be specified. This
includes specifying the validity checks on the input and output data, parameters affected by the
operations, and equations or other logical operations that must be used to transfer the inputs into
corresponding outputs.

An important part of the specification is the system behaviour in abnormal situations, like input unit
(which can occurs in many ways) or error during computations.

17
The functional requirement must clearly state what the system should do if such situations occurs.
Specially, it should specify the behaviour of the system for invalid input and invalid outputs.
Furthermore, behaviour for situations where the input is valid but the normal operations cannot be
performed should also be specified. In short, the system for the foreseen inputs and all foreseen system
states should be specified. These special conditions are often likely to be overlooked, resulting in the
system that is not robust.

4.3.2- Security Requirement

Security requirements are the particularly significant in defence system and many database systems.
Security requirement place restrictions on the use of certain commands, control access to data, provide
different kind of access requirement for different people, require the use of passwords and cryptography
techniques, and maintain a log of activities in system. Given the current security needs even of common
systems, they may also require proper assessment of security threats, proper programming techniques,
and use of tools to detect flaws like buffer overflow.

For the purpose of security process I have added the login feature into my project so as to keep it safe
from the external problem. One can only interact with my project by giving it the suitable i.e. the
accurate ID and password.

This project is made for academic purpose so its security level is quite low.

4.4- Software Requirement

Software requirement plays a very important role in the making and development of a project, as it
provides a suitable language as well as the perfect medium to implement our program or project on the
system. software requirement is very necessary for the implementation of a program.

The Software requirements specification is produced at the culmination of the analysis task. This is the
way to represent requirements in a consistent format. It is a specification for a particular software
product, program or a set of programs that performs certain functions in a specific
environment .The function and allocation to software as part of system engineering are refined
by establishing a complete information description, a detailed functional and behavioural
description, an indication of performance requirements and design constraints, appropriate
validation criteria, and other data pertinent to requirements.

18
Software product, program or set of programs that perform certain functions in a specific
environment. There are two important cases regarding SRS: First one, SRS is used to define
the needs and expectations of the users. The second one, SRS is written for different purpose
and serve as a contract document between customer and developer. This produces the
probability of the customer being disappointment with the final product.

SOFTWARE REQUIREMENT

Operating System - Window 10

Operating System type - 64-bit OS

Web Designing - HTML, CSS, BOOTSTRAP

Client Side Scripting - JavaScript

Server Side Script - PHP (Hypertext Pre-Processor)

Web Server - Apache

Database - MySQL

Control Panel - XAMPP

Web Browser - Google Chrome, Microsoft Edge

Editors - Notepad++, Bracket ,VS code

4.5- Hardware requirement

The hardware requirements specification is produced at the culmination of the analysis task. This is
the way to represent requirements in a consistent format. It is a specification for a particular hardware
product, program or a set of programs that performs certain functions in a specific manner.

In the designation of my project hardware requirement is also very necessary as it provide various tools
for the making of my project.

19
 HARDWARE REQUIREMENT

Hard disk - 512GB

RAM - 4GB

Processor - Intel(R) Core(TM) i7-7700HQ CPU

3.8GHZ

System type - 64-bit Operating System

Interface - Keyboard, Mouse, Display devices

4.6- Module Description

The system comprises of 2 major modules with their sub-modules as follows:

Admin:-

 Login: Admin can login using UserId and Password.

 Manage Student: Admin can manage students.
 Manage College Details: Admin can manage college details.
 View Pending Fees: Admin can see pending fees of students.
 View Paid Student Fees: Admin can check paid fees by students.

User:-

 Home Page: User can see home page.

 Login: User can login using Roll No. And Password.
 View Profile: User can view their profile.
 Fee Payment: User can do pay their fee online.

20
SYSTEM DESIGN

21
 5. SYSTEM DESIGN

System design provides the understandings and procedural details necessary for implementing the
system recommended in the system Emphasis is on the translating the performance requirements into
design specifications. The design phase is a transition from a user oriented document (system proposal)
to a document oriented to the programmers or database personnel.

System design goes through two phases of the development:

1. Logical Design
2. Physical Design
A data flow diagram shows the logical flow of the system. For a system it describes the input (source),
output (destination), database (data stores), and procedures (data flows) all in a format that meets the
user requirements. When analysis prepares the logical system design, they specify the user needs at a
level of detail that virtually determines the information flow into and out of the system and the required
data resources.

5.1- Software Process Model

Waterfall Model:-
The waterfall model is a popular version of the systems development life cycle model for software
engineering. Often considered the classic approach to the systems development life cycle, the waterfall
model describes a development method that is linear and sequential. Waterfall development has distinct
goals for each phase of development. Imagine a waterfall on the cliff of a steep mountain. Once the
water has flowed over the edge of the cliff and has begun its journey down the side of the mountain, it
cannot turn back. It is the same with waterfall development. Once a phase of development is completed,
the development proceeds to the next phase and there is no turning back.

22
The advantage of waterfall development is that it allows for departmentalization and managerial control.
A schedule can be set with deadlines for each stage of development and a product can proceed through
the development process. Theoretically, be delivered on time. Development moves from concept,
through design, implementation, testing, installation, troubleshooting, and ends up at operation and
maintenance. Each phase of development proceeds in strict order, without any overlapping or iterative
steps. The disadvantage of waterfall development is that it does not allow for much reflection or
revision. Once an application is in the testing stage, it is very difficult to go back and change something
that was not well-thought out in the concept stage. Alternatives to the waterfall model include joint
application development (JAD), rapid application development (RAD), synchronize and stabilize, build
and fix problems.

The waterfall model is a sequential design process, often used in software development processes, in
which progress is seen as flowing steadily downwards(like a waterfall)through the phases of conception,
initiation, analysis, design, construction, testing, production, implementation & maintenance.

The whole project is based on waterfall model and follows the Top-down designing Approach.

Feasibility study

Requirements analysis
and specification

Design and
specification

Coding and module

testing

Integration and module

testing

23 Delivery
 5.2- Designing approach

Top down design:-

The TOP DOWN approach starts from the highest level component of the hierarchy and proceed
through to lower levels. A top down design approach start by the major component of the system
decomposing them into their lower level component and iterative until the desired label of detail is
achieved. Top down design method is in some form of step wise refinement. Starting from a abstract
design in each step the design is refine to more concrete level, until we reach a level were no more
refinement is needed.

A system consists of components, which have components of their own; indeed a system is a hierarchy
of components. The highest level component corresponds to the total system. The top down approach
from the highest level component of hierarchy and proceeds through to lower levels. By contrast a
bottom up approach starts with the lowest level component of the hierarchy and proceeds through
progressively higher levels to the top level components.

The top down approach has been promulgated by many researches and has been found to be extremely
useful for design. Most design methodologies are based on the top down approach.

A top down approach suitable only if the specifications of the systems are clearly known and the system
development is from scratch. However, if a system is to be built from an existing system, a bottom
approach is more suitable, as it starts from some existing components.

24
HIGH LEVEL DESIGN

25
 6. HIGH LEVEL DESIGN
A high-level design provides an overview of a system, product, service or process.

Such an overview helps supporting components be compatible to others.

The highest-level design should briefly describe all platforms, systems, products, services and processes
that it depends on and include any important changes that need to be made to them.

6.1- Data Flow Diagram

Features of DFD:

 The exceptional simplicity of the DFD zymology is one reason why data oriented analysis
techniques is the most widely used.
 The data flow diagram is a graphical tool that can be very valuable during the system analysis.
 The DFD depicts information flow without explicit notation of control. (e.g. conditions of loops).
 The level 0 data flow diagram should depict the software as a single bubble.
 Primary input/output files should be maintained.
 One bubble at a time should be refined.

There is a natural tendency to over complicate the DFD. This happens when we try to show too many
details early.

26
Basic Rules of DFD:
Here are the basic rules that apply to all DFD:

 No internal logic should be shown like loops, if-else, this is not a flow chart.
 In order to keep the diagram uncluttered, you can repeat data stores and external entities.
 No process can have only output data flows (a miracle).
 No process can have only input data flows (black hole).
 Data can’t be moved directly from one store to another without a process.
 Data can’t move directly from an external entity to a data store without a process.
 Data stores can’t be sink (only input data flows) or source (only output data flows) in level
1DFD.

0th Level DFD (Context Level Diagram):

It is a diagram which provides the entire systems data flows and processing with a single process
(bubble) is called as context level diagram.

ONLINE
Roll no, Password COLLEGE UserId, Password
STUDENT FEE PAYMENT ADMIN
Profile information SYSTEM Students Details

Payment Details Payment Details

27
 Fig: - Context Level Diagram of Online College Fee Payment
System

1st - Level DFD: This is a more detailed of the previous level that includes the database and

various important units.

Admin Info.
Profile information ADMIN DB
Login
UserId, Password

UserId, Password
Student
Details
STUDENT DB
Add/Update Manage
Students Add/Update
Students Details
Students
Details
Student Details
ADMIN
Payment
Details Payment
Details
Payment
Payment
Details
Details PAYMENT DB
Payment
Details

Payment
Details Payment
Details

Roll no, Password Students Details

28
Login STUDENT DB
Roll no, Password
 STUDENT
Profile information

Fig: - 1st - Level DFD of Online College Fee Payment System

6.2- Entity Relationship Diagram

E-R Model Concept:

The entity relationship model is a generalization of primitive commercial systems, which are based on
hierarchical and network approaches. The E-R relationship, which is also known as Entity Relationship
is based on the theory of real world which consists of a set of basic objects, which are called entities and
relationships among these object. An entity exists as an object and is distinguishable from other objects.

For example: Account number 1002 at the ICICI bank is an entity that uniquely identifies one particular
account.

Entity:

Any distinguishable person, place, thing, event or concept about which information is kept or an object
which can be distinctly identified and distinguished and represented in a database or anything about
which we store information is called an Entity.

Attribute:

Attributes describe the entity to which they are associated. A particular instance of an attribute is a
value. In other words attributes are the characteristics of an entity type. Attributes can be classified as
descriptors or identifiers. A descriptor describes a no uniquely identify an instance of an entity.

Relationship:

29
It is an association among several entities, in other words it provides relationship between one or more
entities.

Notification For E-R Diagram:

There is no standard for representing data objects in E-R diagram. Each modeling methodology uses its
own notation. All notational style represents entities as rectangular boxes and relationship as lines
connecting boxes. Each style uses a special set of symbols to represent the cardinality of a connection.
An entity is represented in E-R diagram as a rectangular box enclosing the entity type name. Attribute
names are enclosed in ellipses and attached to their entity type by straight lines.

The basic symbols used for the E-R constructs are:

Notation Use Symbols

Linking attributes to
Lines entity sets to
relationship sets.

Representing
Ellipse
attributes.

Representing entity
Rectangle
set.

30
 Represent
Diamond
relationship.

Represents multi
Nested Ellipse
valued attribute.

Represents derived
Dotted Ellipse
attributes.

Represents weak
Nested Rectangle
entities.

Represents key
Line with in Ellipse
attribute.

Represents total
Double Lines
relationship.

Represents composite
Ellipse and Lines
attributes.

31
 Represents
Nested diamond identifying
relationship.

Represent is a / has a
Triangle
relationship.

Keys Concept
A key is a value which can always be used to uniquely identify an object instance. It becomes important
to invent a method to distinguish entity and relationships. The differences between entities must be
expressed in terms of attributes.

Super Key:
A Super Key is a set of one or more attributes which, taken collectively, allows us to identify uniquely
an entity in the entity set.

Candidate Key:
Candidate Key is a minimal super key that uniquely identifies a record in a table. Candidate key is also
referred to as Surrogate keys.

Primary Key:
In a database table an attribute which can be used to uniquely identify the records is called Primary Key.
In other words a Primary Key is a key which is a part of candidate key.

Alternate Key:

32
Alternate key is a key which is the part of candidate key but not primary key. In other words if there are
multiple candidate keys in a table, then the keys which are not chosen as primary key will be called as
alternate key.

Composite Keys:
When the key that uniquely identifies the rows of the table is made up of more than one attribute it is
called a composite key. In other words if we use multiple attributes to create a primary key, then that
primary key is refers to as a Composite Key.

Foreign Keys:
A foreign key is column or group of column in a relational database table that provides the link between
data in two tables. It act as cross reference between tables because it references the primary key to other
table thereby establishing a link between them. In other words foreign key is a key that uniquely identify
records from one table to other table.

Guideline for Drawing E-R Diagram

When gathering information i have to:

1. Identify the entities in the system.

2. Identify the attribute of each entity.
3. Identify the relationship between the entities and more things like this.

33
 E- R Diagram of the Project:

Course Semester
Department
Name
Fee_Amount
S ID

Phone_No
STUDENT

Fine ID S ID

Installment_2 Amount
Pays FINE

Installment_1
Installment Due_Date Due_Date

Amount
FEES
S ID
F ID

34
 Collects

Password
Email
Name

ADMIN Phone_No.
A ID

Fig: - ER Diagram of Online College Fee Payment System

6.3- Table Schema

Basically, table schema is all about the structure of tables mention on the database of the project. Name
of database prepared in this project is “paydb” which has following table:

 Admin
 Student
 Fee
 Fine

Table Name: - Admin

Table Description: - Details of Admin

Field Name Data Type Constraints Size Length

Admin ID Integer Primary key 5

35
 Name Varchar Not Null 30

Email Varchar Not Null 30

Phone Number BigInteger Not Null 10

Password Varchar Not Null 30

Table Name: - Student

Table Description: - Details of Students

Field Name Data Type Constraints Size

Student ID Integer Primary Key 10

Name Varchar Not Null 30

Course Varchar Not Null 30

Semester Integer Not Null 10

Department Varchar Not Null 30

Phone Number BigInteger Not Null 10

Address Varchar Not Null 50

36
 Fee Amount Integer Not Null 10

Email Varchar Not Null 30

Password Varchar Not Null 30

Table Name: - Fee

Table Description: - Details of Fees

Field Name Data Type Constraints Size

F ID Integer Primary Key 10

Amount Integer Not Null 10

Installment Integer Not Null 10

Due Date Integer Not Null 10

Table Name: - Fine

Table Description: - Details of Fine

37
Field Name Data Type Constraints Size

Fine ID Integer Primary Key 10

S ID Integer Foreign Key 10

Amount Integer Not Null 10

Due Date Integer Not Null 10

38
 7. LOW LEVEL DESIGN
Low Level Design (LLD) is like design. We would need to incorporate the above and develop some
greater. much later stage where the effort spent will be pseudo-code incrementally. This will be a very
time consuming stage where programming skills are essential. Also, efficiency issues should be
addressed here, otherwise they will have to wait to ailing the HLD. It defines the actual logic for each
and every component of the system. Class diagrams with all the methods and relation between classes
comes under LLD. Programs specs are covered under LLD. LLD describes each and every module in an

LOW LEVEL DESIGN

elaborate manner so that the programmer can directly code the program based on this. There will be at
least 1 document for each module and there may be more for a module. The LLD will contain: - detailed
functional logic of the module in pseudo code – database tables with all elements including their type
and size - all interface details with complete API references (both requests and responses) - all
dependency issues -error message listings - complete input and outputs for a module.

Low Level Design (LLD) is a component level design process that follows a step-by-step refinement
process. This process can be used for designing data structures, required software architecture, source
code and ultimately, performance algorithms. Overall, the data organization may be defined during
requirement analysis and then refined during data design work. Post-build, each component is specified
in detail.

39
The goal of LLD or a low-level design document (LLDD) is to give the internal logical design of the
actual program code. Low-level design is created based on the high-level design. LLD describes the
class diagrams with the methods and relations between classes and program specs. It describes the
modules so that the programmer can directly code the program from the document.

A good low-level design document makes the program easy to develop when proper analysis is utilized
to create a low-level design document. The code can then be developed directly from the low-level
design document with minimal debugging and testing. Other advantages include lower cost and easier
maintenance.

Modulation
A system is considered modular if it consists of discrete component show that each component can be
implemented separately, and a change to one component has minimal impact on other components.

Structure chart
The structure chart is one the most commonly used methods for system design. Structures charts are
used during architectural design to document hierarchical structure, parameters and interconnection in a
system.

40
BIBLIOGRAPHY

41
 8. BIBLIOGRAPHY

BOOKS:-

1. Pankaj Jalote , “ An approach to software engineering” , third edition , 2005 , Narosa

Publishing House.

2. Leon & Leon, “Database Management System” , Vikas Publishing House.

3. Elmasri, Navathe,” Fundamentals of database systems ”, addision Wesley

WEBSITES:-

1. [Link]

2. [Link]

3. [Link]

4. [Link]

42
43