Visvesvaraya Technology University: Jnana Sangama, Belagavi-590018, Karnataka

VISVESVARAYA TECHNOLOGY UNIVERSITY
JNANA SANGAMA, BELAGAVI-590018, KARNATAKA
Mini Project Report

on
“STUDENT MANAGEMENT SYSTEM”

A Mini Project Report Submitted in partial fulfilment of the requirements for the Degree of
BACHELOR OF ENGINEERING
In
COMPUTER SCIENCE AND ENGINEERING
Submitted By
HARSHITH B R [1JV21CS018]
HRUTHWICK RAO KADAM S [1JV21CS021]
Under the Guidance of

Mrs. Nirmala V N
Assistant Professor
Dept. of Computer Science and Engineering
JVIT, Bidadi – 562109
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

JNANA VIKAS INSTITUTE OF TECHNOLOGY
Vidya Soudha, Padmashree G.D. Goyalgi Campus, Bangalore-Mysore Highway
BIDADI, BANGALORE – 562109.
JNANA VIKAS INSTITUTE OF TECHNOLOGY
BIDADI- 562109
(Affiliated to Visvesvaraya Technological University, Belagavi, Approved by AICTE, New Delhi)
CERTIFICATE
Certified that the Mini Project work entitled “STUDENT MANAGEMENT SYSTEM”
carried out by HARSHITH B R [1JV21CS018], HRUTHWICK RAO KADAM S
[1JV21CS021] are bonafide students of Jnana Vikas Institute of Technology in partial
fulfilment for the award of the degree of Bachelor of Engineering in Computer Science
and Engineering of the Visvesvaraya Technological University, Belagavi during the
year 2023-24. It is certified that all corrections/suggestions indicated for Internal
Assessment have been incorporated in the report deposited in the department library. The
mini project report has been approved as it satisfies the academic requirement in respect
of project work prescribed for the said degree.
Mrs. NIRMALA V N Mrs. NIVEDITHA S Dr. AV SEETHA GIRISHA

Assistant Professor HOD & Assistant Professor Principal
Department of CSE Department of CSE JVIT, Bidadi
JVIT, Bidadi JVIT, Bidadi
Name of the Examiners Signature with Date
1. ___________________ _____________________
2. ___________________ _____________________
JNANAVIKAS INSTITUTE OF TECHNOLOGY
BIDADI-562109
DECLARATION
We HARSHITH B R [1JV21CS018] and HRUTHWICK RAO KADAM S

[1JV21CS021] students of 5th semester B.E in Computer Science And Engineering,
Jnana Vikas Institute of Technology, Bidadi, hereby declare that the mini-project work
entitled “STUDENT MANAGEMENT SYSTEM” has been carried out by us and
submitted in partial fulfilment of the course requirements for the award of degree of
Bachelor of Engineering, from Visvesvaraya Technological University during 2023-2024
is a record of an original work done by us under the guidance of NIRMALA V N, Assistant
Professor in Department of Computer Science and Engineering, JVIT, Bidadi. The results
embodied in this work has not submitted to any other University or Institute for the award
of any degree.
HARSHITH B R
USN: 1JV21CS018
Department of Computer Science and Engineering,
Jnana Vikas Institute of Technology
Bengaluru-562109 Signature of the Student
HRUTHWICK RAO KADAM S

USN: 1JV21CS021
Department of Computer Science and Engineering,
Jnana Vikas Institute of Technology,
Bengaluru-562109 Signature of the Student
ACKNOWLEDGEMENT
A Project work is a job of great enormity and it cannot accomplish by an individual

all by them. Eventually We are grateful to a number of individuals whose professional
guidance, assistance and encouragement have made it a pleasant endeavour to undertake this
seminar work.
We have great pleasure in expressing my deep sense of gratitude to founder Sir

C.M Lingappa, Chairman for having provided us with a great infrastructure and well-
furnished labs.
We take this opportunity to express my profound gratitude to Dr. A V SEETHA

GIRISHA, Principal for his constant support and encouragement.
We would like to express my heart full thanks to NIVEDITHA S, Head of the

