SESSION:- 2025-2026

COMPUTER SCIENCE
PROJECT
STANDARD:- 12TH

SUBMITTED BY: SUBMITTED TO:

RAJNANDINI MR. SHANI NISHAD SIR

CLASS: XII

ROLL NO. : 01
PROJECT BASED ON

SCHOOL
MANAGEMENT
SYSTEM
 Certificate
This is to certify that Rajnandini student of class XII
has successfully completed the Project Work entitled
“School management system” in the subject
Computer Science in Maharshi Arvind Vidya Niketan school.
This project file fully implements all the topics and concepts
learnt in Python and MySql covered in class XI and XII
as per the CBSE syllabus of Computer Science.
I certify that this project report file is up to my expectation
and per guidelines issued by CBSE New Delhi.

_____________ _____________
SIGNATURE OF SIGNATURE OF
EXTERNAL INTERNAL
EXAMINER EXAMINER

______________________
PRINCIPAL
 I would like to express my special thanks of gratitude to my
subject
Teacher Mr. Shani Nishad Sir who gave me golden opportunity to
do
this wonderful project on the topic School Management
System(SMS)
which also helped me in doing a lot of Research and I came to
know about so many new things. I am really thankful to them

Secondly I would also like to thanks my parents and friends who

helped me a lot in finishing this project within the limited time.

I express my deep sense of gratitude to The Principal Sir,

Maharshi Arvind Vidya Niketan School who has been
continuously motivating and extending their helping hand to us.

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.

I am making this project not only for marks but to also increase
my knowledge.
 The central board of the secondary education
has included in its course, a full fledged
computer course covering the
Fundamentals of computer and programming.

Exploring the world of computers, and the project is both

Informative and exciting.
The project “School Management System”
Has been allotted to me.

This project work is allotted to me

is a part of the entire process
involved in the computerization of the
“School Management System”.
 The project “school management system has been
Allocated to me with the aim of testing the
knowledge of a computer as a subject and to make
them realize the problems that come during the
software development process. Thus the
methodology adopted by the central board of
secondary education is to make the examination
process more practical based and realistic by
familiarizing the students with real life situations. Its
main aims and objectives are:
i. To develop a database management system
baesd on my sql for maintaining the records
relating to the management of the
organization.
ii. To develop programs to the record the details
of the student, fees, and admission of the
school.
SYSTEM DESCRIPTION AT A
GLANCE

A School management system to record

the system of students admission, students records entry
and fees deposit that involves several entires
relating to new admission of the student of school
and enter students records and display, manipulate
and also can records student fees details.
Thus recording of entries becomes easy and
the expenditures incurred in the
working of the organization
can be easily derived.
 INTRODUCTION
This software is used to maintain the school management like student detail,
address details, mobile details ,teacher’s details, maintain the school in
updated and maintain records of students in and out data of School.

OBJECTIVES OF THE PROJECT:

The objective of this project is to let the students implement the programming
knowledge that they learnt in class XI and Class XII into a real- world
situation/problem and show the students how programming skills use in
developing a good software.
1. Write programs utilizing modern software tools.
2. Apply object oriented programming principles effectively when developing
small to medium sized projects.
3. Write effective procedural code to solve small to medium sized problems.
4. Students will demonstrate a breadth of knowledge in computer science, as
exemplified in the areas of systems, theory and software development.
5. Students will demonstrate ability to conduct a research or applied
Computer Science project, requiring writing and presentation skills which
exemplify scholarly style in computer science.
PROPOSED SYSTEM:

Today one cannot afford to rely on the fallible human beings of be really
wants to stand against today’s merciless competition where not to wise saying
“to error is human” no longer valid, it’s outdated to rationalize your mistake.
So, to keep pace with time, to bring about the best result without
malfunctioning and greater efficiency so to replace the unending hexyzof flies
with a much sophisticated hard disk of the computer.

One has to use the data management software. Software has been an ascent in
atomization various organisations. Many software products working are now
in markets, which have helped in making the organizations work easier and
efficiently. Data management initially had to maintain a lot of ledgers and a lot
of paper work has to be done but now software product on this organization
has made their work faster and easier. Now only this software has to be
loaded on the computer and work can be done.

This prevents a lot of time and money. The work becomes fully automated
and any information regarding the organization can be obtained by clicking
the button. Moreover, now it’s an age of computers of and automating such an
organization gives the better look.

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:
1. Identify and validate an opportunity to improve business
accomplishments of the organization or a deficiency related to a
business need.
2. Identify significant assumptions and constraints on solutions to that
need.
3. 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?
4. 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 and the relationship to the
Agency/Organization.
5. 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:

1. Determine the feasibility and appropriateness of the alternatives.
2. Identify system interfaces.
3. Identify basic functional and data requirements to satisfy the business
need
4. Establish system boundaries; identify goals, objectives, critical success
factors, and performance measures.
5. Establish system boundaries; identify goals, objectives, critical success
factors, and performance measures.
6. Assess project risks
7. 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.
8. 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.
9. 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.
10. 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.

REQUIREMENTS ANALYSIS PHASE

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 requirements in
terms of data, system performance, security, and maintainability
requirements for the system. The requirements are defined in this
phase to a level of detail sufficient for systems design to proceed. They
need to be measurable, testable, and relate to the business need or
opportunity 12 identified in the Initiation Phase. The requirements that
will be used to determine acceptance of the system are captured in the
Test and Evaluation MasterPlan.

The purposes of this phase are to:

1. Further define and refine the functional and data requirements and
document them in the Requirements Document,
2. 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),
3. Develop detailed data and process models (system inputs, outputs,
and the process
4. 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 script programs during the development phase. Program
designs are constructed in various ways. Using a top-down approach,
designers first identify and link major program 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. End
users, designers, developers, database managers, and network
administrators should review and refine the prototyped designs in
an iterative process until they agree on an acceptable design. Audit,
security, and quality assurance personnel should be involved in the
review and approval process. During this phase, the system is
designed to satisfy the functional requirements identified in the
previous phase. Since problems in the design phase could be very
expensive to solve in the later stage of the software development, a
variety of elements are considered in the design to mitigate risk.

These include:
1. Identifying potential risks and defining mitigating design features.
2. Performing a security risk assessment.
3. Developing a conversion plan to migrate current data to the new
system.
4. Determining the operating environment
5. Defining major subsystems and their inputs and outputs.
6. Allocating processes to resources.
7. Preparing detailed logic specifications for each software module.
The result is a draft System Design Document which captures the
preliminary design for the system.
8. 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.
9. This document receives a rigorous review by Agency 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. Procedural programming
involves the line-by-line scripting of logical instructions that are
combined to form a program. Effective completion of the previous
stages is a key factor in the success of the Development phase.

The Development phase consists of:

1. Translating the detailed requirements and design into system
components.
2. Testing individual elements (units) for usability.
3. 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:

1. Testing at the development facility by the contractor and
possibly supported by end users
2. Testing as a deployed system with end users working together
with contract personnel
3. 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 reviewed and 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 user
requirements.

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:

1. Operate, maintain, and enhance the system
2. Certify that the system can process sensitive information.
3. Conduct periodic assessments of the system to ensure the
functional requirements continue to be satisfied.
4. Determine when the system needs to be modernized,
replaced, or retired.

DATABASE CONNECTION

DISPLAY CHOICES FOR USERS

ASK USER TO ENTER HIS CHOICE

RUN METHOD ACCORDING TO CHOICE

 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. 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)
Types of white box testing:-

The following types of white box testing exist:

1. Api testing - Testing of the application using Public and Private APIs.
2. Code coverage - creating tests to satisfy some criteria of code
coverage.
For example, the test designer can create tests to cause all
statements in the program to be executed at least once.
i. fault injection methods.
ii. mutation testing methods.
iii. static testing - White box testing includes all static testing.

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:

1. Function Coverage: Which reports on functions executed and
2. Statement Coverage: Which reports on the number of lines executed
to complete the test.

HARDWARE AND SOFTWARE REQUIREMENTS

1.OPERATING SYSTEM : WINDOWS 7 AND ABOV

2. PROCESSOR : Dual Core or Above
3. MOTHERBOARD : Pletinum
CHIPSET FOR AMD ATHALON
4. RAM : 512MB+
5. Hard disk : SATA 100 GB OR ABOVE
6. CD/DVD r/w multi drive combo : (If back up required)
7. MONITOR 14.1 or 15 -17 inch
8. Key board and mouse
9. Printer : (if print is required – [Hard copy])

SOFTWARE REQUIREMENTS:

I. Windows OS or linux
II. Python(with pandas module )
III. Mysql
IV. IV. MySql Connector.

1. Informatics Practices ( Python) - Class XI By : Sumita Arora

2. Informatics Practices ( Python) - Class XII By : Sumita Arora
3. Website: https://www.w3resource.com
4. Wikipedia