STUDENT MANAGEMENT SYSTEM

A Project Report
Submitted in partial fulfillment of the
Requirements for the award of the Degree of

BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)

By

Shrikant Pandurang Shinde

Seat No :

Under the esteemed guidance of

Prof. Bhavesh Gawde
Assistant Professor

DEPARTMENT OF INFORMATION TECHNOLOGY

D.G. Tatkare Mahavidyalay
(Affiliated to University of Mumbai)
MANGAON-RAIGAD 402104
MAHARASHTRA
 2024-25
PROJECT PROPOSAL

PRN No.: __________________ ROLL NO: _______________

1. Name of the Student:

_________________________________

2. Title of the Project:

___________________________________________________________

3. Name of the Guide:

_________________________________________________________

4 Teaching experience of the Guide: ______________________

5 Is this your first submission? Yes No

Signature of the Student Signature of the Guide

Date: _______________ Date: _____________

Signature of the Coordinator

Date: _________________
 D.G. Tatkare Mahavidyalay
(Affiliated to University of Mumbai)
MANGAON-RAIGAD-MAHARASHTRA 402104

DEPARTMENT OF INFORMATION TECHNOLOGY

CERTIFICATE

This is to certify that the project entitled, "Student Management System", is bonafied
work of Shrikant Pandurang Shinde bearing Seat. No: submitted in partial fulfillment of
the requirements for the award of degree of BACHELOR OF SCIENCE in INFORMATION
TECHNOLOGY from University of Mumbai.

Prof . Bhavesh Gawde

Internal Guide Coordinator

External Examiner

Date: College Seal

 ABSTRACT
The main objective of this project is to build a student database system that will store records of
students. It is purposed to reduce time spent on administrative tasks. The system is intended to accept
process, generate students. The system is also intended to provide better services to users, provide
meaningful, consistent, and timely data and information and finally promotes efficiency by
converting paper processes to electronic form. The system was developed using basic technologies
such as MySQL database and PHP. The system is free of errors and very efficient and less time
consuming due to the care taken to develop it. All the phases of software development cycle are
employed and it is worthwhile to state that the system is user friendly and strong. Provision is made
for future development in the system.
 ACKNOWLEDGEMENT

I would like to take this opportunity to express my gratitude towards all the people who
have in various ways, helped in the successful completion of my project.

I must convey my gratitude to Prof. Bhavesh Gawde for giving me the constant source of
inspiration and help in preparing the project, personally correcting my work and providing
encouragement throughout the project.

I also thank my HOD Mr. Bhanuprasad Vishwakarma for guiding and giving his
valuable time for project development.

I also thank all my faculty members for steering me through the tough as well as easy
phases of the project in a result oriented manner with concern attention.

Last but not least I am great full to my family and friends for their co-operation in every
possible way towards the fulfilment of the project.
 DECLARATION

I hereby declare that the project entitled, “STUDENT MANAGEMENT SYSTEM” done at
Mangaon, has not been in any case duplicated to submit to any other university for the award of any
degree. To the best of my knowledge other than me, no one has submitted to any other university.
The project is done in partial fulfillment of the requirements for the award of degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY) to be submitted as final
semester project as part of our curriculum.

Shrikant Pandurang Shinde

 TABLE OF CONTENTS

CHAPTER TITLE Page No.

1-6
CHAPTER 1 INTRODUCTION
1.1 General 1

1.2 Project Objectives 1-3

1.3 Purpose, Scope, and Applicability 3 -5
1.3.1 Purpose 3
1.3.2 Scope 3-4
1.3.3 Applicability 5
1.4 Achievements 5
1.5 Advantages Disadvantages and Applications 6

7-9
CHAPTER 2 SURVEY OF TECHNOLOGIES

CHAPTER 3 REQUIREMENTS AND ANALYSIS 10-20

3.1 Problem Definition 10 - 11

3.2 Requirements Specification 12 - 13
3.3 Planning and Scheduling 14 -15
3.4 Software and Hardware Requirements 16 - 18
3.5 Preliminary Project Description 19 - 20

CHAPTER 4 SYSTEM DESIGN

4.1 Basic Modules 21 -22
4.2 Data Integrity and Constraints 24 - 26
4.3 Procedural Design 25
4.4 Analysis And Design 26 - 36
4.5 37 - 39
Database Design
4.6 System Testing 40 -41

42
CONCLUSION
43
REFERANCES
 LIST OF TABLES

Sr Page No
No
1 Task Schedule Table 15

2 Hardware Requirement Client Side 16

3 Hardware Requirement Server Side 16

4 Software Requirement Client Side 17

5 Software Requirement Server Side 17

6 tbladmin table Structure 24

7 tblclass table Structure 25

8 tblnotice table Structure 25

9 tblpublicnotice table Structure 25

10 tblstudent table Structure 26

11 tblpage table Structure 26

 List of Figures

Sr No Page No
1 Procedural Design 25

