Project.12

1 | INSTITUTE OF TECHNOLOGY, KORBA (CSE)
A
PROJECT REPORT
ON
STUDENT FEES MANAGEMENT SYSTEM
Submitted To
CHHATTISGARH SWAMI VIVEKANAND TECHNICAL UNIVERSITY BHILAI
For fulfillment of the award of the degree
BachelorofEngineering
In
Computer Science & Engineering
Submitted By: Guided By:
Gauri Shankar Dewangan Miss Shiksha Saxena
Roll No: 3302214009 Lect. CSEDept.
Sanjay Kumar Tondey
Roll No:
Rakesh Kumar Sahu
Roll No: 33022140
Sanjay Kumar Patel
Roll No: 33022140
Approved By:
Mrs. Preeti R. Manke
Head of Department CSE
Principal
Dr. M. L. Agrwal
Institute of Technology Korba(C.G.)
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
INSTITUTE OF TECHNOLOGY KORBA(C.G)
Session 2017-18

DECLARATION BY THE CANDIDATES
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)
NAME: Gauri Shankar Dewangan NAME: Snjay Kumar Tondey
ROLL NO: 3302214009 ROLL NO:
________________________
(Signature of the Candidate)
NAME: Rakeshkumar sahu
ROLL NO: 33022140
_______________________
NAME: Sanjay Kumar Patel
ROLL NO: 33022140

CERTIFICATEBY THE SUPERVISOR
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.
To the best of my/our knowledge and belief the Project
1. Embodies the work of the candidate him/herself.
2. Has not been submitted for the award of any degree.
3. Fulfils the requirement of the Ordinance relating to the B.E degree of the University and,
4. Is up to the desired standard in respect of contents and is being referred to the examiners.
(Signature of the Guide)
Lect. Miss Shiksha Saxena
(Department of CSE/IT)
(Institute of Technology Korba (CG))
Recommendation
The Project work as mentioned above is here by being recommended and forwarded for examination
and evaluation.
(Signature of the Head of Department)
Mrs. Preeti R. Manke
(HOD, Department of Computer Sc. & Engineering)
(Institute of Technology Korba (CG))

ACKNOWLEDGEMENT
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)
NAME: RAKESH KUMAR SAHU
ROLL NO:
NAME: SANJAY KUMAR TONDEY
ROLL NO:
_______________________
NAME : SANJAY KUMAR PATEL
ROLL NO:
_______________________
NAME GAURI SHANKR DEWANGAN
ROLL NO:

ABSTRACT
The project entitled “Student fees management system” is done to make the manual process easier
by making it a computerized system for maintaining the student fees.
This system helps to override the manual work with computerized work result work done in less
time and effort. This system helps to maintain the record of the student fee structure. All this is done
in a click of a button.
By this project to help maintain the fees details of students in computerized ways to easy to handle
compare then files or papers. In pen paperwork for this is so difficult and do it very carefully because
it is a financial matter.
In this project feed the students fee detail in the software window and submit it and then it is saved
in the database of the system.
This project handles the detail of student fees in the digital way in database of system. This project
is also serving to search, update, delete the data from the system database.
Although this project has helped to institution to save the detail of fees of students in the database
system instant of files and papers. It provides two ways that the process of handling of data in the
easiest way for any institution

CHAPTERS PAGE NO.
1. INTRODUCTION 07
2. SYSTEM REQUIRMENTS 08 - 09
2.1 SYSTEM REQUIREMENT 09
2.1.1 HARDWARE SPECIFICATION 09
2.1.2 SOFTWARE SPECIFICATION 09
2.1.2.1 FRONT-END TOOL 09
2.1.2.2 BACKEND TOOL 09
3 SYSTEM DESIGN 10 - 15
3.1 DESIGN OVERVIEW 10
3.2 DESIGN APPROACH 11
3.2.1 WATERFALL MODEL 11
3.3 SOFTWARE DEVELOPMENT LIFE CYCLE ( SDLC ) 13
3.4 DATA FLOW DIAGRAM 15
4 SYSTEM TESTING 16 - 19
4.1 BLACK BOX TESTING 16
4.2 WHITE BOX TESTING 17
4.3 ACCEPTANCE TESTING 18
5 INPUT AND OUTPUT SCREEN DESIGN 19 – 21
6 CONCLUSION 22
INDEX

CHAPTER 01
INTRODUCTION
This software is made to help in any institute by managing fees detail of the students
So that’s we named this project as “FEES MANAGEMENT SYSTEM “. This software is used to
manage student’s 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 student’s 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
3. What services give this software: - this software serves you-
(i) Store - store fees detail for students in the database.
(ii) Delete – delete fees detail of the students from the database.
(iii) Searching – this software is Allow you to search the student fee detail By their Roll numbers.

