SRS

SCSR3014 : APPLICATION DEVELOPMENT
SOFTWARE REQUIREMENT SPECIFICATION
for
SMART TUTOR
Version 1.0
Prepared by
NAME MATRIC NO.
Sakthiseelan A/L Seliyan B17CS3027
Tassvini A/P Gunaseharan B17CS3030
Vishaan A/L Bhaskaran B17CS3031
Neerenraj A/P Nagaraju B17CS3034

Table of Contents
Introduction
Purpose 1
Intended Audience and Reading Suggestion 1-2
Product Scope 3-4
Overall Description
Product Perspective 5-6
Product Function 6
User Classes and Characteristic 7
Operating Environment 8-9
Design and Implementation Constraints 10
User Documentation 10
Assumption and Dependencies 10
External Interface Requirements
User Interface 11-17
Hardware Interfaces 18
Software Interfaces 18
Communication Interfaces 18
System Features
UC01 Student 19-24
UC02 Tutor 25-30
UC03 Admin 31-35
UC04 Forum & Feedback 36-45
Other Non-Functional Requirements
Performance Requirements 46
Safety Requirements 46
Security Requirements 46
Software Quality Attributes 46
Conclusions 47
Other Requirements 48-51

1
1. Introduction
Online tutor websites have existed in the market about a decade in Malaysia but still having a
lot of problem remain unsolved. Searching for suitable candidate to teach their children is not
an easy task because traditionally parents have limited information about availability of tutors
within parents’ housing areas. Besides that, parents will search or get information for tutors
via the word of mouth from friends, family members, flyer sent by local tuition center or local
tuition institute. However, in this information era, parents and tutors matching websites
become more and more common as the technological advancement became more widespread.
Therefore, my team and I come up with an idea of developing an website which make
everyone life easier and suggest private tutor come in house deliver one to one lesson to
children to above average financial status families and they can negotiate the tuition rate with
tutor one to one and suggest more affordable price to parents children attend traditional lesson
with other students that group together according their learning stage the classroom.
1.1 Purpose
The purpose of this document is to describe the Software Requirements Specifications (SRS)
of the proposed application. The application consists of two main parts, the web application
and the backend server. Application architecture design, scopes, functions and its integration
with existing system at application designs are the core elements to be described in this
document. This document provides a complete understanding of what is to be expected from
the application. Clear understanding of the application and its functionalities will allow for
the correct software to be developed for the end users (here referred to as the stakeholders)
and can be used for future development of the application. This document provides the
foundation for the design, construction, and testing of the application.
1.2 Intended Audience and Reading Suggestions
The SRS described in this document is to be used by the stakeholder for developing the
application. The Hello World team will use the SRS to fully understand the expectations and
requirements needed in the application. They will be able to use this SRS as a reference to see
if the (Hello World) team is constructing the application as per stakeholder (tutors)
expectations.
Some other extra points to be noted:
● This document is intended for system analyst, developers, software testers,
documentation writers and stakeholders (tutors).
● The system analyst, developers and software testers are referring to development team
members (Hello World)
● The Hello Worlds team and tutors’ team shall use this document as a result of
mutual agreement on the requirements to be fulfilled by the applications
. ● Each of the intended audience is suggested to review and use this document as such: ○
System analyst and developers - Understand the requirements of users and how they will use
and interact with the system to be developed in order to perform their activities. The
specification for software to be developed, which include functionalities, non-functional
requirements, and software architecture can be found in this document. Integration and

2
interface with existing systems and databases at tutors can also be referred to from
this document.
○ Software testers - Systematically plan the functional and security testing strategy of the
applications. Functional testing is to be guided by system features described in section 4 and
should be about functional conformance to the stated requirements, usability and bugs
detection. Specifications for security testing can be defined by following the guides
○ Documentation writers - Design the use case flow structure and content to show how the
the application can be used in the most effective way. It has to be delivered as end-user
manual and technical documentations that covers all the requirement aspects proposed and
explained in section 4.
○ Stakeholders
■ SJK(T) Tun Aminah teachers

