“STUDENT MANAGEMENT SYSTEM”

MINI PROJECT REPORT

Submitted in partial fulfillment for the award of the degree of

BACHELOR OF COMPUTER SCIENCE

(University of Madras)

Submitted

By

MOUNIKA V - 222211057
SANGEETHA R K - 222211064
VIDHYA M - 222211072

Under the Supervision of and Guidance

Prof. E.S. VIJAY SHANKAR, M.Sc., M.Phil.,
Assistant Professor
DEPARTMENT OF COMPUTER SCIENCE
ESSM COLLEGE OF ARTS AND SCIENCE

DEPARTMENT OF COMPUTER SCIENCE

ESSM COLLEGE OF ARTS AND SCIENCE
(Affiliated to Madras University)
PODHATTOORPET – 631208
APRIL - 2025.

1
 “STUDENT MANAGEMENT SYSTEM”
MINI PROJECT REPORT
Submitted in partial fulfillment for the award of the degree of

BACHELOR OF COMPUTER SCIENCE

(University of Madras)

Submitted

By

MOUNIKA V - 222211057
SANGEETHA R K - 222211064
VIDHYA M - 222211072

Under the Supervision of and Guidance

Prof. E.S. VIJAY SHANKAR., M.Sc., M.Phil.,
Assistant Professor
DEPARTMENT OF COMPUTER SCIENCE
ESSM COLLEGE OF ARTS AND SCIENCE

DEPARTMENT OF COMPUTER SCIENCE

ESSM COLLEGE OF ARTS AND SCIENCE
(Affiliated to Madras University)
PODHATTOORPET – 631208
APRIL - 2025.

2
 ESSM COLLEGE OF ARTS AND SCIENCE
DEPARTMENT OF COMPUTER SCIENCE

DECLARATION
I MONUIKA V, Register No. 222211057, SANGEETHA R K, Reg
No.222211064 and VIDHYA M, Register No. 222211072 a bonafede students of
Department of Computer Science, ESSM College of arts and Science, Podhattorpet,
would like to declare that the Mini project work entitled “STUDENT MANAGEMENT
SYSTEM” in partial fulfillment of B.Sc Computer Science degree course of the
University of Madras is my original work.

DATE: Signature

3
 ESSM COLLEGE OF ARTS AND SCIENCE
DEPARTMENT OF COMPUTER SCIENCE

CERTIFICATE
This is to certify that the Mini project entitled “STUDENT MANAGEMENT
SYSTEM” was carried out by MOUNIKA V, Register No. 222211057, and
SANGEETHA R K, Reg No.222211064 and VIDHYA M, Register No. 222211072
in partial fulfillment of the requirement for the Award Bachelor of Computer
Science Degree University of Madras, during the Sixth Semester under my
guidance.

SIGNATURE OF THE GUIDE SIGNATURE OF THE HOD

Submitted for the Viva-Voce Examination held on

INTERNAL EXAMINER EXTERNAL EXAMINER

4
 ACKNOWLEDGEMENT
I am highly indebted to our beloved correspondent Dr.E.S.S. RAMAN, MD
ESSM College of Arts and Science for the encouragement rendered to us in doing
the mini project work, work is insufficient to express my heartfelt thankfulness to
Dr.ESR.ARUN SUBRAMANIAM, CEO College of Arts Science who provided us
all the facilities during the course of work of this study.

I express my sincere thanks to Dr.N. RAJAVENI, MBA., M.Phil., Ph.D.,

Principal, ESSM College of Arts and science for valuable advice and suggestions to
complete this mini project work.

I am Greatful Dr.D.K.RAMKUMAR.,M.Sc.,M.Phil.,M.Ed.,Ph.D,
Assistant Professor and Head, Department of Computer Science, ESSM College of
Arts and Science for his entire support and guidance.
I express my sincere thanks to Prof.E.S.VIJAYSHANKAR,
M.Sc.,M.Phil., Guide, Department of computer science , ESSM College of Arts
and Science for his entire support and encouragement throughout the mini project
work.

Finally, I bow my head before God almighty who blessed who blessed me with
enough physical and mental strength for the successful completion of the mini
project.

MOUNIKA V
SANGEETHA R K
VIDHYA M

5
S.NO CONTENT PAGE
NO
1 ABSTRACT

INTRODUCTION
1.1 Objective
2 1.2 Introduction
1.3 Scope

HARDWARE & SOFTWARE ARE