Department, Computer Science and Engineering who has guided me in all aspects.
We would like to extend my thanks to my guide NIRMALA V N, who has guided

me in all aspects. I am grateful for his unfailing encouragement and suggestion, given to
me in course of my project works.
We would like to mention special thanks to all my Teaching Faculties of

Department of Computer Science and Engineering, JVIT, Bidadi for their valuable
support and guidance.
We would like to thank to my Family and Friends for their unforgettable support
and encouragement.
HARSHITH B R [1JV21CS018]
HRUTHWICK RAO KADAM S [1JV21CS021]
i
ABSTRACT
Our project explains about the student management. This project mainly explains the
various actions related to student details. This project shows some easy way of adding, editing
and deleting the student details. Student Management System is software which is helpful for
students as well as the school authorities. In the current system all the activities are done
manually. Its time saving and scalable. Our project deals with the various activities related to
the students. In this project we can register as a user and the user had the power to add
students record, attendance status with department wise. All students can search his/her basics
details and attendance status with their respective roll numbers.
ii
TABLE OF CONTENTS
DETAILS Page No.

ACKNOWLEDGEMENT i
ABSTRACT ii
TABLE OF CONTENTS iii
LIST OF FIGURES iv
Chapter 1 INTRODUCTION 1
1.1 Introduction 1
1.2 Objectives 1
Chapter 2 SYSTEM ANALYSIS 2

2.1 Existing System 2
2.2 Proposed System 3
2.3 Feasibility Analysis 4
Chapter 3 SYSTEM REQUIREMENTS SPECIFICATION 5

3.1 Hardware Requirements 5
3.2 Software Requirements 5
Chapter 4 SYSTEM DESIGN 6

4.1 Introduction 6
4.2 Conceptual Design 6
4.2.1 ER Diagram 7
4.2.2 Schema Diagram 8
4.3 Table Description 9
4.3 Logical Design 10
Chapter 5 SOURCE CODE 11

5.1 Backend Python with MySQL Code 11
Chapter 6 SNAPSHOTS 19
6.9 Database Localhost 23
Chapter 7 CONCLUSION 24
BIBILOGRAPHY 25
iii
LIST OF FIGURES
Figure No. Name of the Figure Page No.
6.1 Home Page 19

6.2 Login Page 19
6.3 Add Student Information 20
6.4 Add Attendance Details 20
6.5 Add Department 21
6.6 Student Details 21
6.7 Search Student Details 22
6.8 Trigger Records 22
6.9.1 Structure Of Database 23
6.9.2 Users 23
iv
Student Management System 2023-24
CHAPTER 1
INTRODUCTION
1.1 INTRODUCTION
Student Management System is software which is helpful for students 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 the students.
The user interface of this web application is thoughtfully crafted to provide intuitive
functionalities for various stakeholders within the educational ecosystem. Administrators gain
access to powerful tools for managing student enrolment, generating reports, overseeing
curriculum details, and supervising overall system functionalities. Teachers benefit from
features allowing them to track attendance, input grades, manage course materials, and
communicate with students. Simultaneously, students have access to their academic records,
course schedules, grades, and communication tools, empowering them to stay informed and
engaged in their educational journey.
1.2 OBJECTIVES
➢ The main objective of the project is to design and develop a user friendly-system.
➢ Easy to use and an efficient computerized system.
➢ To develop an accurate and flexible system, it will eliminate data redundancy.
➢ To study the functioning of Students management System.
➢ To make a software fast in processing, with good user interface.
➢ Less chances of information leakage.
➢ To make software with good user interface so that user can change it and it should be
used for a long time without error and maintenance.
➢ Provides Security to the data by using login and password method.
➢ To provide immediate storage and retrieval of data and information.
➢ Reducing paperwork.
Dept. of CSE, Bidadi Page 1