2 Use Case Diagram of User/Student 28

3 Use Case Diagrams Admin 29

4 Class Diagram 30

5 Entity-Relationship Diagrams 34

6 36
Symbols For Data Flow Diagram
CHPTER 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 two main users involved in this system are :

1. User(i.e. Students)
2. Admin

In the Software we can register a student by the authentication code i.e., student id and
password with help of student id and password student can login his/her account and view all
the notices which is announced by admin.

1.1 General

The Student Management System (SMS) is a comprehensive software solution designed to streamline
and enhance the management of student-related information within educational institutions. This
system aims to facilitate the administrative processes of schools, colleges, and universities, making it
easier for educators, administrators, and students to access and manage vital information efficiently.

1.2 Objective

The objectives of a Student Management System aim to create a streamlined, efficient, and user-
friendly solution for managing student data and enhancing communication within educational
institutions. By focusing on these detailed objectives, an SMS can significantly improve operational
efficiency, data accuracy, and overall educational outcomes, ultimately leading to a more effective
learning environment for students and educators a like . Here are the key objectives:

• Streamline Administrative Processes:

- Automate routine tasks such as student enrollment, attendance tracking, and grade management to

1
reduce manual effort and improve efficiency.

• Centralize Student Information:

Create a single repository for all student-related data, making it easily accessible to authorized users,
and ensuring data consistency and accuracy.

• Enhance Communication:

- Facilitate effective communication among students, parents, teachers, and administrators through
integrated messaging and notification systems.

Improve Data Management:

- Enable efficient organization, retrieval, and management of student records, course details, and
academic performance data.

• Support Decision-Making:

- Provide comprehensive reporting and analytics tools to help educators and administrators make
informed decisions based on student performance and trends.

• Increase Student Engagement:

- Offer features that promote student involvement, such as course feedback mechanisms, online
forums, and access to academic resources.

 Ensure Data Security and Privacy:

- Implement robust security measures to protect sensitive student information and comply with data
protection regulations.

• Facilitate Compliance and Reporting:

- Help institutions comply with regulatory requirements by generating necessary reports and
maintaining accurate records.

• Enhance User Experience:

- Design a user-friendly interface that allows easy navigation for all users, including students,

2
teachers, and administrators.

• Scalability and Flexibility:

- Ensure the system can grow with the institution, allowing for the addition of new features and
functionalities as needed.

By achieving these objectives, a Student Management System can significantly improve the overall
efficiency and effectiveness of educational institutions, ultimately contributing to better student
outcomes.

1.3 PURPOSE, SCOPE & ADAPTABILITY

1.3.1 Project Purpose

The objective of Student Management System is to allow the administrator of any organization to
edit and find out the personal details of a student and allows the student to keep up to date his
profile .It’ll also facilitate keeping all the records of students, such as their id, name, mailing address,
phone number, DOB etc. So, all the information about a student will be available in a few seconds.
Overall, it’ll make Student Information Management an easier job for the administrator and the
student of any organization.

1.3.2 Project Scope And Limitation

The proposed system will affect or interface with the user (student) and administrator. The system
works and fulfills all the functionalities as per the proposed system. It will provide reduced response
time against the queries made by different users. This project is based on PHP language with MYSQL
database which manage the details of the student because it is a tedious job for any organization.
Student Information system will store all the details of the students including their background
information.
All possible features such as verification, validation, security, user friendliness etc. have been
considered.

3
The different types of modules present in this project are

1. Admin

2. User

Admin:
1. Dashboard: In this section, admin can see all detail in brief like Total Classes, Total
Students, Total Class Notices and Total Public Notices
2. Class: In this section, admin can manage class (Add/Update/Delete).
3. Students: In this section, admin can manage the students (Add/Update/Delete).
4. Notices: In this section, the admin can manage notices (Add/Update/Delete).
5. Public Notices: In this section, the admin can manage public notices.
6. Pages: In this section admin, can manage about us and contact us page of administration
7. Search: In this section admin, can search students by their student id.
8. Reports: In this section admin, can view how much students has been register in
particular period.
9. Admin can also update his profile, change the password and recover the password.

User (Students):

1. Dashboard: It is welcome page for students.

2. View Notices: In this section, user can view notices which are announced by administrator.
3. Student can also view his profile, change the password and recover the password.

User (Non-Register):

1. Home: It is welcome page for user.

2. About: User can view about us page.
3. Contact: User can view contact us page.

4
1.3.3 Applicability
A Student Management System (SMS) is applicable across various educational contexts, including
K-12 schools, higher education institutions, and online learning platforms. It streamlines
administrative processes by centralizing student data, facilitating enrollment, tracking attendance, and
managing grades, which enhances efficiency and reduces paperwork. The SMS fosters effective
communication between teachers, students, and parents through integrated messaging and
notifications, while providing valuable analytics for performance tracking and retention strategies. Its
customizable and scalable nature allows institutions to tailor the system to their unique needs and
integrate it with other educational tools, ultimately improving the overall learning experience and
supporting student success.

