Service Notification System

Software Development PlanSpecifications

SEMESTER MARCH 2020 – JULY 2020

GROUP: JCS1104A

Ahmad Zhoreef Bin Mohamed, 2018644416

Ahmad Afif Nazhan Bin Ahmad Azzianeizar, 2018406266
Ahmad Uzair Bin Abu Nodin, 2018291214
Ahmad Ashhar Bin Selamat, 2018273964
 <Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

Table of Content

1. Fact-findings 3
1.1 Fact-findings Techniques 3
1.2 Summary of Findings 4-7
1.3 Business Rules/ Logics 8

2. System Specification 9
2.1 Module/Function 9
2.1.1 Lists of Input Data 10
2.1.2 Processes involved 11
2.1.3 Lists of Output Data 12

References 13

Appendixes 13

Confidential  CS1105/A/B/C/D 2011 Page 2 of 16

 <Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

1. Fact-findings
1.1 Fact-findings Techniques

[List down all the fact-findings that have been used in your project. You can use more than 1 technique.
The followings show the information that you must include in the report according to the technique]
//yang highlight merah ni maksudnya kita takdek guna teknik tu but if korang ada idea
teknik lain, isi and edit je template tu
i. Interview
 Interviewee Name:
 Position of Interviewee:
 Organization/ Company:
 Date of Interview:
 Method of Conducting the Interview: (e.g.: Google Meet, Zoom, WhatsApp video call,
phone call, email, face to face)

ii. Survey/ Questionnaire

 Respondent Group: UiTM Segamat Student
 Method of delivering the Survey/ Questionnaire:
Google Form - https://forms.gle/cG6epXzhKLb8nZWD6
WhatsApp
 Duration: 26 April – 7 May (10 days)

iii. Observation
 Date of observation:
 Name of Current Operating Procedure:(e.g.: Procedure of Subject Registration)
 Ownership of Current Operating Procedure: (e.g.: Academic Affair)

iv. Document Review

 Date of Review:
 Name of Document: (e.g.: The List of Subject that have Pre-requisite)
 Ownership of Document: (e.g.: Academic Affair)

v. Research
 Type of Source: (e.g.: Internet, magazine, book, journal etc.)
 Name of Source: (e.g.:The official website of Shopee Malaysia https://shopee.com.my/

Confidential  CS1105/A/B/C/D 2011 Page 3 of 16

 <Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

 Research Scope: (e.g.: The process of transaction)

1.2 Summary of Findings

[In this section, you need to explain the facts that gathered from the stated fact-finding
techniques. The followings are examples of how to explain this section.]

i. Interview
The followings are the facts gathered from the interview session with Encik Ahmad bin Abu, the
officer of Academic Affair of ABC College:

 The Academic Affair will inform the students the date for registering subjects. Students need
to fill in the registration form and submit to Academic Affair Office before semester break.
 Each student can take minimum 12 credit hours per/semester.
 For the subjects that have a pre-requisite subject, a student must pass a pre-requisite
subject with minimum grade, C.
 Currently, the Academic Affair of ABC College face difficulty to trace result of pre-requisite
subject. As a result, the current system cannot trace student who register the subject
although fail in pre-requisite subject.
ii. Survey/Questionnaire //gambar akan diubah lepas habis response (6 May)

The followings are the result of survey analysis (you can present the result in graph format,
percentage, table format etc):
1) The frequency of public computer or printing service use by UiTM Segamat Student at
Cybercafé near Segamat area in a week.

Confidential  CS1105/A/B/C/D 2011 Page 4 of 16

<Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

2) Percentage of students that face the stated problems.

3) Percentage of students already know about the unavailability of the service.

Confidential  CS1105/A/B/C/D 2011 Page 5 of 16

<Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

4) Percentage of students who thinks it is necessary to have Service Notification System.

5) Percentage of students who would use it if the systems are developed.

Confidential  CS1105/A/B/C/D 2011 Page 6 of 16

 <Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

6) Vote percentage on the functions that student would like to have in the system.

