Student Management System

SIMATS SCHOOL OF ENGINEERING

CHENNAI- CAPSTONE
PROJECT REPORT
Course Name: CSA-0550 Database management system
Project Name: Student management system

Submitted in the partial fulfillment for the award of the degree of Bachelor of Engineering

Computer science engineering

Submitted by

S.R.Guruchandru
192211112

Under the Supervision of

Dr.Carmel Mary belinda

June 2024

VI
 2

LIST OF ABBREVIATIONS

HTML = Hyper Text Markup Language

CSS = Cascading Style Sheets
JS = Java Script
SQLite = Structure Query Lite
GUI = Graphical User Interface
PIP = Pip Install Packages
regex = Regular Expressions
 3

LIST OF FIGURES AND GRAPHS

FIGURE TITLE PAGE NO.

NO.
1 Architectural flow chart 6

2 Home page 7

9
3 Home Page (base.html)

Main Home Page (dasboard.js) 9

4

Color selector of menu 10

5

Color selector of menu 10

6

Prototype submission 11
7

Prototype submission 11
8

Performance Analysis 12
9
 4

LIST OF TABLES

TABLE TITLE PAGE NO.

NO.
 5

ABSTRACT

Our main purpose is to make or change the information from offline to online systems i.e., from Pen
and Paper to Digital format. Now-a-days, information becomes the wealth of a person and most of
the information is getting leaked by other persons in the form of paper records. So, we are here to
maintain and convert the complete data into an online format which provides some security to the
personal data or information. Our main aim is to share this project to the various schools and
colleges in order to avoid data theft and the administrator will have complete access to do anything.

The Student Management System will have some kind of modules like Attendance, Marks, Grades,
Academics, Classes, Terms, Student and Faculty Information, Payments, etc. The administrator can
have complete control and access to the addition or deletion of the students/faculties data. We have
developed a website using Front-End technologies like HTML and CSS; Back-End with the help of
Python as a programming language also having JavaScript, Django framework and finally gathering
/ storing the data or information using SQLite database. This is the complete workflow or
methodology for our project.

Finally, we have done a lot of research on the basis of the Student Management System and come up
with one of the best solutions. Our team searched and came up with three different solutions or
methods which were already there or existing. So, we are trying to innovate the process and the
methodologies, techniques and technologies, etc. Hence, we are here to share our views and
experience with our project. Before beginning this project, we all had one overview on this concept
and we hope we tried to achieve that overview successfully.
 6

TABLE OF CONTENTS
CHAPTER TITLE PAGE NO.
NO.

List of Abbreviations iii

iv
List of Figures and Graphs
v
List of Tables
vi
Abstract
1 CHAPTER-1:
PROJECT DESCRIPTION AND OUTLINE 1

1.1 Introduction 1
1.2 Motivation for the work
1
1.3 [About Introduction to the project
1
including techniques]
1.4 Problem Statement 1

1.5 Objective of the work 2

1.6 Organization of the project 2
1.7 Summary
2

2 CHAPTER-2:
RELATED WORK INVESTIGATION 3
2.1 Introduction 3
2.2 <Core area of the project> 3
2.3 Existing Approaches/Methods 3
2.3.1 Approaches/Methods -1 3
2.3.2 Approaches/Methods -2 3
2.3.3 Approaches/Methods -3 3
2.4 <Pros and cons of the stated Approaches/Methods > 4
2.5 Issues/observations from investigation 4
2.6 Summary 4
 7

3 CHAPTER-3:
REQUIREMENT ARTIFACTS 5
5
3.1 Introduction
5
3.2 Hardware and Software requirements
5
3.3 Specific Project requirements
5
3.3.1 Data requirement
5
3.3.2 Functions requirement
5
3.3.3 Performance and security requirement
5
3.3.4 Look and Feel Requirements
5
3.4 Summary
4 CHAPTER-4:
DESIGN METHODOLOGY AND ITS NOVELTY 6
4.1 Methodology and goal 6
4.2 Functional modules design and analysis 6
4.3 Software Architectural designs 6
4.4 Subsystem services 7
4.5 User Interface designs 7
4.6 Summary
8