3
1.3 Product Scope
The main objectives and the expected benefits of the system are:
i. Speed up tutor search
ii. All functionalities for this web application mainly are develop for parents and
tutors except interactive forum that provide service for all members including
students to interact with each other members.
iii. The web application will not handle the parents’ various payment for the tutor service
fees. Although referral fee will be charge on tutors, but all tutors’ service fees will be
received directly from parents.
iv. All users involve in this web application website will able to use the services 24/7 with
only internet connection to World Wide Web (WWW) only.
v. All users access the web application through HTTP internet protocol enable devices
such as mobile smart-phone, personal computer and other capable web browsing
devices.
vi. All users involve in this web application will play its own role such as for
administrator is to manage web application, verify the tutors, view and delete tutors’
account, view and feedback sent to them and verify job posted by tutors’
vii. Get search multiple tutors and can enquiry them.
a. Open job scope for everyone who interested in tutoring.

4
To achieve them two components will be delivered:
viii. TAS - Mobile Application for use by students and parents.
a. TTS – Mobile Application for use by tutors
ix. TAAS - Client-server system to be used by Hello World team for administrative purposes.
TAS will provide the following functions:
x. To allow parents/students to register and view available tutor near their area
xi. To allow students, parents to register tutor by message them
xii. To allow students, parents enquiry about tutors and can post comments on forum
TTS will provide the following functions:
xiii. To allow teachers or anyone who intended to teach can register themselves as tutor
xiv. To allow tutors view messages from students and parent and reply to them
xv. To allow tutors to update their profile as per they have.
a. To allow tutor to upload their legitimate documents and certificate
for authentication.
As for TAAS, it will serve for the following functions:
xvi. To allow tutors, parent and students to register themselves on the system
xvii. To allow Requester responding and submitting amendments.
xviii. To notify tutors when new bookings requested.
. ● To verify the legitimate documents, upload by tutors is authenticate.

5
2. Overall Description
2.1 Product Perspective
The current system was using manual-based information system is one that does not rely on
any computerized systems and for the overall architecture of the system. As shown in the
figure, we have added new features to this system to develop existing system to integrate with
are as listed below.
• To create an application for Tutor to find the students to teach through application.
• Parents and students can a find tutor to teach and interaction between teacher,
parent, student.
• We have Admin to manage and verify their database in this application
• Our system has forum and FAQ to give feedback and can ask question through
the application.
Figure 2.1 Overall System Architecture

6
Figure 2.2 Business Process Diagram
2.2 Product Functions
Figure 2.3 is use case diagram represents the actors involved and their association to the main
functions of the application. There are four main functions proposed for this system (login,
booking tutor and managing data). Main application modules are developed correspond to
these proposed functions.

7
2.3 User Classes and Characteristics
No User Class and Characteristics
1 Students
Description:
The majority of students shall use this application to find private tutor. The technical
experience of these users should not matter as the system will be straightforward and
easy to use. Besides that, student will come to this application to choose subject,
choose tutor, view and download course content.
2 Tutor
Description:
Tutors will allow to accept requested student, upload and update their qualification
then upload a course content, notes and other educational material.
3 Parents
Description:
Who will choose a suitable a tutor and negotiate with tutor about the price and time?
4 System Admin
Description:
The system admin is responsible for maintaining (add, update and delete) the list of
student and tutor. They can also monitor the status of all student and tutor requested.

8
2.4 Operating Environment
The TAS, TTS, TAAS applications operate in client/server mode where the client (TAS)
requests information from the server (TAAS), and the server returns response to the client.
The client is a mobile type application running in Android mobile device. The server not only
act as a backend to response to mobile client request but can also be accessed as a
conventional web application by using web browser. To support this client-server
environment the application will be developed with the utilization of web server, database
server, and frameworks. Server machine, desktop computer, and mobile device (smartphone)
are the hardware to be used in the application. Details requirements for the development and
deployment of the applications are described below.
2.4.1 Software Requirement for client
Software Name Description
Firebase • Server database
• Provide platform to host client
application server and
database for Web application
Google Developer Console • Software service provided by Google to
•
developers who register with them
https://forumd29af.firebaseio.com/forum
2.4.2. Hardware Requirement for client
Hardware Name Description
Client Machine • Desktop computer with browser
software and
Internet connection
• Used by system admin to access client
as Web-based application in desktop
environment

