Faculty of Computer and Mathematical Sciences

UiTM MELAKA KAMPUS JASIN

SOFTWARE REQUIREMENT SPECIFICATIONS

SEMESTER : OCTOBER 2023 – FEBRUARY 2024

COURSE NAME : SOFTWARE ENGINEERING (CSC577)
LECTURER : DR SITI FEIRUSZ BINTI AHMAD FESOL
SYSTEM NAME : ARABIC RESTAURANT MANAGEMENT SYSTEM
PROGRAM NAME : BACHELOR OF COMPUTER SCIENCE MULTIMEDIA COMPUTING (CS253)
CONTACT PERSON : AHMAD DANIAL HAKIM BIN ROSMAN
+60192126574, 2022702955@student.uitm.edu.my

STUDENT ID STUDENT NAME GROUP(A/B) ROLE

2022702955 AHMAD DANIAL HAKIM BIN ROSMAN M3CS253 4A Team Leader
2022753195 MUHAMMAD HARITH IKHWAN BIN ROSMAENI M3CS253 4A Lead Programmer
2022961571 AZZARUDDIN BIN ABDULLAH M3CS253 4A Lead Documenter
2022977615 HEDZWEEN BINTI MOHD PUAD M3CS253 4A Documenter

DATE OF SUBMISSION 13TH NOVEMBER 2023

ACTUAL DATE OF SUBMISSION 14TH NOVEMBER 2023
NO OF DAYS LATE
 Table of Contents

Table of Contents 2
List of Figures 3
1.0. 4
1.1 4
1.2 4
1.3 5
1.4 6
2.0. Error! Bookmark not defined.
2.1 8
2.2 8
3.0. 32
4.0. 32

SRS V 1.0 2 13/11/2023

 List of Figures

Figure 1.2 – Software Process Model 5

Figure 2.1 – Task Breakdown 6
Figure 3.1 – Gantt Chart 7
Figure 4.1 – Overall Usecase Diagram 8
Figure 5.1 - Register Account 11
Figure 6.1 - Login Account 14
Figure 7.1 - Display Menu 16
Figure 8.1 - Order Entry 18
Figure 9.1- Additional Order 21
Figure 10.1 - Display Order 23
Figure 11.1 - Cancel Order 25
Figure 12.1 - Bill Generator 27
Figure 13.1 – Sales 29
Figure 14.1 – Report 31

SRS V 1.0 3 13/11/2023

1.0. Introduction

1.1 Background Study

1.1.1 What kind of system

Arabic restaurant management system is a system application that is managed by the

employees to make sure all the orders from the customers are being received. It also
includes customers ordering through the system application.

1.1.2 Who needs the system

The targeted audience are the customers that want to buy some Arabic food near the
restaurant location without waiting in line for the food to serve. The customers can order
the food beforehand. Also, for the employees to count the sales and report for the month.

1.1.3 Why they need the system

I. The customer can order beforehand to avoid any traffic order inquiries rather than
needing to wait in line to order, therefore the customer can save time and energy.
II. The customer can cancel the order in one single click.
III. The system will help the employee to receive the food order from customers,
generate the bill for the customer and calculate the sales report for the entire month.
IV. The system will also help employees to order for the customer in case the customer
does not have a mobile to order.
V. The system is easy to use for both customers and employees of the restaurant.

1.1.4 How the proposed system can improve their activities

This system will allow the employee to order on the customer’s behalf. Moreover, the
employees can identify the order and prepare the order for the customer. This system will
also allow the employees to view the bill, sales, and report for the month.

1.1.5 An existing or similar system developed for other organizations

The similar system that can be found https://zuscoffee.com/menu/ where user can order
their food and beverages.

SRS V 1.0 4 13/11/2023

1.2 Development Methodology (Software Process Model)

Figure 1.2 Software Process Model

Requirements
• Complete the proposal presentation of “Arabic Restaurant Management System”.
• Sketch the flow of the system.

System Design
The design of the system includes:
• Design use case diagram and description of the system.
• Design activity diagram of the system.
• Design the database of the system.
Software design aims to recognize and delineate the intricacies of the system, enabling the
user to comprehend and effectively utilize it.

Implementation
In this phase, developers will consult the software design as a guide to build the system,
employing tools like Eclipse and Server.