CHAPTER 2
SYSTEM ANALYSIS
2.1 EXISTING SYSTEM
System Analysis is a detailed study of the various operations performed by a system and
their relationships within and outside of the system. Here the key question is- what all
problems exist in the present system? What must be done to solve the problem? Analysis
begins when a user or manager begins a study of the program using existing system.
During analysis, data collected on the various files, decision points and transactions
handled by the present system. The commonly used tools in the system are Data Flow
Diagram, interviews, etc. Training, experience and common sense are required for collection
of relevant information needed to develop the system. The success of the system depends
largely on how clearly the problem is defined, thoroughly investigated and properly carried
out through the choice of solution. A good analysis model should provide not only the
mechanisms of problem understanding but also the frame work of the solution. Thus, it should
be studied thoroughly by collecting data about the system. Then the proposed system should
be analyzed thoroughly in accordance with the needs.
System analysis can be categorized into four parts:
➢ System planning and initial investigation
➢ Information Gathering
➢ Applying analysis tools for structured analysis
➢ Feasibility study
➢ Cost/ Benefit analysis
In the current system we need to keep a number of records related to the student and
want to enter the details of the student and the marks manually. In this system only the teacher
or the school authority views the mark of the student and they want to enter the details of the
student. This is time consuming and has much cost.

2.2 PROPOSED SYSTEM
While there has been no consensus on the definition of Students Management in the
literature, they have proposed that researchers adopt the below definition to allow for the
coherent development of theory in the colleges. In order to have a successful students
management, we need to make many decisions related to the flow of marks, attendance, and
data. Each record should be added in a way to increase the scalability. Student management is
more complex in colleges and other universities because of the impact on people’s number
requiring adequate and accurate information of students need.
In our proposed system we have the provision for adding the details of the students by
themselves. So, the overhead of the school authorities and the teachers is become less.
Another advantage of the system is that it is very easy to edit the details of the student and
delete a student when it found unnecessary. The marks of the student are added in the
database and so students can also view the marks whenever they want.
Our proposed system has several advantages:
➢ User friendly interface
➢ Fast access to database
➢ Less error
➢ More Storage Capacity
➢ Search facility
➢ Look and Feel Environment
➢ Quick transaction
All the manual difficulties in managing the student details in a school or college have
been rectified by implementing computerization.

2.3 FEASIBILITY ANALYSIS
Whatever we think need not be feasible. It is wise to think about the feasibility of any
problem we undertake. Feasibility is the study of impact, which happens in the organization
by the development of a system. The impact can be either positive or negative. When the
positives nominate the negatives, then the system is considered feasible. Here the feasibility
study can be performed in two ways such as technical feasibility and Economical Feasibility.
➢ Technical Feasibility:
We can strongly say that it is technically feasible, since there will not be much difficulty
in getting required resources for the development and maintaining the system as well. All the
resources needed for the development of the software as well as the maintenance of the same
is available in the organization here we are utilizing the resources which are available already.
➢ Economic Feasibility:
Development of this application is highly economically feasible. The organization

needed not spend much money for the development of the system already available. The only
thing is to be done is making an environment for the development with an effective
supervision. If we are doing so, we can attain the maximum usability of the corresponding
resources. Even after the development, the organization will not be in condition to invest
more in the organization. Therefore, the system is economically feasible.

CHAPTER 3
SYSTEM REQUIREMENTS SPECIFICATION
3.1 HARDWARE REQUIREMENTS
➢ Computer with a 1.1 GHz or faster processor
➢ Minimum 2GB of RAM or more
➢ 2.5 GB of available hard-disk space
➢ 5400 RPM hard drive
➢ 1366 × 768 or higher-resolution display
➢ DVD-ROM drive
3.2 SOFTWARE REQUIREMENTS
Frontend - HTML, CSS, Java Script, Bootstrap

Backend - Python flask (Python 3.7), SQL Alchemy
➢ Operating System: Windows 10
➢ Google Chrome/Internet Explorer
➢ XAMPP (Version-3.7)
➢ Python main editor (user interface): VS Code
➢ Workspace editor: VS Code

CHAPTER 4
SYSTEM DESIGN
4.1 INTRODUCTION
System design is a process through which requirements are translated into a