REQUIREMENT
2.1 Hardware Requirement
3
2.2 Software Requirement

TECHNICAL DESCRIPTION
4 3.1 Front End Description
SOFTWARE ANALYSIS & DESIGN
4.1 Software Analysis
4.1.1. Software Development
Life Cycle
5
4.2 Software Design
4.2.1. Data Flow Diagram
4.2.1.1. zero (0) Level Diagram
4.2.2. ER Model

6
 6 DEVELOPMENT

7 TESTING
8 BENEFITS
9 LIMITATIONS
10 FUTURE ENHANCEMENT
11 MODULES DESCRIPTION
10.1. Student
10.2. Staff Management
10.2.1. Attendance
10.2.2. Time Table
10.2.3. Result
10.3. Admin Module
12 SYSTEM OVERVIEW
13 METHODOLOGY
14 LITRERATURE OF SURVEY
15 RESULTS AND DISCUSSIONS
16 CONCLUSION
17 REFERENCE

7
 ABSTRACT

Student management system project that manages all the information of the
student as well as institution (school, colleges). In the current system all activities are
done manually. It is very time consuming and costly. Our student management
system deals with the various activities related to the students.

In the software we can register as a user and user has two types, student and
administrator, Administrator has the power to add new user, edit and delete user. A
Admin can add student records with department wise. All student can search his/her
basic details. Such as student name, id, contact number, address, date of birth and
roll number. Managing the student’s reports become easier with one such system. It
will also help in saving time and effort. The user interface must be user friendly and
easy to understand

8
 1. INTRODUCTION OF PROJECT

1.1 OBJECTIVE

Student Management System is software which is helpful for college as well

as the school authorities. In the current system all the activities are done manually. It
is very time consuming and costly. Our Student Management System deals with the
various activities related to managing student records. Our objective is
computerizing the process of student records management.

1.2 INTRODUCTION

This project is aimed to automate the student management system. This

project is developed mainly to administrate student records. The purpose of the
project entitled as STUDENT MANAGEMENT SYSTEM is to computerize the
Front Office Management of student records in colleges, schools and coaching’s, to
develop software which is user friendly, simple, fast, and cost – effective.
Traditionally, it was done manually. The main function of the system is to register
and store student details, retrieve these details as and when required, and also to
manipulate these details meaningfully.

9
 1.3 SCOPE

The proposed software product is the Student Management System. The

system will be used in any School, College or coaching institute to get the
information from the student and then storing that data for future usage. The current
system in use is a paper-based system. It is too slow and cannot provide updated lists
of students within a reasonable timeframe. The intentions of the system are to reduce
overtime and increase productivity. Requirements statements in this document are
both functional and non-functional.

10
 2.HARDWARE & SOFTWARE REQUIREMENT

2.1 HARDWARE REQUIREMENT

Intel –I5 processor or higher

2 GB RAM (or above)
40 GB or HARDER DISK or SSD
Mouse/Keyboard

2.2 SOFTWARE REQUIREMENT

OS-Windows 7/8/10 python interpreter

Pycharm IDE or VS code
Xampp(For Mysql) or Mysql Workbench

11
 3.TECHNICAL DESCRIPTION

3.1. FRONT END DESCRIPTION LANGUAGE

Python is a widely used general-purpose, high level programming

language. It was initially designed by Guido van Rossum in 1991 and developed by
Python Software Foundation. It was mainly developed for emphasis on code
readability, and is syntax allow programmers to express concepts in fewer lines of
code. Python is a programming language that lets you work quickly and integrate
system more efficiently. Python is dynamically typed and garbage-collected. It
supports multiple programming paradigms, including procedural, object-oriented,
and function al programming. Python is often described as a “batteries included”
language due to its comprehensive standard library Tkinter. Tkinter is a python
binding to the Tk GUI toolkit. It is the standard python interface to the Tk GUI
toolkit, and is python’s DE facto standard GUI. Tkinter is included with standard
Linux, Microsoft Windows and Mac OS X installs of python. The name Tkinter
comes from Tk interface. Tkinter was written by Fredrik Lundh.

12
 4. SOFTWARE ANALYSIS & DESIGE

4.1. SOFTWARE ANALYSIS

4.1.1. Software Development Life cycle

Requirement

Design

Implementation

Verification

Maintenance

Fig: - SDLC

13
 4.1.2. DESCRIPTION OF USED MODEL