Verification and Testing

Every program is integrated and tested as a unified system to guarantee fulfillment of the
software requirements. Upon completion of testing, the system will be delivered to the
user.

Deployment and Maintenance

During this phase, continuous monitoring of the system will take place to prevent any
issues or bugs. Developers will make modifications to the system upon discovery of
errors.

SRS V 1.0 5 13/11/2023

1.3 Project Milestones and Deliverables

Week Date Task

1 2/10 – 9/10 1) Team Carter Submission

2) Project Briefing
3 13/10 – 19/10 1) Project Discussion
2) Proposal Submission
6 6/11 – 14/11 1) SRS Discussion
2) SRS Submission
10 11/12 – 18/12 1) Prototype Development
2) Progress Review
14 15/1 – 19/1 1) Prototype Testing
2) Prototype Presentation

Table 1.1 Milestones and Deliverables

1.4 Project Schedules (Updated and Latest)

1.4.1 Task breakdown

AHMAD DANIAL
HAKIM BIN
ROSMAN

TEAM LEADER

MUHAMMAD AZZARUDDIN BIN HEDZWEEN BINTI

HARITH IKHWAN ABDULLAH MOHD PUAD
BIN ROSMAENI
LEAD DOCUMENTER
LEAD DOCUMENTER
PROGRAMMER

Figure 2.1 Task Breakdown

SRS V 1.0 6 13/11/2023

1.4.2 Job assignments

Name Role Responsibility

Ahmad Danial Team • Ensures the progression of tasks assigned to the

Hakim Bin Leader team.
Rosman • These responsibilities commence prior to the
team’s assembly and persist until the team
disperses.

Muhammad Harith Lead • Developing, modifying, and crafting the

Ikhwan Bin Programmer system.
Rosmaeni • Monitoring programs for errors and assessing
their efficiency.
• Ensuring the programs are both efficient and
well-written, meeting deadlines for work
progress.

Azzaruddin Bin Lead • Oversees material availability and verification,

Abdullah Documenter as well as the preparation of essential
documents.
• Directs procedures in accordance with
authorized permissions.

Hedzween Binti Documenter • Oversees both internal and external audits to

Mohd Puad uphold quality in addressing issues.
• Contributes to maintaining and supervising
quality during maintenance management.

Table 2.1 Job Assignments

1.4.3 Gantt Chart

Figure 3.1 Gantt Chart

SRS V 1.0 7 13/11/2023

2.0. Functional Requirements

2.1 Overall UseCase Diagram

Figure 4.1 Overall UseCase Diagram

Table 3.1 Actor

ACTORS DESCRIPTION
CUSTOMER User that using the system from Arabic Restaurant
Management System to order the food that is listed on the
menu.
ADMINISTRATORS Employees of the Arabic Restaurant Management System.

To order for the customer, view the order from the customer
and review the sales and report for the month.

SRS V 1.0 8 13/11/2023

2.2 Details of Each Use Case

2.2.1 UC100: Register Account

Table 4.1 Register Account

Use Case ID UC100

Use Case Register Account
Name
Created By Ahmad Danial Hakim Last Updated by Muhammad Harith
Bin Rosman Ikhwan Bin Rosmaeni
Data Created 30/10/2023 Data Last Updated 13/11/2023

Actor: Customer, Administrators

Description: Customers need to register their full name, email address and date of birth
to sign up for an account. Customer will be needed to provide password
as a security to the account.
Preconditions: 1. Both the customer and administrators must meet specific criteria to
finalise the registration process.
2. An active email and password are essential for both customers and
administrators.
3. It is crucial for customers and administrators to recall their password
for seamless progression to the login stage.
4. Customers will additionally be asked to input their mobile number and
home address.
Post Conditions: Customer and administrator accounts have registered successfully
Priority: High
Frequency of Frequent
Use:
Normal Course Actor System
of Event:
1. Customer or administrator 1.1 System displays a registration page
navigate to the registration page. with two buttons ‘Admin’ and
‘Customer’.

2. Customers or administrator 2.1 System proceed to the registration

choose the button ‘Admin’ or page for administrator or customer.
‘Customer’.

SRS V 1.0 9 13/11/2023

 3. Customers or administrators
