SCHOOL MANAGEMENT SYSTEM

Software Requirements Specification

SDHInfotech Pvt. LTD.

Table of content

Table of contents for a SRS Document

1. Introduction
 Purpose
 Scope
o Front end user
o Admin
 Definition

2. Overall description
 Product Perspective
 Product Function
 Product Module
 User Characteristics
o Admin
o User
 Constraints
 Assumptions and Dependencies

3. Specific requirements
 External Interface Requirements
o Communication Interfaces
o Software Interfaces
o Hardware Interfaces
 Functional requirements
o Web Application
o Splash Screen
o Welcome screen
o Log in Screen
o Forgot Password
o Sign Up Screen
o Shop By Category
o Search
 o My Notification
o Setting
o About Us
o FAQ
o Contact Us
o Terms and Condition
o Logout
o User Management (Admin)
o Cash back Management
o Cash back Redemption Request Management
o Report
o Promotion Management
o General Setting
o Contact from Management
o Static Content Management
 Design Constraints
o Software Languages
o Development Tools
 Logical Database Requirements
 Software System Attributes
o Platform Support
 Frontend Marketing Website
o Browser Compatibility
o Mobile Application
 Reliability
 Availability
 Security
 Maintainability
 Other Requirements
4. Acceptance of SRS.
1. INTRODUCTION

School Management Software is a complete and customized solution for a school handling
regular management work. It can be very helpful to maintain its student detail, fees detail, ,
Attendance detail, Teachers and other Employee detail, Certificate details, Time Table and
Exam scheduling, Exams and Question Paper detail and Transportation Detail. This software
includes the management of students, Teachers, Accounts, Transportation, library, Fees,
Exam, Time Table, Inventory, Salary and its respective reports with administrative module
to provide better security. User-friendly menus can easily generate all the reports.

 PURPOSE

The purpose of this document is to define all the requirements in details of “School
Management”. This document also defines user characteristics, user interfaces and
external interfaces with other system.

 SCOPE

There are two types of users who will use the application:

 Front End User (Student and Guardian)

 Admin and Sub-Admin (Teachers, HODs, In-charges).

Application will allow both types of users to Login, Register and Manage
their profile respectively. Front End User can join the application via App
or Website. Front End user can visit the website, surf the various
contents like gallery, home page, different notifications, and apply online
for admissions.
The registered user can view the profile of his ward and access other
various information related to his/her ward.
On the other hand the admin will manage the sub admin and manage all
the front end users and students.
 Modules:-
We have designed the following modules based on the needs of different
schools.
1. Student Management:-
This module consists of following components:
o Students Registration
o Students Personal Details
o Students Parents Details
o Students Certificates/ TC management
 o Class And Section Management
o Student Attendance
o Student Examination
o Student Homework Specification
2. Fees Management
o Fee Master
o Class-wise Fee
o Daily Fee Collection
o Monthly Fee Collection
o Admission Fee Collection
o Other Miscellaneous fee Collection like Transportation Fee, Sports Fees, and
Lab Fees etc.
o Fee Fine Collection
o Printing Of Fee Receipt
o Exam Terms Fee Collection
o Fee Defaulter
3. Payroll Management
o Employee Master
o Allocation Of Allowances, Deductions and Leaves
o Attendances Entry
o Maintaining of Leave Record
o Processing Of Monthly Salary
4. Human Resource/Recruitments
o Advertisement Editor
o CV Viewer
o Maintaining Interview Schedule
o Maintaining Interview Results
o Final Recruitments
o Direct Recruitments
o Department Allocation
5. Question Paper
o Question Paper Editor
o Question Paper Browser
o Mark sheet Entry
o Processing Results
6. Reports
o Fees Generation Report
o Computerized Report Card
o Student Identity Card
 Definitions :-
 Front-End User-.
 Admin-Admin will have full control of the app via App Management Console Panel as well
as website .

2. Overall description-
This section will give an overview of the whole system. The system will be explained
in its context to show how the system interacts with other systems and introduce
the basic functionality of it. It will also describe what type of stakeholders will use
the system and what functionality is available for each type. At last, the constraints
and assumptions for the system will be presented.

 Product Perspective

This system will consist of two parts, Mobile Application/website and Admin
Panel. Front end User will use Mobile Application/website where Admin will
be able to manage different resources for the mobile application from the
Admin Panel.
Mobile application will utilize web services which are hosted on a web
server. Mobile application will not access the data directly. All the data will
be stored in database on the web server. However, mobile application may
store data temporarily for faster accessing of data.

