Student Management System Project with Data Analysis Tool

This project outlines the development of a student management system using HTML, CSS, Python, and MySQL. It details the system's purpose, which is to allow students to sign up, view personal details and performance, and for administrators to manage student data. The system includes features such as user authentication, data storage, and a decision-making tool developed in Python. The document covers various aspects of the system, including functional and non-functional requirements, user interfaces, hardware and software interfaces, and security considerations. It also discusses user classes, operating environment, design constraints, and assumptions. The project aims to improve student access to their information and provide administrators with tools for efficient data management. Desklib provides access to this and many other solved assignments and study tools.

Student Management System

Contents
1. Introduction..............................................................................................................................1
1.1 Purpose.......................................................................................................................................1
1.2 Document Convention................................................................................................................1
1.3 Intended Audience and Reading Suggestions.............................................................................1
1.4 Product Scope.............................................................................................................................1
2. References.................................................................................................................................1
3. Overall Description..................................................................................................................1
3.1 Product Perspective....................................................................................................................1
3.2 Product Functions.......................................................................................................................2
3.3 User Classes and Characteristics................................................................................................3
3.4 Operating Environment..............................................................................................................3
3.5 Design and Implementation Constraints.....................................................................................3
3.6 User Documentation...................................................................................................................3
3.7 Assumptions and Dependencies.................................................................................................3
4. External Interface Requirements...........................................................................................4
4.1 User Interfaces............................................................................................................................4
4.2 Hardware Interfaces....................................................................................................................4
4.3 Software Interfaces.....................................................................................................................4
4.4 Communications Interfaces........................................................................................................4
5. System Features.......................................................................................................................4
5.1 System Feature 1........................................................................................................................4
6. Other Nonfunctional Requirements.......................................................................................6
6.1 Performance Requirements.........................................................................................................6
6.2 Safety Requirements...................................................................................................................6
6.3 Security Requirements................................................................................................................7
6.4 Software Quality Attributes........................................................................................................7
6.5 Business Rules...........................................................................................................................7
7. Other Requirements................................................................................................................8
8. Conclusion.................................................................................................................................9

Page 1
1. Introduction
1.1 Purpose
In this project based on the student management system. The student sign up the page
through our website. The student signup webpage to see the student personal details and student
performance. In this webpage contains student details, student level, and student experience and
student technical knowledge (An Enhanced Text Mining Technique using Big Data for Students
Attendance Management System, 2017). We are created the webpage using both admin and student.
1.2 Document Convention
We are using html, css for webpage, And additionally creating the decision tool by using
python. The data are connected to the mysql database. The decision tool check the student database.
The backend is mysql server implement by phpmyadmin.It connected the webpage and store the
value.
1.3 Intended Audience and Reading Suggestions
The student enter their database and it read by admin.The admin read the all student
database. But the student only read our database. The student has particular register number,
username and password should be our date of birth. Every student personal details and student
performance read by admin (Celento and Tavares, 2011).
1.4 Product Scope
The student management system is developing student purpose and they are known their
level. We are additionally creating the student performance page. The students enter their username
password or register number, date of birth (LI and LUO, 2016). Then it directly connected to the
student page and it display the student datas.The information can be used to the student for future
purpose. They are improving our skills.

Page 2
2. References
An Enhanced Text Mining Technique using Big Data for Students Attendance Management
System. (2017). International Journal of Modern Trends in Engineering & Research, 4(7),
pp.236-243.
Celento, D. and Tavares, C. (2011). Students' evaluation regarding the teaching of health system
management. Online Brazilian Journal of Nursing, 10(2).
LI, L. and LUO, S. (2016). The Design and Realization of Management System for College
Students’ Innovation and Entrepreneurship Training Projects. DEStech Transactions on
Economics and Management, (iceme-ebm).
Poorahong, A. (2016). Knowledge Management: Students Development System toward Thailand
Qualification Framework for Higher Education. Journal of Advanced Management Science,
pp.356-360.
Python Algorithms: mastering basic algorithms in the Python language. (2011). Choice Reviews
Online, 48(10), pp.48-5731-48-5731.
Python Algorithms: mastering basic algorithms in the Python language. (2011). Choice Reviews
Online, 48(10), pp.48-5731-48-5731.
Wang, L. (2013). College Students Sports Qualified Standard Integrated Management System
Software Application Analysis. Information Technology Journal, 12(11), pp.2181-2187.
Yalman, M. and Ulker, U. (2017). E-Learning Management System: Students' Views about
Influence of Computer and Internet on Health. New Trends and Issues Proceedings on
Humanities and Social Sciences, 3(3), pp.193-200.
Yao, Z. and Sen, A. (2013). The Realization of Students Ranking Assessment Management
Information System. Journal of Software, 8(3).