1.4 Achivments

The achievements of a Student Management System (SMS) are significant and multifaceted. First, it
dramatically improves administrative efficiency by automating routine tasks like enrollment,
attendance tracking, and grade management, which reduces the workload on staff. Second, the system
centralizes student data, ensuring accuracy and easy access to records, thus minimizing errors
associated with manual data handling. Additionally, SMS enhances communication between
students, parents, and educators through integrated messaging features, fostering better
engagement and timely updates. The provision of robust reporting and analytics tools allows
institutions to analyze student performance, identify trends, and make informed decisions that
drive educational improvement.

Moreover, SMS actively promotes student engagement by offering features such as student portals
and feedback mechanisms, encouraging learners to take ownership of their education. It also
facilitates compliance with regulatory requirements by generating necessary reports with ease,
reducing the administrative burden.

Data security is another key achievement, as SMS protects sensitive student information through
robust security protocols, ensuring compliance with data protection regulations. The system is
scalable and flexible, making it adaptable to the needs of both small and large educational
organizations. Finally, by analyzing engagement levels and performance data, institutions can develop
targeted strategies to support at-risk students, which positively impacts retention rates and overall
student success.

5
1.5 Advantages , Disadvantages and Applications

Advantages:

 It helps the educational administrator to handle and manage students’ records.

 It helps educational administrator to generate report.
 It brings transparency and efficiency in the working of educational system.

Disadvantages:

 The system can only handle single educational organization.

 The system does not include bank payment, dd, cheque status.

Applications:

The website Student Management System is aimed towards recording a considerable

number of student records and needs online assistance for managing records of students.
Website should be user-friendly, quick to learn’ and reliable website for the above purpose.
Student Management System is intended to be a stand-alone product and should not
depend on the availability of other website.

6
CHAPTER 2

SURVEY OF TECHNOLOGIES
A Student Management System (SMS) employs various technologies to streamline processes,
enhance user experience, and ensure data security. Here’s a comprehensive overview of the key
technologies utilized in the development and implementation of an SMS: The effective
implementation of a Student Management System relies on a diverse set of technologies that work
together to enhance functionality, security, and user experience. By leveraging programming
languages, database systems, web technologies, and cloud services, educational institutions can create
an efficient and user-friendly platform that meets the needs of students, educators, and administrators,
ultimately improving the overall educational experience.

1. Frontend Technologies

1 HTML/CSS

Description: HTML (HyperText Markup Language) is used for structuring content on the
web, while CSS (Cascading Style Sheets) is used for styling the layout.
Use in SMS: HTML provides the structure for web pages, and CSS ensures a visually
appealing and responsive user interface that works on various devices.

JavaScript:
Essential for client-side development, JavaScript adds interactivity to web applications. It allows
for dynamic updates and real-time content changes without page reloads. Frameworks like React and
Vue.js help build rich user interfaces and manage application state efficiently

7
2. Backend Technologies
PHP
Description: A popular server-side scripting language designed for web development.
Use in SMS: Handles the backend logic, processes user requests, interacts with the database,
and manages session handling.

3 Database Technologies

MySQL:
Overview: A widely used open-source relational database management system.
Advantages: High performance, reliability, and ease of use.
PostgreSQL:
Overview: An advanced open-source relational database with support for complex queries.
Advantages: Strong support for data integrity, extensibility, and standards compliance.
SQLite:
Overview: A lightweight, file-based database engine.
Advantages: Minimal setup, zero configuration, suitable for small to medium applications.

4. Content Management Systems (CMS)

WordPress:
WordPress can be customized to serve as an SMS through various plugins and themes. Its user-
friendly interface allows non-technical users to manage content and student data effectively.

5. Frameworks and Libraries

Laravel is a PHP framework known for its elegant syntax and powerful features, such as Eloquent
ORM, routing, and middleware. It simplifies development and enhances application scalability
and maintainability.

React/Vue.js:
These JavaScript frameworks allow for building interactive user interfaces. React’s component-
based architecture and Vue.js’s simplicity enable developers to create responsive and dynamic
applications that enhance user engagement.

8
6. Cloud Technologies

Amazon Web Services (AWS):

AWS provides a robust cloud infrastructure for hosting SMS applications. Services like Amazon
RDS offer managed database solutions, while Elastic Beanstalk simplifies deployment and scaling.
Google Cloud Platform (GCP):
GCP offers similar cloud capabilities, with additional tools for data analytics and machine learning.
It provides scalable solutions for hosting applications and managing data.

7. Security Technologies

SSL/TLS:

SSL (Secure Socket Layer) and TLS (Transport Layer Security) protocols encrypt data transmitted
between users and the server, protecting sensitive information from unauthorized access.
OAuth2:

OAuth2 is an authorization framework that enables secure login through third-party accounts (e.g.,
Google, Facebook), simplifying user authentication while enhancing security.

