Software Requirements

Specification
for

TABIKA KEMAS
MANAGEMENT SYSTEM

Version 1.0 approved

Prepared by

NUR FIRSYA FARHANA BINTI RASHDAN

MARINI AQILAH BINTI MOHAMAD

SITI FADHILAH BINTI ROZALI

UNIVERSITI PUTRA MALAYSIA

23rd October 2017

Copyright2017byUPM.Permissionisgrantedtouse,modify,anddistributethisdocument.
SoftwareRequirementsSpecificationforTSMS
Pageii

TableofContents
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.................................................................2
1.4 Product Scope................................................................................................................. 2
1.5 References...................................................................................................................... 2
2. Overall Description....................................................................................................2
2.1 Product Perspective.........................................................................................................3
2.2 Product Functions............................................................................................................ 3
2.3 User Classes and Characteristics....................................................................................4
2.4 Operating Environment....................................................................................................4
2.5 Design and Implementation Constraints..........................................................................4
2.6 User Documentation........................................................................................................ 5
2.7 Assumptions and Dependencies.....................................................................................6
3. External Interface Requirements..............................................................................6
3.1 User Interfaces................................................................................................................. 7
3.2 Hardware Interfaces.........................................................................................................7
3.3 Software Interfaces.......................................................................................................... 7
3.4 Communications Interfaces.............................................................................................7
4. System Features.........................................................................................................8
4.1 Registration Student........................................................................................................ 8
4.2 View Class Schedule and Syllabus Activities.................................................................10
4.3 Enter Fees Payment......................................................................................................12
4.4 Enter Class Schedule and Syllabus Activities................................................................14
4.5 View Student's Profile....................................................................................................16
5. Other Nonfunctional Requirements.......................................................................18
5.1 Performance Requirements...........................................................................................18
5.2 Safety Requirements.....................................................................................................18
5.3 Security Requirements...................................................................................................18
Appendix A: Analysis Models.......................................................................................19

RevisionHistory
Name Date Reason for Changes Version
SoftwareRequirementsSpecificationforTSMS Page1

1. Introduction

This section gives a scope description and overview of everything included in this SRS
document. Also, the purpose for this document is described and a list of abbreviations and
definitions is provided.

1.1 Purpose

The purpose of this document is to write the full descriptions of the Taman Bimbingan
Kanak-kanak (TABIKA) Student Management System (TSMS). It includes the purpose of
the system and the declaration of the development of the system. Besides, this document
will explain about the system constrains, interface and interaction with another external
application or system. Therefore, this document will be presented to the customer to seek
for the approval from them and to be used as the references during the development of
this TSMS system.

1.2 DocumentConventions

Term Definition
User A person who operate the system

Desktop A computer that use at the working space use to install the system

Stakeholder Any person who interact with the system except developers

Function Features in the system

Table 1.0 Definition

SoftwareRequirementsSpecificationforTSMS Page2

1.3 Intended Audience and Reading Suggestions

This document is made for the users and stake holder to understand and to be a guide for
them to follow and use the system later.

1.4 Product Scope

The system establishes the expectation that the manager will ensure that there are
appropriate processes and controls in place to effectively manage the students and class
activities in the TABIKA. The policy focuses on systematic student registration, class
schedule organization.

The teachers can provide the details of the specific student by using the registration
function that featured in the system. If the student made any fees payment, the assistant
teacher will record the successful payment. The system will check if there is any overdue
payment of the fees before the registration takes place. The teacher and the assistant
teacher shall be able to view the class schedule prepared by the manager.

The manager of the TABIKA can enter the activity schedules for the student in the system
as well as the class schedules for the teachers and assistant teachers to view and refer.

1.5 References

http://www.kemas.gov.my/index.php/my/premis/taman-bimbingan-kanak-kanak-tabika

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 that will use the system
and what functionality is available for each type. At last, the constraints and assumptions
for the system will be presented.
SoftwareRequirementsSpecificationforTSMS Page3

2.1 Product Perspective

The system is a web-based application system. It will be able to be used whenever the
computer is connected to the internet. The web-based application system shall be able to
store the data over the cloud database.

2.2 Product Functions

With web-application, user can run the application in the computer of the workspace in the
TABIKA. The user will be given a few options to choose the features such as register
student, enter and check student finance account, view student profile, view and enter
students schedule and activities.

Teacher can register the student by filling up the form in the system. A teacher can refer
to the student class schedules and activities to help teacher find the best teaching
material for the students. Furthermore, the updated student profile can be viewed by all
users.

The student finance account is for the student fees payment. This function is to check
whether the student is qualified to be registered in the system. The assistant teacher can
enter the student payment method and amount of fees that are paid.

The manager of the TABIKA can enter and edit the class activities and schedule. All the
users will be able to view the standardize version of the class schedule and activities for
the TABIKA.
SoftwareRequirementsSpecificationforTSMS Page4

