Software Requirements Specification
(SRS)
School Management System
Name: Syed Adeel Haider
Roll No: 221240
Subject: BSSE(A)
Semester:5th
Course: Software Req
Table of Contents
1. Introduction
2. Overall Description
3. Functional Requirements
4. Non-Functional Requirements
5. System Models
6. Assumptions and Dependencies
1. Introduction
This Software Requirements Specification (SRS) document provides a comprehensive
overview of the School Management System requested by the client Abdul Basit. It outlines
the functional and non-functional requirements of the system, aimed at optimizing school
operations, enhancing communication between stakeholders, and leveraging technology to
improve the overall educational experience.
2. Overall Description
The School Management System will automate key administrative tasks and improve the
management of various aspects such as attendance tracking, timetable generation, student
performance analysis, and communication between parents and teachers. The system will
also include a virtual classroom integration for remote learning, making it a hybrid solution
for both in-person and online education.
3. Functional Requirements
3.1 Smart Attendance System
The system will use facial recognition technology to mark student attendance automatically.
It will eliminate manual attendance processes and store attendance records in the system.
3.2 Automated Timetable Generator
The system will automatically generate timetables for each class and teacher based on their
availability and predefined constraints. It will optimize scheduling to avoid conflicts and
balance workloads.
3.3 AI-based Student Performance Analysis
This module will analyze student academic data and provide personalized performance
reports. Based on the analysis, the system will suggest areas of improvement for each
student, making it easier for teachers to offer targeted assistance.
3.4 Parent-Teacher Interaction Module
The system will have a dedicated platform where parents and teachers can communicate.
Parents will receive real-time updates on their child’s progress and can initiate feedback
sessions with teachers through this platform.
3.5 Virtual Classrooms Integration
The system will seamlessly integrate with virtual classroom tools (e.g., Zoom, Google
Classroom) to facilitate remote learning. Teachers can schedule online classes and manage
virtual lessons through the system.
3.6 Behavioral Tracking Module
This feature will allow teachers to track student behavior and disciplinary actions. It will
store records of extracurricular activities, achievements, and behavioral issues, providing a
holistic view of student development.
4. Non-Functional Requirements
4.1 Performance: The system should support up to 5000 students and handle up to 100
concurrent users.
4.2 Security: All student and school data should be encrypted and protected with role-based
access control.
4.3 Usability: The system should have an intuitive interface, allowing users to perform tasks
with minimal training.
4.4 Scalability: The system should be scalable to support more schools and increased data
storage.
4.5 Reliability: The system should maintain 99.9% uptime to ensure smooth school
operations.
5. System Models
The system model will include use case diagrams, class diagrams, and activity diagrams.
These diagrams will offer a visual representation of the system’s architecture and its
workflows.
6. Assumptions and Dependencies
The system assumes the availability of internet connections for cloud-based services such
as facial recognition and virtual classroom integration. It depends on external APIs for AI-
based performance analysis and timetable generation.