The waterfall model is a sequential software development process, in which

progress is seen as flowing steadily downwards (like a waterfall) through the phases
of conception, initiation, Analysis, Design (Validation), Construction, Testing and
Maintenance.

To follow the waterfall model, one proceeds from one phase to the next in a
sequential manner.

For example, one first completes requirements specification, which after sign-
off are considered “set in stone.” When the requirements are fully completed, one
proceeds to design.

The software in question is designed and a blueprint is drawn for implements

(coders) to follow – this should be a plan for implementing the requirements given.
When the design is fully completed, an implementation of that design is made by
coders.

Towards the later stages of this implementation phase, separate software

components produced are combined to introduce new functionality and reduced risk
through the removal of errors. Thus, the waterfall model maintains that one should
move to a phase only when its preceding phase is completed and perfected.

However, there are various modified waterfall model (including Royce’s and
final model) that may include slight or major variations upon this process. Time
spent early in the software production cycle can lead to greater economy at later
stages.

It has been shown that a bug found in the early stages (such as requirements
specification or design) is cheaper in terms of money, effort and time, to fix than the
same bug found later on in the process.

14
 To take an extreme example, if a program design turns out to be impossible to
implement, it is easier to fix the design at the design stage than to realize months
later,when program components are being integrated, that all the work done so far
has to be scrapped because of a broken design.

This is the central idea behind the waterfall model-time spent early on making
sure that requirements and design are absolutely correct will save you much time and
effort later.

Thus, the thinking of those who follow the waterfall process goes, one should
make sure that each phase is 100% complete and absolutely correct before
proceeding to the next phase of program creation.

Program requirements should be set in stone before design is started

(otherwise work put into a design based before on incorrect requirements is wasted);
the program’s design should be perfect before people begin work on implementing
the design (otherwise they are implementing the wrong design and their work is
wasted), etc.

A further argument for the waterfall model is that it places emphasis on

documentation (such as requirements documented and design documents) as well as
source code.

In less designed and documented methodologies, should team members leave,

much knowledge is lost and may be difficult for a project to recover from. Should a
fully working design document be present (as is the intent of big design up front and
the waterfall model) new team members or even entirely new teams should be able
to familiarize themselves by reading the documents.

15
 Basic principles of the waterfall model are: project is divided into sequential
phases, with some overlap and splash back acceptable between phases. Emphasis is
on planning, time schedules, target dates, budgets and implementation of an entire
system at one time.

Tight control is maintained over the life of the project through the use of
extensive written documentation, as well as through formal reviews and
approval/signoff by the user and information technology management occurring at
the end of most phases before beginning beginning the next phase.

16
 4.2 SOFTWARE DESIGE

4.2.1 Data Flow Diagram

The DFD takes an input-process-output view of a system. That is, data objects
flow into the software, are transformed by the processing elements, and resultant
data objects flow out of the software.

Data objects are represented by labelled arrows and transformations are

represented by circles. The DFD is represented in a hierarchical fashion the first
DFD represents the system as a whole.

Subsequent data flow diagrams enable provide increasing detail with each
subsequent level. The information domain and functional domain at the same time.

As the DFD s refined into levels of greater detail, the analysts perform an
implicit functional decomposition of the system. Also, DFD refinement results in a
corresponding refinement of data as it moves through the processes that embody the
application.

17
 Level
Admin student
Manage

Diagram: Zero-(0) Level

Fig: ER DIAGRAM

18
Use Case Diagram between ADMIN and SYSTEM

19
20
Use Case Diagram between ADMIN and SYSTEM

21
ER DIAGRAM

22
 5. DEVELOPMENT

A UML Deployment diagram is a diagram that shows the configuration of run

time processing nodes and the components that live on them.

Deployment diagram is a kind of structure diagram used in modeling the physical

aspects of an object-oriented system. They are often be used to model the static
deployment view of a system (topology of the hardware).

DEPLOYMENT DIAGRAM

23
 SOURCE CODE
import random

import os

import time

from random import randint

# Later in your code

ID = randint (1000000, 9000000)

class SMS:

# Menu

@staticmethod

def menu ():

print ("1. Admin")

print ("2. Student")

c = input ("Choose from above: ")

if c == "1":

SMS.admin()

elif c == "2":

SMS.student()

else:
24
 print ("Invalid choice")

SMS.menu()

# Student account

@staticmethod

def student ():

print ("Student account")

