DAV PUBLIC SCHOOL

KUSUNDA , DHANBAD

ACADEMIC YEAR : 2020-21

PROJECT REPORT ON
FEE MANAGEMENT SYSTEM

NAME - SOURAV KUMAR

CLASS - 12
SEC - B
ROLL NO -
SUB - IP
SUB TEACHER – MR. SANJAY KUMAR
CLASS TEACHER – MR. N VISWAKARMA
DAV PUBLIC SCHOOL
KUSUNDA ,DHANBAD

CERTIFICATE

This is to certify that Cadet SOURAV KUMAR Roll No:

has successfully completed the project Work entitled

FEE MANAGEMENT SYSTEM in the subject INFORMATIC

PRACTICES laid down in the regulations of CBSE for the

purpose of Practical Examination in Class XII to be held

in DAV PUBIC SCHOOL KUSUNDA on 2020-21.

Examiner:
Name: _______________
Signature:

TABLE OF CONTENTS [ T O C ]
SER DESCRIPTION PAGE NO

01 ACKNOWLEDGEMENT 04

02 INTRODUCTION 05

03 FUNCTION 05

04 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 06

05 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE 07

06 FLOW CHART 13

07 SOURCE CODE 17

08 OUTPUT 22

09 TESTING 25

10 HARDWARE AND SOFTWARE REQUIREMENTS 27

11 BIBLIOGRAPHY 28
ACKNOWLEDGEMENT
Apart from the efforts of me, the success of any project depends
largely on the encouragement and guidelines of many others. I take this
opportunity to express my gratitude to the people who have been
instrumental in the successful completion of this project.

I express deep sense of gratitude to almighty God for giving me

strength for the successful completion of the project.

I express my heartfelt gratitude to my parents for constant

encouragement while carrying out this project.

I gratefully acknowledge the contribution of the individuals who

contributed in bringing this project up to this level, who continues to look
after me despite my flaws,

I express my deep sense of gratitude to the luminary The Principal,

DAV PUBLIC SCHOOL KUSUNDA who has been continuously motivating
and extending their helping hand to us.

I express my sincere thanks to the academician The Vice Principal,

DAV PUBLIC SCHOOL KUSUNDA who, for constant encouragement and
the guidance provided during this project

I am overwhelmed to express my thanks to The Administrative

Officer for providing me an infrastructure and moral support while
carrying out this project in the school.

My sincere thanks to Mr. SANJAY KUMAR Master In-charge, A

guide, Mentor all the above a friend, who critically reviewed my project
and helped in solving each and every problem, occurred during
implementation of the project

The guidance and support received from all the members who
contributed and who are contributing to this project, was vital for the
success of the project. I am grateful for their constant support and help.
 INTRODUCTION
The main of this system is to develop fee management system
by using c language. This system mainly reduces the work task
and it is easy to maintain the records for a long time than normal
hand written records. The user can check his record details by
just entering his name no need to search all the record. With the
help of this system fee calculations can be done very easily by
this system. So the maintenance and management of fee became
very easy.

In this new fee management system the difference between old

fee system and new fee system is shown. The new system can
overcome the old fee system by adding some additional features
likeit is totally computerized and data can be easily maintained in
database for a long time

Problem Statement:
The aim of problem statement was to design a model

 The model must be user-friendly

 It should not allow viewing others data
 The data privileges should be easily viewed
 By all this features the admin can handle data easily

Functions to Be Provided:

 The user interface should be completely menu driven and user-

friendly
 The user should not find any difficulties in options field
 Faster response should be present
 It should also provide view, add, delete features for better fee
management system
Conclusion:

From this system we can conclude that it provides better fee

management system and also lot of convince than the old
system. This process is very fast data can be easily entered lot of
time is also saved. It is very easy to understand and this program
can be used anywhere based on requirement.

Scope:

Our product usage makes work done at faster way the

software is applicable to view the fee details provided by
the administrator of the organization and student can edit
his personal details which can be viewed by the
administrator.
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The systems development life cycle is a project management

technique that divides complex projects into smaller, more easily
managed segments or phases. Segmenting projects allows managers to
verify the successful completion of project phases before allocating
resources to subsequent phases.
Software development projects typically include initiation, planning,
design, development, testing, implementation, and maintenance phases.
However, the phases may be divided differently depending on the
organization involved.
For example, initial project activities might be designated as
request, requirements-definition, and planning phases, or initiation,
concept-development, and planning phases. End users of the system
under development should be involved in reviewing the output of each
phase to ensure the system is being built to deliver the needed
functionality.
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