The Fact-findings Techniques that we use in this project is survey or Questionnaire. The survey
has been created in google form platform and was spread in WhatsApp group that have
participants of students UITM Segamat. This survey is intended to avoid biased approach where
it can appear in other fact-findings techniques. By using this technique, we can gather
meaningful opinions, comments and feedback. A non-face to face survey environment is one
that best suits the privacy needs of the respondent. Respondents are more prefer to give open
and honest feedback in private survey method such as google form online like what our group
did in this project. This survey was held in one week at 1st May2020 until 7th May 2020. The
survey proceeded on very structured path because the question set comes with the answer
option to help and saves the respondent’s time.

Confidential  CS1105/A/B/C/D 2011 Page 7 of 16

 <Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

Here are the saved copies of surveys completed online.

iii. Observation

From the observation towards the current procedure of subject registration, we found:

 ????
 ????

iv. Document Review

The followings are the facts that gathered from reviewing process of the List of Pre-requisite

Confidential  CS1105/A/B/C/D 2011 Page 8 of 16

 <Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

Subject file:

 ????
 ????

v. Research:
From our research analysis towards the official website of Shopee Malaysia, we found:
 ????
 ????

1.3 Business Rules/ Logics

[Based on the fact-findings and user requirements, you can identify the modules/functions of your
project. In this section, you will list down all related business rules/logics of the stated modules.
Here, business rules represent policies, procedures, and constraints regarding how the system
works. The followings show an example how you can explain this section]
Joli semperit
Kena siapkan:-
business rule //edit2
page number

 Registration Module
1. Only cyber cafe shop owner within Segamat area can register an account.
2. For the new cybercafé who want to use our system they can register.

 Login Module
1. Cyber café owner need to login to their account in order to update the status of their
services.

 Add Shop Module

1. Cybercafe owner need to add their cybercafe shop.
2. Cybercafe owner can add custom if he/she owns a new or more than one Cybercafe.

 Insert Service Module

1. Cybercafe owner need to add the detail of their provided service such as operational unit
including price or charge rate.
2. Cybercafe owner can freely customize the service if happen some changes in the shop like
adding a new computer or printing unit.

Confidential  CS1105/A/B/C/D 2011 Page 9 of 16

 <Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

 Update Service and Shop Status Module

1. Cybercafe owner must update their shop status.
2. Cybercafe owner set if the shop is open or close.
3. Cybercafe owner set the availability of the service provided.

 Booking Module
1. UiTM Segamat Student’s fill in the detail required for booking to book a service at chosen
Cybercafe shop.
2. Cybercafe owner will decide either to accept or reject the booking request.

 Calculate Price Module

1. The system will calculate and display the total price of the service depends on the type of
service booked to the student.
 Display Service’s Status Module
1. //ISI

2. System Specification
2.1 Module/Function
[Brief explanation on the module or function involve in the system. You can refer sub-section 3.3 to
identify the modules or functions of the system. Here, you can explain the purpose of each module, who
involve in the module, the roles of person/stakeholder etc. The following shows an example to explain this
section]

 Registration Module
This module will be used by cybercafé owner to register a new account. An account is required in
order for cybercafé owner to add a new shop and manage the shop’s status. However, unlike
cybercafé owner, student does not require a registration to use this website. They can freely view
the availability of service without an account.

 Login Module
This module is used to login the cybercafé owner into the system to enable the owner to update
the status of their shop and service.

 Add Shop module

Confidential  CS1105/A/B/C/D 2011 Page 10 of 16

<Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

This module used by cybercafé owner to a new shop into the system.
Cybercafe owner can reuse this module anytime later in order to add a new shop.

 Insert Service Module.

This module used by cybercafé owner to insert or add new services into the system.
Cybercafe owner can reuse this module anytime in order to add new services to the shop.

 Update Service and Shop Status Module

This module used by cybercafé owner to update their service’s status. This module will be
commonly used by the cybercafe owner every operating day of the shop.

 Booking Module
This module used by student to book the computer services that are currently available at any
cybercafé shop. When booking request is made, cybercafé owner will be notified. They later can
accept or reject the booking request.

 Calculate Price Module

This module is used to calculate and display the final total prices. The system will calculate
according to the price rates that are set by the cybercafé shop owner and the duration. Calculated
price later will be displayed to the student

 Display Service’s Status Module