5 CHAPTER-5:
TECHNICAL IMPLEMENTATION & ANALYSIS 8

5.1 Outline 8
9
5.2 Technical coding and code solutions
10
5.3 Working Layout of Forms
11
5.4 Prototype submission
12
5.5 Test and validation
12
5.6 Performance Analysis(Graphs/Charts) 12
5.7 Summary 12
 8

6 CHAPTER-6:
PROJECT OUTCOME AND APPLICABILITY 13

6.1 Outline 13
6.2 key implementations outlines of the System 13
6.3 Significant project outcomes
13
6.4 Project applicability on Real-world applications
13
6.4 Inference
13

7 CHAPTER-7:
CONCLUSIONS AND RECOMMENDATION 14

7.1 Outline 14
7.2 Limitation/Constraints of the System 14
7.3 Future Enhancements
14
7.4 Inference 14

Appendix A -

Appendix B -

References 15

Note: List of References should be written as per IEEE/Springer

reference format. (Specimen attached)
 1

CHAPTER - 1
PROJECT DESCRIPTION AND OUTLINE
1.1 INTRODUCTION:
Currently, we keep records on paper, but our student information system will be created and
put into place to replace them, through a secure and better online user interface that has been applied
properly and well.
The admin will have direct access to all aspects of a student's academic achievements,
student data, notes, and numerous student activities. The college administrator manages the cloud
servers where all the data is stored, ensuring the highest level of security.
1.2 MOTIVATION FOR THE WORK:
In the olden days, we used to have a record system to store the data (It may be from the
Schools and Colleges in the form of Pen and Paper). This kind of recommendation will be secured
for temporary purposes. Due to some natural calamities like floods or heavy rains, tsunamis,
earthquakes, and maybe some kind of man-made activities like Fire Accidents, Short Circuits, etc
will destroy the records in physical format.
To avoid these kinds of issues or problems, we will propose one new system which will store
the student’s data in a digital format. Our Student Management System will update the data in a form
of a website and the admin will have the access to add or delete the student data. The website
contains Student information, faculty details and additional information like class, marks,
attendance, sessions, terms, etc. In this way, our project is going to provide additional security for
the student data or information.
1.3 ABOUT INTRODUCTION TO THE PROJECT INCLUDING TECHNIQUES:
The technologies that are used to complete the project are:
1. Front End Development: HTML, CSS, JS
2. Back End Development: Python, Django
3. Server Side Development: SQL
1.4 PROBLEM STATEMENT:
To offer an integrated system that tracks all academic-related activity for faculties and
students, like everything as a service, for educational institutions. In general, the project concept can
be compared to the SMS or Student Management System. It functions and behaves like a tool that
gives tasks while managing and monitoring student performance and activities using their data.
Additionally, it offers grades, a marks sheet, a report card, etc
 2

1.5 OBJECTIVE OF THE PROJECT:

The main objective of this project is to manage the student data and it provides some external
activities related to the student information like class, marks, grades, attendance, etc. The
administrator is the key source for this project. Since he has all the rights to add or remove the
information from the database. So the admin will play the main role in managing the student and
faculty data secured with SHA256 encryption making it secured.
1.6 ORGANIZATION OF THE PROJECT:
We have faced some difficulties in our childhood and based on true events, we have come
forward to propose one idea on the basis of the management of the data to avoid all those mistakes
and problems for future purposes. So we decided to do a project and it helps the schools and college
management to work effectively.
1.7 SUMMARY:
Finally, from this project, we hope at least a few schools and colleges will come ahead and
update their student details and data with advanced technologies. Nowadays, most people want to
learn some good and new stuff and are willing to implement it in their day-to-day lives. With the
help of this project, there might be some chances of the data to make it as safe, and secure, also
avoiding cyber crimes like Theft, Corrupting and Manipulation of the data, etc., being decreased to a
greater and higher level. Hence, therefore this idea will bring some drastic and greater changes in the
education department and keeping or providing security of the public data or information is really
much important and crucial.
 3

CHAPTER 2
RELATED WORK INVESTIGATION
2.1 INTRODUCTION:

