Project Name:

School Management System

Prepared By:
Muhammad
Nadeem

REG No:
GU-0763

Ghazi University Dera Ghazi

Khan

Department of CS & IT

1_ABSTRACT:
We are make this project to help user friendly. In this project the on the School Management. In the this
project user can see the details of all about the school details in the web site. Administrator can add the details of
the students, staff details, & online addmission details in the web sites.

This project is very useful to the any type of school manage & store the all types details on the web site
without any paper work.

Help of this project any one can access the details of the school & if any one stdent want to know about
the couses of this school than they are see without visiting the school & without wating the their time. If they are
intrasted in the couse than they are registare or the get the fill addmission form on line.

1|Page
 If any one use want to give sugession about the school or the project than user give their details using
feedback form.

If any one user want to contect to the administrator or manager of the school or get the details of the contect
number & addresses know in the contecct us page & user can contect the administraot using this page.

2. INTRODUCTION

2.1. Title of the project:

School Management System

2.2. Objective
The School Management System is designed to automate and streamline various
administrative tasks related to school management. The primary focus is on user management,
allowing administrators to efficiently handle the addition, removal, update, and deletion of
teachers, students, classes, subjects, and classrooms.
.

2.3. Project Category:

Web Application

3. SYSTEM ANALYSIS

3.1. Existing System:

The existing system for school management involves manual processes for handling user-
related tasks. Administrators have to manage teacher, student, class, subject, and classroom
details manually, leading to potential errors, inconsistencies, and inefficiencies.

3.2. Drawbacks of the Existing System:

The existing system has the following disadvantages:

1) Manual handling of tasks leads to potential errors
2) Inconsistencies in data due to lack of automation.
3) Inefficient use of time and resources.
4) Limited access to information for administrators.
5) Difficulty in tracking changes and updates.

3.3. Need For the Proposed System:

The proposed School Management System aims to address the drawbacks of the existing
system by providing:
1) Automation of user management tasks.

2|Page
 2) Streamlined processes for adding, removing, updating, and deleting users.
3) Improved data consistency and accuracy.
4) Efficient allocation of resources.
5) Enhanced access to information for administrators.

3.4. System Configuration:

3.4.1. Hardware Configurations:

Processor : Pentium 4, higher version

RAM : 8 GB
Hard Disk : 40 GB space

3.4.2.Software Configurations:
Front End: HTML, CSS, JAVASCRIPT, JQUERY,
BOOTSTRAP
Back End: PHP laravel, MySQL
Operating System: Windows 10
Web server: XAMPP
Package Manager: Composer
Text Editor: Sublimtex

4. SYSTEM DESIGN

4.1. Introduction:
This chapter gives a detailed view of the project and elaborates how this project will be
work.

4.2. Program Description:

3|Page
4.2.1. Application flow:

Homepage

About us
Contact Admission Staff Standard Contact us Feedback

History Stud details Staff details Standard Contact Feedback

Details Details

4.2.2. Data Flow Diagram (DFD):

Data Flow Diagrams show the flow of data from external entities into the system, and from one
process to another within the system.

Data Flow Diagram level 0 (DFD):

This is the Zero Level DFD of School Management System, where we have eloborated
the high level process of School. It's a basic overview of the whole School Management System
or process being analyzed or modeled. It's designed to be an at-a-glance view of Fees Attendance
and Subjects showing the system as a single high-level process, with its relationship to external
entities of Students, Class and Teachers. It should be easily understood by a wide audience,
including Students, Teachers and Fees

Level Entities and proccess flow of School Management System:

Managing all the Students

Managing all the Class

Managing all the Teachers

Managing all the Timetable

Managing all the Fees

4|Page
Managing all the Attendance

Managing all the Subjects

Data Flow Diagram level 1 (DFD):

First Level DFD (1st Level) of School
Management System shows how the system is divided into sub-systems (processes), each of
which deas ath one or more of the data flows to or from an external agent, and which together
provide all of the functionality of the School Management System system as a whole. It also
identifies internal data stores of Subjects, Attendance, Fees, Timetable, Teachers that must be
present in order for the School system to do its job, and shows the flow of data between the
various parts of Students, Teachers, Attendance, Subjects, Fees of the system.

Main entities and output of First Level DFD (Ist Level DFD)

Processsing Students records and genereate report of all Students

Processsing Class records and genereate report of all Class

Processsing Teachers records and genereate report of all Teachers

5|Page
 Processsing Timetable records and genereate report of all Timetable

Processsing Fees records and genereate report of all Fees

Processsing Attendance records and genereate report of all Attendance

Data Flow Diagram level 2 (DFD):

DFD Level 2 then goes one step deeper into parts of Level 1 of School. It may require
more functionalities of School to reach the necessary level o detail about the School functioning,
First Level DFD (1st Level) of School Management System shows how the system is divided
into subsystems (processes) The 2nd Level DFD contains more detalls of Subjects, Attendance,
Fees, Timetable, Teachers, Class Students

