Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

Software Requirements
Specification
for

Student drop Out Analysis

Version 1.0 approved

Prepared by <author>

<organization>

<date created>

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page 3

Table of Contents
Software Requirements Specification for <Project> Page 4

Table of Contents
Revision History
1. Introduction
1.1Purpose
1.2Document Conventions
1.3Intended Audience and Reading Suggestions
1.4Product Scope
1.5References
2. Overall Description
2.1Product Perspective
2.2Product Functions
2.3User Classes and Characteristics
2.4Operating Environment
2.5Design and Implementation Constraints
2.6User Documentation
2.7Assumptions and Dependencies
3. External Interface Requirements
3.1User Interfaces
3.2Hardware Interfaces
3.3Software Interfaces
4. System Features
4.1 User Authentication
4.2 Data Collection
4.3 Drop-out Trend Analysis
5. Other Nonfunctional Requirements
5.1Performance Requirements
5.2Safety Requirements
5.3Security Requirements
5.4Software Quality Attributes
6. Other Requirements
Appendix A: Glossary
Appendix B: Analysis Models
Appendix C: To Be Determined List

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 1

1. Introduction
1.1 Purpose
This Document outline the software requirements for developing a system to analyze student
dropouts in school education,aiming to provide valuable insights for education institutions.

1.2 Document Conventions

This document was created based on the IEEE template for system requirements specification
documents.

1.3 Intended Audience and Reading Suggestions

● Advanced / professional users,engineers or researchers,who want to use this school
dropout analysis for more demanding graph analysis.
● Programmers who are interested in working on the project by further developing it or fixed
existing bugs.
● Testers who test the accuracy of the school drop out analysis.

1.4 Product Scope

System will focus on collecting and analyzing data to identify patterns and potential causes to help
the educational officer to make precise decisions.

1.5 References

www.gcphi.org/users/gchi_srs_document.pdf

2. Overall Description
2.1 Product Perspective
This model was developed by the higher educational offices who only have access.
● They use these models to analyze the data in order to make precise decisions.
● Handles various kinds of data and relevant the data after analysis
● The system will be Indian standalone application interacting with school database together
relevant student information
Software Requirements Specification for <Project> Page 2

2.2 Product Functions

It functions to show the graph of student drop-out rates and analyze the data sets of past student
dropouts.
Tools
Options: user can change categories and visualization options
Language:changes the language
Online documentation and support:Redirect the user to support team
Window
Visualization: display various visualization options.
Category types:allow users to choose different categories i.e. gender caste area financial
background.
\Welcome: This place is the starting page where it allows users to interact through signing in.
Help
check for updates:
About: Displays the information related to the system and user guidelines and rules and regulation
Dependencies: Systems after production stipend on parameters like gender caste is student
academic performance data quantity and privacy and accessibility.

2.3 User Classes and Characteristics

● Typical uses or administration such as higher officials who want to analyze the data
● Advanced or proficient uses such as engineers or researchers work on project project by
further developing it
● School administrations input drop out data

2.4 Operating Environment

Windows,Linux

2.5 Design and Implementation Constraints

Basic constraint: School Dropbox student details.

Assumption: Missing values of data set replaced with repeated values in the particular
School.
Technologies: web development Technologies like (NodeJs, JavaScript, HTML, CSS)
Databases: My SQL database server
language: This system is developed using Python libraries
Software Requirements Specification for <Project> Page 3

2.6 User Documentation

User manual, online help, tutorials, FAQs, glossary, release notes, sample data, training materials.
Common formats: PDF, HTML, video, Markdown. Adhere to accessibility standards like WCAG.

2.7 Assumptions and Dependencies

● This system was developed in Python and therefore required python to be installed
in this application.
● This applies to Windows and LINUX user
● Dependencies: School dropout students data quantity and accessibility

3. External Interface Requirements

3.1 User Interfaces

Implement secure login functionality only for educational administrators.

3.2 Hardware Interfaces

Compatible with standard web browsers.

3.3 Software Interfaces

 MySql Database server.

 Interface with educational databases and data sources.
 Python should be installed on systems.

4. System Features
4.1 User Authentication

 Secure login for different user roles.

 Role based access control (i.e for admin and higher educational officers.)

4.2 Data Collection

 Interface with educational databases.

4.3 Drop Out Trend analysis

 Analyse historical data to identify trends.
 Provide visualization of dropout rates.
Software Requirements Specification for <Project> Page 4

5. Other Nonfunctional Requirements

5.1 Performance Requirements

 Response time should be within 2 seconds for user interactions.

 Appropriate Analysis.

5.2 Safety Requirements

Bug tracker availability, where users can report any bugs they have encountered so that
developers can fix it.

5.3 Security Requirements

Role-based access control.

5.4 Software Quality Attributes

 Due to its well designed system provides flexible interface.

 However, users must already have knowledge related to visualization.

6. Other Requirements
 Database requirements for storing student data and analysis results.
 Internationalization considerations for accommodating diverse educational contexts.
 Legal compliance regarding data privacy and usage regulations.
 Objectives for code reuse to enhance efficiency and maintainability.
Software Requirements Specification for <Project> Page 5

Appendix A: Glossary
 SRS: Software Requirements Specification

 TBD: To Be Determined

Appendix B: Analysis Models

 Data flow diagrams illustrating information flow within the dropout analysis system.

 Class diagrams depicting the structure of software components related to student data
handling.

 Entity-relationship diagrams representing relationships between data entities in the

system.

Appendix C: To Be Determined List

 Data retention policy for student records.
 Algorithm for predicting dropout likelihood.
 Integration method with existing student information systems.
 User roles and access control specifications.