print ("---------------")

print ("1. Login")

print ("2. Register")

c = input ("Choose from above: ")

if c == "1":

SMS.studentLogin()

elif c == "2":

SMS.studentRegister()

else:

print ("Invalid choice")

SMS.student()

@staticmethod

def studentLogin():

print ("Login as a student")

print ("------------------")

25
 fname = input ("Firstname: ")

ID__ = input ("ID: ")

# Assuming files are saved in a directory 'students/'

if os.path.exists(f"students/{fname}.{ID__}"):

SMS.studentDashboard()

else:

print ("Invalid details!")

SMS.studentLogin()

# Student Registration

@staticmethod

def studentRegister():

print ("Student registration")

print ("--------------------")

fname = input ("Firstname: ")

lname = input ("Lastname: ")

age = input ("Age: ")

gender = input ("Gender: ")

ID = randint (1000000, 9000000)

if fname and lname and age and gender:

os.makedirs("students", exist_ok=True) # Make sure the 'students' directory

exists

with open(f"students/{fname}.{ID}", "w") as f:

f.write(f"Firstname: {fname}\n")
26
 f.write(f"Lastname: {lname}\n")

f.write(f"Age: {age}\n")

f.write(f"Gender: {gender}\n")

f.write(f"ID: {ID}\n")

f.write("\n")

print (f"Student registered successfully with ID {ID}")

SMS.studentDashboard()

else:

print ("All fields are required!")

SMS.studentRegister()

# Student dashboard

@staticmethod

def studentDashboard():

print ("\nStudent dashboard")

print ("---------------")

print ("1. My details")

print ("2. Messages")

print ("3. Logout")

c = input ("Choose from above: ")

if c == "1":

name = input ("Firstname: ")

ID = input ("ID: ")

27
 file_path = f"students/{name}. {ID}"

if os.path.exists(file_path):

with open (file_path, "r") as f:

print(f.read())

SMS.studentDashboard()

else:

print ("Student could not be found!")

SMS.studentDashboard()

elif c == "2":

SMS.studentMessages()

elif c == "3":

SMS.student()

else:

print ("Invalid entry!")

SMS.studentDashboard()

@staticmethod

def studentMessages ():

print("Messages")

print ("1. Send message")

print ("2. View message")

c = input ("Choose from above: ")

if c == "1":

28
 m = input ("Message: -->: ")

fname = input ("Firstname: ")

ID = input ("ID: ")

file_path = f"students/{fname}. {ID}"

if os.path.exists(file_path):

with open(f"{fname}. {ID}. message", "w") as mess:

mess.write(m + "\n")

else:

print ("Invalid details")

elif c == "2":

ID_ = input ("ID: ")

message_file = f"{ID_}. adminMessage"

if os.path.exists(message_file):

with open (message_file, "r") as fi:

print(fi.read())

else:

print ("No message for you!")

SMS.studentMessages()

else:

print ("Invalid choice!")

SMS.studentMessages()

# Admin

29
 @staticmethod

def admin ():

print ("Admin account")

print ("=============")

name = input ("Username: ")

password = input ("Password: ")

if name == "vidhya" and password == "24680":

SMS.adminDashboard()

else:

print ("Invalid admin details")

# Admin dashboard

@staticmethod

def adminDashboard ():

print ("\nAdmin dashboard")

print ("===============")

print ("1. View Student's details")

print ("2. Messages")

print ("3. Remove student")

print ("4. Sign in a new student")

print ("5. Logout")

c = input ("Choose from above: ")

if c == "1":

30
 name = input ("Firstname: ")

ID = input ("ID: ")

file_path = f"students/{name}. {ID}"

if os.path.exists(file_path):

with open (file_path, "r") as f:

print(f.read())

SMS.adminDashboard()

else:

print ("Student could not be found!")

SMS.adminDashboard()

elif c == "2":

SMS.adminMessages()

elif c == "3":

fname = input ("Firstname: ")

ID_ = input ("ID: ")

file_path = f"students/{fname}. {ID_}"

if os.path.exists(file_path):

os.remove(file_path)

print ("Deleting account...")

time.sleep(2)

print ("Account deleted successfully!")

31
 SMS.adminDashboard()

else:

print ("Account could not be found!")

SMS.adminDashboard()

elif c == "4":

SMS.studentRegister()

elif c == "5"

SMS.admin()

# Admin message center

@staticmethod

def adminMessages():