Page 3
3. Overall Description
3.1 Product Perspective
The proposed system id developing by the python. The front end using html and css and
back end is developed by the mysql server. The front end display the student information and back
end is store the data.Additonally we creating the decision tool for student decision making process.
It developed by the python language (Celento and Tavares, 2011).
3.2 Product Functions
The student sign up the webpage using username and password. The username and
password is already created by the student. First step to sign up the page. If the username and
password is correct then the page is directly connected to the student information page. If the
username and password is incorrect then the page is discard. The database is automatically saved.
The decision tool is making the decision process for student (Poorahong, 2016).

Page 4
No
Yes
Start
Sign up the page
Usernam
e and
password
Discard
Student persona
details and
performance
Stop
Database

Page 5
3.3 Decision Tree
The decision tree based on the student performance. It has student database in tree method.

Page 6
3.4 User Classes and Characteristics
In this project the user classes are student level, student experience, student technical and
platform. The student mostly works in our school or colleges. They have some role in our
organization. So we are creating the student performance. It describes the each student quality and
their grade level. we include the student level, student role, student experience and student
platform. For example the student level is senior, junior or super senior. It depending the student
level of year. And the next one is student experience. The experience is depending the student
studying year. The platform is which role they worked (Python Algorithms: mastering basic
algorithms in the Python language, 2011). Some students are working supervisor, Leader and office
admin.Finally give the grade for their level.
3.5 Operating Environment
The system is applicable for all the operating system. We are using the window 10 operating
system and the language such as html,css and python. The html and css for developing the webpage
and python for using decision tool. The backend is mysql and it store the student personal details
and student performance database.
3.6 Design and Implementation Constraints
The student system management system maintain by the student admin.The record can be
deleted by the admin.So the admin carefully delete the record and the student are responsible for
their data constraints (Python Algorithms: mastering basic algorithms in the Python language,
2011). The data should be maintain by the admin.The student only read our record, But the data can
be add, delete and modify by the admin.The design process are the student signup their page and
give the username and password. If the username and password is correct then it directly connected
to the webpage. The total databases are maintained by the admin.
3.7 User Documentation
The software manages by the end user. It only read by the end user. In our project the end
user is student admin.The admin can read all student databases and maintain the software.

Page 7
3.8 Assumptions and Dependencies
The student signup the page using username and password. The username and password
must be created the user administrators. They are communicated to the student and they maintain
their database. The user must be avoiding the unauthorized access to the system. The database only
maintains by the admin.The student level and grade change by their performance. The student
register the page and it will only specific person and specific duration (Wang, 2013).
4. External Interface Requirements
4.1 User Interfaces
Sign up:The student sign up the page using the username and password. The student
already register the page and give the details for sign up the page. So the username and password
create the every student (Yalman and Ulker, 2017).
Student Personal details: The student personal details contains the firstaname, lastname,
age, gender,email id,date of birth and mobile number. The details display the student personal page.
Student performance details: It contains the student name, student level, experience, and
platform student grade.
4.2 Hardware Interfaces
It supports the all printers and it modify the all then document type. It is multi user system.
They are more than student using the system. It will be networked environment.
4.3 Software Interfaces
 MS window operating system.
 Html and css using front end.
 Mysql server 2000 for back end
 Python 3.6 for decision tool.
4.4 Communications Interfaces
It is depending netwok.It communicate with that page or their email or gmail.