Please refer to the below block diagram for reference.

 Product functions-
 Front end user will use the mobile/web application to access all the
functionality of the application. Users will be able to browse the various
information of the college provided in the website. The user has to log-in in
order to view the different information of his/her ward. User can also apply
online for new admission.

Admin panel will allow Admin user(s) to manage all the data for the
application like managing records of registered students, teachers and other
staff members, constant values those are to be used in the mobile/web
application. Admin also, create Sub-Admin and give role management
authority for adding Details.

Product Module

 User Characteristics

There are two types of users those will access the mobile application, Front end
Users and Admin.

o Admin-Admin will have full control over the app via App Management Console
Panel. Admin user will be able to access the Admin Panel from provided login
credentials.
o User-Users will be able to browse the list of all the projects/plots according to the
locations. Once the order is accepted, cash back will be added to the user’s account
after the approval of admin and will receive the notification for the same on his/her
mobile.
 Constraints
Internet connection is required to run mobile application on the mobile.
Since, application often requires retrieving and sending data to the web
server. Mobile application also depends on device’s GPS service to find the
distance of the merchant from the users and display it on the map.

 Assumptions and Dependencies

Mobile application will be constrained by the performance of the hardware
of the device, it is running on. Application may not launch or crash in case of
required resources is not available on the mobile device.

3. Specific requirements
This section contains all of the functional and quality requirements of the system. It
gives a detailed description of the system and all its features.
  External interface requirements- This section provides a detailed
description of all inputs into and outputs from the system. It also gives a
description of the hardware, software and communication interfaces and
provides basic prototypes of the user interface.

o Communication Interfaces- The communication between the different

parts of the system is important since they depend on each other. However,
in what way the communication is achieved is not important for the system
and is therefore handled by the underlying operating systems for both the
mobile application and the web portal.

o Software Interfaces-The mobile application communicates with the GPS

application in order to get geographical information about where the user is
located and the visual representation of it, and with the database in order to
get the information about the location. The communication between the
database and the web portal consists of operation concerning both reading
and modifying the data, while the communication between the database and
the mobile application consists of only reading operations.

o Hardware Interfaces -Since neither the mobile application nor the web
portal have any dedicated hardware, it does not have any direct hardware
interfaces. The physical GPS is managed by the GPS application in the mobile
phone and the hardware connection to the database server is managed by
the underlying operating system on the mobile phone and the web server.

 Functional Requirements
This section includes the requirements that specify all the fundamental actions
of the software system.

o Web application

Title Download application

Actor Front End User

Description  User will download the application from the Play

store
o Splash Screen

Title Splash screen

Actor Front End user

Description  Splash screen will be the initial screen of the application.
 When user taps on application icon, this screen will appear
to him/her.
 User can select the Location of Services.
 Login for existing customer is also available in this screen.

o Welcome screen

Title Welcome screen

Actor Front End User

Description  Your selected location is showing on the Top.

 Promotional Offers are also display on this page.
 You can select the category of shopping in this page.
 In the bottom of the screen- Home, Categories,
Search, Offers and Basket option are available.

o Login screen

Title Login

Actor Front End User

Description  System will allow users to log into the mobile application
using their email address and password
 After clicking on the login button, system will validate
credentials by consuming web services and will redirect
user to his/her respective home screen.
 System will allow users to log into the application using
their Face book account or Google Account. In that case,
user will need to grant access to some of his/her profile
information from Face book or Google.
 For the mobile number verification, OTP Feature will be
used. Client will provide the SMS API for this purpose.
 .

o Forgot password –

Title Forgot password

Actor Front End User

Description  Once user will click on submit button then system will
verify the entered email from the database. If email will
be in wrong format or does not exist in database then
system will generate the error message “Please enter
valid email” Or “Email does not exists in database”
respectively.
 OTP Will be received on Email id and Mobile Number.
After the valid OTP submission.
 You can create a new password for further login.

o Signup screen -

Title Sign up

Actor Front End User

 Description  By clicking on “Signup” button from the
Welcome Screen user will be redirected to the
registration page.
 On registration screen, user would be able to
register him/her by filling the registration form.
 Following will be the detail information:
○ First Name (Text type Alpha validation)
○ Last Name (Text type Alpha validation)
○ Email ID (Text type alphanumeric validation
with special characters)
○ Password (Minimum 8 character)
○ Referral Code (Optional)
 By click face book or Google Button user also