8. Analytics Tools

Business Intelligence Tools:

Tools like Tableau and Power BI can be integrated to visualize student performance data, helping
institutions analyze trends and make data-driven decisions.

9
CHAPTER 3

REQUIREMENTS AND ANALYSIS

3.1 Problem Defination

In the context of educational institutions, managing student information and administrative tasks
efficiently poses several challenges. A Student Management System (SMS) aims to address these
issues by providing a centralized platform for managing various aspects of student data and academic
administration. Below are the key problems that an SMS seeks to resolve:

1. Inefficient Data Management

- Educational institutions often rely on manual processes for managing student records, attendance,
grades, and course enrollments. This can lead to data inaccuracies, difficulties in retrieval, and time-
consuming administrative tasks. An SMS provides a structured and automated solution for storing
and managing this data effectively.

2. Poor Communication

- Communication between students, parents, and faculty can be fragmented and inefficient.
Important information regarding grades, attendance, and course updates may not be communicated
timely, leading to misunderstandings and lack of engagement. An SMS integrates communication
tools that facilitate timely notifications and updates, enhancing stakeholder engagement.

3. Lack of Accessibility

- Traditional methods of managing student information often result in limited accessibility.

Stakeholders may struggle to access necessary data when needed, particularly in emergencies or for
decision-making. An SMS offers web-based access, enabling users to retrieve information anytime
and anywhere, which is crucial for modern educational environments.

10
4. Difficulties in Data Analysis

- Educational institutions generate vast amounts of data, but analyzing this information to derive
insights can be challenging without proper tools. Manual analysis is prone to errors and is time-
consuming. An SMS incorporates reporting and analytics features that provide real-time insights into
student performance, attendance trends, and academic outcomes, aiding informed decision-making.

5. Compliance and Security Issues

- Educational institutions must adhere to various regulations concerning student data privacy and
security (e.g., FERPA, GDPR). Managing compliance can be complex without a robust system in
place. An SMS implements security measures such as encryption, access controls, and audit trails to
ensure compliance with legal requirements and protect sensitive information.

6. Resource Management Challenges

- Managing resources, such as classrooms, schedules, and staff assignments, can be cumbersome.
Manual scheduling often leads to conflicts and inefficiencies. An SMS provides tools for resource
allocation and scheduling, ensuring optimal use of facilities and personnel.

7. Scalability Issues

- As educational institutions grow, their needs evolve. Traditional systems may not scale effectively,
leading to limitations in functionality and performance. An SMS is designed to be scalable, allowing
institutions to expand their capabilities as enrollment increases or new programs are introduced.

The implementation of a Student Management System addresses these critical issues by providing a
centralized, efficient, and secure platform for managing student data and administrative tasks. By
automating processes, enhancing communication, and ensuring data integrity, an SMS significantly
improves the overall educational experience for students, educators, and administrators alike.

11
3.2 REQUIREMENTS SPECIFICATION

The requirements specification for a Student Management System (SMS) outlines the functional and
non-functional requirements necessary for the successful development and implementation of the
system. These requirements serve as a foundation for the design, development, and testing phases.

1. Functional Requirements

1.1 User Management

Users shall have role-based access control, ensuring that different roles (e.g., student, teacher,
admin) have appropriate permissions.

1.2 Student Information Management

The system shall allow for the uploading and management of documents (e.g., transcripts,
identification).

1.3 Course Management

The system shall allow students to enroll in and drop courses, with real-time updates on
availability.

1.4 Attendance Tracking

Attendance data shall be accessible by faculty and administrators for reporting and analysis.

1.5 Grading and Assessment

The system shall generate report cards and transcripts based on accumulated grades.

1.6 Communication Tools

The system shall provide notifications for important events (e.g., assignment due dates, grades
posted).

1.7 Reporting and Analytics

The system shall provide dashboards for visualizing key metrics and insights.

12
2. Non-Functional Requirements

2.1 Performance

The system shall support a minimum of 500 concurrent users without performance degradation.

Page load times shall not exceed 2 seconds under normal operating conditions.

2.2 Security

The system shall implement secure authentication and authorization mechanisms, including
password hashing and role-based access control.
The system shall encrypt sensitive data both in transit (using SSL/TLS) and at rest.

2.3 Usability

The system shall have an intuitive user interface that requires minimal training for users to
navigate.

The system shall provide accessibility features to accommodate users with disabilities.

2.4 Scalability

The system shall be designed to accommodate future growth, supporting increased user numbers
and additional features without significant re-engineering.

2.5 Reliability

The system shall have an uptime of 99.5% to ensure consistent availability for users.

The system shall include backup and disaster recovery mechanisms to protect data integrity.

2.6 Compliance

The system shall comply with relevant data protection regulations (e.g., FERPA, GDPR) to ensure
the privacy and security of student data.

13
3.3 PLANING AND SCHEDULING