level functionalities of School Managernent System

Admin logins to the system and manage all the functionalities of School Management
System
Admin can add, edit delete and view the records of Students, Teachers Fees. Subjects

Admin can manage all the details of Class, Timetable, Attendance

6|Page
 Admin can also generate reports of Students Class Teachers, Timetable, Fees. Attendance

Admin can search the details of Class Fees. Attendance

Admin can apply different level of filters on report of Students, Timetable, Fees

Admin can tracks the detailed information of Class Teachers, Timetable,, Fees

4.2.3. School-Management-System-Use Case-Diagram:

Use Case Diagram is a
graphic depiction of the interactions among the elements of School Management System It
represents the methodology used in system analysis to identify, clarity, and organize system
requirements of School Management System. The train actors of School Management System in
this Use Case Diagram are: Super Admin, System User, Teacher, Student, who perform the
different type of use cases such as Manage Schoots, Manage Students, Manage Classes, Manage
Teachers, Manage Cources, Manage Registrations, Manage Users and Full School Management
System Operations .

7|Page
Admin Entity: Use cases of Super Admin are Manage Schools, Manage Students, Manage
Classes Manage Teachers Manage Courtes Manage Registrations. Manage Users and Full School
Management System Operations
Teacher Entity: Use cases of Teacher are Create Timetable Add Exams Add Results. Add
Syllabus
Student Entity: Use cases of Student are View Fees Pay Fees, View Syllabus View Temetable

8|Page
4.2.4. School-Management-System-ER-Diagram
This ER (Entity Relationship)
Diagram represents the model of School Management Systern Entity. The entity-relationship
diagram of School Management System shows all the visual instrument of database tables and
the relations between Students. Teachers, Schools, Registrations etc. If used structure data and to
define the relationships between structured data groups of School Management System
functionalities. The main entities of the School Management System are Schools. Students,
Classes. Teachers Cources and Registrations

9|Page
School Management System entities and their attributes:

Schools Entity: Attributes of Schools are school_id, school_name, school_type,

school_description

Students Entity: Attributes of Students are student_id, student_college_id, student_name,

student_mobile, student_email, student_usemame student_password, student_address

Classes Entity: Attributes of Classes are class_id, class_student_id, class_name, class_room,

class_type, class_description

Teachers Entity: Attributes of Teachers are teacher_id, teacher_college_id, teacher_name,

teacher_mobile teacher_emalt, teacher_username

teacher_password, teacher_address

Cources Entity: Attributes of Cources are course_id, course_student_id, course_registration

course_name, course_type, course_year course _description

Registrations Entity: Attributes of Registrations are registration_id, registration_student_id,

registration_course_id. registration_name registration_type, registration_number,
registration_date registration_description

5. DATABASE DESIGN
5.1. Database Introduction

The details of Schools is store into the Schools tables respective with all tables
Each entity (Registrations, Classes, Cources, Students, Schools) contains primary key and
unique keys. The entity Classes, Cources has binded with Schools, Students entities with
foreign key
There is one-to-one and one-to-many relationships available between Cources, eachers,
Registrations, Schools
All the entities Schools, Cources, Classes, Registrations are normalized and reduce
duplicacy of records
We have implemented indexing on each tables of School Management System tables for fast
query execution.

5.2. Selected Database

10 | P a g e
 5.2.1 Functional and Non-Functional Requirements

Functional Requirements:
Functional
Requirement Description
Data storage and
retrieval The system should allow the storage and retrieval of data in a structured manner.
Data manipulation Users should be able to manipulate and update data within the system.
Data integrity and
security The system should ensure the integrity and security of stored data.
Transaction The system should support transactional operations to maintain consistency
management during data updates.
Scalability and The system should be scalable to accommodate a growing volume of data and
performance perform efficiently under varying loads.
Integration with other
The system should integrate seamlessly with other specified applications to
applications exchange data and functionalities.
There should be a mechanism for regular data backup and a robust recovery
Backup and recovery process in case of data loss or system failure.

Non-Functional Requirements:
Non-Functional
Requirement Description
The system should respond to user requests within 2 seconds under normal load
Performance conditions.
The system should have an uptime of at least 99.9% and minimal downtime for
Reliability maintenance.
All data transmission and storage should be encrypted to ensure the confidentiality
Security and integrity of sensitive information.
The user interface should be intuitive and user-friendly, requiring minimal training
Usability for users to navigate and perform tasks.
The system should be compatible with common web browsers (e.g., Chrome,
Compatibility Firefox) and operating systems (e.g., Windows, Linux).
The system should be designed with modularity and clear documentation to
Maintainability facilitate easy maintenance and updates.
The system architecture should be designed to scale horizontally and vertically to
Scalability accommodate increased user and data loads.

11 | P a g e
6. CONCLUSION
The proposed School Management System aims to revolutionize user
management in educational institutions by introducing automation, efficiency, and accuracy.
With its user-friendly interface and robust features, it is designed to enhance the overall
administration of schools

12 | P a g e