This module will be used by student. This module will display cybercafé’s shop information to the
student.

Confidential  CS1105/A/B/C/D 2011 Page 11 of 16

 <Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

2.1.1 Lists of Input Data

[In this section, you need to list all related inputs for each module such as Student ID, Grades etc. The
following shows an example to explain this section]
 Registration Module
1. Shop owner username.
2. Shop owner password.
3. Shop owner email.

 Login Module
1. Shop owner login username.
2. Shop owner login password.

 Add Shop module

1. Shop’s name.
2. Shop’s address.
3. Shop’s contact information.
4. Shop’s opening hours

 Insert Service Module.

1. Service type.
2. Service price or charge rate.
3. Number of services available for each type.

 Update Service and Shop Status Module

1. Service availability.
2. New service price.
3. Updated opening hours.

 Booking Module
1. Name
2. Phone number.
3. Date and time.
4. Duration.
5. Acceptation or rejection of the booking request.

Confidential  CS1105/A/B/C/D 2011 Page 12 of 16

<Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

 Calculate Price Module

1. Service type.
2. Service duration.
3. Price rate.
4. Amount of service.

Confidential  CS1105/A/B/C/D 2011 Page 13 of 16

 <Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

2.1.2 Processes involved

[Identify the process(es) in each module as stated in 4.1]

 Registration Module
1. Check if username already register or not.
2. Check if password is meet requirement.
3. Send verification through email.
4. If everything is valid user’s information will be added to database.

 Login Module
1. Check if username is in the database.
2. Check if password is match with the one stored in the database.

 Add Shop module

1. Add the updated shop information into database.

 Insert Service Module.

1. Add the updated service info into database.

 Update Service and Shop Status Module

1. Update the current information service into the database.

 Booking Module
1. Cybercafé owner can accept or reject incoming service booking request.
2. If service booking request accepted, it will be added into the database.

 Calculate Price Module

1. Calculate total price according to service type.

Confidential  CS1105/A/B/C/D 2011 Page 14 of 16

 <Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

2.1.3 Lists of Output Data

[In this section, you need to list all related outputs for each module such as a list of subjects that still not
registered yet, examination result etc. The following shows an example to explain this section]

 Registration Module
1. Confirmation output of successful registration.

 Login Module
1. Login successful output.

 Add Shop module

1. Confirmation that if shop information is successfully added into database or not.

 Insert Service Module

1. Display all inserted information.

 Update Service Status Module

1. Display updated service that going to be change.
2. Ask for final confirmation

 Booking Module
1. Ask final confirmation before sending the service request.
2. Ask whether to accept or reject the service request.
3. Display if the service request is accepted or rejected.

 Calculate Price Module

1. Final total price.

 Display Service’s Status Module

1. Shop’s service availability
2. Shop’s service type.
3. Shop’s service type amount.
4. Shop’s service price rate.
5. Shop’s address.
6. Shop’s opening hours.

Confidential  CS1105/A/B/C/D 2011 Page 15 of 16

 <Project Name> Date: <dd/mmm/yy>
Software Requirements Specification (SRS)

References
1. Nilufar Ahsan(2009). Cyber Cafe Usage in Malaysia: An Exploratory Study. Retrieved from
http://www.icommercecentral.com/open-access/cyber-caf-usage-in-malaysia-an-exploratory-study.php?aid=38302

2. Sharifah, M.A. (2005). A Case Study of Urban Cyber Cafés in Malaysia, Retrieved on 24-10-2007 at
http://www.apiap.org/research/case-of-urban-cyber-cafes-in-malaysia

Appendixes
Appendix A: Lecturer

Madam Safura Adeela Binti Sukman, ITS332 Lecturer, Faculty of Computer Sience and
Mathematic (FSKM), University Teknologi Mara Johor.

Appendix B: Document

Faculty of Computer Sciene and mathematics (FSKM), UITM Segamat Johor,Service

Notification System, System Development Plan(SDP)

Appendix C: Website

Deepak Chawla, Ramesh Behl (2006 ), Perception Study of Cyber Café Users, retrieved at
https://journals.sagepub.com/doi/10.1177/097215090500700102

Confidential  CS1105/A/B/C/D 2011 Page 16 of 16