Software requirements specification (SRS) on

Student Result Management System

Submitted by: Submitted to:

Name: Sushant Khadka BIKRAM KARKI

Student id: 1910965

Submission Date: June 14th, 2024

1
Contents
1. Introduction .............................................................................................................................................. 3
1.1 Purpose ............................................................................................................................................... 3
1.2 Scope ................................................................................................................................................... 3
1.3 Definitions, Acronyms, and Abbreviations .......................................................................................... 3
1.4 References ........................................................................................................................................... 3
2. Overall Description .................................................................................................................................... 3
2.1 Product Perspective ............................................................................................................................ 3
2.2 Product Functions ............................................................................................................................... 4
2.3 User Classes and Characteristics ......................................................................................................... 4
2.4 Operating Environment ....................................................................................................................... 4
2.5 Design and Implementation Constraints............................................................................................. 4
2.6 Assumptions and Dependencies ......................................................................................................... 4
3. System Features ........................................................................................................................................ 4
3.1 Login System ....................................................................................................................................... 4
3.2 Admin Panel ........................................................................................................................................ 5
3.3 Create/Manage Classes ....................................................................................................................... 5
3.4 Create/Manage Subjects ..................................................................................................................... 5
3.5 Add/Manage Students ........................................................................................................................ 5
3.6 Declare Results .................................................................................................................................... 5
4. External Interface Requirements .............................................................................................................. 6
4.1 User Interfaces .................................................................................................................................... 6
4.2 Hardware Interfaces ............................................................................................................................ 6
4.3 Software Interfaces ............................................................................................................................. 6
4.4 Communications Interfaces ................................................................................................................ 6
5. System Requirements ............................................................................................................................... 6
5.1 Functional Requirements .................................................................................................................... 6
5.2 Non-functional Requirements ............................................................................................................. 6
6. Other Nonfunctional Requirements.......................................................................................................... 7
6.1 Performance Requirements ................................................................................................................ 7
6.2 Safety Requirements ........................................................................................................................... 7
6.3 Security Requirements ........................................................................................................................ 7
6.4 Software Quality Attributes................................................................................................................. 7

2
1. Introduction

1.1 Purpose

The purpose of this Software Requirements Specification (SRS) document is to outline the
requirements for the development of a web-based School Result Management System for
government schools in Nepal. This system aims to streamline the process of managing student
performance records, ensuring accuracy, efficiency, and accessibility.

1.2 Scope

The School Result Management System will provide a comprehensive solution for managing
student performance data. The system will include functionalities such as login, admin panel,
class and subject management, student management, and result declaration. The application will
be developed using PHP, JavaScript, and MySQL, and will run on XAMPP and Mozilla Firefox, or
other platforms after hosting.

1.3 Definitions, Acronyms, and Abbreviations

• SRS: Software Requirements Specification

• XAMPP: A free and open-source cross-platform web server solution stack package
• PHP: Hypertext Preprocessor
• MySQL: Structured Query Language for managing databases
• CRUD: Create, Read, Update, Delete

1.4 References

• Google and group member contributions for initial research and planning.

2. Overall Description

2.1 Product Perspective

The School Result Management System is an independent web application designed to facilitate
the management of student performance records in government schools. It replaces manual
processes with an automated system, reducing errors and improving efficiency.

3
2.2 Product Functions

The main functions of the system include:

• User authentication and role-based access control.

• Administrative panel for managing classes, subjects, and students.
• Tools for declaring and viewing student results.

2.3 User Classes and Characteristics

• Administrators: Manage the entire system, including user roles, classes, subjects, and
student data.
• Teachers: Input and update student performance data, declare results.
• Students: View their performance data and results.
• Parents: Access their child's performance data and results.

2.4 Operating Environment

• Development Environment: PHP, JavaScript, MySQL, XAMPP.

• User Environment: Any device with an internet connection and a web browser).

2.5 Design and Implementation Constraints

• Limited internet connectivity in some regions.

• Limited access to modern hardware in government schools.

2.6 Assumptions and Dependencies

• Users have basic knowledge of operating a web browser.

• Schools have minimal access to the internet and basic computing infrastructure.

3. System Features

3.1 Login System

Description: Secure login functionality for different user roles (administrators, teachers,
students, parents).

Requirements:

• Users must authenticate using unique credentials.

• Password encryption for security.

4
3.2 Admin Panel

Description: Centralized control panel for administrators to manage the system.

Requirements:

• Manage user roles and permissions.

• Access to all functionalities (class, subject, student management).

3.3 Create/Manage Classes

Description: Functionality to create and manage class records.

Requirements:

• CRUD operations for classes.

• Assign students and subjects to classes.

3.4 Create/Manage Subjects

Description: Functionality to create and manage subject records.

Requirements:

• CRUD operations for subjects.

• Assign subjects to classes.

3.5 Add/Manage Students

Description: Functionality to add and manage student records.

Requirements:

• CRUD operations for students.

• Assign students to classes and subjects.

3.6 Declare Results

Description: Functionality for teachers to input and declare student results.

Requirements:

• Input marks/grades for students.

• Generate and publish result reports.

5
4. External Interface Requirements

4.1 User Interfaces

• Web-based graphical user interface accessible via web browsers.

• Responsive design for access from various devices.

4.2 Hardware Interfaces

• Basic computing devices (PCs, laptops, tablets).

• Internet connectivity.

4.3 Software Interfaces

• XAMPP for local server setup.

• Mozilla Firefox for accessing the application.

4.4 Communications Interfaces

• HTTP/HTTPS protocols for web communication.

5. System Requirements

5.1 Functional Requirements

• User Authentication: Users must be able to log in securely.

• Admin Management: Administrators must be able to manage all aspects of the system.
• Class Management: Administrators and teachers must be able to create and manage class
records.
• Subject Management: Administrators and teachers must be able to create and manage
subject records.
• Student Management: Administrators and teachers must be able to add and manage
student records.
• Result Declaration: Teachers must be able to input and publish student results.

5.2 Non-functional Requirements

• Usability: The system should be user-friendly and easy to navigate.

• Reliability: The system should be reliable with minimal downtime.
• Performance: The system should perform efficiently under normal usage conditions.
• Supportability: The system should be easy to maintain and update.

6
6. Other Nonfunctional Requirements

6.1 Performance Requirements

• The system should handle concurrent access by multiple users without significant
performance degradation.

6.2 Safety Requirements

• Regular data backups to prevent data loss.

• Secure data storage and transmission to protect student information.

6.3 Security Requirements

• Implement strong password policies and encryption for user data.

• Regular security audits and updates.

6.4 Software Quality Attributes

• Maintainability: The code should be well-documented and modular.

• Scalability: The system should be scalable to accommodate increasing numbers of users
and data.