9
2.4.3 Software Requirement for server
Software Name Description
HTML Atom • Atom enables users to install third-party packages and
themes to customize the features and looks of the editor.
Packages can be installed, managed and published via
•
Atom's package manager apm.
https://en.wikipedia.org/wiki/Atom_(text_editor)
Xampp • XAMPP tool provides one easy solution to run server and
database which beneficial for web developers to host their
•
web application locally.
https://en.wikipedia.org/wiki/XAMPP
2.4.4 Hardware Requirement for server
Hardware Name Description
Development PC • Computer installed with all required
software and libraries described in
section 2.4.3
• Server development and coding as a
combination mobile application to
be carried out using the
Development PC
Android Mobile Device • The mobile platform with internet
connection where mobile server
applications are to be installed.
• Used by student, tutor and parents to
access services provided by client in
mobile environment.

10
2.5 Design and Implementation Constraints
Some of the design and implementation constraints identified are listed below:
- Student is allowed to register for more than one courses
- Student doesn’t have the authority to edit or access data in system
- This system is support distributed database which Xampp
- System is limited to HTTP/HTTPS Protocols
2.6 User Documentation
This user documentation contains user manuals for end users. End users are tutors, students
and parents. The user guide explains how to use the software from the user's perspective. A
well written user guide will welcome first-time users by providing basic information about
how to get started quickly, but also include more in-depth information for power users
wanting to understand how to use the more advanced features of the software. The user
manual also will be produced accessible to end users and accessible in both hard and soft
copies of papers
2.7 Assumptions and Dependencies
It is assumed that alumni data will be made available for the project in some phase of its
completion. Until that, test data will be used for providing the demo for the presentations.
It is assumed that the students and parents is familiar with application find themselves easier
to look for tutor.

11
3. External Interface Requirements
3.1 User Interfaces
Here we have we type of interfaces for admin and user. For the user and admin
we both use web interfaces.
Based on the login, the user will see the listing page. Each listing page has the same
format containing several components as shown in Figure 3.2 and described as
below:
Figure 3.1: The Student Login page
Login = There are two different user logins. Either we can login as a tutor or as a
student or parents or admin. There only require contact number and password for
the login process
Register = Those who don’t have an account can register first in order to login.
The registration requires full name, date of birth, contact number, ic and address.

12
Figure 3.2: Student Registration Portal

13
Figure 3.3: Student Dashboard
Dashboard = On student dashboard, each and every module have its own function.
Search Tutor = Students can find the tutor using search tutor options, they can filter the
option by city or payments.
Create Post = Sometimes students didn’t get the corresponding tutor for them. Students
can create post about themselves for looking tutors. In this way tutors can find the
students and make them contact for tutoring.

14
Account Settings = Any change of password or account management can be done
here.
Logout = For log out options it will automatically redirect to main page
Figure 3.4: Tutor Dashboard
Tutor dashboard have more options than students. The page display information about
the tutor.
Search parents/ student = This option enable tutor to search students who were
looking for tutors. Tutors can filter the result by city, and subject
Create Post = Here tutors can create post about the subject they can teach
Edit Post = Any changes of post can edit here
Account Settings = Changes of details can be done here.

15
Logout = Go to Main Page
Figure 3.5: Feedback Page
Feedback Page lets tutors, students and parents can write down their comments and
issue that they are facing on the application. Technical problem known as any
problem that cause the application to crash. Connectivity problem usually comes with
loading page. Upload problem for having issue in uploading certificate for
verification process. Others problem can be described as other than above mentioned
problem.