representation of software. Initially the representation depicts a holistic view of software.
Subsequent refinement leads to a design representation that is very close to source code.
Design is a place where quality fostered in software development. Design provides us with
representation of software that can be assessed for quality; this is the only way that can
accurately translate the customer requirements into finished software product or system.
System design serves as the foundation for all software engineering and software maintenance
steps that follow.
We look the design process from three distinct perspectives:
➢ Conceptual Design
➢ Logical Design
The higher view is the conceptual view, followed by the logical view and finally the
physical view. In designing an application, we generally begin and end each phase in a
sequentially order, although they may overlap one another along the way.
4.2 CONCEPTUAL DESIGN
Conceptual Design is the process of acquiring and evaluating, documenting and then
validating what the user envisions to be the business relation. It identifies the user and
business requirements of the application and leads to a business solution as seen by the user.
All applications are built to solve business problems, and it is important to pay close
attention to principle that the business need drives application development. At any point in
the design process, the current state of the design should be directly traceable to a business
problem and requirements.
To achieve this conceptual design is driven by developing usage scenarios. These

scenarios are a direct representation of the user’s view of the solution to a specific business
problem. A conceptual view places the emphasize on solving a business problem and deriving
a solution that corresponds to the needs and requirements of the users.

4.2.1 E-R DIAGRAM
The Entity Relational Model is a model for identifying entities to be represented in the
database and representation of how those entities are related. The ER data model specifies
enterprise schema that represents the overall logical structure of a database graphically.
The Entity Relationship Diagram explains the relationship among the entities present
in the database. ER models are used to model real-world objects like a person, a car, or a
company and the relation between these real-world objects. In short, the ER Diagram is the
structural format of the database.

4.2.2 SCHEMA DIAGRAM
➢ A database schema is a logical representation of data that shows how the data in a
database should be stored logically. It shows how the data is organized and the
relationship between the tables.
➢ Database schema contains table, field, views and relation between different keys
like primary key, foreign key.
➢ Data are stored in the form of files which is unstructured in nature which makes
accessing the data difficult. Thus, to resolve the issue the data are organized in
structured way with the help of database schema.
➢ Database schema provides the organization of data and the relationship between the
stored data.
➢ Database schema defines a set of guidelines that control the database along with that it
provides information about the way of accessing and modifying the data.

4.3 TABLE DESCRIPTION
Table Name: Student

Field Name Data Type Size
Id Number 2
Roll_no Varchar 12
S_name Varchar 20
Sem Number 1
Gender Char 1
Branch Varchar 20
Email Varchar 20
S_num Number 10
P_num Number 10
Address Varchar 40
Table Name: Attendance

Id Number 2
Roll_no Varchar 12
Attend1 Number 3
Attend2 Number 3
Attend3 Number 3
Attend4 Number 3
Table Name: Department

D_id Number 2
Branch Varchar 20

Table Name: Users

Id Number 2
User_name Varchar 20
Email Varchar 20
Password Varchar 20
Table Name: Triggers

T_id Number 2
Roll_no Varchar 16
Action Varchar 16
Timestamp Date
4.4 LOGICAL DESIGN
Logical Design derives business objects and their related services directly from these
usage scenarios. The logical view of the solution provides a basis for evaluating different
physical options. It also formalizes the solution for the project team.
The idea of the application is that the system first emerges in logical design. Its
boundaries and business objects and it contain the system definition. Logical design specifies
the interfaces between the system and external entities, such as users and other systems.
Within a system there may be a number of sub-systems, and these boundaries are also
specified.
Logical System Design consists of the following steps:
➢ Input/Output Specifications
➢ File Specifications
➢ Processing Specifications
Logical design should be technologically independent as possible, in order to separate

system behavior issues from system implementation issues. Implementation constraints
should only be considered only after the project team verifies that the essential behavior has
been incorporated onto a logical design. This approach does not establish a technical direction
until the system is well understood and documented.

CHAPTER 5
SOURCE CODE
5.1 BACKEND PYHTON WITH MYSQL CODE
from flask import Flask, render_template, request,session,redirect,url_for,flash

from flask_sqlalchemy import SQLAlchemy
from flask_login import UserMixin
from werkzeug.security import generate_password_hash,check_password_hash
from flask_login import login_user, logout_user,login_manager,LoginManager
from flask_login import login_required, current_user
import json
# MY db connection
local_server= True
app = Flask(__name__)
app.secret_key='myproject'
# This is for getting unique user access