Effective planning and scheduling are essential for the successful implementation of a Student
Management System (SMS) tailored for college students. This overview outlines a structured
approach that focuses on the specific needs of college environments.

1. Project Overview

Objective: Develop a web-based Student Management System (SMS) to manage student

information, attendance, and grades.

Timeline: Define the overall duration for the project (e.g., 8 weeks).

2. Task Breakdown

 Project Planning
Define project objectives
Gather Information

 Design Phase
Database design
User interface design

 Development Phase
Setup environment
Develop student management features
Develop class management features

 Testing Phase
Unit testing
Integration testing
User acceptance testing

14
3.3.1 Task Schedule

Task Task Description Status

ID

1 Define project objectives Completed

2 Gather requirements Completed

3 Database design In Progress

4 UI DEsign Not Started

5 Develop student management features Not Started

6 Develop class management features Not Started

7 Testing phase Not Started

8 Collect feedback and improvements Not Started

Table No 1: Task Schedule

15
3.4 SOFTWARE & HARDWARE REQUIRENMENT

To ensure smooth development, deployment, and operation of the Student Management System,
software and hardware requirements must be met. These requirements are essential for both the
development team and end users (students, instructors, and administrators).

Hardware Requirement :

Client Side:

RAM 512 MB

Hard disk 10 GB

Processor 1.0 GHz

Table No 2: Hardware Requirement Client Side

Server side:

RAM 1 GB

Hard disk 20 GB

Processor 2.0 GHz

Table No 3: Hardware Requirement Server Side

16
 Software Requirement:

Client Side:

Web Browser Google Chrome or any compatible

browser

Operating System Windows or any equivalent OS

Table No 4: Software Requirement Client Side

Server Side:

Web Server APACHE

Server side Language PHP5.6 or above version

Database Server MYSQL

Web Browser Google Chrome or any

compatible browser
Operating System Windows or any equivalent OS

Table No 5: Software Requirement Server Side

APACHE

The Apache HTTP Server Project is an effort to develop and maintain an open-source HTTP server
for modern operating systems including UNIX and Windows. The goal of this project is to provide a
secure, efficient and extensible server that provides HTTP services in sync with the current HTTP
standards. The Apache HTTP Server ("httpd") was launched in 1995 and it has been the most popular
web server on the Internet since April 1996. It has celebrated its 20th birthday as a project in February
2015.

17
PHP
PHP stands for PHP: Hypertext Preprocessor
PHP is a server-side scripting language, like ASP.
PHP scripts are executed on the server.
PHP supports many databases (MYSQL, Informix, Oracle, Sybase, Solid, Generic ODBC, etc.).
PHP is an open source software.
PHP is free to download and use

MYSQL

MYSQL is a database server

MYSQL is ideal for both small and large applications

MYSQL supports standard SQL
MYSQL compiles on a number of platforms
MYSQL is free to download and use
How to access MySQL:

18
3.5 PRELIMINARY PROJECT DESCRIPTION

The Student Management System aims to enhance the efficiency of educational institutions by
providing a comprehensive solution for managing student data and academic processes. Through
its user-friendly interface and robust features, the system will support administrators, teachers, and
students in achieving their academic goals.

1 Overview

Version: 1.0

Release Date: [Insert Date]

2. Product Purpose

The Student Management System is designed to streamline the management of student data and
academic processes within educational institutions. It facilitates efficient tracking of student
information, attendance, grades, and class assignments, providing a centralized platform for
administrators, teachers, and students.

3. Key Features

Student Management:

Add, edit, delete, and view student records.

Store essential information such as name, email, date of birth, gender, and class enrollment.

Class Management:

Create and manage classes.

Assign teachers to specific classes and enroll students.

Reporting:

Generate detailed reports on attendance and academic performance.

Export reports in formats such as PDF or CSV.

19
4. Target Users

Teachers: Input student grades, track attendance, and manage class-related tasks.

Students: Access their own information, view grades, and track attendance.

5. Technical Requirements

Backend: PHP for server-side logic and processing.

Database: MySQL for data storage and management.

Server: XAMPP or WAMP for local development and testing.

6. System Architecture

Client-Server Model: The system will follow a client-server architecture where the frontend
interacts with the backend via PHP scripts. The backend communicates with the MySQL
database to store and retrieve data.

8. Future Enhancements

Mobile application development for on-the-go access.

Advanced analytics for performance tracking and reporting

20
CHAPTER 4

SYSTEM DESIGN

Design is the first step in the development phase for any techniques and principles for the purpose of
defining a device, a process or system insufficient detail to permit its physical realization Once the
software requirements have been analyzed and specified the software design involves three technical
activities - design, coding, I implementation and testing that are required to build and verify the
software.The design activities are of main importance in this phase, because in this activity, decisions
ultimately affecting the success of the software implementation and its ease of maintenance are made.
These decision shave the final bearing upon reliability and maintainability of the system. Design is
the only way to accurately translate the customer’s requirements into finished software or a system.
Design is the place where quality is fostered in development. Software design is a process through
which requirements are translated into a representation of software. Software design is conducted in
two steps Preliminary design is concerned with the transformation of
requirements into data