16
Figure 3.6: Admin Page Main Menu
On admin page they are three functions available, view tutors, verify tutors and read
feedback.
Figure 3.7: View Tutor List
If admin click view tutors, list of tutors can be view by admin.

17
Figure 3.8: Verify Tutor’s Profile
If admin click verify tutor, tutors’ profile will be display in the table. The
certificates uploaded will be store here. Admin can view the certificate and
download. Then later can click to verify.
Figure 3.9: View Tutor’s Profile
This is the feedback panel. Any feedback from tutors, students and guardian can be view.

18
3.2 Hardware Interfaces
All the hardware used within the system are the standard hardware for client-server
computing. We use laptop for build the application.
3.3 Software Interfaces
Figure 3.18 presents the integration and interconnections among the tutor
system. Apache Web Server, MySQL, Database, and are the internal components
of the application.
Figure 4.0: Software Architecture
3.4 Communications Interfaces
The system relies on HTTPS, FTP, and MySQL protocols for communications
among its components.

19
4.0 System Features
This section describes main features of the proposed system.
4.1 UC01 – Student Login System
Figure 4.1 Use Case diagram of Student Login

20
4.1.1 Description
Name Student and Parents Login and Register System
Identifier UC01.1
Description Login and register to the system
Goal To allow actor login and register to system
Actor Student, Parents, Tutor
Packages UC01 Login
Assumption Student and Parent successfully login and register to this system
and browsing the account.
Frequency Moderate
Basic Course 1. Student and Parent expect system provide username and
password
2. System send login information to admin
3. System processing the query and display list of tutors that
match the query entered
4. Student and Parent browse the tutors list and select a tutor
5. System pop-up user to choose for a functionality
Alternate Course 1. User enter information not valid, such as username
repeated in existing database record, confirmation
password not same as the password entered.
2. User cancel registration in the middle of process.
Condition High
Post Condition Actor able to access module based their role in system
Included use case None
Extended use case None

21
Name Search Tutor
Identifier UC01.2
Description Search the tutor
Goal To allow search tutor on system
Packages UC01 Login
Assumption Student and Parent successfully search tutor to this system and
browsing the account.
Frequency Moderate
password
3. System processing the query and display list of tutor that
Condition High

22
Name Filter Tutor
Identifier UC01.3
Description Filter the tutor
Goal To allow filter tutor on system
Packages UC01 Login
Assumption Student and Parent successfully search tutor to this system and
browsing the account.
Frequency Moderate
password
Condition High

23
Name Alert Tutor
Identifier UC01.4
Description Alert the tutor
Goal To allow alert tutor on system
Packages UC01 Login
Assumption Tutor get alert from this system and browsing the account.
Frequency Moderate
password
Condition High

24
Name Book Tutor
Identifier UC01.5
Description Book the tutor
Goal To allow book tutor on system
Packages UC01 Login
Assumption Tutor get book from this system and browsing the account.
Frequency Moderate
password
4. Student and Parent browse the tutors list and select a
tutor
Condition High

25
4.2 UC02 – Tutor Login System
Figure 4.2 Use Case diagram of Tutor Login

26
4.1.2 Description
Name View Students
Identifier UC02.1
Description Tutor view student in the system
Goal To allow actor view student to system
Actor Student, Parent, Tutor, Administrator
Packages UC02 Tutor Login
Assumption Tutor successfully login and view to system and
browsing student list summited by parents account
Frequency Moderate
Basic Course 1. Tutor click on the student want to apply.
2. System check on the student availability to ensure
the student still available and not yet found
associate tutor required and then display apply
student form to tutor.
3. Tutor fill in information such as tutor’s
qualification, location and submit to the system.
4. System update database, prompt successful
message to tutor and notify parent via in the
application.
Alternate Course 1. Tutor click on the student want to apply.
2. System check on the student availability which
considering not yet found tutor required and then
display apply student form to tutor.
4. System found that tutor input is not valid and then
pop-up error message.
5. System navigate back to previous section to enter
again the form.
Condition Student status listed are available for tutor to occur
Post Condition Tutor is notified with the result message and navigate to
homepage