are required to input their full
name, email address, password,
and date of birth. The password
must include letters and a
number. Additionally, the
password must have a minimum
length of 6 characters.
4. Customer or administrators
click on ‘Register’ button.
Exception: <E1> Either customer or
administrator has skipped a step.
<E2> The email for the
customer or administrator has
been previously utilized.
<E3> The password for the
customer or administrator is less
than 6 characters in length.
<E4> The password for the
client or admin is invalid as it
lacks both upper- and lower-case
characters.
Includes: Login Account
Special Security
Requirements:
SRS V 1.0 10
3.1 System identifies and captures the
full name, email address, password,
and date of birth.
<E1> <E2> <E3> <E4>
4.1 System registers the personal
details of both customer and
administrator. Upon successful
registration, a confirmation will be
sent to the respective customer or
administrator email.
<E1.1> The system will display a
message for the client or
administrator: "Registration
unsuccessful.”
<E2.1> The system displays a
message for the client or
administrator: "Your email has been
used before. Please use another
email."
<E3.1> The system displays a
message for the client or
administrator: "Your password must
be longer than 6 characters."
<E4.1> The system displays a
message for the client or
administrator: "Your password must
contain both uppercase and lowercase
characters."
13/11/2023
 Assumptions: N/A
Notes and Issue: N/A

Activity Diagram

Figure 5.1 Register Account

SRS V 1.0 11 13/11/2023

2.2.2 UC200: Login Account

Table 5.1 Login Account

Use Case ID UC200

Use Case Login Account
Name
Created By Muhammad Harith Last Updated by Azzaruddin Bin Abdullah
Ikhwan Bin Rosmaeni
Data Created 30/10/2023 Data Last Updated 13/11/2023

Actor: Customer, Administrators

Description: Customers and administrators who have registered an account need to
login into the system by filling in their email and password.
Preconditions: 1. Both the customer and administrators are required to register their
accounts.
2. The password and email entered by both customers and administrators
must match.
3. The subsystem for both clients and administrators must be operational.
Post Conditions: Customer and administrator accounts have logged in successfully
Priority: High
Frequency of Frequent
Use:
Normal Course Actor System
of Event:
1. Customer or administrator 1.1 System displays a registration page
navigate to the login page. with two buttons ‘Admin’ and
‘Customer’.
2. Customers or administrator 2.1 System proceed to the login page
choose the button ‘Admin’ or for administrator or customer.
‘Customer’.

3. Customers or administrators 3.1 System detects email and

are required to input their email password matching.
address and password. <E1> <E2>

4. Customer or administrators 4.1 System redirect to menu.

click on ‘Login’ button.

SRS V 1.0 12 13/11/2023

 Exception: <E1> Either customer or <E1.1> The system will display a
administrator password and message for the client or
email does not match. administrator: "The email or password
you enter is incorrect.”

<E2> The email for the <E2.1> The system displays a

customer or administrator does message for the client or
not exist. administrator: "Your account does not
exist.”
Includes: N/A
Special Security
Requirements:
Assumptions: N/A
Notes and Issue: N/A

SRS V 1.0 13 13/11/2023

Activity Diagram

Figure 6.1 Login Account

SRS V 1.0 14 13/11/2023

2.2.3 UC300: Display Menu

Table 6.1 Display Menu

Use Case ID UC300

Use Case Display Menu
Name
Created By Azzaruddin Bin Last Updated by Hedzween Binti Mohd
Abdullah Puad
Data Created 30/10/2023 Data Last Updated 13/11/2023

Actor: Customer, Administrators

Description: Customers and administrators who have login to the account can view the
menu from the restaurant.
Preconditions: 1. Both the customer and administrators are required to log into the
system.
2. Customer and administrator may observe the displayed menu.
Post Conditions: Customer and administrator successfully select their order
Priority: High
Frequency of Frequent
Use:
Normal Course Actor System
of Event:
1. Customer or administrator 1.1 System displays the menu page.
choose the “menu” button.

2. Customers or administrators 2.1 System will display the item that is

can select on the item to view selected.
more detailed ingredients. <E1>
Exception: <E1> The item displayed is sold <E1.1> The system will display a
out. message for the client or
administrator: "This item is sold out.”
Includes: N/A
Special Security
Requirements:
Assumptions: N/A
Notes and Issue: N/A