As we see, the Student management system consists of three parts, front-end development, back-end
development, and database management. Front-end development mostly consists of HTML and
CSS. The backend consists of Javascript and some tools to host the server like Python-Django and
RestAPI-PHP. The Database part consists of any one SQL like MySQL, PostgreSQL, SQLite, etc.

2.2 CORE IDEA OF THE PROJECT:

The core idea of this project is to provide a solution to convert paper records into paperless i.e.,
digital records. This will reduce the consumption of paper and become environmentally friendly.
Children will get aware of technology and its development.

2.3 EXISTING APPROACHES/METHODS:

There are many common existing approaches in the student management system. We have described
the three approaches/methods here.

2.3.1 EXISTING APPROACHES/METHOD 1:

In this student management system, the Back end system consists of a NODE JS server, mongoose
JS Library, and Mongo Database. Front end system as React JS and REST API to connect front end
and the back end.

2.3.2 EXISTING APPROACHES/METHOD 2:

This student management system uses HTML, CSS for Front-end and PHP for Back-end and SQL
for the database.

2.3.3 EXISTING APPROACHES/METHOD 3:

Student Management System is developed using React as frontend, Spring Boot as backend and
MySQL as Database.
 4

2.4 PROS & CONS OF THE EXISTING APPROACHES/METHODS:

Pros:

● Better Utilization of Time & Resources.

● There’s absolutely no need for maintaining files and papers.
● The system contains a simple and easy User Interface. Hence no prior knowledge and
experience are required for the Users.
● Enhanced Productivity.
● Cloud-Based SIS For Enhanced Security.
● Automatic Updates and Multiple Backups.
● Improved Inter-Relations Between Departments.
● Identifying & Improving Learning Gaps.
● Student's Personal Safety
Cons:

● User-Interface.
● Absence and Lacking Good Internet Facility.
● User’s Device or System Requirements.

2.5 ISSUES/OBSERVATION FROM METHODS:

One of the most common issues I saw is the user interface. There is no proper interface to navigate
through it. Another one is security in the data store we should have strong encryption to avoid data
theft which will lead to crimes

2.6 SUMMARY:

From the above mentioned the student management system should have a clean/fresh user interface
and a proper security measure so that we make a better student management system. This helps the
society and school/college department to come forward to take this initiative in the coming future.
 5

CHAPTER 3

REQUIREMENTS ARTIFACT

3.1 INTRODUCTION:

The student management system needs many requirements that include hardware, software and
security requirements.

3.2 HARDWARE AND SOFTWARE REQUIREMENTS:

Hardware requirements include SSD for smoothest performance, should have at least 16 GB of
RAM for memory, Input devices for data entering and output devices like a full HD monitor for
checking and reviewing the data.

Software requirements include Front end and Back end tools along with database management tools.

3.3 SPECIFIC PRODUCT REQUIREMENTS

3.3.1 DATA REQUIREMENT

We need faculty and student data to be entered and saved in the database.
3.3.2 FUNCTION REQUIREMENT
For the functioning of this project we need software and hardware requirements along with internet
connectivity with the required software installed for better function of this project.
3.3.3 PERFORMANCE AND SECURITY REQUIREMENT
To have the best performance we need a good server connected to high-speed internet. For security,
we have 256 encryption password security for the admin to avoid data theft.
3.3.4 LOOK AND FEEL REQUIREMENT
We have a clean and simple User Interface for a better experience.
3.4 SUMMARY
Student management system needs some requirements to fulfill the project to be completed. we need
to provide the requirement for better working of the project to provide its best results.
 6

CHAPTER 4

DESIGN METHODOLOGY AND ITS NOVELTY

4.1 METHODOLOGY AND GOAL:

To offer an integrated system that tracks all academic-related activity for faculties and students, like
everything as a service, for educational institutions.

4.2 FUNCTIONAL MODULES, DESIGN AND ANALYSIS:

Technologies that we used for front-end development: HTML, CSS

Technologies that we used for back-end development: JavaScript, Python, Django(framework)

Technologies that we used for server-side development: SQLite

Modules we used for this project: pip, regex, Django, db-sqlite3, pyflakes, etc.