login_manager=LoginManager(app)
login_manager.login_view='login'
@login_manager.user_loader
def load_user(user_id):
return User.query.get(int(user_id))
app.config['SQLALCHEMY_DATABASE_URL']='mysql://username:password@localhost/
database_table_ name'
app.config['SQLALCHEMY_DATABASE_URI'] ='mysql://root:@localhost/students'
db=SQLAlchemy(app)
# Here we will create db models that is tables

class Test(db.Model):
id=db.Column(db.Integer,primary_key=True)
name=db.Column(db.String(100))
email=db.Column(db.String(100))

class Department(db.Model):
cid=db.Column(db.Integer,primary_key=True)
branch=db.Column(db.String(100))
class Attendence(db.Model):
id = db.Column(db.Integer, primary_key=True)
rollno = db.Column(db.String(20), nullable=False)
attend1 = db.Column(db.Integer)
class Trig(db.Model):
tid=db.Column(db.Integer,primary_key=True)
rollno=db.Column(db.String(100))
action=db.Column(db.String(100))
timestamp=db.Column(db.String(100))
class User (UserMixin,db.Model):

username=db.Column(db.String(50))
email=db.Column(db.String(50),unique=True)
password=db.Column(db.String(1000))
class Student(db.Model):
rollno=db.Column(db.String(50))
sname=db.Column(db.String(50))
sem=db.Column(db.Integer)
gender=db.Column(db.String(50))
branch=db.Column(db.String(50))
email=db.Column(db.String(50))
number=db.Column(db.String(12))
number1=db.Column(db.String(12))
address=db.Column(db.String(100))

@app.route('/')
def index():
return render_template('index.html')
@app.route('/studentdetails')
@login_required
def studentdetails():
# query=db.engine.execute(f"SELECT * FROM `student`")
query=Student.query.all()
return render_template('studentdetails.html',query=query)
@app.route('/triggers')
@login_required
def triggers():
# query=db.engine.execute(f"SELECT * FROM `trig`")
query=Trig.query.all()
return render_template('triggers.html',query=query)
@app.route('/department',methods=['POST','GET'])
@login_required
def department():
if request.method=="POST":
dept=request.form.get('dept')
query=Department.query.filter_by(branch=dept).first()
if query:
flash("Department Already Exist","warning")
return redirect('/department')
dep=Department(branch=dept)
db.session.add(dep)
db.session.commit()
flash("Department Added","success")
return render_template('department.html')

@app.route('/addattendance',methods=['POST','GET'])
@login_required
def addattendance():
query = Student.query.all()
if request.method == "POST":
rollno = request.form.get('rollno')
attend1 = request.form.get('attend1')
print(attend1,attend2,attend3,attend4, rollno)
atte=Attendence(rollno=rollno,attend1=attend1,attend2=attend2,attend3=attend3,attend4=atte
nd4)
db.session.add(atte)
db.session.commit()
flash("Attendance Added Successfully", "warning")
return render_template('attendance.html', query=query)
@app.route('/search',methods=['POST','GET'])
@login_required
def search():
rollno = request.form.get('roll')
bio = Student.query.filter_by(rollno=rollno).first()
# Assuming your Attendance model has an 'attendances' attribute to store multiple values
attend1 = Attendence.query.filter_by(rollno=rollno).first()
return render_template('search.html ',bio=bio,attend1=attend1,attend2=attend2,

attend3=attend3, attend4=attend4)
return render_template('search.html')