27
Name View Notification
Identifier UC02.2
Description Tutor view notification to the System
Goal To allow actor notify to system
Assumption Tutor successfully get notify to system and browsing
student list summited by parents account
Frequency Moderate
Basic Course 1. Tutor click on the student want to apply.
2. System check on the student availability to
ensure the student still available and not yet
found associate tutor required and then display
apply student form to tutor.
4. Tutor will be notified if they get student
application.
4. Tutor will be notified if they get student
5. System found that tutor input is not valid and
then pop-up error message.
again, the form.
Post Condition Tutor is notified with the result message and navigate to
homepage

28
Name Send Message and Book Tutor
Identifier UC02.3
Description Student/Parent send message and book the tutor in system
Goal To allow actor send message and book to system
Assumption Tutor successfully send message and book student to
system and browsing student list summited by parents
account
Frequency Moderate
Basic Course 1. 1.Tutor click on the student want to apply.
associate tutor required and then display apply
student form to tutor.
4. Tutor will be sent message and book if they get
student
application.
student
5. System found that tutor input are not valid and
again the form.
Post Condition Tutor is sent with the result message and navigate to
homepage

29
Name Edit Profile
Identifier UC02.3
Description Student/Parent/Tutor can edit their profile according
current status updates
Goal To allow actor edit profile to system
Assumption Tutor successfully edit profile to system and browsing
student list summited by parents account
Frequency Moderate
Basic Course 1.Tutor click on the student want to apply.
associate tutor required and then display apply student
form to tutor.
4. Tutor can edit their profile if needed
application.
student
again, the form.
Post Condition Tutor is update new information about them

30
Name Change Password
Identifier UC02.5
Description Student/Parent/Tutor change password the in system
Goal To allow actor change password to system
Assumption Tutor successfully change password to system and
browsing student list summited by parents account
Frequency Moderate
Basic Course 1. 1.Tutor click on the student want to apply.
the student still available and not yet found associate
tutor required and then display apply student form to
tutor.
3. Tutor fill in information such as tutor’s qualification,
location and submit to the system.
4. Tutor/student/parent can change password
5. System update database, prompt successful message
to tutor and notify parent via in the application.
4. Tutor/Student/Parent can change password
again, the form.
Post Condition Tutor/Student/Parents successfully change password

31
UC03-Manage Student and Tutor Account
Figure 4.3 Use Case diagram of Manage Student and Tutor Account

32
4.3.1 Description
Name View Tutor
Identifier UC03.1
Description This use case is created for the administrator to view tutor
list and applied Student/Parents
Goal To view tutor and manage account by administrator
Actor Administrator
Packages UC03 Manage Account
Assumption Student and Tutor existing in the system
Frequency High
Basic Course 1. Administrator click on mange user account in
webpage
2. System display search box for administrator to
search by username and help on to send any
messages to tutor or student and parents
3. Administrator enter the username want to perform
manage on it account and help tutor to verify
student account.
4. System perform the function required by updating
the user in database and display the result on
screen.
Alternate Course Not Applicable
Condition Administrator already logged in into the system.
Post Condition None

33
Name Download Document
Identifier UC03.2
Description This use case is created for the student/parents to
download documents such as notes and exercises, tutors
or upload notes and administrator to keep an eye on
documents uploads
Goal To download document account by administrator
Actor Administrator
Packages UC03
Frequency High
webpage
student account.
4. Student/parents to download documents such as
notes and exercises, tutors or upload notes and
administrator to keep an eye on documents
uploads
screen.
Condition Administrator keep track on documents upload into the
system.
Post Condition None