Analysis: First, With the help of front-end tools like HTML and CSS, we created a login page for
our project. Then we used Python to develop back-end structure along with the Django framework.
SQLite database will store the students and faculty information. Finally, the admin will login and he
has the complete access to add or remove the data.

4.3 SOFTWARE ARCHITECTURAL DESIGNS:

FIG -1 Architectural flow chart

 7

4.4 SUB SYSTEM SERVICES:

In our project, we have added the students and faculty information using SQLite. The admin is the
responsible person to display the complete student data like academics, marks, grades, attendance,
etc…

In the sub system, we added some of the key modules like academics, attendance, etc.

1. Academics: In this section, we added the academic terms as terms 1,2,3, etc.
2. Attendance: Here, the attendance of a particular person will be displayed. Based on this
attendance, he or she will be eligible for exams.
3. Marks and Grades: In these sections, the student obtained marks and grades will be
calculated and shown by the administrator.
4. Payments: Here, parents are able to get the access to pay the particular student’s academic
fees. Later, the administrator will be able to show the bills.

4.5 USER INTERFACE DESIGNS:

The User Interface that we created will be very easy to access and simple to view. Here is the output
of our User Interface page.

FIG-2 Home page

 8

4.6 SUMMARY:

In this chapter, we mentioned and covered the technologies, frameworks and modules installed for
this project. Also, we discussed the sub-system designs like academics, attendance, marks and
grades, etc. There is a software architecture diagram which covers and explains the complete
workflow of the project.

CHAPTER-5

TECHNICAL IMPLEMENTATION AND ANALYSIS

5.1 OUTLINE:

We used some of the advanced technologies to gain more knowledge and attention towards the
schools and college management.

Front-End:

We used HTML (Hyper Text Markup Language) as a skeleton of our website. HTML provides the
structure to the website. Along with this HTML, we added CSS (Cascading Style Sheets) to give
some attributes like style, color, font-size, font-style, background color / image, etc.

Back-End:

Python is the key role for complete back-end development. Supporting frameworks such as Django
helped to run the server. Javascript adds the behavior or functions to the website.

Server-side:

Only one technology will help to store the data. So, here SQLite plays the most important role.
 9

5.2 TECHNICAL CODING AND CODE SOLUTIONS:

FIG-3: Home Page (base.html)

FIG-4: Main Dashboard (dashboard.js)

 10

5.3 WORKING LAYOUT OF FORMS:

Color: The color that we used for our UI (User Interface) is a combination of White and Grey and
the menu page is in white color. We provided multiple colors which can be selected by the user
itself. The colors will be changed according to the user’s wish.

FIG-5 and FIG-6 color selector of menu

Layout: The layout that we used for our project is in rectangular format. It has 2 frames. One is
having all the attributes and modules, the other is to display the final value.

Order of data items: The data is in a grouped manner and the data is arranged into the database as the
form of tables. Then the data will be arranged in those tables. This is the complete order of the data.

Data Entry: With the help of SQLite database, we can select a particular student and provide the
selected student data. Using the Django forms, the arrangement of data will be done by this
framework. The administrator will display the data using the front-end development.

Size and Arrangement: The size that we considered for this project is approx. 10 students and the
arrangement is in tabular form. With the help of rows and columns, we entered the data.
 11

5.4 PROTOTYPE SUBMISSION:

FIG-7

FIG-8
 12

5.5 TEST AND VALIDATION:

First, we have taken a raw data of students biodata and the faculty biodata as a form of tables. Then
we loaded the data into the SQLite database and it worked successfully.

Second, we connected the database to the backend using Django framework and it has given a
positive sign. Then we integrated it to the frontend as a website. It was able to display the student
and faculty information in a correct manner.

Finally, It was able to calculate the required marks for the particular student. The validation for the
marks was successful. Then, the payment validation is also successful.

5.6 PERFORMANCE ANALYSIS (GRAPHS, CHARTS):

Here is the complete performance analysis of this project.

5.7 SUMMARY:

Here, we have discussed in detail about the project, source codes, performance, layouts, color, styles
and sizes, data entry, etc.
 13

CHAPTER 6