@app.route("/delete/<string:id>",methods=['POST','GET'])
@login_required
def delete(id):
post=Student.query.filter_by(id=id).first()
db.session.delete(post)
db.session.commit()
# db.engine.execute(f"DELETE FROM `student` WHERE `student`.`id`={id}")
flash("Slot Deleted Successful","danger")
return redirect('/studentdetails')
@app.route("/edit/<string:id>",methods=['POST','GET'])
@login_required
def edit(id):
# dept=db.engine.execute("SELECT * FROM `department`")
rollno=request.form.get('rollno')
sname=request.form.get('sname')
sem=request.form.get('sem')
gender=request.form.get('gender')
branch=request.form.get('branch')
email=request.form.get('email')
num=request.form.get('num')
num1=request.form.get('num1')
address=request.form.get('address')
post=Student.query.filter_by(id=id).first()
post.rollno=rollno
post.sname=sname
post.sem=sem
post.gender=gender
post.branch=branch
post.email=email
post.number=num
post.number1=num1
post.address=address

db.session.commit()
flash("Slot is Updated","success")
return redirect('/studentdetails')
dept=Department.query.all()
posts=Student.query.filter_by(id=id).first()
return render_template('edit.html',posts=posts,dept=dept)
@app.route('/signup',methods=['POST','GET'])
def signup():
username=request.form.get('username')
password=request.form.get('password')
user=User.query.filter_by(email=email).first()
if user:
flash("Email Already Exist","warning")
return render_template('/signup.html')
encpassword=generate_password_hash(password)
newuser=User(username=username,email=email,password=encpassword)
db.session.add(newuser)
db.session.commit()
flash("Signup Succes Please Login","success")
return render_template('login.html')
return render_template('signup.html')
@app.route('/login',methods=['POST','GET'])
def login():
password=request.form.get('password')
user=User.query.filter_by(email=email).first()
if user and check_password_hash(user.password,password):
login_user(user)

return redirect(url_for('index'))
else:
flash("invalid credentials","danger")
@app.route('/logout')
@login_required
def logout():
logout_user()
flash("Logout SuccessFul","warning")
return redirect(url_for('login'))
@app.route('/addstudent',methods=['POST','GET'])
@login_required
def addstudent():
# dept=db.engine.execute("SELECT * FROM `department`")
dept=Department.query.all()
rollno=request.form.get('rollno')
sname=request.form.get('sname')
sem=request.form.get('sem')
gender=request.form.get('gender')
branch=request.form.get('branch')
num=request.form.get('num')
num1=request.form.get('num1')
address=request.form.get('address')
query=Student(rollno=rollno,sname=sname,sem=sem,gender=gender,
branch=branch, email=email,number=num,number1=num1,address=address)
db.session.add(query)
db.session.commit()

flash("Details Added Successfully","info")

return render_template('student.html',dept=dept)
@app.route('/test')
def test():
try:
Test.query.all()
return 'My database is Connected'
except:
return 'My db is not Connected'
app.run(debug=True)

CHAPTER 6
SNAP SHOTS
Fig 6.1: Home Page
Fig 6.2: Login Page

Fig 6.3: ADD STUDENT INFORMATION
Fig 6.4: ADD ATTENDANCE DETAILS

Fig 6.5: ADD DEPARTMENT
Fig 6.6: STUDENT DETAILS

Fig 6.7: SEARCH STUDENT DETAILS
Fig 6.8: TRIGGER RECORDS

6.9 DATABASE LOCALHOST
Fig 6.9.1: STRUCTURE OF DATABASE
Fig 6.9.2: USERS

CHAPTER 7
CONCLUSION
Our project Student Management System is only a humble venture to satisfy the needs
in an Institution. Several user-friendly coding has also adopted. This package shall prove to be
a powerful package in satisfying all the requirements of the organization
The project successfully implemented based on online data filling which helps us in
administrating the data user for managing the tasks performed in students. The project
successfully used various functionalities of Xampp and python flask and also create the fully
functional database management system for online portals. Using MySQL as the database is
highly beneficial as it is free to download, popular and can be easily customized. The data
stored in the MySQL database can easily be retrieved and manipulated according to the
requirements with basic knowledge of SQL.
With the theoretical inclination of our syllabus, it becomes very essential to take the at
most advantage of any opportunity of gaining practical experience that comes along. The
building blocks of this major project “Students Management System” was one of these
opportunities. It gave us the requisite practical knowledge to supplement the already taught
theoretical concepts thus making us more competent as a computer science student. The
project from a personal point of view also helped us in understanding the following aspects of
project development:
➢ The planning that goes into implementing a project.
➢ The importance of proper planning and an organized methodology.