34
Name Send Message
Identifier UC03.3
Description This use case is created for the administrator to send
messages to student/parents and tutor as well as
student/parents can send messages to tutor and
administrator.
Goal To send message account by administrator
Actor Administrator
Packages UC03
Frequency High
webpage
student account.
4. Administrator to send messages to student/parents
and tutor as well as student/parents can send
messages to tutor and administrator.
screen.
Condition Administrator send messages into the system.
Post Condition None

35
Name Verify Tutor
Identifier UC03.1
Description This use case is created for the administrator to verify
tutor list which applied Student/Parents
Goal To verify tutor by administrator
Actor Administrator
Packages UC03 Manage Account
Frequency High
webpage
manage on it account and help to verify tutor
account.
screen.
Condition Administrator help verify tutor account into the system.
Post Condition None

36
UC04 – Manage Forum & FAQ
Figure 4.4 Use Case diagram of Manage Forum & FAQ

37
4.4.1 Description
Name Manage Forum
Identifier UC04.1
Description Parent, student, tutor or administrator want to manage a
single forum functionalities that manage forum, topic and
reply.
Goal To manage forum
Actor Parent, student, tutor, Administrator
Packages UC04
Assumption Student or Tutor logged in the forum that want to post a
new topic or reply message to current existing topic that
want ask opinion, idea, discussion, answer or other
functionalities to all public users in the forum. Besides,
user able to send private message and reply private
message specifically to a user existed in the forum.
Frequency Low
Basic Course 1. User successful perform a function such as post or
delete a forum, post or delete a topic, post update
or delete a reply, change forum avatar, signature
or others.
Alternate Course 1. User cancel the verification process during the
function
Condition 1. User logged in forum as a parent, tutor, student or
administrator role.
2. User have a permission of perform certain task.
Post Condition 1. User prompt for result on perform manage forum.

38
Name Manage Topics
Identifier UC04.2
Description Tutor uploads topics related to subject can be seen by
administrator too.
Goal To manage forum
Packages UC04
Assumption Tutor to upload topics on related subjects
Frequency Low
Basic Course 1. User uploads topics or students to review
Alternate Course None
Condition None
Post Condition None

39
Name Manage Post
Identifier UC04.3
Description Student/Tutor can upload post regarding educations
Goal To manage post
Packages UC04
Assumption Student/Tutor can uploads post regarding educations
Frequency Low
Basic Course 1. User uploads post about education purpose which
can be seen by administrator also
Condition None
Post Condition None

40
Name Manage Reply
Identifier UC04.4
Description Student/Tutor can upload post regarding educations
Goal To manage post
Packages UC04
Assumption Student/Tutor can reply on forum
Frequency Low
Basic Course 1. User uploads post in forum and gets reply for it
and answer frequently asked questions
Condition None
Post Condition None

41
Name Manage private message
Identifier UC04.5
Description Student/Parent can send private messages to Tutor
Goal To send private messages
Packages UC04
Assumption Student/Parent can send private messages to Tutor
Frequency Low
Basic Course 1. User can send private messages to tutors
regarding educations
Condition None
Post Condition None

42
UC-05 Manage Feedback
Figure 4.5 Use Case diagram of Manage Feedback

43
4.5. 1 Description
Name Submit feedback forms
Identifier UC05.1
Description Parent/Student can give feedback on tutor
Goal To give feedback on tutor’s performance and personality.
Actor Parents and Students
Packages UC05
Assumption Parent already having some idea and familiar with the
tutor apply for their children
Frequency High
Basic Course 1. Parent click feedback button.
2. System check and confirm parent qualified to give
feedback for the tutor and then display the form to
let parent write.
3. Parent enter the feedback then submit to the
system.
4. Parent confirmation to submit.
5. System update database and display the result on
screen.
Alternate Course 1. Parent click feedback button.
let parent write
3. Parent enter the feedback then submit to the
system.
4. Parent cancel the process.
5. System display user cancel result on screen.
Condition 1. 1. Parent only able to give feedback
Post Condition None