Page 8
5. System Features
The system requirements divided to the two type.The type of requirements are functional
requirements and non functional requriments.The functional requirements is defined the functional
engineering and it specify the results of a system and it is describe the behavior between inputs and
outputs. Non functional requirement is judge the operation of the system and specify the criteria.
5.1 System Feature
4.1.1 Description and Priority
The student priority depending the student level, performance and grade. It has low priority,
high priority and medium priority. Low priority means is give opportunity is low level. Medium
priority means between the high and low level prority.High level priority is the student has more
opportunity to develop their skills.
4.1.2 Stimulus/Response Sequences
S.No User stimulus Software response
1 Admin sign up using username and password The software check the
username and password valid
or not.
2 Admin choose student level The software display the
student performance.
3 Admin add the student The software add the student
by valid username and
password.
4 Username and password correct The software directly
connected to the student
personal details and student
performance.
5 Username and password is incorrect The software id discards the
page.
6 Admin delete the student database The software delete the
database in valid userid
7 Admin modify the student database The software modify the
particular student database if
valid username and password
8 Admin ad the new faculty The software also add the

Page 9
faculty
9 Logout the page The software logout the
page.
4.1.3 Functional Requirements
Use case description: The user sign up the page using the username and password.
Actors:
 Admin
 Student
Pre conditions: The student signup the page must be valid username and password.
Post conditions: If the username and password correct then it display the student personal
details and student performance details otherwise it will be discard.
6. Other Nonfunctional Requirements
The non functional requirements means that specify the criteria to judge the operation of the
system. In the student management system has the non functional requirement. It divided the
performance requritemnts, safety requirements, security requritments, software quality attributes
and so on (Yao and Sen, 2013).
6.1 Performance Requirements
It based on the performance. The requirements using display the student performance. It
commonly contains the platform, response time, workload and scalabilty.The response time is
depending the student. They are complete their work in particular time. The student work with
particular domain. The student has the platform to work.

Page 10
6.2 Safety Requirements
The safety requirements are implement the system to achieve the safety integrity. We using
the webpage is safely. The student database maintain by the admin.The admin can be delete, add
and modify the student database. So the admin should be maintain the carefully. The admin must be
delete the record is carefully and the student response for current data.
6.3 Security Requirements
It using to observe and testing. It describes the functional behavior and that forces security.
The password must have the password. The password known the particular student. The student has
username and password. The password is different from each student. The password may be the
date of birth of the student. So the date of birth differ from one student to another student.
6.4 Software Quality Attributes
The software quality attributes are portability, correctness, realability, maintainability,
useability, integrity, testability and efficiency. Portability can be measured by the student using the
webpage. The correctness can be measured by the calculation and navigation class. And also
calculate the student efficiency of this student management system. The student management
system is fully maintained by the student performance.
6.5 Business Rules
It is rule either the process true or false. The business rule can be apply the student, people,
behavior and process. It is mostly applicable for the business organizations.

Page 11
7. Other Requirements
Appendix A: Glossary
HTML – Hyper test markup language
CSS- Cascade style sheet
OS-Operating System
Appendix B: Analysis Models
Admin
Username
Password
Student Database
Student
Username
Password
Sign up
Student
database
Database
Student personal details
Student performance
details
Database
MySQL

Page 12
The admin enter the username and password to read student database. The student using the
username and password for signup the webpage. If the student username and password is correct
then it directly opens the student page. It include such as student personal details and student
performance details. The personal details contain the student first name, lastname, age, gender,
email id, mobile no and date of birth. The student performance details contain the student level,
experience, technical knowledge, grade level and experience.Evey student has work with particular
domain. They are separated in their experience and grade level. In the student grade level is differ
from one student to another student. The database stores the mysql database. The admin can be
deleting, add and modify the student records. The admin delete the record is carefully. The student
is response for our database. The decision tool using for student. It developed by the python.
Appendix C: To Be Determined List
 Username should be valid and begin with any letter
 Password should contain one capital letter
 Password should be contain one small letter
 Password should be one number
 Password should be one special character
 Password should be contains 6 characters.
8. Conclusion
The student management system contains student personal details and student performance.
The admin maintain the database. The student sign up the page using username and password. If the
username is valid then it directly connected to the student database page. If the username and
password is incorrect then the page is discarding. The admin can be add the student, delete and also
modify. The student database can be store by the mysql server. The decision tool using by the

Page 13
python. The decision tool creating for student. In this project to using develop the student skills and
database maintain by admin