2.3 User Characteristics

There are three main users designed for this system. Those three users are teachers,
assistant teachers and managers. Each of them have different use of the system so they
have their own requirements.

The teachers use the TSMS application to enter the fees payment details in the system to
proceeding the registration of the student information in the system. Teachers also can
view the student schedule and activities in the system.

Assistant teachers responsible for entering the details for the tuition fees for the TABIKA.
They must fill up the form in the system to record the successful payment made by the
parents to be able to register.

Managers are the person who responsible to monitor, supervise and prepare the activity
and syllabus to the teachers and student. The manager will be able to enter and update
the class activities and schedules in the system.

2.4 Operating Environment

The system should be able to operate on any internet browser if the device is connected
to the internet.

2.5 Design and Implementation Constraints

The main constraint of this system is the internet. The system only can be use if the
device is connected to the internet, otherwise data cannot be fetches from the database.

2.6 User Documentation

There will be a few steps to use this system;

SoftwareRequirementsSpecificationforTSMS Page5

2.6.1 Teachers

User login with unique ID

Verified teachers will have the option to fill in the student registration form.
Teachers submit the form to the system to save.
Teachers can view the student profile
Teachers can view class schedule and activities

2.6.2 Assistant Teachers

User login with unique ID

Verified assistant teachers will be able to enter the amount of paid student tuition
fees.
Assistant teachers can view the student profile
Assistant teachers can view class schedule and activities

2.6.3 Managers

User login with unique ID

Verified manager will be able to enter the student syllabus activities and schedule
Manager can view the student profile
Manager can view class schedule and activities
SoftwareRequirementsSpecificationforTSMS Page6

2.7 Assumptions and Dependencies

Serve as an online system, this system can only be used by specific user that has the
unique id to recognize. The system provides the users to add and update the records of
student information, tuition fees and class activities and schedule by the assigned users
specifically. Means that the users can change the record by their own responsibility. After
teachers submitted the registration form, the system will display the profile of the students.

3. External Interface Requirements

3.1 User Interfaces

UI 1 - Home page - home page will contain general information about the system
including the description of every sections. There will be a button to go to the login
page.
UI 2 - Login page - this interface will appear for the user to login. The user should
fill their username and password. There also will be a login button to initiate the
login process.
UI 3 - Student Register page - this interface will allow the user to register the
student. The information that they will need to fill in are student s name, gender,
age, religion, parents name and contact number and healths condition. There will
be register button to proceed the process and cancel button to cancel the
registration process.
UI 4 - View Student Profile page - this interface will allow user to view the student
profile.
UI 5 Student Tuition Fees Records page this interface allows the assistant
teacher to enter the tuition fees records of each student.
UI 6 Management page - this interface will allow the managers to add and
change the class syllabus activities and schedule. There will be upload button and
save to confirm the changes made by the admin.
SoftwareRequirementsSpecificationforTSMS Page7

UI 7 View Class Schedule and Activities page this page allows the users to view
the class schedules and activities set by the managers. There will be button
download to download the files.

3.2 Hardware Interfaces

TSMS supported by hardware devices such as computers, smartphones and laptops.

3.3 Software Interfaces

TSMS can be accessed using Windows7, Windows 8, Windows 10 and Macintosh

Operating System (MAC OS X).

3.4 Communications Interfaces

TSMS can be accessed using Google Chrome, Safari, Mozilla Firefox and Internet
Explorer.

4. SYSTEM FEATURES

4.1 Registration of students

SoftwareRequirementsSpecificationforTSMS Page8

Register
Student

Teacher

4.1.1 Description

A teacher whose identity has been verified will register the student by checking the fee
payment made by the assistant teachers first. Teacher then will register the student by fill
in the student information. such as name, gender, age, date of birth, religion, parents
name and contact number and healths condition.

4.1.2 Stimulus / Response Sequences

Stimulus : Teacher request to log in into Tabika Student Management System ( TSMS )
Response : System will allow teacher to log in into TSMS .
Stimulus : Teacher will check fees payment by click to view Fees Payment
Response : System will display the list of student that already paid the fees.
Stimulus : Teacher will continue for registration process by click Register
Response : System will proceed to display registration form of TSMS.
Stimulus : Teacher will key in students name , gender , age , date of birth , religion,
parents name and contact number and healths condition and click Register
Response : The system will stored the information in database .

4.1.3 Functional Requirement

SoftwareRequirementsSpecificationforTSMS Page9

The system shall let teacher to register the

student by checking the fees payments
status of the student first. Teacher will
Register Student
register student by entering students name,
gender, age, religion, parents name and
contact number and healths condition.
Teacher also can update this details at any
time.

4.2 View Class Schedules & Syllabus activities