Unified Modelling Language Diagrams (UML):

The unified modelling language allows the software engineer to express an analysis model using
the modelling notation that is governed by a set of syntactic semantic and pragmatic rules.
A UML system is represented using five different views that describe the system from distinctly
different perspective. Each view is defined by a set of diagrams, which is as follows.

User Model View

i. This view represents the system from the user’s perspective.
ii. The analysis representation describes a usage scenario from the end-user’s perspective.
Structural model view
In this model the data and functionality are arrived from inside the system.
This model view models the static structures

21
Behavioral Model View
It represents the dynamic of behavioral as parts of the system, depicting the interactions of collection
between various
structural elements described in the user model and structural model view.

Implementation Model View

In this the structural and behavioral as parts of the system are represented as they are to be built.

Environmental Model View

In these the structural and behavioral aspects of the environment in which the system is to be
implemented are represented.

UML is specifically constructed through two different domains they are

UML Analysis modelling, which focuses on the user model and structural model views of the
system?

UML design modelling, which focuses on the behavioral modelling, implementation modelling
and environmental model views.

22
4.2 Data Integrity and Constraints

Data Integrity and Constraints are crucial for ensuring the accuracy, consistency, and reliability of
the data within a Student Management System. Let's look at how they can be applied in various
parts of the system:

Data integrity and constraints ensure that:

 Data is consistent across the system.

 Relationships between tables are preserved.
 Invalid or inconsistent data is prevented from entering the system.
 Business rules are automatically enforced, reducing manual intervention and errors.
 System reliability is improved by maintaining accurate, valid, and properly linked data.

This ensures the smooth operation of a Student Management System, which is critical for tracking
student progress, managing courses, and ensuring academic records are reliable.

1. Data Integrity Types

a. Entity Integrity:

Purpose: Ensures that each record in a table can be uniquely identified.

Implementation: Use Primary Keys.
Example:
student_id in the students table must be unique and not null.
course_id in the courses table must be unique and not null

b. Referential Integrity:

Purpose: Maintains the consistency between related tables by ensuring valid relationships.
Implementation: Use Foreign Keys.
Example:

student_id in the enrollments table must refer to a valid student_id in the students table.
course_id in the grades or attendance table must refer to a valid course_id in the courses table.

23
c ) Domain Integrity:

Purpose: Ensures that the data entered into a column falls within a valid set of values.
Implementation: Use Data Types, Constraints, and Validation.
Example:
The grade column in the grades table should only accept values between 0 and 100.
The email column in the students table should follow a valid email format.

d. User-Defined Integrity:

Purpose: Enforces specific business rules that may not be covered by the above types.
Implementation: Custom Constraints and Triggers.
Example:
A student cannot be enrolled in the same course more than once at the same time.

c. Domain Integrity:

Purpose: Ensures that the data entered into a column falls within a valid set of values.
Implementation: Use Data Types, Constraints, and Validation.
Example:
The grade column in the grades table should only accept values between 0 and 100.
The email column in the students table should follow a valid email format.

d. User-Defined Integrity:

Purpose: Enforces specific business rules that may not be covered by the above types.
Implementation: Custom Constraints and Triggers.
Example:
A student cannot be enrolled in the same course more than once at the same time.

24
4.3 Procedural Design

Procedural design refers to the planning and structuring of the processes and operations within a
system. In a Student Management System, procedural design focuses on how various functionalities
(such as enrollment, attendance tracking, and reporting) are implemented, ensuring that they operate
smoothly and efficiently.

Key Concepts of Procedural Design

Inputs: Data required to begin a process.
Example: Student ID, Course ID, Attendance Status, etc.

Processes: A series of steps or actions performed on the inputs.

Example: Validating input, adding student data to the database, generating reports.
Decision Points: Conditions that determine the next step based on inputs or process results.
Example: Checking if a student ID is valid.
Outputs: Results generated from the processes.
Example: Confirmation message, attendance status recorded, error message, etc.
Error Handling: Procedures for managing errors that occur during the process

Fig No 1: Procedural Design

25
4.4 ANALYSIS AND DESIGN

Design Introduction:
Design is the first step in the development phase for any techniques and principles for the purpose of
defining a device, a process or system in sufficient detail to permit its physical realization.

Once the software requirements have been analyzed and specified the software design involves three
technical activities - design, coding, implementation and testing that are required to build and verify
the software.
The design activities are of main importance in this phase, because in this activity, decisions
ultimately affecting the success of the software implementation and its ease of maintenance are made.
These decisions have the final bearing upon reliability and maintainability of the system. Design is
the only way to accurately translate the customer’s requirements into finished software or a system.
Design is the place where quality is fostered in development. Software design is a process through
which requirements are translated into a representation of software. Software design is conducted in
two steps. Preliminary design is concerned with the transformation of requirements into data

