Sri Seshaas International Public School

C.S. PROJECT FILE

TOPIC: STUDENT MANAGEMENT SYSTEM

ALL INDIA SENIOR SCHOOL CERTIFICATE

EXAMINATION (AISSCE)

SESSION 2024-25

SUBMITTED BY : KRIETHIKESH RM

CLASS: XII

ROLL NO:
1
 CERTIFICATE
This is to certify that KRIETHIKESH RM Has
successfully completed this project report entitled “Student
Management System” During the academic year 2024-2025
towards partial fulfillment of Computer Science Practical
Examination conducted by CBSE.

---------------------------- ------------------------------
Teacher’s Signature Principal’s Signature

--------------------------- ------------------------------
Internal Examiner External Invigilator’s Signature

2
ACKNOWLEDGEMENT

We take this opportunity to express our

Profound gratitude and deep regards to
our subject teacher for his exemplary
guidance, monitoring and constant
encouragement throughout the course of
this project.
The blessing, help and guidance given by
him time to shall carry us a long way in
the journey of life on which we are about
to embark.

- KRIETHIKESH RM
- SUKANDHAN VIDYASANKAR
- SHREE SABARINATHAN

3
 DECLARATION
I hereby declare that the project work
Entitled:

“STUDENT MANAGEMENT SYSTEM”

is prepared by us,

- KRIETHIKESH RM
- SUKANDHAN VIDYASANKAR
- SHREE SABARINATHAN

Under the supervision of our subject teacher

For the partial fulfillment of

All India Senior Secondary Certificate

Examination (AISSCE)

4
 INDEX
1. Certificate
2. Acknowledgements
3. Declaration
4. Aim
5. Coding
6. Output Screenshots
7. Hardware Requirements
8. Bibliography

5
 AIM
Write a program using Python and MY-SQL
Connectivity for STUDENT MANAGEMENT
SYSTEM

6
INTRODUCTION
"STUDENT MANAGEMENT SYSTEM" This project is useful for the

Student management system is an environment where all the process of the

student in the institution is managed .This system saves the time of the student

and of the administrator. It includes process like registration of the student’s

details, assigning the department based on their course and maintenance of the

record. This system reduces the cost and workforce required for this job. As the

system is online the information is globally present to everyone. This makes the

system easy to handle and feasible for finding the omission with updating at the

same time. As for the existing system, they use to maintain their record

manually which makes it vulnerable to security. If filed a query to search or

update in a manual system, it will take a lot of time to process the query and

make a report which is a tedious job.

Get the forms from the counter while standing in the queue which

consumes a lot of the student’s time as well as of management team. As the

number of the student increases in the institute manually managing the strength

becomes a hectic job for the administrator.

This computerized system store all the data in the database which makes

it easy to fetch and update whenever needed.

7
OBJECTIVES OF THE PROJECT

The objective of this project is to let the students apply the programming

knowledge into a real- world situation/problem and exposed the students how

programming skills helps 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.

8
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 err is human” no longer valid, it’s out dated 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 heaps of 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 paperwork has to be done but now software production 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 cans be obtained by

9
clicking the button. Moreover, nowit’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

10
planning phases. End users of the system under development should be involved

interviewing 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.

Identify significant assumptions and constraints on solutions to that 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 and the relationship to the

Agency/Organization.

11
 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.
12
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, and Develop 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.

13
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’s job is to coordinate discussions

between user, audit, security, design, development, and network personnel to

14
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 identified in the Initiation Phase. The requirements

that will be used to determine acceptance of the system are captured in the Test

and Evaluation Master Plan.

The purposes of this phase are to:

15
 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 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
16
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:

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

17
 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 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:

Translating the detailed requirements and design into system components.

18
 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 access

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 reviewed and accepted prior to acceptance of the system.

19
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 on-going. 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 re-enter the planning

phase.

20
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

21
 SOURCE CODE

import os

import platform

# Global list of students

listStd = ["FREYA", "MOHAK", "RAJESH", "DWIVEDI"]

def manageStudent():

# Good-bye message

global bye

bye = """

##############################

# ========================== #

# ===> Brought To You By <=== #

# ===> code-projects.org <=== #

# ========================== #

##############################

"""
22
 # Welcome message and menu

print("""

------------------------------------------------------

|======================================================|

|======== Welcome To Student Management System ========|

|======================================================|

------------------------------------------------------

Enter 1 : To View Student's List

Enter 2 : To Add New Student

Enter 3 : To Search Student

Enter 4 : To Remove Student

""")

try:

userInput = int(input("Please Select An Above Option: ")) # Take

user input

except ValueError:

exit("\nHy! That's Not A Number.") # Error message

else:

print("\n") # Print a new line

# Check user option

23
if userInput == 1:

# View list of students

print("List of Students:\n")

for student in listStd:

print(f"=> {student}")

elif userInput == 2:

# Add a new student

newStd = input("Enter New Student: ").strip()

if newStd.upper() in listStd: # Check if student already exists

print(f"\nThis Student {newStd} Already Exists In The Database.")

else:

listStd.append(newStd.upper())

print(f"\n=> New Student {newStd} Successfully Added!\n")

print("Updated List of Students:")

for student in listStd:

print(f"=> {student}")

elif userInput == 3:

# Search for a student

srcStd = input("Enter Student Name To Search: ").strip()

if srcStd.upper() in listStd: # Check if student exists

24
 print(f"\n=> Record Found: {srcStd}")

else:

print(f"\n=> No Record Found For Student {srcStd}")

elif userInput == 4:

# Remove a student

rmStd = input("Enter Student Name To Remove: ").strip()

if rmStd.upper() in listStd: # Check if student exists

listStd.remove(rmStd.upper())

print(f"\n=> Student {rmStd} Successfully Removed.\n")

print("Updated List of Students:")

for student in listStd:

print(f"=> {student}")

else:

print(f"\n=> No Record Found For Student {rmStd}")

else:

print("Please Enter a Valid Option.") # Invalid option

def runAgain():

# Prompt user to run the program again

runAgn = input("\nWant To Run Again? (Y/n): ").strip().lower()

25
 if runAgn == 'y':

# Clear screen based on the operating system

if platform.system() == "Windows":

os.system('cls')

else:

os.system('clear')

manageStudent()

runAgain()

else:

print(bye) # Print goodbye message and exit

# Run the program

manageStudent()

runAgain()

26
OUTPUT

27
28
29
 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.

30
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

31
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:

api testing - Testing of the application using Public and Private

APIs.
32
 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.

fault injection methods.

mutation testing methods.

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:

FunctionCoverage : Which reports on functions executed and

StatementCoverage : Which reports on the number of lines executed

to complete the test.

They both return coverage metric, measured as a percentage

33
HARDWARE REQUIREMENTS

I.OPERATING SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : PENTIUM (ANY) OR AMD

ATHALON (3800+- 4200+ DUALCORE)

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

K9MM-V VIAK8M800+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])

34
SOFTWARE REQUIREMENTS:

I. Windows OS

II. Python

35
 CONCLUSION
Student Management System can be used by educational institutions to

maintain their student records easily. Achieving this objective is difficult using

the manual system as the information is scattered, can be redundant and

collecting relevant information may be very time-consuming.

All these problems are solved by this project. This system helps in maintaining

the information of pupil of the organization. It can be easily accessed by the

manager and kept safe for a long period of time without any changes.

36
 BIBLIOGRAPHY

1. Computer science With Python - Class XI By : Sumita Arora

2. Website: https://www.w3resource.com

3. https://en.wikipedia.org/wiki/E_(mathematical_constant)

*****************

37