creating a user account.
 All the above fields are mandatory field.
 There will be a “Submit” button on which user
needs to click to save the above detail
information.

o Shop by Category-

Title Shop by category

Actor Front End User

Description  User can shop by category; all the main

categories have sub categories. This help to
user to find out the entire product by category.
 User would be able to order the list of product
which will be associated with the portal.
 User can go back to Browse product screen by
clicking on the back button.
 User will be redirected to the Filter screen where he
can search the list of product depending on the
following options:

○ Cash back%
○ Area/location
○ Price range

o Search-
 Title Search

Actor Front End User

Description  You can Search all the product by name or by

barcode scanner.
 Big Basket Apps has special feathers that by
which you can easily search your product by
scanning the product bar code.

o Offer screen-

Title Offer section

Actor Front End User

Description  In offer section user and see and select all

the weekly, monthly and daily promotional
offers. Like cash back offer on different
payment app (Pay tm, Airtel Payment bank,
Freecharge, Mobiwiki etc.)
 Also user and see and select “Chatpata Offer”
Like (buy 1 Get 1 Free).
 Offers on special category product like
personal care, life style, gamming, snacks,
starters etc.
 The entire offer currently running in this
App.

o About us :-

Title About us
Actor Front end user

Description  By Clicking on “About Us” link on the home screen of

the application, by selecting the “More” option fro
m the footer of the home page.
 Also, User would be able to view any associated ima
 ge.
 Admin will have the privilege to edit the content pr
ovided in this screen and also he/she will be able to
save the changed content which will be displayed t
o the User in the frontend of the application.

o FAQ:

Title FAQ
Actor Front End User
Description  On clicking this link from the “More option” user woul
d be redirected to FAQ Page.

o Contact us:-

Title Contact us

Actor Front End User

Description  User would be able to click on “Contact Us” link prese

nt on the home page under the “More tab”.
 By clicking on which user would be able to go through
the screen where he/she can view content regarding
the contact information to the user.
 User would also be able to view any associated image.

Image of map will display the location of the Admin’sO

ffice.
 This section will be managed by the Admin of the app
lication. .
 The page would contain the Contact Us email link fro
m where user can contact the admin.
 This page will consists of the simple form with below
given details:
o Name (Text type Alpha validation)
o Email ID (Text type Alphanumeric valid
ation)
o Contact Number (Text type numeric vali
dation)
o Enquiry (Text type Alphanumeric valida
tion)
  By filling the above given detail and clicking on “Send
message” button, he/she will be able to Contact the A
dmin.
 Admin will also have the privilege to edit the content
provided for the user in the screen of the application.
 By clicking on the “save” button all the edited content
will be saved and thus displayed in the frontend.

o Term and condition :-

Title Term and condition

Actor Front end user

Description On clicking this link in the menu bar the user would be redirected
to Terms and conditions page.

o Log out:-

Title Logout

Actor Front End User

Description  Users can logout from the application from the option give
n in the bottom of side navigation menu.
 Logging out from the application will close a user session a
nd user will be redirected to login screen.

o User management:-

Title User management

Actor Admin

Decription  In this section of the application, Admin will have the privi
lege to manage the Users.
 Users list will be provided in the User Management panel.
 Also, screen has the link to add new user and each user in
the list will have two links alongside their name for editing
and deleting the users.
 Admin will also be facilitated to track all the information
of the Users from their profile.
 Admin will be able to add, Edit and Delete User as describe
d below:
Add new User:
 Admin will have to click the link of “Add new User”
.
 By clicking on that link admin will be able to enter i
n the new screen where he/she will have to fill the
information for adding new user.
Below will be the information:
 Name (text field)
 Username (text field)
 Email ID (text field)
 Password (text field)
 By clicking on the given “Save”button, Admin will b
e able to create a new User. User would be come to
know regarding his/her account creation on their r
egistered Email ID along with his login credentials.
Edit a user:
 Admin will have to click on the “edit”
link available on alongside of the user
whose details will be edited .
 By clicking on the link admin would be
able to redirect the user edit page
where the below information will be
avaliable in editable form:
 Name
 Username
 e-mail id
 password
by clicking on the given “save” button,
admin will be able to edit the
information of the user.

Delete a user:
 Admin will have to privilege to delete
the existing user .
 Admin needs to click on the “delete”
link available alongside the user in the
user list.
o Cashback management:-

Title Cashback management

Actor Admin

Description  Admin would be provided with a panel where he would