SRS V 1.0 15 13/11/2023

Activity Diagram

Figure 7.1 Display Menu

SRS V 1.0 16 13/11/2023

2.2.4 UC400: Order Entry

Table 7.1 Order Entry

Use Case ID UC400

Use Case Order Entry
Name
Created By Hedzween Binti Mohd Last Updated by Ahmad Danial Hakim Bin
Puad Rosman
Data Created 30/10/2023 Data Last Updated 13/11/2023

Actor: Customer, Administrators

Description: Customers and administrators choose the order from the menu listed.
Preconditions: 1. Customers and administrators must check the availability of the item.
2. Customer and administrators must select an order from the menu.
Post Conditions: Customer and administrator successfully order food and beverages.
Priority: High
Frequency of Frequent
Use:
Normal Course Actor System
of Event:
1. Customer or administrator 1.1 System displays the order page.
select the item that is being <E1>
ordered.
2.1 System will display the altered
2. Customers or administrators selection.
choose to alter the order. <E2>

3. Customer or administrators 3.1 System will display a message for

select on ‘Order’ to confirm the client or administrator: “Your food has
order been ordered.”
Exception: <E1> The item displayed is sold <E1.1> The system will display a
out. message for the client or
administrator: "This item is sold out.”

<E2> The altered selection is not <E2.2> The system will display a
available message for the client or

SRS V 1.0 17 13/11/2023

 administrator: “The altered selection is
not available.”
Includes: N/A
Special Security
Requirements:
Assumptions: N/A
Notes and Issue: N/A

Activity Diagram

Figure 8.1 Order Entry

SRS V 1.0 18 13/11/2023

2.2.5 UC500: Additional Order

Table 8.1 Additional Order

Use Case ID UC500

Use Case Additional Order
Name
Created By Muhammad Harith Last Updated by Azzaruddin Bin Abdullah
Ikhwan Bin Rosmaeni
Data Created 30/10/2023 Data Last Updated 13/11/2023

Actor: Customer, Administrators

Description: Customers and administrators choose to add more orders.
Preconditions: 1. Customers and administrators must check the availability of the item.
2. Customer and administrators must select an order from the menu.
Post Conditions: Customer and administrator successfully order additional food and
beverages.
Priority: High
Frequency of Frequent
Use:
Normal Course Actor System
of Event:
1. Customer or administrator 1.1 System displays the menu page.
select on ‘Add More Items’
button.

2. Customers or administrators 2.1 System displays the order page.

choose the item to order. <E1>

3. Customers or administrators 3.1 System will display the altered

choose to alter the order. selection.
<E2>

4. Customer or administrators 4.1 System will display a message for

select on ‘Order’ to confirm the client or administrator: “Your food has
order been ordered.”

SRS V 1.0 19 13/11/2023

 Exception: <E1> The item displayed is sold <E1.1> The system will display a
out. message for the client or
administrator: "This item is sold out.”

<E2> The altered selection is not <E2.2> The system will display a
available message for the client or
administrator: “The altered selection is
not available.”
Includes: Additional Order
Special Security
Requirements:
Assumptions: N/A
Notes and Issue: N/A

SRS V 1.0 20 13/11/2023

Activity Diagram

Figure 9.1 Additional Order

SRS V 1.0 21 13/11/2023

2.2.6 UC600: Display Order

Table 9.1 Display Order

Use Case ID UC600

Use Case Display Order
Name
Created By Azzaruddin Bin Last Updated by Ahmad Danial Hakim Bin
Abdullah Rosman
Data Created 30/10/2023 Data Last Updated 13/11/2023

Actor: Customer, Administrators

Description: Customers and administrators view the items that is ordered.
Preconditions: Customers and administrators must check the item that is ordered.
Post Conditions: Customer and administrator successfully satisfied with the order.
Priority: High
Frequency of Frequent
Use:
Normal Course Actor System
of Event:
1. Customer or administrator 1.1 System displays the order detail
select on ‘Display Order’ button. page.

2. Customers or administrators 2.1 System will change the quantity of

can add the quantity of the item. data.
<E1>