print("Messages")

print ("========")

print ("1. View message")

print ("2. Send message")

c = input ("Choose from above: ")

if c == "1":

n = input ("Firstname: ")

file_path = f"students/{n}. message"

if os.path.exists(file_path):

with open (file_path, "r") as f:

print(f.read())

32
 SMS.adminMessages()

else:

print ("No messages to view!")

SMS.adminMessages()

elif c == "2":

message = input ("Message: -->: ")

_ID = input ("Student ID: ")

with open(f"{_ID}. adminMessage", "w") as adminM:

adminM.write(message + "\n")

SMS.adminMessages()

else:

print ("Invalid choice!")

SMS.adminMessages()

# Start the application

SMS.menu()

33
SEREENSHOTS

34
35
36
37
38
39
40
41
42
43
44
 6. TESTING

Testing is more than just debugging. The purpose of testing of testing can be
quality assurance, verification and validation, or reliability estimation.

Correctness testing and reliability testing are two major areas of testing trade-off
between budget, time and quality.

Software Testing

Software Testing is the process of executing a program or system with the intent
of finding errors. Or it involves any activity aimed at evaluating an attribute or
capability of a program or system and determining that it meets its required results.

Software is not unlike other physical processes where inputs are received, and
outputs are produced. Where software differs is in the manner in which it fails.

Unlike most physical systems, most of the defects in software are design errors,
not manufacturing defects.

To improve quality

As computers and software are used in critical applications, the outcome of

a bug can be severe. Bugs can cause huge losses.

For Verification & Validation (V&V)

Another important purpose of testing is verification and validation (V&V). It is

heavily used as a tool in the V&V process.

Testers can make claims based on interpretations of the testing results, which
either the product works under certain situations, or it does not work.

45
Software Testing Types

Black-box testing

The black-box approach is a testing method in which test data are derived from
the specified functional requirements without regard to the final program structure.

It is also termed data-driven, input/output driven or requirements-based testing.

A testing method emphasized executing the function and examination of their input
and output data.

White-box testing

Contrary to black-box testing, software is viewed as a white-box, or glass-box in

white-box testing, as the structure and flow of the software under test are visible to
the tester.

This testing is based on knowledge of the internal logic of an application’s code.

Testing plans are made according to the details of the software implementation, such
as programming language, logic, and styles.

Test cases are derived from the program structure. White-box testing is also
called glass-box testing, logic-driven testing or design-based testing.

Unit testing

This involves testing of individual software components or modules. Typically

done by the programmer and not by testers, as it requires detailed knowledge of the
internal program design and code.

System testing

The entire system is tested as per the requirements. Black-box type testing that is
based on overall requirements specifications, covers all combined parts of a system.

46
End-to-end testing

Similar to system testing, involves testing of a complete application environment

in a situation that mimics real-world use, such as interacting with a database, using
network communications, or interacting with other hardware, application, or system
if appropriate.

Usability testing

User-friendliness check. Application flow is tested, can new understand the

application easily, proper help documented whenever user stack at any point.
Basically, system navigation is checked in this testing.

Install/uninstall testing

Tested for full, partial, or upgrade install/uninstall processes on different operating

system under different hardware, software environment.

Recovery testing

Testing how well a system recovers from crashes, hardware failures, or other
catastrophic problems. Security testing can system be penetrated by any hacking
way.

Testing how well the system protects against unauthorized internal or external
access. Checked if the system and database is safe from external attacks.

Compatibility testing

Testing how well software performs in a particular hardware/software/operating

system/network environment and different combinations of above.

Comparison testing

Comparison of product strengths and weaknesses with previous versions or other

similar products.

47
Alpha testing

In -house virtual user environment can be created for this type of testing. Testing
is done at the end development. Still minor design changes may be made as a result
of such testing.

Beta testing

Testing is typically done by end-users or other. Final testing before releasing

application for commercial purpose.

48
 7. BENEFITS

 Software provides easy management of student records.

 Software has a very user-friendly interface which is very easy to handle and
understand.
 Software provides security to private data by hiding them.
 Software uses very less memory and takes less time to startup.
 You can store and manage student data in an organized manner. Information
like names, roll numbers, courses, marks, etc., are all stored and managed
centrally.
 Paper records are prone to errors or loss. A Python-based system reduces the
risk of losing important student information and makes the records searchable
and sortable.
 Quickly finding student data, such as grades, attendance, or contact
