Here's a structured format for your School Management System project document, similar

to the format you provided for the Library Management System:

Darshan University
A Project Report on
“School Management System”

Under the subject

Software Engineering (2301CS405)

B. Tech, Semester – IV

Computer Science & Engineering Department

Submitted By

Student Name: [Your Name]

Enrollment No.: [Your Enrollment No.]
Academic Year: 2024-2025

Internal Guide
Prof. R. B. Gondaliya
Darshan University

Dean-DIET
Dr. Gopi Sanghani
Darshan University

Declaration

We hereby declare that the SRS, submitted along with the Software Engineering
(2301CS405) for entitled “School Management System” submitted in partial fulfillment for
the Semester-5 of Bachelor Technology (B. Tech) in Computer Science and Engineering
(CSE) Department to Darshan University, Rajkot, is a record of the work carried out at
Darshan University, Rajkot under the supervision of R. B. Gondaliya and that no part of any
of report has been directly copied from any students’ reports, without providing due
reference.
(Student name)
Student’s Signature
Date: __________

Certificate

This is to certify that the SRS on “School Management System” has been satisfactorily
prepared by Student name (Enrollment) under my guidance in the fulfillment of the course
Software Engineering (2301CS405) work during the academic year 2024-2025.

Internal Guide
Prof. R. B. Gondaliya
Darshan University

Dean-DIET
Dr. Gopi Sanghani
Darshan University

Acknowledgement

I wish to express my sincere gratitude to my project guide Prof. R. B. Gondaliya and all the
faculty members for their continuous support, suggestions, and valuable coordination in
completing this work.

I would also like to extend my thanks to my parents, friends, and family for their
encouragement, which helped me through the completion of this project. I am grateful to
Darshan University for allowing me to use the resources needed to complete the project.

Once again, I express my heartfelt thanks to everyone involved in making this project a
success.

Thanking You,
Student Name

Abstract

The School Management System is a web-based system designed to manage the various
academic and administrative functions of a school. This system will help the management,
faculty, students, and parents keep track of grades, schedules, fees, and more, providing a
user-friendly interface to simplify the management processes. The system will include
features such as student enrollment, attendance tracking, grade management, fee
management, teacher performance evaluations, and communication between all stakeholders.
This system aims to reduce administrative overhead, streamline processes, and provide a
more efficient and transparent school management system.
Table of Contents
1. Introduction
1.1 Product Perspective
1.2 Product Features
1.3 Functional Requirements
1.3.1 Administrator
1.3.2 Teacher
1.3.3 Student
1.3.4 Parent
1.4 Non-Functional Requirements
1.4.1 Usability
1.4.2 Accuracy
1.4.3 Availability
1.4.4 Maintainability
2. Design and Implementation Constraints
2.1 Use Case Diagram
2.2 Activity Diagram
2.3 Sequence Diagram
2.4 Class Diagram
2.5 Data Flow Diagram
3. External Interface Requirements (Screens)
3.1 Registration Form
3.2 Login Form
3.3 View Grades Form
3.4 School Events Form
4. Database Design
4.1 List of Tables
4.2 Entity-Relationship Diagram
5. Stories and Scenarios
5.1 Scenario: Add New Student
5.2 Scenario: Assign Grades
5.3 Scenario: Track Fee Payments
6. Test Cases
7. References

1. Introduction

1.1 Product Perspective

The School Management System is designed to automate and streamline the administrative
functions of a school. The system aims to provide an efficient platform for managing student
records, teacher information, class schedules, grades, attendance, school fees, and
communication between stakeholders like students, teachers, parents, and administrators. The
system will cater to both academic and administrative requirements and is accessible by users
with different roles.

1.2 Product Features

1.2.1 There are four different types of users in this system:

 Administrator: Manages overall system operations, user accounts, and school-wide

features.
 Teacher: Responsible for managing students' grades, attendance, and communicating
with students and parents.
 Student: Accesses personal academic data such as grades, schedules, and attendance
records.
 Parent: Monitors their child's academic performance, attendance, and communicates
with teachers.

1.2.2 Features for the Administrator:

 Manage user accounts (student, teacher, parent)

 Manage class schedules, subjects, and teacher assignments
 Generate reports on school performance
 Oversee fee management
 Manage school-wide announcements

1.2.3 Features for the Teacher:

 Assign and grade student assignments

 Record and monitor student attendance
 Create and share lesson plans
 Communicate with students and parents
 Generate student performance reports

1.2.4 Features for the Student:

 View academic records, grades, and attendance

 Submit assignments and track their status
 Access class schedules and school events
 Communicate with teachers for academic queries

1.2.5 Features for the Parent:

 Track child's grades and performance

 Monitor child's attendance and behavior
 Communicate with teachers
 Track and manage fee payments

1.3 Functional Requirements

Here’s an expanded functional requirement section with additional functionalities for the
School Management System:

Functional Requirements

Sure! Here are the atomic requirements for all the given functionality, rephrased without
using the words "manage" or "management":