CHAPTER 02
REQUIREMENT ANALYSIS
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
phase’s one is system requirement and software requirement.
Fig 3.1: Requirement Analysis.
Requirements analysis in systems engineering and software engineering, encompasses those
tasks that go into determining the needs or conditions to meet for a new or altered product, taking
account of the possibly conflicting requirements of the various stakeholders, such as beneficiaries or
users. It is an early stage in the more general activity of requirements engineering which encompasses
all activities concerned with eliciting, analyzing, documenting, validating and managing software or
system requirements.
Requirements analysis is critical to the success of a systems or software project.
The Requirements should be documented, actionable, measurable, testable, traceable, related to
identified business needs or opportunities, and defined to a level of detail sufficient for system design.
2.1 SYSTEM REQUIREMENT
System requirement containing hardware and software requirements for our project. Let us see the
some related aspects of system requirements.
2.1.1Hardware Specification:
 PROCESSOR: Intel Pentium 4s or More
A processor, or "microprocessor," is a small chip that resides in computers and other electronic
devices. Its basic job is to receive input and provide the appropriate output.
 RAM: 1.00 GB Ram

RAM is computer memory that holds instructions and data. When the computer is switched off, the
contents of the RAM are lost.
 HARD DISK: 220 GB
A hard disk is part of a unit, often called a "disk drive," "hard drive," or "hard disk drive," that store
and provides relatively quick access to large amounts of data on an electromagnetically charged
surface or set of surfaces.
2.1.2 Software Specification:
2.1.2.1 Front-end Tool: - It is visual basic .NET to design and coding the software or project.
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
 OPERATING SYSTEM: Widows 7/8/10.
An Operating System is a computer program that manages the resources of a computer. It accepts
keyboard or mouse inputs from users and displays the results of the actions and allows the user to run
applications, or communicate with other computers via networked connections.

CHAPTER 03
SYSTEM DESIGN
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.
3.1 DESIGN OVERVIEW
It goes through logical and physical with emphasis on preparing input / output specifications,
specification of implementation program; the following points were kept in mind while designing
the new system.
1) Data entry and data editing through well laid screen format
2) Data validation, whenever necessary to ensure correctness of input data
3) Reduce the redundancy
4) Should be menu driven
5) Data security
6) The system should be user friendly
Logical design
It covers following aspects:
1) Review of the current system.
2) Preparation of input specification.
3) Preparation of output specification.
4) Preparation of logical design.
Physical design
It covers following aspects:
1) Design database
2) Specify input/output screen
3) Specify the report

3.2 DESIGN APPROACH
Design is a meaningful engineering representation of something that is to be built. It can be traced
to a customer’s requirement and at the same time assessed for quality against a set of predefined
criteria for ‘good’ design. In the software engineering context, the design focuses on four major
areas of concern, data, architecture, interfaces and components.
1) User requirements specifications, documentation in the form of SRS.
2) High Level Systems Documentations in the form of HLD manual.
3) Level System Documentation in the form of LLD manual.
4) User requirements Manual/Guide.
Operations manual to aid the users in running the designated system.
3.2.1 WATERFALL MODEL
The waterfall model is a sequential design process, often used in software development
process in which progress is seen as flowing steadily downwards (like a waterfall) through the
phases of Conception, initiation analysis design, Construction,
Testing, Production/Implementation and Maintenance. 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.
Figure 4.1: - Waterfall Model
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.3. IMPLEMENTATION
An implementation is a realization of a technical specification or algorithm as a program, software
component or other computer system through programming and deployment. For example, web
browsers contain implementations of World Wide Web Consortium-recommended specifications,
and software development tools contain implementations of programming languages.
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 SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
. Software life cycle models describe phases of the software cycle and the order in which those
phases are executed. There are tons of models, and many companies adopt their own, but all have
very similar patterns. The general, basic model is shown below: Each phase produces deliverables
required by the next phase in the life cycle. Requirements are translated into design. Code is
produced during implementation that is driven by the design. Testing verifies the deliverable of
the implementation phase against requirements.
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

software, communication, software design (UML is produced here) are all part of the deliverables
of a design phase
.
3.3.3 IMPLEMENTATION
Code is produced from the deliverables of the design phase during implementation and this is the
longest phase of the software development life cycle. For a developer, this is the main focus of the
life cycle because this is where the code is produced. Implementation my overlaps with both the
design and testing phases. Many tools exist (CASE tools) to actually automate the production of
code using information gathered and produced during the design phase.
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 let’s delve into some of the traditional and widely used variations.
3.4 DATA FLOW DIAGRAM
Window
for input
fee
details of
students
Window for
search and
print and
delete student
Window for
print of full
database of
student fee
detail
1. Window for input fee details of students :- trough this input the detail of Roll No., Name,
Father’s 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.