View Class
Schedule

View
Syllabus
Teacher activities
SoftwareRequirementsSpecificationforTSMS Page10

4.2.1 Description

A teacher whose identity has been verified also can view the class schedule made by the
Manager

4.2.2 Stimulus / Response Sequences

Stimulus : Teacher request to log in into Tabika Student Management System ( TSMS )
Response : System will allow teacher to log in into TSMS .
Stimulus : Teacher view class schedule by clicking View Class Schedule
Response : System will display the schedule in TSMS .
Stimulus : Teacher can continue view the syllabus and curricular activities by clicking
Syllabus activities
Response : System will display the syllabus and curricular activities from Manager

4.2.3 Functional Requirement

The system shall let the teachers to view

the class schedule once they click View
Class Schedule.

View class schedule & syllabus/

The system shall let the teachers to view
activities the syllabus /activities once they click
Syllabus /activities
SoftwareRequirementsSpecificationforTSMS Page11

4.3 Enter Fees Payment

Enter Fees
Payment

Assistant Teachers

4.3.1 Description
SoftwareRequirementsSpecificationforTSMS Page12

An assistant teacher whose identity has been verified can enter the fees payment and
update the status.

4.3.2 Stimulus / Response Sequences

Stimulus : Assistant Teachers request to log in into Tabika Student Management System
( TSMS )
Response: System will allow assistant teachers to log in into TSMS.
Stimulus : Assistant Teachers will update and enter fees payment status once the
students paid.
Response : System will update list of students that have been paid .

4.3.3 Functional Requirement

The system shall let the assistant teachers

to update and enter the fees payment made
Enter Fees Payment
by the students. The system shall update
the list of students that have been paid.
SoftwareRequirementsSpecificationforTSMS Page13

4.4 Enter Class Schedule & Syllabus activities

Enter Class
Activities &
Schedule

Manager

4.4.1 Description
SoftwareRequirementsSpecificationforTSMS Page14

A teacher whose identity has been verified also can view the class schedule made by the
Manager

4.4.2 Stimulus / Response Sequences

Stimulus : Manager request to log in into Tabika Student Management System ( TSMS )
Response : System will allow teacher to log in into TSMS .
Stimulus : Manager will enter/edit the schedule and syllabus /activities related in TSMS .
Response : System will update the schedule and syllabus for Teachers and Assistant
Teachers .

4.4.3 Functional Requirement

Enter class Schedule & Syllabus / The system shall let the Manager to enter
the schedule and the syllabus /activities in
activities
TSMS. Manager also shall update and edit
the schedule & syllabus if needed.
SoftwareRequirementsSpecificationforTSMS Page15

4.5 View Students profile

Teachers

View
Students
profile

Assistant Teachers

Manager
SoftwareRequirementsSpecificationforTSMS Page16

4.5.1 Description

All teachers / assistant teachers / manager whose identity has been verified, can view the
students profile in TSMS.

4.5.2 Stimulus / Response Sequences

Stimulus : Teacher/Assistant Teachers / Manager request to log in into Tabika Student

Management System ( TSMS )
Response : System will allow Teacher/Assistant Teachers / Manager to log in into TSMS .
Stimulus : . Teacher/Assistant Teachers / Manager can view the students profile by click
on Students Profile
Response : System will display the profile of students in Tabika .

4.5.3 Functional Requirement

The system shall let all users to view the

Students profile. The students profile
View Students profile include all details of the student such as
SoftwareRequirementsSpecificationforTSMS Page17

name, gender, age , date of birth , religion,

parents name and contact number and
healths condition .

5. Other Nonfunctional Requirements

5.1 Performance Requirements

The system should be available 24 hours for accessing. If the internet service gets
disrupted while sending information to the server, the information can be sent again for
verification. The system response time must be less than 15 seconds when the user tries
to Login into the system. The server downtime should be less than 1 minutes in 24
hours. The web pages generated by the system shall be fully download-able in no more
than 30 seconds over a 100kbps Wi-Fi connection.

5.2 Logical Database Requirements

The system must store all the username and password. All the data shall be stored in
database to make sure the Manager, Teachers and Assistant Teachers can retrieve the
students profile information. Information transmission also should be securely
transmitted to server without any changes in information.

5.3 Software Quality Attributes

Availability: The system will only run infrequently. The system will allow the user to
restart the application after a crash. All data beyond the last save point will be lost. The
user will be able to load his or her data file after the system has been restarted and
continue using the system by re-login. The system will have an average run time of 15 to
20 min per session depending on the user, although the user may use the system longer.

Security: The system will use the computers default operating system security. The
SoftwareRequirementsSpecificationforTSMS Page18

main security concern is for users account hence a proper authentication method should
be using to avoid hacking.

Appendix A: Analysis Models

TabikaStudentManagementSystem(TSMS)