Software Requirements
Specification
for
PholPotro – Web-based
School Result Management
System
Version 1.0 approved
Prepared by Md Imran Nazir Udoy
Clariti Soft
11.07.2025
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page 2
Table of Contents
Table of Contents ii
Revision History ii
1. Introduction 1
1.1 Purpose 1
1.2 Document Conventions 1
1.3 Intended Audience and Reading Suggestions 1
1.4 Product Scope 1
1.5 References 2
2. Overall Description 2
2.1 Product Perspective 2
2.2 Product Functions 2
2.3 User Classes and Characteristics 2
2.4 Operating Environment 3
2.5 Design and Implementation Constraints 3
2.6 User Documentation 3
2.7 Assumptions and Dependencies 3
3. External Interface Requirements 3
3.1 User Interfaces 3
3.2 Hardware Interfaces 3
3.3 Software Interfaces 3
3.4 Communications Interfaces 3
4. System Features 4
4.1 Authentication & Roles 4
4.2 Super Admin Panel 4
4.3 Teacher Panel 5
4.4 Grade & GPA Engine 5
4.5 Student Result View 5
4.6 Basic Reports 5
4.7 Better Print 5
4.8 Mobile-Friendly Interface 5
4.9 Attendance Tracking 5
4.10Fees & Payment Tracking 6
4.11Parent WhatsApp/SMS Alerts 6
5. Other Nonfunctional Requirements 6
5.1 Performance Requirements 6
5.2 Safety Requirements 6
5.3 Security Requirements 6
5.4 Software Quality Attributes 6
5.5 Business Rules 7
6. Other Requirements 7
Appendix A: Glossary 7
Appendix B: Analysis Models 7
Appendix C: To Be Determined List 7
Software Requirements Specification for <Project> Page 3
Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 1
1. Introduction
1.1 Purpose
This document specifies the software requirements for the “PholPotro” web-based school result
management system. It outlines the core features, interfaces, constraints, and performance
expectations for a multi-user platform that enables teachers to input marks, automatically convert
them to grades and GPA, and allow students to view and print their results. The scope includes
result management, role-based access control, and basic extensions like attendance and fee
tracking.
1.2 Document Conventions
● All requirements are uniquely numbered (REQ-#).
● High Priority features are core functionalities needed for MVP delivery.
● Medium Priority features are important but can be deferred if time-limited.
● Low Priority features are planned for future expansion.
1.3 Intended Audience and Reading Suggestions
● Developers: Implement features according to functional and non-functional requirements.
● Testers: Use the functional requirements to design and execute test cases.
● Stakeholders: Review system features to ensure alignment with needs.
● Project Managers: Use the priority levels to set timelines and milestones.
1.4 Product Scope
PholPotro will allow:
● Teachers to securely enter marks only for their assigned subjects.
● Automatic conversion of marks to grades, GPA, and student rankings.
● Students to view results via roll number and class search.
● Administrators to manage users, subjects, grading criteria, and generate reports.
Future enhancements include attendance tracking, fee management, and automated parent
notifications.
Software Requirements Specification for <Project> Page 2
1.5 References
● IEEE SRS Template (IEEE Std 830-1998).
● Bangladesh GPA Grading System Guidelines.
2. Overall Description
2.1 Product Perspective
PholPotro is a standalone web application designed for educational institutions. It may integrate
with external SMS/WhatsApp APIs for parent notifications and hardware devices (e.g., fingerprint
scanners) for attendance in later phases.
2.2 Product Functions
● Authentication and role-based access.
● Marks entry and editing (Teacher).
● Automatic grading and GPA calculation.
● Result search and printing (Student).
● Admin management of users, subjects, and grading rules.
● Attendance and fee tracking (future phase).
● Parent alerts via SMS/WhatsApp (future phase).
2.3 User Classes and Characteristics
Super Admin: High technical authority; manages entire system.
Teacher: Limited to assigned classes/subjects; moderate technical skills.
Student/Parent: View-only access; minimal technical skills.
Software Requirements Specification for <Project> Page 3
2.4 Operating Environment
Backend: Python (Django).
Frontend: HTML/CSS/JavaScript (React ).
Database: PostgreSQL/MySQL.
Hosting: Cloud-based (Heroku, Vercel, AWS).
Compatible with modern browsers and responsive for mobile devices.
2.5 Design and Implementation Constraints
● Must use secure authentication .
● Support mobile responsiveness.
● Must handle at least 500 concurrent users.
● Follow local grading policy.
2.6 User Documentation
● Web-based user manual.
● Admin quick start guide.
● Teacher mark-entry guide.
2.7 Assumptions and Dependencies
● School will provide student and subject data.
● Internet connection required for all operations.
● SMS/WhatsApp services require third-party integration.
Software Requirements Specification for <Project> Page 4
3. External Interface Requirements
3.1 User Interfaces
● Login page.
● Dashboard for each role.
● Marks entry forms (Teacher).
● Result search & display page (Student).
● Printable report card view.
3.2 Hardware Interfaces
● Optional biometric devices for attendance tracking (future).
3.3 Software Interfaces
● Database connection.
● SMS/WhatsApp API for notifications (future).
● PDF generation library for print/export.
3.4 Communications Interfaces
● HTTPS for all communications.
● API-based interactions between frontend and backend.
4. System Features
4.1 Authentication & Roles (High Priority)
Secure login/logout.
Role-based dashboards and permissions.
Software Requirements Specification for <Project> Page 5
4.2 Super Admin Panel (High Priority)
● Manage teachers, students, subjects.
● Assign teachers to subjects.
● Set grading rules.
4.3 Teacher Panel (High Priority)
● Enter marks for assigned subjects only.
● Edit existing marks.
4.4 Grade & GPA Engine (High Priority)
● Convert marks → percentage → grade.
● Calculate GPA and rank.
4.5 Student Result View (High Priority)
● Search results by Roll + Class.
● Printable mark sheet.
4.6 Basic Reports (Medium Priority)
● Average marks per subject.
● Top students list.
4.7 Better Print (Medium Priority)
● PDF export of results.
4.8 Mobile-Friendly Interface (Medium Priority)
● Responsive UI for mobile devices.
4.9 Attendance Tracking (Low Priority)
Software Requirements Specification for <Project> Page 6
● Record daily attendance (future).
4.10 Fees & Payment Tracking (Low Priority)
● Track student payments (future).
4.11 Parent WhatsApp/SMS Alerts (Low Priority)
● Send notifications for irregularities or result release.
5. Other Nonfunctional Requirements
5.1 Performance Requirements
● Load time ≤ 3 seconds on standard broadband.
● Handle 500+ concurrent users.
5.2 Safety Requirements
● Prevent accidental deletion of student data via confirmation prompts.
5.3 Security Requirements
● Password hashing (bcrypt/argon2).
● Role-based access control.
● Secure API endpoints.
5.4 Software Quality Attributes
● Maintainability: Modular architecture.
● Usability: Simple forms and clear navigation.
● Reliability: 99% uptime target.
5.5 Business Rules
Software Requirements Specification for <Project> Page 7
● Only assigned teachers can edit marks for their subjects.
● Grade thresholds must follow institution policy.
6. Other Requirements
● Database backup every 24 hours.
● Export results in CSV/PDF formats.
Appendix A: Glossary
● GPA: Grade Point Average.
● SMS: Short Message Service.
Appendix B: Analysis Models
● ER diagram and Use Case diagram (to be created during design).
Appendix C: To Be Determined List
● Choice of SMS/WhatsApp API provider.
● Final decision on backend stack.