Académique Documents
Professionnel Documents
Culture Documents
PROJECT REPORT
ON
STUDENT FEES MANAGEMENT SYSTEM
Submitted To
CHHATTISGARH SWAMI VIVEKANAND TECHNICAL UNIVERSITY BHILAI
Principal
Dr. M. L. Agrwal
Institute of Technology Korba(C.G.)
Session 2017-18
We the undersigned solemnly declare that the report of the project work entitled STUDENT FEES
MANAGEMENT SYSTEM is based on our own work carried out during the course of our study
under the guidance of Lect. Miss Shiksha Saxena, Department of Computer Science & Engineering,
Institute of Technology Korba(C.G).
We further declare that the statements made and conclusions drawn are an outcome
of our project work.
_______________________ _____________________
(Signature of the Candidate) (Signature of the Candidate)
________________________ _______________________
(Signature of the Candidate) (Signature of the Candidate)
NAME: Rakeshkumar sahu NAME: Sanjay Kumar Patel
ROLL NO: 33022140 ROLL NO: 33022140
This is to certify that the project entitled STUDENT FEES MANAGEMENT SYSTEM is a record
of work carried out by GAURI SHNKAR DEWNGAN(AP2690), SANJAY KUMAR
PATEL(ENROLLMENT NO), RAKESH KUMAR SAHU(ENROLLMENT NO), SANJAY
KUMAR TONDEY (ENROLLMENT NO) bearing Under my/our guidance and supervision for the
award of Degree of Bachelor of Engineering, Chhattisgarh Swami Vivekananda Technical
University, Bhilai (C.G.), India.
Recommendation
The Project work as mentioned above is here by being recommended and forwarded for examination
and evaluation.
At every outset we express my gratitude to almighty lord for showering his grace and blessing upon us
to complete this project.
Although our name appears on the cover of this project, many people had contributed in some form or
the other form to this project development. We could not done this project without the assistance or
support of each of the following we thank you all.
We wish to place on our record our deep sense of gratitude to our project guide Lect. Miss Shiksha
Saxena, Dept. of C.S.E, I T Korba for their constant motivation and valuable help through the project
work. Express our gratitude to Prof. Mrs. Preeti Manke, H.O.D. of C.S.E, I T Korba for his valuable
suggestions and advices throughout the course. We also extend our thanks to other faculties for their
cooperation during our course.
We finally wish to extend our sincere thanks to those personalities who motivate us and have direct or
indirect assistance in the preparation of this project work.
______________________ _______________________
(Signature of the Candidate) (Signature of the Candidate)
_______________________ _______________________
(Signature of the Candidate) (Signature of the Candidate)
1. INTRODUCTION 07
2. SYSTEM REQUIRMENTS 08 - 09
3 SYSTEM DESIGN 10 - 15
4 SYSTEM TESTING 16 - 19
6 CONCLUSION 22
This software is made to help in any institute by managing fees detail of the students
So thats we named this project as FEES MANAGEMENT SYSTEM . This software is used to
manage students fees detail in the digital format. Discuss some topics of this software introduction as-
1. The idea for this software: - the idea of this software is that manage the documents of fees detail of
students in a digital format. So, easy to handle documents. And also, this is saving paper.
2. Why we need this: - in the old time the database of students fees detail is stored in paper documents
and these are difficult to manage. This software is helping to manage the database of Students fee detail
in digital form to easy to modify and easy to manage
In the requirement analysis, we analysis, project related requirement. In this analysis related to
documentation such as chapters, coding, testing, and implementation. So now we consider their two
phases one is system requirement and software requirement.
2.1.2.2 Backend Tool: - the baking tool for developing a database for this software is.
An item or implement used for a specific purpose and a device, such as a saw, used to perform or facilitate
manual or mechanical work
Systems design is the process of defining the architecture, components, modules, interfaces,
and data for a system to satisfy specified requirements. One could see it as the application
of systems theory to product development. There is some overlap with the disciplines of systems
analysis, systems architecture and systems engineering.
If the broader topic of product development "blends the perspective of marketing, design,
and manufacturing into a single approach to product development," then design is the act of taking
the marketing information and creating the design of the product to be manufactured. Systems
design is therefore the process of defining and developing systems to satisfy
specified requirements of the user. Until the 1990s systems design had a crucial and respected role
in the data processing industry.
In the 1990s standardization of hardware and software resulted in the ability to
build modular systems. The increasing importance of software running on generic platforms has
enhanced the discipline of software engineering.
Logical design
It covers following aspects:
1) Review of the current system.
Physical design
It covers following aspects:
1) Design database
3.2.1.1 REQUIREMENTS
A software requirements specification (SRS) 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 use cases that describe all the interactions the users will have with the software.
3.2.1.2. DESIGN
Software design is a process of problem solving and planning for a software solution. After the
purpose and specifications of software are determined, software developers will design or
employ designers to develop a plan for a solution. It includes low-level component
and algorithm implementation issues as well as the architectural view.
3.2.1.4 VERIFICATION
Comparison of two or more items, or the use of supplementary test, to ensure the accuracy,
correctness or truth of the information.
3.2.1.5 MAINTENANCE
The waterfall model maintains that one should move into a phase only when its preceding phase
is completed and perfected. Phases of development in the waterfall model are thus discrete, and
there is no jumping back and forth or overlap between them. As many find this approach,
particularly rigid, modifications have been made over the years and new variants of the model
have emerged.
3.3.1 REQUIREMENTS
Business requirements are gathered in this phase. This phase is the main focus of the project
managers and stakeholders. Meetings with managers, stakeholders and others are held in order to
determine the requirements.
Who is going to use the system?
How will they use the system?
What data should be input into the system?
What data should be output by the system?
These are general questions that get answered during a requirements gathering phase. This
produces a nice big list of functionality that the system should provide, which describes functions
the system should perform, business logic that processes data, what data is stored and used by the
system, and how the user interface should work. The overall result is the system as a whole and
how it performs, not how it is actually going to do it.
3.3.2 DESIGN
The software system design is produced from the results of the requirements phase. Architects have
the ball in their court during this phase and this is the phase in which their focus lies. This is where
the details on how the system will work are produced. Architecture, including hardware and
3.3.4 TESTING
During testing, the implementation is tested against the requirements to make sure that the product
is actually solving the needs addressed and gathered during the requirements phase. Unit tests and
system/acceptance tests are done during this phase. Unit tests act on a specific component of the
system, while system tests act on the system as a whole.
So in a nutshell, that is a very basic overview of the general software development life cycle
model. Now lets delve into some of the traditional and widely used variations.
1. Window for input fee details of students :- trough this input the detail of Roll No., Name,
Fathers Name, Mobile No., Address, Email, Semester, Branch, Fee and Date of payment.
2. DATABASE :- Here all the data are saved which is input from the Window for input fee
details of students .
3. Window for search and print and delete student detail :- From this window the individually
perform the action on the Printing and Deleting of any students fee detail by searching their roll no.
4. Window for print of full database of student fee detail:- Through this window we can print the
whole Students fee detail by one click.
Software testing is an investigation conducted to provide stakeholders with information about the
quality of the product or service under test. Software testing can also provide an objective,
independent view of the software to allow the business to appreciate and understand the risks of
software implementation. Test techniques include, but are not limited to, the process of executing
a program or application with the intent of finding software bugs (errors or other defects
Testing is the process of reviewing and executing a program with an intention to identify the errors.
After completing and integrating the software module, software must be tested to uncover as many
errors as possible before delivering to our customers. Testing is a process of executing with the
intent of finding an error.
Software testing is a crucial element of software quality assurance and represents the ultimate
review of specification, design and code generation. Basically, once the code (source) has been
generated s/w must be tested to uncover and correct as many errors as possible before delivery to
your customer. The objective of s/w testing is to uncover errors [23]. To uncover all possible errors
of our project we are going to perform following four tastings:
25000
Now days computerizations of the existing manual system are going on a large scale because of the
versatility, speed, accuracy and diligence it offers to its users. Computers provide practical means to
organize things systematically and economically in the organization the use of computers for
managing transactions; information processing and preparation of reports can prove to be a blessing.
The project in discussion is an attempt to attain all the above said objectives. Its development
was mean to replace the manual system and to achieve the goal to maximum accuracy and most
efficiently. But like every other system might process faults to its credits and has its own limitation.
Neglecting these few negations, the project can be called a stepping stone to automate processes in
organizations. This project have faster than human, but have some limitation like need to run this
electricity, computer of required configuration.