CHAPTER 04
TESTING
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:
4.1 BLACK BOX TESTING
Black Box Testing is also known as ‘BEHAVIORAL TESTING’ which focuses on the functional
requirements of the s/w. Black box testing enables the s/w engineer to derive sets of input condition
that will fully exercise all functional requirements for a program.
Black-box testing treats the software as a "black box"—without any knowledge of internal
implementation. Black-box testing methods include: equivalence partitioning, boundary value
analysis, all-pairs testing, fuzz testing, model-based testing, exploratory testing and specification-
based testing.
4.1.1 ISSUE WITH BLACK BOX TESTING
It is possible to test all inputs? Without complete knowledge of internal workings it is difficult to
design test cases. Black box testing is also called Behavioural testing, focuses on the functional
requirements of the software. That is black box testing enables us to derive sets of input conditions
that will fully exercise all functional requirements of the program. Black box testing is not an
alternative to White box testing. Rather, it is complimentary approach that is likely to uncover a
different class of errors than white box methods.
1) Black box testing attempts to find errors.
2) Incorrect or missing functions.
3) Interface errors.
4) Errors in data structure or external database access.
5) Behaviour or performance errors.
6) Initialization and termination errors.
Black box tests are used to demonstrate that the software is functioning properly, that is, input is
properly accepted and output is correctly produced and that the integrity of external information is
maintained. A black box test examines fundamental aspects of a system with little regard for the
internal logical structure of the s/w.

4.2 WHITE BOX TESTING
Although Visual Basic 6 it is capable to judge the control structure errors quite accurately, but still
to ensure that the correct logical flow of coding, white box testing is required.
White box testing of software is predicted on close examination procedural detail. Logical paths
through the software are tested by providing test cases that exercise specific sets of condition
and/or loops. The status of the program may be examined at various points to determine if the
expected or asserted status corresponds to the actual status. But in practice it is revealed that taking
logical paths is almost impossible even for small program and hence several white box testing is
done on a small number of paths where the flow of data is important from result point of view.
White box testing is also called, as glass box testing is a case design method that used the control
structures of the procedural design test case. Using white box some tests were derived that:
1) Guarantee that all independent paths within a module have been exercised at least once.
2) Exercise all logical decisions on their true and false sides.
3) Execute all selected loops at their boundaries and within their operational bounds.
4) Exercise internal data structures to ensure their validity.
White-box testing is when the tester has access to the internal data structures and algorithms
including the code that implement these.
We are using an acceptance testing in our project
4.3 ACCEPTANCE TESTING
Acceptance testing can mean one of two things:
A smoke test is used as an acceptance test prior to introducing a new build to the main testing
process, i.e. Before integration or regression.
Acceptance testing performed by the customer, often in their lab environment on their own
hardware, is known as user acceptance testing (UAT). Acceptance testing may be performed as
part of the hand-off process between any two phases of development.
4.3.1 ALPHA TESTING
Alpha testing is simulated or actual operational testing by potential users/customers or an
independent test team at the developers' site. Alpha testing is often employed for off-the-shelf
software as a form of internal acceptance testing, before the software goes to beta testing.
4.3.2 BETA TESTING
Beta testing comes after alpha testing and can be considered a form of external user acceptance
testing. Versions of the software, known as beta versions are released to a limited audience outside
of the programming team. The software is released to groups of people so that further testing can
ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open
public to increase the feedback field to a maximal number of future users.
4.3.3 ADVANTAGES OF ACCEPTANCE TESTING
4.3.3.1 ESTABLISH BASELINES READINGS

Many electrical test results are objective or must be trended with previous test results. For
example, a transformer insulation resistance test could appear acceptable until it is compared with
the transformers acceptance values.
4.3.3.2 VERIFY INTEGRITY OF COMPONENTS.
Manufacturers of electrical equipment strive to provide the best products. Major Insurance Carriers
recommend that Infrared Testing (CNA Letter)
4.3.3.3 VERIFY PROPER INTERFACE B/WCOMPONENTS /COMMISSIONING
How many people are involved in your latest project? One or more equipment manufacturers,
multiple engineers a construction company and an electrical contractor? Finding a problem on
the first day of energization is too late! One minor equipment or wiring problem can delay
project completion by hours or even days. Building Assessment Group, Inc. Can provide you
"Third Party Litigation" to assist you with peace of mind regarding the proper interface of
components is in place.

CAHPTER 05
INPUT AND OUTPUT SCREENSHOT
1.HOMEPAGE
2.1 SUBMMIT AND UPDATE PAGE FOR DATA

2.2 SUBMMITED DATA
3. SEARCH AND DELTE OR PRINT DATA
4. VIEW AND PRINT FULL DATABASE
25000

CAHPTER 06
CONCLUSION
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.

Project.12

More Related Content

What's hot

Similar to Project.12

Recently uploaded

Project.12