information, is much faster than searching through paper records.
 By automating tasks like generating reports or calculating grades, it saves time
for both the student and the admin.
 The system can be easily updated to handle larger amounts of data as the
number of students grows, unlike paper-based systems that become
cumbersome.
 Building this project helps you understand and practice Python concepts like
object-oriented programming (OOP), file handling, databases, and user
interfaces (if GUI-based).

49
 8. LIMITATIONS

 Software is limited to Desktop only

 System requires python interpreter installed on the system.
 All options of student management are not included in current version.
 Security options provide only low-level security against beginner attackers.
 GUI is in English only.
 Most SMS projects built in Python (especially those for beginners) tend to use
a command-line interface (CLI).
 A CLI is not intuitive or user-friendly for non-technical users. The lack of a
Graphical User Interface (GUI) can make the system difficult to navigate for
those unfamiliar with coding or terminal commands.
 A typical SMS built in Python may use a lightweight database system like
SQLite or even store data in flat files.
 While SQLite is sufficient for small-scale projects, it can quickly become
inefficient as the number of records grows. For larger institutions with
thousands of students, more powerful databases like MySQL or PostgreSQL
would be required. The system may struggle with performance when handling
large amounts of data.
 Basic SMS systems are typically designed for single-user access or only
support a very limited number of users.
 The system might not support simultaneous multi-user access efficiently. It
may lack features like role-based access control, making it difficult to manage
permissions for different user types (admins, teachers, students).
 Many beginner-level projects focus more on functionality than security.
 The system might not have robust security mechanisms, such as:
 Authentication and authorization: Lack of user login functionality or weak
password handling.
 Storing sensitive data (like student records) in plaintext without encryption
can pose privacy risks.

50
 9. FUTURE ENHANCEMENT

 This Software can be made for all OS.

 Higher security features can be included in this software.
 Program scheduling can also be included in this software.
 This software can be developed to use as tutorial to teach basic concepts of OS
to new users.
 This system can be implemented with OS to reduce overhead of installing and
running interface of each and every tool at different place.
 Automatic shutdown through SMS service can be implemented in this.

51
 10.MODULES DESCRITION

The department portal system is a web – based website developed to

connect and communicate with teachers, parents, students and department
administration. Few packages that are available include Student, Staff, Admin, and
parents.

The department system enables schools and colleges as well as educational

institutions to supervise student related activities such as keeping track of attendance,
records of tests or examination conducted performance in the examination including
details of marks scored and other school related activities. Therefore, we can say that
the software provides comprehensive student record system.

10.1 Student

Taking attendance manually was time consuming so with the development

of this module has mode the task easier. Teachers can now take attendance on the
software so that the parents can view the attendance and be updated whether their
student have attended the class or not.

A comprehensive report of each student and class wise can be generated.

Teachers can take attendance on device or on phone.

10.2. Staff management

Details of staff and non-teaching staff are maintained. One can maintain
details such as name, phone number and subject details. The main functions of these
modules are

1.Add staff details.

2.Syllabus report.

3.Edit or Delete staff details.

52
10.2.1. Attendance:

Taking attendance manually was time consuming so with the development of

this module has made the task easier. Teacher can now take attendance on the
software so that the parents can view the attendance and be updated whether their
student have attended the class or not.

A comprehensive report of each student and class wise can be generated.

Teachers can take attendance on device or on phone.

10.2.2. Time Table:

The Department authority can efficiently plan the timetable by using this
staff module which will help them to run the department smoothly. Management of
admin becomes easier through this module as mapping of class, subject and teacher
can be done as well as creation of time slots. Further, classes can be assigned and
sections too. The functions are as mentioned below:

1.Management of faculties and staff can be done efficiently.

2.Multiple time creation in one month can be done.

3.Time table can be created in advanced.

4.Alert and conflict warning will be intimated if same teacher is assigned

with another class for the same period.

5.Management of substitution is easy through this module in case if any

teacher is absent

6.Edit and delete facility is available.

53
10.2.3 Result:

The staffs update the examination result to the student in a simple way read.
This is useful for students, parent and institutions for getting the results in simple
manner. It’s to uploading image format.

The system is intended for the student. And the privileges that are provided to
students and parents to read and execute his/her result by providing user name and
password for secure login and in case of new student the registration is available and
the parent user has the privilege only to read.