3. Customers or administrators 3.1 System sends the order details to

select on the ‘Confirm’ button. the kitchen.
Exception: <E1> The item quantity is <E1.1> The system will display a
unavailable. message for the client or
administrator: "The quantity is not
available”.
Includes: Cancel Order
Special Security
Requirements:
Assumptions: N/A
Notes and Issue: N/A

SRS V 1.0 22 13/11/2023

Activity Diagram

Figure 10.1 Display Order

SRS V 1.0 23 13/11/2023

2.2.7 UC700: Cancel Order

Table 10.1 Cancel Order

Use Case ID UC700

Use Case Cancel Order
Name
Created By Muhammad Harith Last Updated by Hedzween Binti Mohd
Ikhwan Bin Rosmaeni Puad
Data Created 30/10/2023 Data Last Updated 13/11/2023

Actor: Customer, Administrators

Description: Customers and administrators cancel the items that is ordered.
Preconditions: Customers and administrators ordered an item.
Post Conditions: Customer and administrator cancel the order.
Priority: High
Frequency of Frequent
Use:
Normal Course Actor System
of Event:
1. Customer or administrator 1.1 System displays the message “Are
select on ‘Cancel’ button. you sure to cancel?”.
<E1>
2. Customers or administrators 2.1 System will display a message for
select on ‘Yes’ button. the client or administrator: “The order
is cancelled.”
Exception: <E1> The customer or <E1.1> The system will display a
administrator select on ‘No’ message for the client or
button. administrator: "The order is not
cancelled”.
Includes: N/A
Special Security
Requirements:
Assumptions: N/A
Notes and Issue: N/A

SRS V 1.0 24 13/11/2023

Activity Diagram

Figure 11.1 Cancel Order

SRS V 1.0 25 13/11/2023

2.2.8 UC800: Bill Generator

Table 11.1 Bill Generator

Use Case ID UC800

Use Case Bill Generator
Name
Created By Ahmad Danial Hakim Last Updated by Hedzween Binti Mohd
Bin Rosman Puad
Data Created 30/10/2023 Data Last Updated 13/11/2023

Actor: Customer, Administrators

Description: Customers and administrators can view the bill generated for the order.
Preconditions: Customers and administrators ordered an item.
Post Conditions: Customer and administrator successfully paid.
Priority: High
Frequency of Frequent
Use:
Normal Course Actor System
of Event:
1. Customer or administrator 1.1 System displays the bill id and
select on ‘Bill’ button. billing for the ordered.

2. Customers or administrators 2.1 System will display the receipt for

will pay the amount of the bill. the order.
<E1>
Exception: <E1> The customer or <E1.1> The system will display a
administrator has insufficient message for the client or
money. administrator: "The amount is
insufficient”
Includes: N/A
Special Security
Requirements:
Assumptions: N/A
Notes and Issue: N/A

SRS V 1.0 26 13/11/2023

Activity Diagram

Figure 12.1 Bill Generator

SRS V 1.0 27 13/11/2023

2.2.9 UC900: Sales

Table 12.1 Sales

Use Case ID UC900

Use Case Sales
Name
Created By Hedzween Binti Mohd Last Updated by Azzaruddin Bin Abdullah
Puad
Data Created 30/10/2023 Data Last Updated 13/11/2023

Actor: Administrators
Description: Administrators can record the sales daily or monthly.
Preconditions: Must have at least one transaction in a day.
Post Conditions: Sales must be recorded in the system.
Priority: High
Frequency of Frequent
Use:
Normal Course Actor System
of Event:
1. Administrator select on 1.1 System displays the sales page.
‘Sales’ button.
2.1 System will display the sales for
2. Administrators select on daily or monthly.
‘Daily’ or ‘Monthly’ button. <E1>

3. Administrator select on 3.1 System will record the data into a

‘Record the data’ button. file.
Exception: <E1> There is no sales for a day <E1.1> The system will display a
message for the administrator: "There
is no sales today”
Includes: N/A
Special Security
Requirements:
Assumptions: N/A
Notes and Issue: N/A

SRS V 1.0 28 13/11/2023

Activity Diagram

Figure 13.1 Sales

SRS V 1.0 29 13/11/2023

2.2.10 UC1000: Report

Table 13.1 Report

