SYSTEM REQUIREMENT SPECIFICATION
SCHOOL FEE MANAGEMENT SYSTEM
BY: ROYSTONE LICHA WERE
REG NUMBER -19/02496
Contents
1. Introduction ......................................................................................................................................... 3
1.1 Purpose .......................................................................................................................................... 3
1.2 Intended audience and reading suggestions .................................................................................... 3
1.3 Project Scope ................................................................................................................................. 3
2. Overall Description.............................................................................................................................. 4
2.1 Product Perspective........................................................................................................................ 4
2.2 Product Features ............................................................................................................................ 4
2.3 User classes and characteristics ...................................................................................................... 5
2.4 Operating Environment .................................................................................................................. 5
2.5 Design and implementation constraints .......................................................................................... 5
2.6 User documentation ....................................................................................................................... 5
2.7 Assumption And Dependencies...................................................................................................... 6
3. System Features ................................................................................................................................... 6
Business Use Case #1: Requirements of the administrator .................................................................... 6
Business Use Case#2: Requirements of the Accountants ...................................................................... 7
4. External Interface Requirements ......................................................................................................... 8
4.1 User Interface ................................................................................................................................ 8
4.2 Hardware interfaces ....................................................................................................................... 8
4.3 Software Interfaces ........................................................................................................................ 8
4.4 Communication interfaces.............................................................................................................. 8
5. Non-functional Requirements .............................................................................................................. 8
5.1 Performance Requirements ............................................................................................................ 8
5.2 Safety Requirements ...................................................................................................................... 8
5.3 Security Requirements ................................................................................................................... 9
6. Other Requirements ............................................................................................................................. 9
6.1 APPENDIX A ............................................................................................................................... 9
6.2 APPENDIX B : GLOSSARY ................................................................................................................ 9
7. REFERENCES.................................................................................................................................... 9
1. Introduction
1.1 Purpose
The purpose of this document is to develop a system to manage school fee data in Saint Kevin Hill
Academy.
1.2 Intended audience and reading suggestions
This project is a prototype for the fee management system and is restricted within the school premises.
This is useful to the fee management staff and the whole school.
1.3 Project Scope
The purpose of this fee management system is to ease school fee management and create a convenient
and easy to use environment for students who need their fee information
The system is based on a database that contains details for various students who are registered in the
school premises.
We will have a database that is relational to the accountant and the administrator who are the two ends
that will interact in the system
Also a comfortable user experience will be provided to the staff, which will use the system.
2. Overall Description
2.1 Product Perspective
This school system is a replacement of a manual system that was being used to manage fee information.
The diagrams describes the high level management of the system
Part 1 Creation and maintenance off adding student details
Accountan
t clicks on
add new
student
Data is
filled
S1
S2
START
Submit
button is
hit
S3
STOP
Part 2 creation and maintaining and modifying student fee information
Accountan
t clicks on
edit
student
S1
START
Data is
modified
Submit
button is
clicked
S1
S1
2.2 Product Features
The software package is expected to offer the following services
a)
b)
c)
d)
To facilitate the maintenance of imported records of students currently studying in the school
Provides contact details of students to reach them when needed
To keep track on the amount of fees paid by each student
Add or modify student details
START
2.3 User classes and characteristics
Administrator
In the aspect of the students, the administrator will create new accountants profiles that will manage
students.
The administrator will have complete control over the Accountants who will be managing the students
Accountant
This user will be able to add students into the database system, and create profiles. The accountant can be
contacted by the students when information in the system is wrong for it to be changed.
Students
This user will only view what the final information is and will not be able to make changes alone.
2.4 Operating Environment
The software package is expected to work in the following atmosphere
-Operating System Windows 10
-Eclipse IDE
-Java
-MySQL
2.5 Design and implementation constraints
The design time constraints are
a) The software package should be designed to handle the access of seven accountants, one
administrator and 150 students concurrently
2.6 User documentation
a) The software will come with a user manual as a guide to the users
b) Analysis, design and test cases of the software will offered with the system
2.7 Assumption And Dependencies




We assume that the office personnel do all data entry based on correct values
We assume the computers that will use the system will be part of the college LAN
We assume administrators will be careful in deleting or modifying information knowingly or
unknowingly will cause inconsistency
Accountants are assumed to have badic computer knowledge
3. System Features
Business Use Case #1: Requirements of the administrator
3.1 Adding Accountants into the database
3.1.1 Description and Priority




To add new accountants into the database
Assigning passwords and username
Viewing and modifying accountants details
Assigning username to accountants
3.1.2 Stimulus/Response sequence
Stimulus from the user
Response from the software
1
Admin logs in
2
Admin choses to add an accountant
3
Admin will fill all user details
4
If an error occurs
System will validate the user-id
and password
System will ask for the
registration details and he/she will
be added to the database
Password is generated same with
the username and may be changed
which is recommended
Initial page will be shown again
5
Admin chooses to view an existing accountants profile
Authentication will be performed
and admin will be allowed or not
6
Admin can Modify an existing accountants profile
7
If an error is displayed, the admin re submits the details
8
Admin can choose log out
Authentication will be performed
and admin will be allowed to
modify or not
System will show initial screen to
the administrator
System will log the admin out
Business Use Case#2: Requirements of the Accountants
Adding, editing and viewing students in the database
i)



Description and priority
Add new students into the database
Assigning username and passwords to the students
Modifying student details
ii)
Stimulus/response
Stimulus
Response
1
Accountant logs in
2
Accountant can choose to add student
3
Accountant will fill all the blank boxes
4
Accountant can choose to view student
5
Accountant can choose to edit student details
6
Accountant can choose to log out
The system authenticates the credentials and
show an error if the they are wrong
System will ask for the registration details to be
added to the database
System will validate if there is an existing
student with the same name
The system will show a list of existing students
in the database
Roll number will be asked and the accountant
can modify details
The system will logout
4. External Interface Requirements
4.1 User Interface
The set of user interface consist of.
i)
ii)
iii)
iv)
v)
Gui to log in in respective accounts
Add and modify student details
Access data allowed to be reached by the administrator
View due fee of the students
To view student contact details
4.2 Hardware interfaces
System configuration RAM 2GB and SSD 80GB
4.3 Software Interfaces
Front end - Java
Backend - My SQL
4.4 Communication interfaces
Communication will be through the Local Area Network available in the school
5. Non-functional Requirements
5.1 Performance Requirements
The system should be capable of handling the following tasks.
i)
ii)
At least 3 Accountants can log into the software in a day within 3 hours in a week
Ability to handle MySQL database of 100 students
5.2 Safety Requirements
All details should be maintained as hard copy and an excel backup in case of any fault
5.3 Security Requirements
The System will
i)
ii)
Authenticate each user who logs in
An error message will be shown if a user is not allowed to perform a certain action in the
system.
6. Other Requirements
6.1 APPENDIX A
I)
II)
III)
IV)
Username should begin with any letter
Username should be unique
Username should be at-least 4 characters long
Password should contain at-least 4 characters long
6.2 APPENDIX B : GLOSSARY
SRS - System Requirement Specification
SQL - Structured Query Language
LAN - Local Area Network
S1, S2, S3 - SESSION 1, 2, 3
7. REFERENCES
i)
ii)
iii)
Fundamentals of database system by Ramez lmarsi and Shamkant Navarthe
System Requirement Specification sample shared by supervisor Catherine Gachiri.
https://www.slideshare.net/SumanSaurabh9/srs-for-student-database-management-system by
Suman Saurabh