The whole result analyser will be under the control of the administrator and
the admin as the full privileges to read, write and execute the result and admin gives
the privileges to the teacher and student and the guest user to access the result. The
student can share or download his/her result.

The staffs update the examination result to the student in a simple way read.
This is useful for students, parent and institutions for getting the results in simple
manner. It’s to uploading image format.

10.3. Admin Module

This is the first and the base module of the project by this module a admin is
provided to the project to manage the faculty and student module. An admin have the
authority to add and remove the faculty, Add and delete the notification, view
progress and attendance status of the students, update academic calendar etc.

The Department authority can efficiently plan the timetable by using this staff
module which will help them to run the department smoothly. Management of admin
becomes easier through this module as mapping of class, subject and teacher can be
done as well as creation of time slots. Further, classes can be assigned and sections
too

54
 11. SYSTEM OVERVIEW

Student Management System (SMS) is a software application that tracks

current student’s academic information. It maintains academic information for ready
access by office staff, students, their faculty advisors, and committee members.

Instead of tedious paper work, students will be able to submit required

information electronically, and the departments will be able to evaluate the
submissions with a much quicker turnaround.

The Student Management System has been modularized into following

modules.

LOGIN MODULE
The purpose of this module is to provide entry to the system. Based on the
type of login, the user is provided with various facilities and functionalities.

The main function of this module is to allow the user to use SMS. This
module provides two types of login — Admin login and Student login.

ADMINISTRATOR MODULE
In this module when the administrator will enter his/her user and password,
then he/she enter in to the administrator page and this page consists of two following
sub modules.

 Student addition/Updation/Deletion: In SMS each student is added,

updated or deleted according to its branch.
 Notice/Attendance/Result Generation: In SMS information about
notice, ate ndance and internal result is generated.
 Fee Detail and Schedules: Fee information detail and schedule
detail are managed.

55
STUDENT MODULE
In this module when a user enters his student id and password, then he can
visit all the following pages.
 Profile View:
When the student clicks on this link he /she will get this/her
information like student id, student name, password, father name, date of birth,
nationality, city, address, country, phone number, mobile number, email. If he/she
wants than he/she can change the profile.
 Notice View:
When the student clicks on this link, he can see latest notices released
by the administrator.

 Attendance View:
When the student clicks on this, one, the student can get his overall
attendance percentage (present and absent).

 Internal Result View:

When the student clicks on this, he/she will get the internals result
in all the subjects. How much grade point he/she secure out of 20 he/she can
know.

 Time Table View:

When the student clicks on this link then he/she get all the
information that on which day which room which class will be held at which
time.

56
 Fee Detail View:
When the student clicks this link he/she can get all the fees structure
semester wise and annual fee.

 The Student Helpdesk:

This helpdesk is staffed by faculty who are there to help you. You
may contact on (faculty phone no).

57
 12. METHODOLOGY

The project is divided into 2 Main modules such as:

12.1. Student record

12.2. Fees detail

We have sub modules for this:

12.3 Add record modules

12.4 Delete record modules

12.5 Reset record modules

12.6 User modules

12.1 Student record

Student record management system is designed to help manage the daily

school activities of recording and maintaining by automating it. It is also known as
the student information system (SIS) or school records system (SRS).

12.2. Fees detail

This module represents how the transactions are doing every day. It manages
all the fees transactions of students. So, it’s easier the maintain accounting books of
students. In this screen, it also shows all the fee payment details of the students.
While entering the fee details. It indicated the balance payment to make the student.

12.3 Add record

Add Record Module is used to add details about students like Name, Date of
birth, Gender, Department, Mobile Number and Total Fees.

After Adding a Record, you can see the indication Record Was Successfully
Added.

58
12.4 Delete record

 Delete Record Module Is used to Delete the saved details easily.

 Select the name which you have delete it.
 Click the delete record button.
 Now can see the indication Record was deleted Successfully.

12.5 Reset record

 Reset Field Module is used to clear the details to add another detail.
 Now you can add other details easily.

12.6 User modules

Purpose of project is to maintain details of the students such as storing

information about:

 Student Name
 department
 Mobile Number
 Gender

 Total Fees

59
 13.LITRERATURE OF SURVEY

13.1 Automatic Attendance Monitoring System

According to (P. Padma Rekha, V.Narendhiran, D. Amudhan, S Ramya

and N. Pavithra 2016) attendance is taken in every organization. The
traditional approach for attendance is the professor calls student name and
records attendance. For each lecture this is wastage of time. The study
maintained that to avoid losses, an automatic process based on image
processing is to be utilized. This project approach is to use face detection
and face recognition system.