Use Case ID UC1000

Use Case Sales
Name
Created By Hedzween Binti Mohd Last Updated by Muhammad Harith
Puad Ikhwan Bin Rosmaeni
Data Created 30/10/2023 Data Last Updated 13/11/2023

Actor: Administrators
Description: Administrators record the profit report monthly.
Preconditions: Must have at least one transaction in a day.
Post Conditions: Report must be recorded in the system.
Priority: High
Frequency of Frequent
Use:
Normal Course Actor System
of Event:
1. Administrator select on 1.1 System displays the report page.
‘Report’ button. <E1>

2. Administrator select on 2.1 System will record the data into a

‘Record the data’ button. file.
Exception: <E1> There is no transaction for <E1.1> The system will display a
a month message for the administrator: "There
is no report”
Includes: N/A
Special Security
Requirements:
Assumptions: N/A
Notes and Issue: N/A

SRS V 1.0 30 13/11/2023

Activity Diagram

Figure 14.1 Report

SRS V 1.0 31 13/11/2023

3.0. Nonfunctional Requirements
3.1 Performance Requirements

The development of the Arabic Restaurant Management System's webpage will adhere to
a structured approach guided by the Software Development Life Cycle (SDLC). This
comprehensive process involves several distinct stages: planning, analysis, design,
implementation, and testing. Anticipated to be completed within a year, the system is designed to
address specific functionalities. It will store essential client information, such as full names, email
addresses, passwords, and dates of birth. Additionally, the system is configured to generate
receipts efficiently when clients complete their payments.

Considering the potential growth in the client base over time, a scalable database
architecture is a critical component of the system. This scalability ensures that the system can
accommodate an increasing volume of data and users without sacrificing performance.Response
times are a key consideration, especially in a scenario where multiple users may access the
system simultaneously. The goal is to maintain optimal efficiency, ensuring a seamless and
responsive experience for users interacting with the Arabic Restaurant Management System. This
emphasis on a well-structured SDLC, along with attention to scalability and response times,
contributes to the development of a robust and effective restaurant management solution.

3.2 Safety and Security Requirements

To ensure the security of the Arabic Restaurant Management System requirements, the
system must be safeguarded against any vulnerabilities, particularly the unauthorized disclosure
of client data. To achieve this, the system will implement a password authentication mechanism
to verify users before granting access to the webpage. This measure is designed to prevent the
leakage of client information and unauthorized access from external parties. Clients are only
permitted to initiate a booking session after establishing a client account and successfully logging
into the system. Within the system, clients are limited to managing bookings and updating their
personal details. For unique identification, the system will employ the telephone number as the
client ID. On the administrative side, an admin must create an admin account to access the
webpage. Admins have the capability to oversee bookings, track payment statuses, and cancel
reservations.

SRS V 1.0 32 13/11/2023

4.0. Requirements Reviews

Use Case Name Completed by Reviewed by Review Results

UC_100: Register Ahmad Danial Hakim Muhammad Harith Completed
Account Bin Rosman Ikhwan Bin
Rosmaeni
UC_200: Login Muhammad Harith Azzaruddin Bin Completed
Account Ikhwan Bin Rosmaeni Abdullah
UC_300: Display Azzaruddin Bin Hedzween Binti Completed
Menu Abdullah Mohd Puad
UC_400: Order Hedzween Binti Mohd Ahmad Danial Completed
Entry Puad Hakim Bin Rosman
UC_500: Additional Muhammad Harith Azzaruddin Bin Completed
Order Ikhwan Bin Rosmaeni Abdullah
UC_600: Display Azzaruddin Bin Ahmad Danial Completed
Order Abdullah Hakim Bin Rosman
UC_700: Cancel Muhammad Harith Hedzween Binti Completed
Order Ikhwan Bin Rosmaeni Mohd Puad
UC_800: Bill Ahmad Danial Hakim Hedzween Binti Completed
Generator Bin Rosman Mohd Puad
UC_900: Sales Hedzween Binti Mohd Azzaruddin Bin Completed
Puad Abdullah
UC_1000: Report Hedzween Binti Mohd Muhammad Harith Completed
Puad Ikhwan Bin
Rosmaeni

SRS V 1.0 33 13/11/2023