PROJECT OUTCOME AND APPLICABILITY

6.1 OUTLINE:

The main aim of this project is to maintain and publish the complete information in a digital format
and we have successfully completed this project with the help of our team or project members. Our
aims and goals were matched exactly while working on this project.

6.2 KEY IMPLEMENTATION OUTLINE OF THE SYSTEM:

The implementation of using these advanced technologies like HTML, and CSS in the front-end of
the tour website; Python as a key programming language along with the Javascript, and Django
framework in the back-end development and finally SQLite is the database language that we used to
gather and store the data.

6.3 SIGNIFICANT PROJECT OUTCOMES:

Yes, Our significant project output is exactly the same as what we expected at the beginning. Our
main goal was to create a website that includes all the data regarding the student and the faculty.
Hence, we have successfully created or developed a full stack project that is our Student
Management System.

6.4 PROJECT APPLICABILITY ON REAL-WORLD APPLICATIONS:

Yes, we thought to share this project with the schools and colleges after making it successful.
Initially, our thought was to provide the entire information in digital form. Now, after the completion
of this project, We are feeling that our tasks were accomplished successfully. Hence, we are always
willing to share this project with any of the school and college management.

6.5 INFERENCE:

Our team got official permission to gather the relevant information from open sources like Google,
GitHub, etc. Finally, we shared our ideas with our supervisor and then we got official permission to
do the project. Our team is thanking everyone who has supported us to do this project in a successful
way.
 14

CHAPTER 7

CONCLUSIONS AND RECOMMENDATION

7.1 OUTLINE:

Hence, we are here to conclude our project. This project was designed for the sake of storing useful
information about the student and faculty in the form of a database, and then linking it with the help
of backend tools like Django and Javascript technologies. Finally, the combination of frontend and
backend along with the server-side management helps us to fulfill the dreams of this project and thus
we made this project a full-stack Student Management System.

7.2 LIMITATION/CONSTRAINTS OF THE SYSTEM:

➔ We can add only a limited number of students and faculties for this project.
➔ The Student Management System project is completely done as an offline project.
➔ There is a big obstacle that is to overcome in the connection of cloud services.
➔ Everyone will do this project either as a frontend or backend development.

7.3 FUTURE ENHANCEMENTS:

Nowadays, everyone is addicted to technology and they want everything to be done in the online
format. Half of the percentage of people are using smartphones and smart gadgets in their homes.
So, day by day, the world is becoming technically strong and everyone wants everything to become
online. Finally, we are proposing one system as a digital format which helps to remove the offline
system that is the pen and paper should be removed up to some extent. Let’s save the paper and learn
some good and advanced technologies, we will try to maintain the ecosystem in a balanced manner.

7.4 INFERENCE:

Our team got official permission to gather the relevant information from open sources like Google,
GitHub, etc. Finally, we shared our ideas with our supervisor and then we got official permission to
do the project. Our team is thanking everyone who has supported us to do this project in a successful
way. We are feeling a bit proud after completing this project successfully. Hence, our entire team is
willing to share this complete project and the codes to the schools and colleges if it is required and
we are thankful to everyone who has supported us to complete this project in a successful manner.
 15

REFERENCES

1. Liu, Zhibing, Huixia Wang, and Hui Zan. "Design and implementation of student
information management system." 2010 International symposium on intelligence
information processing and trusted computing. IEEE, 2010.

2. Bharamagoudar, S. R., R. B. Geeta, and S. G. Totad. "Web based student information

management system." International Journal of Advanced Research in Computer and
Communication Engineering 2.6 (2013): 2342-2348.

3. Weaver, Debbi, Christine Spratt, and Chenicheri Sid Nair. "Academic and student use
of a learning management system: Implications for quality." Australasian journal of
educational technology 24.1 (2008).

4. Patel, Unnati A., and S. Priya. "Development of a student attendance management

system using RFID and face recognition: a review." International Journal of Advance
Research in Computer Science and Management Studies 2.8 (2014): 109-119.

5. Natek, Srečko, and Moti Zwilling. "Student data mining solution–knowledge

management system related to higher education institutions." Expert systems with
applications 41.14 (2014): 6400-6407.