BIBILOGRAPHY
[1] Database Systems: Design, Implementation, and Management by Carlos Coronel,

Steven Morris, and Peter Rob.
[2] Web Development on platforms like Coursera, Udemy, or edX, which cover topics like
database management, backend development, and frontend development.
[3] Software Engineering courses focusing on system design and architecture.
[4] Medium articles and blog posts on topics like Building a Student Management System
with Django or Creating a Student Management System with Flask and SQLAlchemy.
[5] YouTube tutorials covering step-by-step development processes for building student
management systems.
[6] Search academic databases like Google Scholar or IEEE Xplore for research papers
related to student management systems, educational technology, or database design.
[7] Papers might cover topics such as user requirements analysis, system architecture,
security considerations, and usability studies.

Visvesvaraya Technology University: Jnana Sangama, Belagavi-590018, Karnataka

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Visvesvaraya Technology University: Jnana Sangama, Belagavi-590018, Karnataka

Uploaded by

Copyright:

Available Formats

VISVESVARAYA TECHNOLOGY UNIVERSITY

JNANA SANGAMA, BELAGAVI-590018, KARNATAKA

Mini Project Report

“STUDENT MANAGEMENT SYSTEM”

Under the Guidance of

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

Mrs. NIRMALA V N Mrs. NIVEDITHA S Dr. AV SEETHA GIRISHA

Name of the Examiners Signature with Date

We HARSHITH B R [1JV21CS018] and HRUTHWICK RAO KADAM S

HRUTHWICK RAO KADAM S

A Project work is a job of great enormity and it cannot accomplish by an individual

We have great pleasure in expressing my deep sense of gratitude to founder Sir

We take this opportunity to express my profound gratitude to Dr. A V SEETHA

We would like to express my heart full thanks to NIVEDITHA S, Head of the

We would like to extend my thanks to my guide NIRMALA V N, who has guided

We would like to mention special thanks to all my Teaching Faculties of

DETAILS Page No.

Chapter 2 SYSTEM ANALYSIS 2

Chapter 3 SYSTEM REQUIREMENTS SPECIFICATION 5

Chapter 4 SYSTEM DESIGN 6

Chapter 5 SOURCE CODE 11

Figure No. Name of the Figure Page No.

6.1 Home Page 19

➢ Easy to use and an efficient computerized system.

➢ To develop an accurate and flexible system, it will eliminate data redundancy.

➢ To study the functioning of Students management System.

➢ To make a software fast in processing, with good user interface.

➢ Less chances of information leakage.

➢ Provides Security to the data by using login and password method.

➢ To provide immediate storage and retrieval of data and information.

Dept. of CSE, Bidadi Page 1

System analysis can be categorized into four parts:

➢ System planning and initial investigation

➢ Applying analysis tools for structured analysis

➢ Cost/ Benefit analysis

Dept. of CSE, Bidadi Page 2

2.2 PROPOSED SYSTEM

Our proposed system has several advantages:

➢ User friendly interface

➢ Fast access to database

➢ More Storage Capacity

➢ Look and Feel Environment

Dept. of CSE, Bidadi Page 3

2.3 FEASIBILITY ANALYSIS

Development of this application is highly economically feasible. The organization

Dept. of CSE, Bidadi Page 4

3.1 HARDWARE REQUIREMENTS

➢ Computer with a 1.1 GHz or faster processor

➢ Minimum 2GB of RAM or more

➢ 2.5 GB of available hard-disk space

➢ 5400 RPM hard drive

➢ 1366 × 768 or higher-resolution display

3.2 SOFTWARE REQUIREMENTS

Frontend - HTML, CSS, Java Script, Bootstrap

➢ Operating System: Windows 10

➢ Google Chrome/Internet Explorer

➢ Python main editor (user interface): VS Code

➢ Workspace editor: VS Code

Dept. of CSE, Bidadi Page 5

System design is a process through which requirements are translated into a

We look the design process from three distinct perspectives:

4.2 CONCEPTUAL DESIGN