UML Diagrams:

Actor:
A coherent set of roles that users of use cases play when interacting with the use `cases.

Use case: A description of sequence of actions, including variants, that a system performs that yields

26
UML stands for Unified Modeling Language. UML is a language for specifying, visualizing and
documenting the system. This is the step while developing any product after analysis. The goal from
this is to produce a model of the entities involved in the project which later need to be built. The
representation of the entities that are to be used in the product being developed need to be designed.

USECASE DIAGRAMS:

Use case diagrams model behavior within a system and helps the developers understand of what the
user require. The stick man represents what’s called an actor.
Use case diagram can be useful for getting an overall view of the system and clarifying who can do
and more importantly what they can’t do.
Use case diagram consists of use cases and actors and shows the interaction between the use case and
actors.
• The purpose is to show the interactions between the use case and actor.
• To represent the system requirements from user’s perspective.
• An actor could be the end-user of the system or an external system.

USECASE DIAGRAM: A Use case is a description of set of sequence of actions. Graphically it is

rendered as an ellipse with solid line including only its name. Use case diagram is a behavioral
diagram that shows a set of use cases and actors and their relationship. It is an association between
the use cases and actors. An actor represents a real-world object. Primary Actor – Sender, Secondary
Actor Receiver.

27
Use Case Daigram of Student

Fig No 2 :Use Case Diagram of User/Student

28
Use Case Diagrams Admin

Fig No 3: Use Case Diagram Admin

29
Class Diagram:

The class diagram shows a set of classes, interfaces, collaborations and their relationships.

Fig No 4 : Class Diagram

30
ER Diagram:

The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a way to
unify the network and relational database views. Simply stated the ER model is a conceptual data
model that views the real world as entities and relationships. A basic component of the model is the
Entity-Relationship diagram which is used to visually represent data objects. Since Chen wrote his
paper the model has been extended and today it is commonly used for database design for the database
designer, the utility of the ER model is:

• It maps well to the relational model. The constructs used in the ER model can easily be
transformed into relational tables.

• It is simple and easy to understand with a minimum of training. Therefore, the model can be
used by the database designer to communicate the design to the end user.

• In addition, the model can be used as a design plan by the database developer to implement a
data model in specific database management software.

ER Notation

There is no standard for representing data objects in ER diagrams. Each modeling methodology uses
its own notation. The original notation used by Chen is widely used in academics texts and journals
but rarely seen in either CASE tools or publications by non-academics. Today, there are a number of
notations used; among the more common are Bachman, crow's foot, and IDEFIX.

All notational styles represent entities as rectangular boxes and relationships as lines connecting
boxes. Each style uses a special set of symbols to represent the

cardinality of a connection. The notation used in this document is from Martin. The symbols used for
the basic ER constructs are:

Entities are represented by labeled rectangles. The label is the name of the entity. Entitynames.

should be singular nouns

Relationships are represented by a solid line connecting two entities. The name of the relationship
is written above the line. Relationship names should be verbs

Attributes, when included, are listed inside the entity rectangle. Attributes which are identifiers
are underlined. Attribute names should be singular nouns.

31
Cardinality of many is represented by a line ending in a crow's foot. If the crow's foot is omitted, the
cardinality is one.

Existence is represented by placing a circle or a perpendicular bar on the line. Mandatory existence
is shown by the bar (looks like a 1) next to the entity for an instance is required. Optional existence
is shown by placing a circle next to the entity that is optional.

Cardinality of a connection. The notation used in this document is from Martin. The symbols used for

basic ER constructs are:

• Entities are represented by labeled rectangles. The label is the name of the entity. Entity
names should be singular nouns.

• Relationships are represented by a solid line connecting two entities. The name of the
relationship is written above the line. Relationship names should be verbs

• Attributes, when included, are listed inside the entity rectangle. Attributes which are
identifiers are underlined. Attribute names should be singular nouns.

• Cardinality of many is represented by a line ending in a crow's foot. If the crow's foot is
omitted, the cardinality is one.

Existence is represented by placing a circle or a perpendicular bar on the line. Mandatory existence
is shown by the bar (looks like a 1) next to the entity for an instance is required. Optional existence
is shown by placing a circle next to the entity that is optional.

32
E-R (Entity-Relationship) Diagram is used to represents the relationship between entities in
the table

The symbols used in E-R diagrams are:

SYMBOL PURPOSE

Represents Entity sets.

Represent attributes.

Represent Relationship Sets.

Line represents

33
To develop a new kind of a system:
The traditional approach focuses on the cost benefit and feasibility analysis, Project management, and
hardware and software selection a personal consideration

Fig No 5: Entity-Relationship Diagrams

34
Data Flow Diagrams

A Data Flow Diagram (DFD) is a traditional visual representation of the information flows within a
system. A neat and clear DFD can depict the right amount of the system requirement graphically. It
can be manual, automated, or a combination of both.

It shows how data enters and leaves the system, what changes the information, and where data is
stored.

The objective of a DFD is to show the scope and boundaries of a system as a whole. It may be used
as a communication tool between a system analyst and any person who plays a part in the order that
acts as a starting point for redesigning a system. The DFD is also called as a data flow graph or bubble
chart.

The following observations about DFDs are essential:

1. All names should be unique. This makes it easier to refer to elements in the DFD.
2. Remember that DFD is not a flow chart. Arrows is a flow chart that represents the order of
events; arrows in DFD represents flowing data. A DFD does not involve any order of events.
3. Suppress logical decisions. If we ever have the urge to draw a diamond-shaped box in a DFD,
suppress that urge! A diamond-shaped box is used in flow charts to represents decision points
with multiple exists paths of which the only one is taken. This implies an ordering of events,
which makes no sense in a DFD.
4. Do not become bogged down with details. Defer error conditions and error handling until the
end of the analysis.

Standard symbols for DFDs are derived from the electric circuit diagram analysis and are
shown in fig:

35
 Sy

Fig No 6 : Symbols For Data Flow Diagram

Circle: A circle (bubble) shows a process that transforms data inputs into data outputs.

Data Flow: A curved line shows the flow of data into or out of a process or data store.

Data Store: A set of parallel lines shows a place for the collection of data items. A data store indicates
that the data is stored which can be used at a later stage or by the other processes in a different order.
The data store can have an element or group of elements.

36
4.5 Database Design

The data in the system has to be stored and retrieved from database. Designing the database is part of
system design. Data elements and data structures to be stored have been identified at analysis stage.
They are structured and put together to design the data storage and retrieval
System. A database is a collection of interrelated data stored with minimum redundancy to serve many
users quickly and efficiently. The general objective is to make database access easy, quick,
inexpensive and flexible for the user.

Relationships are established between the data items and unnecessary data items removed.
Normalization is done to get an internal consistency of data and to have minimum redundancy and
maximum stability. This ensures minimizing data storage required ,minimizing chances of data
inconsistencies and optimizing for updates. The MySQL database has been chosen for developing the
relevant databases.

Student Management System (SMS) contains 6 MySQL tables:

tbladmin table Structure: This table store the admin login and
personal Details.

Table No 6: tbladmin table Structure

37
blclass table Structure : This table store the class and section.

Table No 7 : tblclass table Structure

tblnotice table Structure: This table store the notices detail which is announced

Table No 8 : tblclass table Structure

tblpublicnotice table Structure : This table store the public notices detail which is announced by
admin.

Table No 9 : tblpublicnotice table Structure

38
tblstudent table Structure : This table store the students details of educational organization.

Table No 10 : tblpublicnotice table Structure

tblpage table Structure: This table store the details of about us and contact us page

Table No 11 : tblpage table Structure

39
4.6 SYSTEM TESTING

SOFTWARE TESTING TECHNIQUES:

Software testing is a critical element of software quality assurance and represents the ultimate review
of specification, designing and coding.

TESTING OBJECTIVES:
1. Testing is process of executing a program with the intent of finding an error.
2. A good test case design is one that has a probability of finding an as yet undiscovered error.
3. A successful test is one that uncovers an as yet undiscovered error. These above objectives imply a
dramatic change in view port. Testing cannot show the absence of defects, it can only show that
software errors are present.
There are three types of testing strategies
1. Unit test
2. Integration test
3. Performance test

Unit Testing:
Unit testing focuses verification efforts on the smallest unit of software design module. The unit test
is always white box oriented. The tests that occur as part of unit testing are testing the module
interface, examining the local data structures, testing the boundary conditions, execution all the
independent paths and testing error-handling paths.

Integration Testing:
Integration testing is a systematic technique or construction the program structure while at the same
time conducting tests to uncover errors associated with interfacing. Scope of testing summarizes the
specific functional, performance, and internal design characteristics that are to be tested. It employs
top-down testing and bottom-up testing methods for this case.

40
Performance Testing:

Timing for both read and update transactions should be gathered to determine whether system
functions are being performed in an acceptable timeframe.

41
 CONCLUSION

The project titled as Student Management System was deeply studied and analyzed to design the
code and implement. It was done under the guidance of the experienced project guide. All the current
requirements and possibilities have been taken care during the project time.

Student Management System can be used by education institutes to maintain the records of students
easily. Achieving this objective is difficult using a manual system as the information is scattered, can
be redundant and collecting relevant information may be very time consuming. All these problems
are solved using this project.

42
 REFERANCES
For PHP

https://www.w3schools.com/php/default.asp

https://www.sitepoint.com/php/

https://www.php.net/

For MySQL

https://www.mysql.com/

http://www.mysqltutorial.org

For XAMPP

https://www.apachefriends.org/download.html

43