be able to manage the Cashback request for users when
They submit bills for associated merchants.
 On the panel, admin will see the status of Cashback req
uest.
 Based on the activities performed by admin, the concern

Cashback will be added in the user's account as mention

ed in user’s cashback section.
 Admin to view and edit the live cashback transaction det
ails, including: date/time, transaction amount, cashback
amount, commission amount, user ID/mobile no, Merch
ant name/ID, and transaction status.

o Cashback redemption request management:-

Title Cashback redemption request mangement

Actor Admin
Description  Admin would be provided with a panel where he would b
e able to manage the Cashback redemption request.
 On the panel, admin will see the status of redemption req
uest: pending, successful, failed, cancelled.
 Admin can change the status of redemption as per the sce
nario and user will be notified on the app for the same stat
us change.

o Reports:-

Title Report

Actor Admin
Description  The admin will be able to generate monthly or specific ti
me period report for user or cumulative data for the com
plete system.
 Admin can generate monthly cashback report for each en
d user and go through.
 The purpose of this report is to serve the purpose of colle
ction of commission from the concerned merchant
 User will also receive a monthly statement for the cashba
ck received
 Merchants will also receive a monthly statement over em
ail for the bills and cashback associated with them.

o Promotion management:-

Title Promotion managemnt

Actor Admin

Description  The admin will be able to create promotional offers in whic

h admin can offer more Cashback for the particular time pe
riod.
 Admin can post promotion here which will be visible in ap
p.
 Admin will change the general percentage of cashback or s
pecific to particular merchant.

o General setting

Title General setting

Actor Admin
Description The admin will be able to set following standards from the sett
ings
 E- mail formats
 general cashback percentage
 threshold amount for reimbursement request
 other general setting

o Contact from management

 Title Contact from managemnt

Actor Admin

Description  Once in front end any visitor fills the contact form, an ackno
wledgment email will be sent to that visitor.
 In admin panel, there is a feature that allows admin to see al
l contact inquiries and can also reply by sending an email fr
om same section.

o Static content managemnt-

Title Static content management

Actor Admin

Description Admin can edit all static pages and its content from admin
panel like:
o About Us
o FAQ
o Contact Us
o Privacy Statement
o T&C
o Blog (Text field to set URL of Eatback Facebook Page) Static
content in the destination section will also be managed
from this section where the admin personnel can add any
content reference links or URL links for ease of user to pre-
plan all the required .

 Design constraints :

o Software Languages:

Php 7.2

o Development Tools:

IDE & Netbeans

 Logical database requirement

A logical database can stretch over multiple physical hard disks and information files. The
data storage unit is still a single database for information retrieval purposes. To have a logi
cal database, all given hard disks and information files must be accessible from a single sou
rce. Currently, application has no such requirements.

 Software system attributes

o Plateform support :

This section provide details for the platforms on which the application will be supported.

 Frontend marketting website

Responsive : Yes

o Browser compatibility:

Browser name Supported version

Internet explorer
Mozilla firefox
Google chrome
Safari (android)

o Mobile application

Plateform Devices and ios version

Android (PHp) Latest version 5.x

 Reliability

All modules will be tested individually in Unit Testing, and then, Integration Testing will be
performed to test complete system. Application will be tested under several test environme
nts and test data to ensure reliability of the overall system.

 Availability

However, application will be available and up for all the time . But application can goes
offline or in read-only mode in certain cases like maintenance, recovery etc

 Security
All the passwords will be encrypted using oneway encryption algorithm. All sensitive infor
mation will be encrypted before entering into network and will be decrypted back by the re
ceiver into usable information to avoid eavesdropping.

 Maintainability

All codes must be written in standard design patterns by following modern code design me
thodologies in a way it will require as much as less rework when new features or changes a
re introduced.

 Other requirements

No other requirements have been identified so far.

4 Acceptance of SRS
This SOW, in conjunction with the Agreement shall upon execution by both parties, constitu
te the complete and exclusive agreement between client and Singsys with respect to the co
nsulting services described herein. Unless and until such mutual execution, neither party s
hall have any obligation to the other hereunder.

IN WITNESS WHEREOF, THE PARTIES HAVE AGREED TO THIS SOW AS EVIDENCED BY

THEIR SIGNINGS BELOW

A TO Z…………………. SDH INFOTECHPVT.LTD.

By:______________________________ By:_____________________________

Signature: ________________________ Signature: ________________________

Title:_____________________________ Title:_____________________________

Date:_____________________________ Date:______________________________