INITIATION PHASE

The Initiation Phase begins when a business sponsor identifies a need or

an opportunity.

The purpose of the Initiation Phase is to:

Identify and validate an opportunity to improve business

accomplishments of the organization or a deficiency related to a
business need.
Recommend the exploration of alternative concepts and methods to
satisfy the need including questioning the need for technology, i.e.,
will a change in the business process offer a solution?
Assure executive business and executive technical sponsorship. The
Sponsor designates a Project Manager and the business need is
documented in a Concept Proposal. The Concept Proposal includes
information about the business process andthe relationship to the
Agency/Organization.
Infrastructure and the Strategic Plan. A successful Concept Proposal
results in a Project Management Charter which outlines the
authority of the project manager to begin the project.

Careful oversight is required to ensure projects support strategic business

objectives and resources are effectively implemented into an
organization's enterprise architecture. The initiation phase begins when
an opportunity to add, improve, or correct a system is identified and
formally requested through the presentation of a business case. The
business case should, at a minimum, describe a proposal’s purpose,
identify expected benefits, and explain how the proposed system supports
one of the organization’s business strategies. The business case should
also identify alternative solutions and detail as many informational,
functional, and network requirements as possible.

SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after a business need or

opportunity is validated by the Agency/Organization Program Leadership
and the Agency/Organization CIO.

The purpose of the System Concept Development Phase is to:

Determine the feasibility and appropriateness of the alternatives.

Identify system interfaces.
Identify basic functional and data requirements to satisfy the
business need.
Establish system boundaries; identify goals, objectives, critical
success factors, and performance measures.
Evaluate costs and benefits of alternative approaches to satisfy the
basic functional requirements
Assess project risks
Identify and initiate risk mitigation actions, andDevelop high-level
technical architecture, process models, data models, and a concept
of operations. This phase explores potential technical solutions
within the context of the business need.
It may include several trade-off decisions such as the decision to
use COTS software products as opposed to developing custom
software or reusing software components, or the decision to use an
incremental delivery versus a complete, onetime deployment.
Construction of executable prototypes is encouraged to evaluate
technology to support the business process. The System Boundary
Document serves as an important reference document to support
the Information Technology Project Request (ITPR) process.
The ITPR must be approved by the State CIO before the project can
move forward.
PICTORIAL REPRESENTATION OF SDLC:

PLANNING PHASE
The planning phase is the most critical step in completing
development, acquisition, and maintenance projects. Careful planning,
particularly in the early stages of a project, is necessary to coordinate
activities and manage project risks effectively. The depth and formality of
project plans should be commensurate with the characteristics and risks
of a given project. Project plans refine the information gathered during
the initiation phase by further identifying the specific activities and
resources required to complete a project.
A critical part of a project manager’ sjob is to coordinate discussions
between user, audit, security, design, development, and network
personnel to identify and document as many functional, security, and
network requirements as possible. During this phase, a plan is developed
that documents the approach to be used and includes a discussion of
methods, tools, tasks, resources, project schedules, and user input.
Personnel assignments, costs, project schedule, and target dates are
established.
A Project Management Plan is created with components related to
acquisition planning, configuration management planning, quality
assurance planning, concept
 of operations, system security, verification and validation, and
systems engineering management planning.

This phase formally defines the detailed functional user requirements

using high-level requirements identified in the Initiation, System Concept,
and Planning phases. It also delineates the, System Concept, and
Planning phases.
The purposes of this phase are to:

Further define and refine the functional and data requirements and
document them in the Requirements Document,
Complete business process reengineering of the functions to be
supported (i.e., verify what information drives the business process,
what information is generated, who generates it, where does the
information go, and who processes it),
Develop detailed data and process models (system inputs, outputs,
and the process.
Develop the test and evaluation requirements that will be used to
determine acceptable system performance.

DESIGN PHASE

The design phase involves converting the informational, functional, and

network requirements identified during the initiation and planning phases
into unified design specifications that developers use to scriptprograms
during the development phase. Program designs are c onstructed in
various ways. Using a top-down approach, designers first identify and link
majorprogram components and interfaces, then expand design layouts as
they identify and link smaller subsystems and connections. Using a
bottom-up approach, designers first identify and link minor program
components and interfaces, then expand design layouts as they identify
and link larger systems and connections. Contemporary design techniques
often use prototyping tools that build mock-up designs of items such as
application screens, database layouts, and system architectures

Identifying potential risks and defining mitigating design features.

Performing a security risk assessment.
 Developing a conversion plan to migrate current data to the new
system.
Determining the operating environment.

Defining major subsystems and their inputs and outputs.

Allocating processes to resources.

Preparing detailed logic specifications for each software module. The
result is a draft System Design Document which captures the
preliminary design for the system.
Everything requiring user input or approval is documented and
reviewed by the user. Once these documents have been approved
by the Agency CIO and Business Sponsor, the final System Design
Document is created to serve as the Critical/Detailed Design for the
system.
This document receives a rigorous review byAgency technical and
functional representatives to ensure that it satisfies the business
requirements. Concurrent with the development of the system design, the
Agency Project Manager begins development of the Implementation Plan,
Operations and Maintenance Manual, and the Training Plan

DEVELOPMENT PHASE

The development phase involves converting design specifications into

executable programs. Effective development standards include
requirements that programmers and other project participants discuss
design specifications before programming begins. The procedures help
ensure programmers clearly understand program designs and functional
requirements. Programmers use various techniques to develop computer
programs. The large transaction oriented programs associated with
financial institutions have traditionally been developed using procedural
programming techniques.

Translating the detailed requirements and design into system

components.
Testing individual elements (units) for usability.
Preparing for integration and testing of the IT system.
INTEGRATION AND TEST PHASE

Subsystem integration, system, security, and user acceptance

testing is conducted during the integration and test phase. The
user, with those responsible for quality assurance, validates that the
functional requirements, as defined in the functional requirements
document, are satisfied by the developed or modified system. OIT
Security staff assess the system security and issue a security
certification and accreditation prior to installation/implementation.

Multiple levels of testing are performed, including:

Testing at the development facility by the contractor and possibly

supported by end users

Testing as a deployed system with end users working together with

contract personnel
Operational testing by the end user alone performing all functions.
Requirements are traced throughout testing,a final Independent
Verification & Validation evaluation is performed and all documentation is
reviewedand accepted prior to acceptance of the system.

IMPLEMENTATION PHASE

This phase is initiated after the system has been tested and
accepted by the user. In this phase, the system is installed to support the
intended business functions. System performance is compared to
performance objectives established during the planning phase.
Implementation includes user notification, user training, installation of
hardware, installation of software onto production computers, and
integration of the system into daily work processes. This phase continues
until the system is operating in production in accordance with the defined
userrequirements.
OPERATIONS AND MAINTENANCE PHASE

The system operation is ongoing. The system is monitored for

continued performance in accordance with user requirements and needed
system modifications are incorporated. Operations continue as long as the
system can be effectively adapted to respond to the organization’s needs.
When modifications or changes are identified, the system may reenter the
planning phase.

The purpose of this phase is to:

Operate, maintain, and enhance the system.

Certify that the system can process sensitive information.
Conduct periodic assessments of the system to ensure the
functional requirements continue to be satisfied.
Determine when the system needs to be modernized, replaced, or
retired
FLOW CHART
 SOURCE CODE
import pandas as pd

def add():
## in this section one can add the details of every stuudent
print(" PLEASE FILL ALL THE REQUIRED DETAILS GIVEN
BELOW ")
NAME = input(" ENTER STUDENTS NAME - ")
ADMNO = input(" ENTER ADMISSION NUMBER - ")
father = input(" ENTER FATHER'S NAME - ")
mother = input(" ENTER MOTHER'S NAME - ")
import pandas as pd

def add():
## in this section one can add the details of every stuudent
print(" PLEASE FILL ALL THE REQUIRED DETAILS GIVEN
BELOW ")
NAME = input(" ENTER STUDENTS NAME - ")
ADMNO = input(" ENTER ADMISSION NUMBER - ")
father = input(" ENTER FATHER'S NAME - ")
mother = input(" ENTER MOTHER'S NAME - ")
contact ="0"
while(len(contact)!=10):
contact=input("PLEASE ENTER A VALID MOBILE NO - ")
rollno = input(" ENTER ROLL NUMBER ALLOTED - ")
CLASS = input(" ENTER CLASS WITH SECTION - ")
print("PRESS 1 FOR VIEWING ALL DETAILS AND 0 FOR DONE")
 file = open('details.csv','a')
file.write('\n')
file.writelines([NAME,',',CLASS,',',rollno,',',ADMNO,',',mother,',',
father,',',contact])
file.close()

response=int(input("enter your choice"))

if response==1:
print("NAME =",NAME)
print("ADMISSION NO. = ",ADMNO)
print("FATHER'S NAME = ",father)
print("MOTHER'S NAME = ", mother)
print("MOBILE NO. = ",contact)
print("CLASS = ",CLASS)
print("ROLL NO. = ",rollno)

elif response==0:
print("THANKU FOR THE INFORMATION DATA HAS BEEN
UPDATED")

def fee():
print("THE SCHOOL FEES AS PER CLASS IS LISTED BELOW")
a1=1500
b1=1800
c1=2000
d1=2000
sc=300
ip=200
bus=600
J1=2200
print("CLASS 1-5 ","\t",":-" , a1 , "PER MONTH")
 print("CLASS 6-10","\t"," :-" , b1 , "PER MONTH")
print("CLASS 11-12(SCIENCE)","\t",":-" , c1 , "PER MONTH")
print("CLASS 11-12(COMMERCE)","\t",":-" , d1 , "PER MONTH")
print("CLASS 11-12(PCMB)","\t",":-" , J1 , "PER MONTH")
print("SCIENCE FEE","\t",":-" , sc , "PER MONTH")
print("BUS FEE","\t",":-" , bus , "PER MONTH")
print("COMPUTER FEE","\t",":-" , ip , "PER MONTH")

def dues():
a1=1500
b1=1800
c1=2000
d1=2000
sc=300
ip=200
bus=600
J1=2200
Class1 =int(input ("ENTER STUDENTS CLASS - "))
ADMNO = int(input("ENTER STUDENTS ADMISSION NUMBER -
"))
month=int(input("ENTER THE NO OF MONTH YOU WANT TO
PAY = "))
bs=str(input("IF BUS PRESS YES AND IF NOT PRESS NO - "))
if Class1>=1 and Class1<=5 and bs=="YES":
print ("NET PAYABLE AMOUNT IS - ", a1+bus )
elif Class1>=1 and Class1<=5 and bs=="NO":
print ("NET PAYABLE AMOUNT IS - ", a1)
elif Class1<=10 and bs=="YES":
print("NETPAYABLE FFEES IS -" ,b1+bus)
elif Class1<=10 and bs=="NO":
print("NETPAYABLE FFEES IS -" ,b1)
elif Class1 ==11 or Class1==12 :
l= str(input("ENTER THE STREAM OF THE STUDENT - "))
ss=str(input("ENTER SIDE SUBJECT IP FOR COMPUTER AND
HN FOR HINDI - "))
if l=="SCIENCE" and bs=="YES" and ss=="IP":
fee=month*(c1+bus+ip+sc)
print("NET PAYABLE AMOUNT IS -" ,fee)
if l=="SCIENCE" and bs=="NO" and ss=="IP":
fee=month*(c1+ip+sc)
print("NET PAYABLE AMOUNT IS -" ,fee)
if l=="SCIENCE" and ss=="HN" and bs=="YES" :
fee=month*(c1+sc+bus)
print("NET PAYABLE AMOUNT IS -" ,fee)
if l=="SCIENCE" and ss=="HN" and bs=="NO" :
fee= month*(c1+sc)
print("NET PAYABLE AMOUNT IS -" ,fee)
if l=="COMMERCE" and ss=="HN" and bs=="NO":
fee=month*d1
print("NET PAYABLE AMOUNT IS -" ,fee)
if l=="COMMERCE" and ss=="HN" and bs=="YES":
fee=month*(d1+bus)
print("NET PAYABLE AMOUNT IS -" ,fee)
if l=="COMMERCE" and ss=="IP" and bs=="NO":
fee=month*(d1+ip)
print("NET PAYABLE AMOUNT IS -" ,fee)
if l=="COMMERCE" and ss=="IP" and bs=="YES":
fee=month*(d1+bus+ip)
print("NET PAYABLE AMOUNT IS -" ,fee)
while(1):
print()
print()
print (“ WELCOME TO THE FEE MANAGEMENT PORTAL ")
print (" ******************************************* ")
print()
print("Press 1 :- for adding students details")
print("Press 2 :- for viewing students details ")
print("Press 3 :- for viewing fee structure")
print("Press 4 :- for clearing the due fees")
print("Press 0 :- for exit")
print()
print("PLEASE ENETR ALL THE DETAIL IN CAPITAL LETTER")
command= int(input("Enter the work you like to perform :- "))
if (command == 2):
details = pd.read_csv('details.csv')
print(details)
elif (command == 1):
add()
elif (command == 3):
fee()
elif (command == 4):
dues()
elif (command == 0):
break
else:
print("Sorry Wrong Input")
 OUTPUT
1.HOME PAGE

2.ADDING STUDENT DETAIS

3. VIEWING STUDENT DETAILS

4.VIEWING FEE STRUCTURE

5. CEARING DUE FEES
 TESTING
Software Testing is an empirical investigation conducted to provide
stakeholders with information about the quality of the product or service
under test[1] , with respect to the context in which it is intended to
operate. Software Testing also provides an objective, independent view of
the software to allow the business to appreciate and understand the risks
at implementation of the software. Test techniques include, but are not
limited to, the process of executing a program or application with the
intent of finding software bugs.
It can also be stated as the process of validating and verifying that
a software program/application/product meets the business and technical
requirements that guided its design and development, so that it works as
expected and can be implemented with the same characteristics. Software
Testing, depending on the testing method employed, can be implemented
at any time in the development process, however the most test effort is
employed after the requirements have been defined and coding process
has been completed.

TESTING METHODS
Software testing methods are traditionally divided into black box
testing and white box testing. These two approaches are used to describe
the point of view that a test engineer takes when designing test cases.

BLACK BOX TESTING

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, traceability matrix, exploratory testing and
specification-based testing.
SPECIFICATION-BASED TESTING

Specification-based testing aims to test the functionality of software

according to the applicable requirements.[16] Thus, the tester inputs data
into, and only sees the output from, the test object. This level of testing
usually requires thorough test cases to be provided to the tester, who
then can simply verify that for a given input, the output value (or
behaviour), either "is" or "is not" the same as the expected value
specified in the test case. Specification-based testing is necessary, but it
is insufficient to guard against certain risks

ADVANTAGES AND DISADVANTAGES

The black box tester has no "bonds" with the code, and a tester's
perception is very simple: a code must have bugs. Using the principle,
"Ask and you shall receive," black box testers find bugs where
programmers don't. But, on the other hand, black box testing has been
said to be "like a walk in a dark labyrinth without a flashlight," because
the tester doesn't know how the software being tested was actually
constructed.
That's why there are situations when (1) a black box tester writes
many test cases to check something that can be tested by only one test
case, and/or (2) some parts of the back end are not tested at all.
Therefore, black box testing has the
advantage of "an unaffiliated opinion," on the one hand, and the
disadvantage of "blind exploring," on the other.
WHITE BOX TESTING

White box testing, by contrast to black box testing, is when the tester has
access to the internal data structures and algorithms (and the code that
implement these)

CODE COMPLETENESS EVALUATION

White box testing methods can also be used to evaluate the

completeness of a test suite that was created with black box testing
methods. This allows the software team to examine parts of a system that
are rarely tested and ensures that the most important function points
have been tested.

Two common forms of code coverage are:

Function Coverage: Which reports on functions executed and
Statement Coverage: Which reports on the number of lines
executed to complete the test.
They both return coverage metric, measured as a percentage
 HARDWARE AND SOFTWARE
REQUIREMENTS

HARDWARE REQUIRMENTS

I.OPERATING SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : PENTIUM(ANY) OR AMD

ATHALON(3800+- 4200+ DUAL CORE)

III. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0R

MSI

K9MM-V VIA K8M800+8237R PLUS

CHIPSET FOR AMD ATHALON

IV. RAM : 512MB+

V. Hard disk : SATA 40 GB OR ABOVE

VI. CD/DVD r/w multi drive combo: (If back up required)

VII. FLOPPY DRIVE 1.44 MB : (If Backup required)

VIII. MONITOR 14.1 or 15 -17 inch

IX. Key board and mouse

X. Printer : (if print is required – [Hard copy])

SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
III. MS Excel
IV. Notepad
 BIBLIOGRAPHY

1. INFRMATICS PRACTICES - Class XI - XII By : Sumita Arora

2. A Project Report On Fee Management System
3. Website: https://www.w3resource.com

***