44
Name Comment
Identifier UC05.2
Description Parent give comment that will show to public about the
tutor’s performance and personality.
Goal To give feedback on tutor’s performance and personality.
Actor Parents and Students
Packages UC05
Assumption Parent already having some idea and familiar with the tutor
apply for their children
Frequency High
Basic Course 1. Parent click comment button.
let parent write.
3. Parent enter the comment then submit to the system.
4. Parent confirmation to submit.
screen.
Alternate Course 1. Parent click comment button.
let parent write
3. Parent enter the comment then submit to the system.
4. Parent cancel the process.
5. System display user cancel result on screen.
Condition 6. 1. Parent can to give comment
Post Condition None

45
Name Contact Us
Identifier UC05.3
Description Parent can contact us for any enquiries or for frequently
asked questions
Goal To contact administrator for questions
Actor Parents
Packages UC05
Assumption Parent can contact us for any enquiries or for frequently
asked questions
Frequency Low
Basic Course 1. Parent can contact administrator and call records
will records for training purposes
screen.
Condition 1. Only parents can contact administrator
Post Condition None

46
5. Others Non-functional Requirement
5.1 Performance Requirements
1. The database shall be able to accommodate a minimum of 3,000 records of students
2. The software shall support use of multiple users at a time. There are no other specific
performance requirements that will affect development.
5.2 Safety Requirement
1. The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup.
5.3 Security Requirement
1. Some of the factors that are identified to protect the software from accidental or malicious
access, use, modification, destruction, or disclosure are described below.
- Keep specific log or history data sets
- Assign certain functions to different modules.
- Restrict communications between some areas of the program
- Communication needs to be restricted when the application is validating the user or
license. For example, using https.
5.4 Software Quality Attributes
1. The Quality of the System is maintained in such a way so that it can be very user friendly
to all the users.
2. The software quality attributes are assumed as under:
- Accurate and hence reliable
- Secured
- Fast speed
- Compatibility

47
6.0 Conclusion
In conclusion, this project will develop a web application that will include all core tutors and
parents matching website functionalities that most similar websites in Malaysia have. For
example, easy searching and automatic suggestion suitable tutors’ system according to tutor’s
profile or ranking in the website and a suitable services fees payment system for tutors. But,
before my team and I decided to choose SMART TUTOR, we initially choose a topic called
BIKE RENTAL SYSTEM. During worked on initial topic, we prepared problem statement,
proposed solution and objectives. On our first consultation with Ms. Marina, we proposed our
topic with some prepared material. During the consultation Ms. Marina advised us to collect
some real evidence such as survey form to proceed further, but in our second consultation
with her we got to know that we couldn't find enough problem to proceed the project and we
go back to square one where need to find new topic which is Smart Tutor and work on
problem statement, proposed solution, objectives and survey forms. Then, the topic was
approved by Ms. Marina and we start work on looking for stakeholders, prepare survey form
and create Gantt Charts.
As well in preparing this report, we found out that current tutors and parents’ website not
ease of use and lack of functionalities. This motivate us to develop a better web application to
contribute to the public. Besides, my team and I also facing problem on the studying the
requirement of the website through surveys. This is due to the nature of this website nature
that need opinion from tutors. However, actual situation that is very hard for me to surveying
tutors due to less opportunities contact them.
Last but not the least, to summarize the highlights of the previous chapters, the goal is to
develop a matching web application for tutors and parents enhancing the existing similar
website in Malaysia. This project will ultimately enable engagement of tutors and parents to
facilitate participation in this scheme by using a forum that proved research capable of
increasing the academic achievement of learners through a better and easier communicating
setting for tutors and parents.

48
APPENDIX A: Sequence Diagrams
Figure A.1: Sequence Diagram of Tutor

49
Figure A.2: Sequence Diagram of Student
Figure A.3: Sequence Diagram of Admin

50
Figure A.4: Sequence Diagram of Forum & Feedback

51
Figure A.5: Sequence Diagram of FAQ

SRS

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to SRS

Similar to SRS (20)

Recently uploaded

Recently uploaded (20)

SRS