1. Teacher User:

 Class Scheduling: Create and update class schedules.

 Grade Entry: Enter and update student grades and assignments.
 Attendance Recording: Record and update student attendance.
 Communication with Parents and Students: Send messages or notifications to
students and parents about assignments, grades, and class-related information.
 Student Feedback: Provide feedback on individual student progress and
performance.
 Assignment Posting: Post assignments, grade submissions, and track their status.
 Resource Sharing: Share study materials, notes, and resources with students.
 Class Participation Tracking: Monitor student participation during class activities.

2. Student User:

 Profile Viewing: View and update personal details (name, class, contact information).
 Grade Tracking: Access and track grades, assignments, and exam scores.
 Attendance Viewing: View attendance records and track overall attendance.
 Class Schedule Access: Access class schedules, exam dates, and academic events.
 Assignment Submission: Submit assignments and track grading status.
 Discussion Participation: Participate in discussion forums for academic discussions.
 Event Registration: View and sign up for school events, extracurricular activities,
and parent-teacher meetings.
 Teacher Communication: Contact teachers for academic-related questions or
clarification.
 Report Download: Download academic progress reports.
 Fee Tracking: View pending and paid fees and receive reminders.
 Book Request: Request new books or materials to be added to the library.

3. Parent User:

 Child’s Academic Tracking: View and track the child's grades and attendance.
 Fee Tracking: View fee payments and payment history.
  Report Access: Download reports on academic progress and behavior.
 Teacher Communication: Communicate with teachers about academic or behavioral
issues.
 Notification Receiving: Receive notifications about events, parent-teacher meetings,
exams, and assignments.
 Event Registration: Register for school events, parent-teacher meetings, and
extracurricular activities.
 Behavior Tracking: View behavioral feedback and comments from teachers.
 Schedule Viewing: View the child’s class timetable and exam schedule.
 Contact Information Update: Update personal and contact details.
 Activity Approval: Approve or request changes to the child's extracurricular
participation.

4. Principal User:

 School Analytics: Monitor and analyze overall school performance, including grades,
teacher performance, and activities.
 Schedule Approval: Approve class schedules, teacher workloads, and exam dates.
 Staff Evaluation: Conduct staff performance evaluations and generate reports.
 Fee Supervision: Monitor fee payment status and ensure timely payments.
 Strategic Planning: Generate analytics for guiding school planning and decisions.
 Announcement Issuing: Issue announcements about schedule changes, policies, and
events.
 Compliance Checking: Ensure the school adheres to educational and legal
regulations.
 Record Access: Access and ensure the accuracy and security of student and teacher
records.

1.4 Non-Functional Requirements

Here are the non-functional requirements in one line each:

1. Usability: The system should have an intuitive, user-friendly interface, accessible

across devices and multiple languages.
2. Performance: The system should handle concurrent users efficiently, with page load
times under 3 seconds.
3. Availability: The system should ensure 99.9% uptime and only have downtime for
scheduled maintenance.
4. Scalability: The system should support growth in users and features without
performance degradation.
5. Security: Data should be encrypted, with role-based access and multi-factor
authentication for sensitive access.
6. Data Integrity: The system should validate inputs, ensuring data consistency and
providing regular backups.
7. Maintainability: The system should be modular, easy to troubleshoot, and support
regular updates.
 8. Interoperability: The system should integrate with external systems and support
common data formats.
9. Compliance: The system should comply with data privacy regulations (e.g., GDPR)
and educational standards.
10. Backup and Recovery: Automated backups should be implemented with recovery
within one hour of system failure.

2. Design and Implementation Constraints

2.1 Use Case Diagram

A use case diagram representing the functionalities of the School Management System and
interactions with various user roles.

2.2 Activity Diagram

A diagram showing the sequence of actions taken in processes like grade entry, attendance,
etc.

3. External Interface Requirements (Screens)

3.1 Registration Form

Screen for new students, teachers, and parents to register their accounts.

3.2 Login Form

Screen for users to log into the system securely.

4. Database Design

4.1 List of Tables

 Students: ID, Name, Date of Birth, Grades, Attendance, etc.

 Teachers: ID, Name, Subject, etc.
 Parents: ID, Name, Contact Info, Child’s ID, etc.

5. Stories and Scenarios

5.1 Scenario: Add New Student

  A new student is registered in the system, and their records are created in the
database.

6. Test Cases

Test cases for verifying functionalities like login, grade entry, report generation, etc.

7. References

List of books, websites, and academic papers referenced during the project.

This document serves as a comprehensive Software Requirements Specification (SRS) for

your School Management System project. You can customize each section as per your
project requirements, and the structure provided will help you in designing and implementing
the system efficiently. Here is an abstract for the School Management System similar to the
one you provided for the Library Management System:

This abstract highlights the core features and objectives of the School Management System,
focusing on simplifying administrative processes, enhancing user experience, and providing a
digital solution for school management.