12.2 Biometric Student Identification

According to (Raymond J. D. Anne Marie Dunphy March 2015), One of

the many challenges facing schools today is accurately identifying
students. The bottom line is that schools receive federal and state money
based on accurate and auditable records. In addition, schools need to
provide a safe and secure environment for everyone on campus. Now more
than ever, accurate student identification is the key to the efficient
operation of a school. Over the past few decades, schools have been
implementing all kinds of new technologies to both enhance and improve
operations. Smart boards, laptop and real-time internet resources are just a
part of a student’s everyday experience. Schools worldwide have been
implementing biometric finer scanning to streamline operations, increase
teaching time and enhances security.

13.3 Attendance Monitoring

According to Casas, Ibanez, and Pilongco (2013), this is a study that tries to
formulate an easy way of monitoring the attendance of students and faculty. This
study includes the use of a radio frequency identification card reader and tags.

60
With the help of this study, the reader will be able to see the flow of attendance of
every Faculty and students in their respective classes.

13.4 School Management Software

According to (Ren Web 2019) is school information System software. It allows

the user to take attendance, track grades, and generate report cards, as well as a
HOST of other features. Very features-rich. In years past, Renweb sot of ost its
way with not really understanding who its coe customer was k-12 schools.

13.5 Veyon

According to (Morpus 2017) Veyon is an open sourced digital classroom

management software built off of ITALC that gives you complete control of your
student’s computers, allowing you to display lessons, aid in corrections, view
workstation progress, and lock out particular users. The first impression I had
about Veyon was how clean the user interface was for a free and open-source
software. Veyon is visually pleasing and straightforward with 3D icons, simple
prompts, and easy navigation. Adding to its userfriendly nature, Veyon is also
easy to install and run on any majoroperating System (Windows, Linux OSX).

61
 14. RESULTS AND DISCUSSIONS

14.1. Performance Requirements:

Our software will perform and fulfill all the tasks that any Student
Adminstrator would desire. It is developed as a software program for managing the
Student Adminstration related to keep every track about their details efficiently.
Hereby, our main objective is the customer’s satisfaction considering today’s faster
world.

14.2. Security Requirements:

Student who will be viewing either all or some specific information form the
database. Depending upon the category of user the access rights are decided. It
means if the user is an administrator then he can be able to modify the data, append
etc.

14.3 DISCUSSION

14.3.1 Purpose:

Talking about the system, it consists of basic features which encompass Add
students,view college students, search college students and get rid of the student.
Also it maintains the fee payment details of the students. The following presentation
provides the specification for the system.

14.3.2 Overall System Design Objectives:

The availability of the software’s for almost every process or every system has
taken the world in its top-gear and fastens the day-to-day life. So, we have tried our
best to develop the software program for the Student Management System where all
the tasks to manage the admin operations are performed easily and efficiently. Thus,
above features of this software will save transaction time and therefore increase the
efficiency of the system.

62
 15. CONCLUSION

The project entitled “Student Management System” is developed using

python Tkinter as front end and MYSQL database in back end to computerize the
process of management of student records. This project covers only the basic
features required.

In this Student Management System (SMS) Python project, we have

developed a simple yet effective system for managing student data. The system
allows users (such as administrators or teachers) to perform various operations,
including:

Adding new students: New student information, including name, roll number,
and course details, can be added to the system.
Viewing student records: All registered student details can be displayed in a
readable format.
Updating student information: Existing student records can be updated to keep
the data accurate.
Deleting student records: Unnecessary or outdated student information can be
removed from the system.
Search functionality: The system enables searching for specific student
records based on various criteria such as roll number or name.

This project was built using Python’s core libraries like sqlite3 for database
management, allowing for persistent storage and retrieval of data. Additionally, the
system uses simple input/output operations and basic conditional statements to
navigate through different features.

63
 16. REFERENCE

o https://www.wikipedia.org/
o https://www.geeksforgeeks.org/python-gui-tkinter
o https://www.javatpoint.com/python-tkinter
o https://www.python.org
o https://www.scribd.com
o https://library.ucmerced.edu/data-dictionaries
o https://drive.google.com/drive/folders/1NcZwCNNsgRdq8AMlh1M
Qv82-7vDSMeF4?usp=sharing

64