CAPSTONE PROJECT REPORT

Report 3 – Software Requirement Specification

– Hanoi, June 2021 –

FBS - Software Requirement Specification v2.0

Table of Contents
I. Project Report 11
1. Status Report 11
2. Team Involvements 11
3. Issues/Suggestions 11

II. Software Requirement Specification 12

1 Introduction 12
1.1 Purpose 12
1.2 Definitions, Acronyms and Abbreviations 12
1.3 References 13
2 Overall Description 14
2.1 Product Overview 14
2.2 Product Features 15
2.3 User requirements 20
2.4 User Classes and Characteristics 22
2.5 Operating Environment 22
2.6 Assumptions and Dependencies 23
2.7 Apportioning of Requirements 23
3 Functional Specification 23
3.1 Screen Overview 23
3.1.1 Screen Flow 23
3.1.2 Screen Description 24
3.2 Security Matrix 28
3.3 Entity Description 32
3.3.1 Entity Relationship Diagram 32
3.3.2 Entity Details 34
3.4 Common Business Rules 41
3.5 Detailed Functional Specification 43
3.5.1 Guest Functions 44
3.5.1.1 Use Case diagram 44
3.5.1.2 UC-01 - Search Restaurant 46
3.5.1.2.1 Screen Design 46

SWP490_G35 2/303
FBS - Software Requirement Specification v2.0

3.5.1.2.2 Use case Specification 49

3.5.1.3 UC-02 - View Restaurant Services 51
3.5.1.3.1 Screen Design 51
3.5.1.3.2 Use case Specification 53
3.5.1.4 UC-03 - View Restaurant Infor 54
3.5.1.4.1 Screen Design 54
3.5.1.4.2 Use case Specification 56
3.5.1.5 UC-04 - View Restaurant Combo 56
3.5.1.5.1 Screen Design 56
3.5.1.5.2 Use case Specification 58
3.5.1.6 UC-05 - Search Restaurant Dishes 59
3.5.1.6.1 Screen Design 59
3.5.1.6.2 Use case Specification 61
3.5.1.7 UC-06 - View Restaurant Dishes 62
3.5.1.7.1 Screen Design 62
3.5.1.7.2 Use case Specification 64
3.5.1.8 UC-07 - View Detail Item 65
3.5.1.8.1 Screen Design 65
3.5.1.8.2 Use case Specification 66
3.5.1.9 UC-08 - View All Promotions 68
3.5.1.9.1 Screen Design 68
3.5.1.9.2 Use case Specification 69
3.5.1.10 UC-09 - Register Account 70
3.5.1.10.1 Screen Design 70
3.5.1.10.2 Use case Specification 71
3.5.1.11 UC-10 – Chat With System 75
3.5.1.11.1 Screen Design 75
3.5.2 Customer Functions 75
3.5.2.1 Use Case diagram 75
3.5.2.2 UC-11 - Reset Password 78
3.5.2.2.1 Screen Design 78
3.5.2.2.2 Use case Specification 79

SWP490_G35 3/303
FBS - Software Requirement Specification v2.0

3.5.2.3 UC-12 - Sign In 82

3.5.2.3.1 Screen Design 82
3.5.2.3.2 Use case Specification 83
3.5.2.4 UC-13 - View Profile 84
3.5.2.4.1 Screen Design 84
3.5.2.4.2 Use case Specification 87
3.5.2.5 UC-14 - Update Profile 88
3.5.2.5.1 Screen Design 88
3.5.2.5.2 Use case Specification 89
3.5.2.6 UC-15 - Change Password 91
3.5.2.6.1 Screen Design 91
3.5.2.6.2 Use case Specification 92
3.5.2.7 UC-16 - Charge Account 95
3.5.2.7.1 Screen Design 95
3.5.2.7.2 Use case Specification 97
3.5.2.8 UC-17 - View Transaction Infor 99
3.5.2.8.1 Screen Design 99
3.5.2.8.2 Use case Specification 101
3.5.2.9 UC-18 - Withdraw 102
3.5.2.9.1 Screen Design 102
3.5.2.9.2 Use case Specification 104
3.5.2.10 UC-19 - Rate and Comment Restaurant 107
3.5.2.10.1 Screen Design 107
3.5.2.10.2 Use case Specification 108
3.5.2.11 UC-20 - Report Restaurant 109
3.5.2.11.1 Screen Design 109
3.5.2.11.2 Use case Specification 110
3.5.2.12 UC-21 - Create Feast Order 112
3.5.2.12.1 Screen Design 112
3.5.2.12.2 Use case Specification 114
3.5.2.13 UC-22 - View Order History 116
3.5.2.13.1 Screen Design 116

SWP490_G35 4/303
FBS - Software Requirement Specification v2.0

3.5.2.13.2 Use case Specification 118

3.5.2.14 UC-23 - View Order Detail 119
3.5.2.14.1 Screen Design 119
3.5.2.14.2 Use case Specification 122
3.5.2.15 UC-24 - Cancel Feast Order 123
3.5.2.15.1 Screen Design 123
3.5.2.15.2 Use case Specification 124
3.5.2.16 UC-25 - Add Restaurant 126
3.5.2.16.1 Screen Design 126
3.5.2.16.2 Use case Specification 128
3.5.2.17 UC-26 - View Notifications 131
3.5.2.17.1 Screen Design 131
3.5.2.17.2 Use case Specification 132
3.5.2.18 UC-27 - Sign Out 133
3.5.2.18.1 Use case Specification 133
3.5.3 UC-28 - Refund 134
3.5.3.1 Use case Specification 134
3.5.4 UC-29 - Authorize User 134
3.5.4.1 Use case Specification 134
3.5.5 Provider Functions 135
3.5.5.1 Use Case diagram 135
3.5.5.2 UC-30 - View List All Restaurants 139
3.5.5.2.1 Screen Design 139
3.5.5.2.2 Use case Specification 141
3.5.5.3 UC-31 - Update Restaurant Profile 142
3.5.5.3.1 Screen Design 142
3.5.5.3.2 Use case Specification 144
3.5.5.4 UC-32 - View List All Orders 147
3.5.5.4.1 Screen Design 147
3.5.5.4.2 Use case Specification 148
3.5.5.5 UC-33 - Search Order 150
3.5.5.5.1 Screen Design 150

SWP490_G35 5/303
FBS - Software Requirement Specification v2.0

3.5.5.5.2 Use case Specification 150

3.5.5.6 UC-34 - View Order 152
3.5.5.6.1 Screen Design 152
3.5.5.6.2 Use case Specification 154
3.5.5.7 UC-35 - Accept Order 155
3.5.5.7.1 Screen Design 155
3.5.5.7.2 Use case Specification 156
3.5.5.8 UC-36 - Cancel Order 159
3.5.5.8.1 Screen Design 159
3.5.5.8.2 Use case Specification 160
3.5.5.9 UC-37 - Complete Order 163
3.5.5.9.1 Screen Design 163
3.5.5.9.2 Use case Specification 164
3.5.5.10 UC-38 - View List All Combos 166
3.5.5.10.1 Screen Design 166
3.5.5.10.2 Use case Specification 167
3.5.5.11 UC-39 - Add Combo 168
3.5.5.11.1 Screen Design 168
3.5.5.11.2 Use case Specification 170
3.5.5.12 UC-40 - Update Combo 172
3.5.5.12.1 Screen Design 172
3.5.5.12.2 Use case Specification 175
3.5.5.13 UC-41 - View List All Dishes 177
3.5.5.13.1 Screen Design 177
3.5.5.13.2 Use case Specification 179
3.5.5.14 UC-42 - Search Dishes 180
3.5.5.14.1 Screen Design 180
3.5.5.14.2 Use case Specification 182
3.5.5.15 UC-43 - Add Dish 183
3.5.5.15.1 Screen Design 183
3.5.5.15.2 Use case Specification 185
3.5.5.16 UC-44 - Update Dish 187

SWP490_G35 6/303
FBS - Software Requirement Specification v2.0

3.5.5.16.1 Screen Design 187

3.5.5.16.2 Use case Specification 189
3.5.5.17 UC-45 - View List All Services 191
3.5.5.17.1 Screen Design 191
3.5.5.27.2 Use case Specification 193
3.5.5.18 UC-46 - Search Services 194
3.5.5.18.1 Screen Design 194
3.5.5.18.2 Use case Specification 196
3.5.5.19 UC-47 - Add Service 198
3.5.5.19.1 Screen Design 198
3.5.5.19.2 Use case Specification 199
3.5.5.20 UC-48 - Update Service 202
3.5.5.20.1 Screen Design 202
3.5.5.20.2 Use case Specification 203
3.5.5.21 UC-49 - View List All Promotions 206
3.5.5.21.1 Screen Design 206
3.5.5.2.2 Use case Specification 207
3.5.5.22 UC-50 - Add Promotion 208
3.5.5.22.1 Screen Design 208
3.5.5.22.2 Use case Specification 209
3.5.5.23 UC-51 - Update Promotion 213
3.5.5.23.1 Screen Design 213
3.5.5.23.2 Use case Specification 214
3.5.5.24 UC-52 - Add Restaurant Image 217
3.5.5.24.1 Screen Design 217
3.5.5.24.2 Use case Specification 219
3.5.5.25 UC-53 - Delete Restaurant Image 220
3.5.5.25.1 Screen Design 220
3.5.5.25.2 Use case Specification 222
3.5.6 Admin Functions 223
3.5.6.1 Use Case diagram 223
3.5.6.2 UC-54 - View Dashboard 227

SWP490_G35 7/303
FBS - Software Requirement Specification v2.0

3.5.6.2.1 Screen Design 227

3.5.6.2.2 Use case Specification 229
3.5.6.3 UC-55 - Search Order For Admin 229
3.5.6.3.1 Screen Design 229
3.5.6.3.2 Use case Specification 231
3.5.6.4 UC-56 - View Order Information 232
3.5.6.4.1 Screen Design 232
3.5.6.5.2 Use case Specification 234
3.5.6.5 UC-57 - Search Restaurant For Admin 235
3.5.6.5.1 Screen Design 235
3.5.6.5.2 Use case Specification 237
3.5.6.6 UC-58 - View Pending Restaurants 239
3.5.6.6.1 Screen Design 239
3.5.6.7.2 Use case Specification 240
3.5.6.7 UC-59 - View Detail Restaurant 241
3.5.6.7.1 Screen Design 241
3.5.6.7.2 Use case Specification 243
3.5.6.8 UC-60 - Approve Restaurant 244
3.5.6.8.1 Screen Design 244
3.5.6.8.2 Use case Specification 246
3.5.6.9 UC-61 - Cancel Restaurant 247
3.5.6.9.1 Screen Design 247
3.5.6.9.2 Use case Specification 249
3.5.6.10 UC-62 - Block Restaurant 250
3.5.6.10.1 Screen Design 250
3.5.6.10.2 Use case Specification 251
3.5.6.11 UC-63 - Unblock Restaurant 253
3.5.6.11.1 Screen Design 253
3.5.6.11.2 Use case Specification 254
3.5.6.12 UC-64 - View Notifications For Admin 255
3.5.6.12.1 Screen Design 255
3.5.6.12.2 Use case Specification 256

SWP490_G35 8/303
FBS - Software Requirement Specification v2.0

3.5.6.13 UC-65 - View All Reports 257

3.5.6.13.1 Screen Design 257
3.5.6.13.2 Use case Specification 258
3.5.6.14 UC-66 - Deactivate Item In Restaurant 259
3.5.6.14.1 Screen Design 259
3.5.6.14.2 Use case Specification 262
3.5.6.15 UC-67 - View FBS Wallet 263
3.5.6.15.1 Screen Design 263
3.5.6.15.2 Use case Specification 265
3.5.6.16 UC-68 - Search Transaction 266
3.5.6.16.1 Screen Design 266
3.5.6.16.2 Use case Specification 267
3.5.6.17 UC-69 - Search Money Processing 268
3.5.6.17.1 Screen Design 268
3.5.6.17.2 Use case Specification 270
3.5.6.18 UC-70 - Accept Money Processing 271
3.5.6.18.1 Screen Design 271
3.5.6.18.2 Use case Specification 272
3.5.6.19 UC-71 - Cancel Money Processing 273
3.5.6.19.1 Screen Design 273
3.5.6.19.2 Use case Specification 273
3.5.6.20 UC-72 - Recharge Processing 274
3.5.6.20.1 Screen Design 274
3.5.6.20.2 Use case Specification 276
3.5.6.21 UC-73 - Search User 278
3.5.6.21.1 Screen Design 278
3.5.6.21.2 Use case Specification 280
3.5.6.22 UC-74 - View User Profile 281
3.5.6.22.1 Screen Design 281
3.5.6.22.2 Use case Specification 282
3.5.6.23 UC-75 - Block User 283
3.5.6.23.1 Screen Design 283

SWP490_G35 9/303
FBS - Software Requirement Specification v2.0

3.5.6.23.2 Use case Specification 285

3.5.6.24 UC-76 - Unblock User 286
3.5.6.24.1 Screen Design 286
3.5.6.24.2 Use case Specification 288
4 Non-Functional Requirements 289
4.1 External Interfaces 289
4.1.1 User Interfaces 289
4.1.2 Software Interfaces 289
4.1.2.1 Microsoft SQL Server 289
4.1.2.2 FireBase 289
4.1.2.3 Facebook Messenger 289
4.1.2.4 PayPal 289
4.1.3 Communications Interfaces 290
4.2 Quality Attributes 290
4.2.1 Usability 290
4.2.2 Reliability 290
4.2.3 Availability 290
4.2.4 Performance 290
4.2.5 Security 291
4.2.6 Safety 291
4.2.7 Supportability 291
4.2.8 Design Constraints 291
4.2.9 Support Documents 292
5 Other Requirements 292
5.1 Appendix1 - Messages List 292
5.2 Appendix2 - Firebase 300
5.3 Appendix3 - Facebook Messenger 301
5.4 Appendix4 - PayPal 302

SWP490_G35 10/303
FBS - Software Requirement Specification v2.0

I. Project Report
1. Status Report

# Work Item Status Notes (Work Item in Details)

1 Overall Description Completed

2 Functional Specification Completed

Non-functional
3 Requirements Completed

4 Other Requirements Completed

2. Team Involvements

# Task Member Notes (Task Details, etc.)

1 Write SRS Document TrangTLH

2 Design Use Case ThaoHTP

AnhHT -
3 Design Mockup TrangTLH

3. Issues/Suggestions

# Issue Status Notes (Solution, Suggestion, etc.)

1 Pending

2 In Progress

3 Completed

SWP490_G35 11/303
FBS - Software Requirement Specification v2.0

II. Software Requirement Specification

1 Introduction
1.1 Purpose

This chapter outlines functional and non-functional requirements of our system. It also provides
some format constraints in common requirements and project success criteria. The content of this
chapter is used as the basis for the work in the subsequent chapters.

1.2 Definitions, Acronyms and Abbreviations

# Acronym Definition

1 FBS Online Feast Booking System

2 BR Business rules

3 UC Use case

4 PRE Preconditions

5 E1, E2,... Exceptions

6 BA Business Analysis

7 QA Quality Assurance

8 REQ Requirement

Guest, who does not have an account and accesses the Online
9 FBSGuest
Feast Booking System website

Customer, who has an account and accesses Online Feast Booking

10 FBSCustomer
System website

Provider, who has an account and accesses and completed

11 FBSProvider registration as a provider of the Online Feast Booking System
website

12 FBSAdmin The Online Feast Booking System website system manager

13 User The term includes FBSGuest, FBSCustomer, FBSProvider, FBSAdmin

14 MSG Message

15 URL Uniform Resource Locator

16 MVC Model - View - Controller

17 HTTP Hypertext Transfer Protocol

18 RAM Random Access Memory

SWP490_G35 12/303
FBS - Software Requirement Specification v2.0

19 OS Operating System

20 OTP One Time Passcode

21 TCP/IP Transmission Control Protocol/ Internet Protocol

22 CPU Central Processing Unit

23 SSL Secure Sockets Layer

Table 1-1: Definitions, Acronyms, and Abbreviations

1.3 References

Title/Filename/ Effective Source/

# Author Version Description
Web address Date Location

Website Trống Đồng Trống Đồng Website for function

1 05/2021
Palace Palace reference

Website for function

2 Website The Food 05/2021 The Food
reference

Refer to the
documentation and
3 MVC Overview 05/2021 MVC
usage of the MVC
model

Refer to the
documentation and
4 Spring boot Overview 05/2021 Spring boot
usage of the Spring
boot

Refer to the
documentation,
5 React Overview 05/2021 React usage, and templates
of the ReactJS
framework

Refer to the
FBS_Report2_Project
SWP490 documentation about
6 Management 1 05/2021 Project folder
_G35 the project
Plan.docx
management plan

SWP490 Refer to the Use case

7 FBS_Work assignment 2 05/2021 Project folder
_G35 plan of the system

Refer to the design

SWP490
8 FBS_Mock up 2 05/2021 Project folder document mockup of
_G35
the system
Table 1-2: References of System

SWP490_G35 13/303
FBS - Software Requirement Specification v2.0

2 Overall Description
2.1 Product Overview

FBS is a new software system that replaces manual processes for party booking, menu selection, and
service. The context diagram below illustrates the external entities and system interfaces for version
2.0. The system is expected to evolve over several releases, eventually connecting to an Internet party
booking service for party centers and customers

Figure 2-1: FBS System Overview

As described in figure 2-1, the system will have the following components:
● FBS Software
● FBS Guest
● FBS Customer
● FBS Provider
● FBS Admin
● PayPal

SWP490_G35 14/303
FBS - Software Requirement Specification v2.0

● Firebase
● Facebook Messenger

2.2 Product Features

The software has the functions described in the table below

Group Use Case

User case Name Description
Function ID

Allow the user to search restaurant

by province/city, county/district, by
UC-01 Search Restaurants
organizing a roving feast or
organizing a restaurant feast

Allow the user to view all services of

UC-02 View Restaurant Services
the restaurant.

Allow the user to view detailed

UC-03 View Restaurant Infor
information about the restaurant.

Allow the user to view all combos of

UC-04 View Restaurant Combos
the restaurant.

Allow the user to search dishes of

UC-05 Search Restaurant Dishes
the restaurant by keywords.
FBSGuest Allow the user to view all dishes of
Functions UC-06 View Restaurant Dishes Commented [1]: Đổi Features --> Functions
the restaurant.

Allow the user to view detailed

UC-07 View Detail Item information of items in the
restaurant.

Allow the user to view all coming

UC-08 View All Promotions and ongoing promotions of all
restaurants on the FBS system.

Allow the user who does not have an

UC-09 Register Account account in the system to register a
new account.

Allow the user to chat with FBS’s

UC-10 Chat With System page in Facebook via Facebook
Messenger

Allow the authorized user to reset

UC-11 Reset Password
the password.
FBSCustomer
Functions Allow the authorized user to sign in
UC-12 Sign In
to FBS.

SWP490_G35 15/303
FBS - Software Requirement Specification v2.0

Allow the authorized user to view

UC-13 View Profile
his/her profile.

Allow the authorized user to update

UC-14 Update Profile
his/her information.

Allow the authorized user to change

UC-15 Change Password
the password.

Allow the authorized user to top up

UC-16 Charge Account
their accounts on the FBS system.

Allow the authorized user to review

UC-17 View Transaction Infor
all transactions history.

Allows the authorized user to

UC-18 Withdraw withdraw funds from their FBS
system accounts.

Rate and Comment Allow the authorized user to rate

UC-19
Restaurant and comment on a restaurant.

Allow the authorized user to report

UC-20 Report Restaurant dishes, combos, or services of the
restaurant to the admin.

Allow the authorized user to create a

feast order by choosing the menu
UC-21 Create Feast Order
and services, and fill in some
information.

Allow the authorized user to view

order history such as pending
UC-22 View Order History
orders, preparing orders, accomplish
orders, and canceled orders.

Allow the authorized user to view

UC-23 View Order Detail
detailed information on orders.

Allow authorized the user to cancel

UC-24 Cancel Feast Order
his/her order.

Allow the authorized user to add a

UC-25 Add Restaurant
new restaurant into the FBS system.

Allow the authorized user to view

UC-26 View Notifications
notifications

Allow the authorized user to sign out

UC-27 Sign Out
to FBS.

The system automatically deducts

Refund UC-28 Refund the commission and refunds the
deposit to the provider after the

SWP490_G35 16/303
FBS - Software Requirement Specification v2.0

order is completed. In addition, if

the customer cancels the order, the
deposit will also be refunded
according to the regulations and
based on the time of cancellation

Authorize User UC-29 Authorize User Verify the user's role.

Allow the authorized user to view all

UC-30 View List All Restaurants
restaurants that he/she has.

Allow the authorized user to update

UC-31 Update Restaurant Profile
restaurant detailed information.

Allow the authorized user to view

UC-32 View List All Orders
the list of all orders from customers.

Allow the authorized user to search

UC-33 Search Order the order from customers by order
code.

Allow the authorized user to view

UC-34 View Order the detailed information of the
order from the customer.

Allow the authorized user to accept

UC-35 Accept Order
orders from the customers.

Allow the authorized user to cancel

UC-36 Cancel Order
the order from the customer.
FBSProvider
Functions Allow the authorized user to
UC-37 Complete Order complete the order from the
customer.

Allow the authorized user to view

UC-38 View List All Combos the list of all combos of own
restaurant

Allow the authorized user to add a

UC-39 Add Combo
new combo into the restaurant.

Allow the authorized user to update

UC-40 Update Combo detailed information about a combo
of the restaurant.

Allow the authorized user to view

UC-41 View List All Dishes the list of all dishes of own
restaurant

Allow the authorized user to search

UC-42 Search Dish the dish of his/her restaurant by
keywords name and dish’s category.

SWP490_G35 17/303
FBS - Software Requirement Specification v2.0

Allow the authorized user to add a

UC-43 Add Dish
new dish to the restaurant.

Allow the authorized user to update

UC-44 Update Dish detailed information about a dish of
the restaurant.

Allow the authorized user to view

UC-45 View List All Services the list of all services of own
restaurant

Allow the authorized user to search

the service of his/her restaurant by
UC-46 Search Service
keywords name and service’s
category.

Allow the authorized user to add a

UC-47 Add Service
new service to the restaurant.

Allow the authorized user to update

UC-48 Update Service detailed information about a service
of the restaurant.

Allow the authorized user to view

UC-49 View List All Promotions the list of all promotions of own
restaurant

Allow the authorized user to add a

UC-50 Add Promotion
new promotion to the restaurant.

Allow the authorized user to update

UC-51 Update Promotion detailed information about a
promotion of the restaurant.

Allow the authorized user to add a

UC-52 Add Restaurant Image
description image for the restaurant.

Allow the authorized user to delete a

UC-53 Delete Restaurant Image
description image of the restaurant.

Allow the authorized user to view

UC-54 View Dashboard
the dashboard in the days.

Allow the authorized user to search

UC-55 Search Order For Admin
orders of the system.

FBSAdmin Allow the authorized user to view

Functions UC-56 View Order Information detailed information about the
system.

Search Restaurant For Allow the authorized user to search

UC-57
Admin restaurants on the system.

UC-58 View Pending Restaurants Allow the authorized user to view

SWP490_G35 18/303
FBS - Software Requirement Specification v2.0

the list of all pending restaurants of

the system.

Allow the authorized user to view

UC-59 View Detailed Restaurant the detailed information restaurant
of the system.

Allow the authorized user to

UC-60 Approve Restaurant
approve a new restaurant.

Allow the authorized user to change

UC-61 Cancel Restaurant
the status of restaurants to cancel.

Allow the authorized user to block

UC-62 Block Restaurant
the reported restaurant.

Allow the authorized user to unblock

UC-63 Unblock Restaurant
the restaurant.

View Notifications For Allow the authorized user to view

UC-64
Admin notifications.

Allow the authorized user to view

UC-65 View All Reports
the list of all reports of the system.

Allow the authorized user to

Deactivate Item In
UC-66 deactivate the reported dish,
Restaurant
combo, or service of the restaurants

Allow the authorized user to view all

UC-67 View FBS Wallet
transactions history.

Allow the authorized user to search

UC-68 Search Transaction
transaction history.

Allow the authorized user to search

money processing including
UC-69 Search Money Processing
recharge manager, withdrawal
management.

Allows the authorized user to

UC-70 Accept Money Processing confirm deposit and withdrawal
requests from customers.

Allows the authorized user to cancel

UC-71 Cancel Money Processing deposit and withdrawal requests
from customers.

Allow authorized users to top up FBS

UC-72 Recharge Processing wallets for customers after receiving
customer’s cash.

Allow the authorized user to search

UC-73 Search User
for users of the system.

SWP490_G35 19/303
FBS - Software Requirement Specification v2.0

Allow the authorized user to view

UC-74 View User Profile
the profile of the user of the system.

Allow the authorized user to block

UC-75 Block User
the violated user.

Allow the authorized user to unblock

UC-76 Unblock User
the user.

Table 2-1: Products Features of System

2.3 User requirements

REQ1: Guest does not need to register or log in to still search, view information, and view items in
the restaurant
REQ2: User should be able to search for restaurants by province/city, county/district, by organizing a
roving feast or organizing a restaurant feast
REQ3: User should be able to view search results in the search screen
REQ4: User should be able to view all restaurants information such as restaurant overview, menu,
combo, services, promotions, and customers’ feedbacks of restaurants
REQ5: User should be able to search dishes and services by keyword in the restaurant Commented [2]: Thay các từ can thành các từ should
be able to - nếu là các yêu cầu bắt buộc
REQ6: User should be able to select restaurants through promotions on the promotion view page
REQ7: User can chat with the system through Facebook Messenger in case of items being removed, Commented [3R2]: _Marked as resolved_
the restaurant is blocked or account is blocked or any other case where the user needs help Commented [4R2]: _Re-opened_
REQ8: Guest should be able to register an account of the system to become a customer
REQ8: User should be able to sign in, sign out the system when he/she has an account
REQ9: Customer should be able to reset password if he/she forgets, and change password if he/she
needs
REQ10: Customer should be able to view and edit their information in their profile
REQ11: Customer should be able to review transaction history, see the amount added and
subtracted from the FBS wallet
REQ12: Customer should be able to pay in by transferring money to the system and making a request
for the admin to transfer that amount to the FBS wallet. When he/she pays in, he/she can choose
the payment method.
REQ13: Customer should be able to withdraw money by making a withdrawal request and providing
account information or going to a cash pick-up place. When he/she withdraws, he/she can choose
the payment method.
REQ14: Customer should be able to review transaction history, see the amount added and
subtracted from the FBS wallet
REQ15: Customer should be able to rate, comment for each restaurant. He/she should be able to
choose a star number to rate and fill the comment
REQ16: Customer should be able to report a restaurant or an item in the restaurant for the system
REQ17: Customer should be able to choose dishes from the restaurant menu, service from one
restaurant to add to his/her cart, and then he/she will be able to deposit. When he/she deposits,
he/she can choose the payment method.

SWP490_G35 20/303
FBS - Software Requirement Specification v2.0

REQ18: Customer should be able to view the order history. In the order list, he/she should be able to
view the detailed information of an order.
REQ19: Customer should be able to cancel the order but the deposit will not be refunded if the
cancellation time exceeds the time allowed to cancel the order. In some cases, if the customer
cancels the order close to the time, compensation must be paid
REQ20: Customer should be able to view notifications from the system or restaurant
REQ21: Customer should be able to come to a provider when he/she registers a restaurant to the
system and wait for the admin to accept this restaurant.
REQ22: Provider should be able to view all his/her restaurants. In this list, he/she should be able to
view detailed information about the restaurant.
REQ23: Provider should be able to view and manage detailed information about the restaurant.
REQ24: Provider should be able to search his/her orders from the customer by order code or by date
to date.
REQ25: Provider should be able to view his/her orders from the customer. In the order list, he/she
should be able to view the detailed information of the order and reject or accept orders that have
pending status.
REQ26: Provider should be able to view all items in his/her restaurant including dishes, combos,
services, and promotions. He/she should be able to add a new item, and manage items.
REQ27: Provider should be able to search dishes and services of his/her restaurant by keyword name
and category.
REQ28: Provider should be able to view and manage all images of his/her restaurant, including
avatar and description image.
REQ29: Admin should be able to understand the data related to the number of orders, the number
of restaurants in the system, and the number of customers using the system.
REQ30: Admin should be able to view all the orders of the system.
REQ31: Admin should be able to search order by order code or by date to date.
REQ32: Admin should be able to view detailed information of an order to be able to manage the
amount of commission that the system receives after each order.
REQ33: Admin should be able to view all restaurants of the system. In case the restaurant violates
the system's terms or is reported by the customer, the admin should be able to block that
restaurant.
REQ34: Admin should be able to unblock the restaurant if the provider proves the restaurant is not
violated or the restaurant has resolved problems with the customer.
REQ35: Admin should be able to view detailed information about a restaurant.
REQ36: Admin should be able to search a restaurant by keyword name, status, or type.
REQ37: Admin should be able to view notifications from users.
REQ38: Admin should be able to view customer’s reports and resolve customer complaints. In case
the customer complains correctly, the admin should be able to solve it. For example, for a dish to
stop selling.
REQ39: Admin should be able to view all items of the restaurant and remove them from the system
if they are reported by the customer and they violate the law or the terms of the system.
REQ40: Admin should be able to search dishes and services of his/her restaurant by keyword name
and category.
REQ41: Admin should be able to manage the system's transactions, manage money in and out of the
system.

SWP490_G35 21/303
FBS - Software Requirement Specification v2.0

REQ42: Admin should be able to search transactions by transaction code, date, and status of the
transaction.
REQ43: Admin should be able to manage the accounts registered with the system. In case an account
has bad behavior, admin should be able to block that account from the system.
REQ44: Admin should be able to unblock the account if the user proves the account is not violate
REQ45: Admin should be able to view the profile of an account.
REQ46: Admin should be able to search an account by keyword name, phone login, or role of
account.
REQ47: Guest should be able to view detailed information on dishes, combos, and services.
REQ48: Once the order has been completed and the customer has successfully paid for the
restaurant, the provider should be able to mark the order status as completed.
REQ49: Admin should be able to search the transaction history of the FBS system by transaction
code, transaction status, or transaction execution date.
REQ50: Admin should be able to search customer's deposit and withdrawal requests by transaction
code transaction execution date.
REQ51: Admin should be able to confirm or cancel deposit and withdrawal requests from customers.
REQ52: Admin should be able to top up the FBS wallet for customers after receiving customer’s cash.
REQ53: Provider authorizes employee accounts to manage the restaurant.
REQ54: Customers can give specific feedback for food, service, service quality.
REQ55: The provider has to pay for advertising to have the restaurant appear on the homepage.
REQ56: The percentage of commission that the system receives with each order depends on each
restaurant and each order.
REQ57: Restaurants should be able to decide when customers are allowed to cancel orders and how
to compensate for canceled orders.

2.4 User Classes and Characteristics

The software will have the following user groups

# Actor/User group Description

Everyone who does not have an account and accesses FBS

1 FBSGuest
websites.

2 FBSCustomer Everyone who has an account and accesses FBS websites.

Everyone who has an account and accesses FBS websites and

3 FBSProvider
completed registration as a provider

4 FBSAdmin The FBS website system manager

Table 2-2: Description of Software Actors

2.5 Operating Environment

- Server: Amazon Web Service (AWS)

- Database: SQL Server 2017

SWP490_G35 22/303
FBS - Software Requirement Specification v2.0

- Clients are Laptop and PC devices. The target OS is:

+ Window 7 or above
- FBS is supported on many web browsers:
+ Chrome
+ Internet Explorer
+ Microsoft Edge
+ Cốc Cốc
All communications with clients have to comply with public HTTP, TCP/IP communication protocol
standards.

2.6 Assumptions and Dependencies

Assumptions:
- Customer supports in the coding process, the requirements are researched from customer
- Customer will provide adequately supporting the effort to understand the requirements of
the current system
- Customer will provide the graphic assets (images, icons…) so that team can use them to
design the UI of the new systems
- Customer will provide the data so that team can use them to design the database of the new
systems
- Assuming restaurants can be managed by a provider
- Assuming the system's ordering process is correct
- Assuming that each restaurant in a certain period only holds one promotion
- Assuming the process of depositing and withdrawing money into the system is correct
- Admin's account will be provided by the system and admin does not have the right to edit
information
Dependencies:
- Verifying phone number by OTP code with Firebase Phone Authentication
- Chat with the system's page via Facebook messenger
- Pay order, top-up FBS wallet, and withdraw money from FBS wallet via PayPal

2.7 Apportioning of Requirements

- Provider authorizes employee accounts to manage the restaurant

- Customers can specific feedback for food, service, service quality
- The provider has to pay for advertising to have the restaurant appear on the homepage
- The percentage of commission that the system receives with each order depends on each
restaurant and each order
- Restaurants should be able to decide when customers are allowed to cancel orders and how
to compensate for canceled orders

3 Functional Specification
3.1 Screen Overview
3.1.1 Screen Flow

SWP490_G35 23/303
FBS - Software Requirement Specification v2.0

Commented [5]: Các màn hình dùng hình chữ nhật để

biểu diễn cho thống nhất
Figure 3-1: Screen flow
Commented [6R5]: _Marked as resolved_
Commented [7R5]: _Re-opened_

3.1.2 Screen Description

# Feature Screen Description

1 Guest Home Home

SWP490_G35 24/303
FBS - Software Requirement Specification v2.0

2 Guest Search Restaurant The screen is used for search restaurants

Restaurant Detail The screen is used to view restaurant detailed

3 Guest
Information information

4 Guest Restaurant Detail Menu The screen is used for view and search dishes

5 Guest Restaurant Detail Combo The screen is used to view restaurant combo

6 Guest Restaurant Detail Service The screen is used for view and search services

The screen is used to view detailed information of

7 Guest Item Detail
item: dish, combo, service

The screen is used to view all coming an active

8 Guest Promotion
promotions of the system

Guest enter full name, phone number, password,

9 Guest Register
and OTP code to register their account

This screen is used to get password if user forgot

10 Customer Forget Password
their password

This screen is used to sign in to the system with

11 Customer Login
phone login and password

12 Customer User Profile View user information profile

13 Customer Update Profile This screen is used to update user profile

This screen is used for the user to change

14 Customer Change Password
password

This screen is used to view all information of the

15 Customer Wallet Information
FBS wallet

16 Customer Pay In This screen is used to top-up for the FBS wallet

This screen is used to withdraw from the FBS

17 Customer Withdrawal
wallet

This screen is used to report a restaurant to the

18 Customer Report
system admin

This screen is used to enter information about the

19 Customer Cart
order and create a feast order

This screen is used to choose a method and make

20 Customer Deposit
a deposit for the order

21 Customer Pending Orders This screen is used to view all pending orders

This screen is used to view all orders waiting to be

22 Customer Preparing Orders
accepted

SWP490_G35 25/303
FBS - Software Requirement Specification v2.0

This screen is used to view all accomplished

23 Customer Accomplished Orders
orders

24 Customer Canceled Orders This screen is used to view all canceled orders

25 Customer Add Restaurant This screen is used to add a restaurant

This screen is used to view detailed

26 Customer User Profile Order Detail
information order

This screen is used to enter password to cancel an

27 Customer Cancel Order
order

28 Customer Notification This screen is used to view all notifications

When a customer logs into the system, there is an

Restaurant Detail
29 Customer additional feedback function for the restaurant
Information
on this screen

This screen is used to view all restaurants in the

30 Provider My Restaurants
system

My Restaurant This screen is used to view detailed information

31 Provider
Information about a restaurant

This screen is used to view all orders of restaurant

32 Provider My Restaurant Order
and search order by order code

My Restaurant Order This screen is used to view detailed information

33 Provider
Detail on the order

My Restaurant Accept This screen is used to enter password to accept

34 Provider
Order an order from the customer

My Restaurant Cancel This screen is used to enter password to reject an

35 Provider
Order order from the customer

My Restaurant Complete This screen is used to enter password to complete

36 Provider
Order an order from the customer

My Restaurant Complete This screen is used to enter password to mark an

37 Provider
Order order as completed order

My Restaurant Confirm This screen is used to enter password to accept

38 Provider
Deposit deposits for an order

This screen is used to view all combos of

39 Provider My Restaurant Combo
restaurant

My Restaurant Add This screen is used to add a new combo to the

40 Provider
Combo restaurant

My Restaurant Update This screen is used to update a combo of

41 Provider
Combo restaurant

SWP490_G35 26/303
FBS - Software Requirement Specification v2.0

My Restaurant Add Dish This screen is used to add a dish to the combo of
42 Provider
Combo restaurant

This screen is used to view all dishes and search

43 Provider My Restaurant Menu dishes by keyword name and category of dishes
in the restaurant

This screen is used to add a new dish to the

44 Provider My Restaurant Add Menu
restaurant

My Restaurant Update This screen is used to update a dish of the

45 Provider
Menu restaurant

This screen is used to view all services and search

46 Provider My Restaurant Service services by keyword name and category of
services in the restaurant

My Restaurant Add This screen is used to add a new service to the

47 Provider
Service restaurant

My Restaurant Update This screen is used to update service of the

48 Provider
Menu restaurant

My Restaurant This screen is used to view all promotions of

49 Provider
Promotion restaurant

My Restaurant Add This screen is used to add a new promotion to the

50 Provider
Promotion restaurant

My Restaurant Update This screen is used to update a promotion of a

51 Provider
Promotion restaurant

My Restaurant Add This screen is used to add a new image to the

52 Provider
Image restaurant

This screen is used to view description images

53 Provider My Restaurant Image
and remove an image from the restaurant

This screen is used to view the dashboard of the

54 Admin Admin
system

This screen is used to view all orders of the

55 Admin Admin Orders
system

This screen is used to view detailed information

56 Admin Admin Order Detail
of an order

This screen is used to view all accounts of the

57 Admin Admin Customers
system

This screen is used to view the profile of the

58 Admin Admin Customer Profile
account

59 Admin Admin List Restaurants This screen is used to view all restaurants of the

SWP490_G35 27/303
FBS - Software Requirement Specification v2.0

system

This screen is used to view all new registered

60 Admin Admin New Restaurants
restaurants of the system

Admin Restaurant This screen is used to view detailed information

61 Admin
Information about a restaurant

This screen is used to view all images of a

62 Admin Admin Restaurant Image
restaurant

This screen is used to view all dishes of a

63 Admin Admin Restaurant Menu
restaurant

This screen is used to view detailed information

Admin Restaurant Menu
64 Admin about a dish, if the dish is violated the terms,
Detail
users can block it from the restaurant

This screen is used to view combos of a

65 Admin Admin Restaurant Combo
restaurant

This screen is used to view detailed information

Admin Restaurant Combo
66 Admin of a combo, if the combo is violated the terms,
Detail
users can block it from the restaurant

This screen is used to view all services of a

67 Admin Admin Restaurant Service
restaurant

This screen is used to view detailed information

Admin Restaurant Service
68 Admin about a service, if the service is violated the
Detail
terms, users can block it from the restaurant

Admin Wallet This screen is used to view all information of the

69 Admin
Information FBS wallet

This screen is used to manage the top-up history

70 Admin Admin Pay In Information
of the FBS wallet

Admin Recharge This screen is used to process FBS wallet deposit

71 Admin
Processing requests for customers

Admin Withdrawal This screen is used to manage to withdraw history

72 Admin
Information of the FBS wallet

73 Admin Admin Notification This screen is used to view all notifications

74 Admin Admin Report This screen is used to view all report

Table 3-1: Screen Description

3.2 Security Matrix

SWP490_G35 28/303
FBS - Software Requirement Specification v2.0

UC ID Use Case Name Screen Name Guest Customer Provider Admin

UC-01 Search Restaurants Search Restaurant X X X

View Restaurant Restaurant Detail

UC-02 X X X
Services Service

View Restaurant Restaurant Detail

UC-03 X X X
Infor Information

View Restaurant Restaurant Detail

UC-04 X X X
Combos Combo

Search Restaurant Restaurant Detail

UC-05 X X X
Dishes Menu

View Restaurant Restaurant Detail

UC-06 X X X
Dishes Menu

UC-07 View Detail Item Item Detail X X X

UC-08 View All Promotions Promotion X X X

UC-09 Register Account Register X

UC-10 Chat With System Home X X X

UC-11 Reset Password Forget Password X X

UC-12 Sign In Login X X X

UC-13 View Profile User Profile X X

UC-14 Update Profile Update Profile X X

UC-15 Change Password Change Password X X

UC-16 Charge Account Pay In X X

View Transaction
UC-17 Wallet Information X X
Infor

UC-18 Withdraw Withdrawal X X

Rate And Comment Restaurant Detail

UC-19 X X
Restaurant Information

UC-20 Report Restaurant Report X X

UC-21 Create Feast Order Cart X X

UC-22 View Order History User Profile Order X X

User Profile Order

UC-23 View Order Detail X X
Detail

SWP490_G35 29/303
FBS - Software Requirement Specification v2.0

UC-24 Cancel Feast Order Cancel Order X X

UC-25 Add Restaurant Add Restaurant X X

UC-26 View Notifications Notification X X

UC-27 Sign Out Home X X X

UC-28 Refund Commented [8]: Gắn liền với màn hình nào??

UC-29 Authorize User

View List All

UC-30 My Restaurants X
Restaurants

Update Restaurant My Restaurant

UC-31 X
Profile Detail

My Restaurant
UC-32 View List All Orders X
Order

My Restaurant
UC-33 Search Order X
Order

My Restaurant
UC-34 View Order X
Order Detail

My Restaurant
UC-35 Accept Order X
Accept Order

My Restaurant
UC-36 Cancel Order X
Cancel Order

My Restaurant
UC-37 Complete Order X
Complete Order

View List All My Restaurant

UC-38 X
Combos Combo

My Restaurant Add
UC-39 Add Combo X
Combo

My Restaurant
UC-40 Update Combo X
Update Combo

My Restaurant
UC-41 View List All Dishes X
Menu

My Restaurant
UC-42 Search Dish X
Menu

My Restaurant Add
UC-43 Add Dish X
Menu

My Restaurant
UC-44 Update Dish X
Update Menu

SWP490_G35 30/303
FBS - Software Requirement Specification v2.0

View List All My Restaurant

UC-45 X
Services Service

My Restaurant
UC-46 Search Service X
Service

My Restaurant Add
UC-47 Add Service X
Service

My Restaurant
UC-48 Update Service X
Update Service

View List All My Restaurant

UC-49 X
Promotions Promotion

My Restaurant Add
UC-50 Add Promotion X
Promotion

My Restaurant
UC-51 Update Promotion X
Update Promotion

Add Restaurant My Restaurant Add

UC-52 X
Image Image

Delete Restaurant My Restaurant

UC-53 X
Image Image

UC-54 View Dashboard Admin X

Search Order For

UC-55 Admin Orders X
Admin

View
UC-56 Admin Order Detail X
Order Information

Search Restaurant Admin List

UC-57 X
For Admin Restaurants

View Pending Admin New

UC-58 X
Restaurants Restaurants

Admin Restaurant
Information/
Admin Restaurant
Image/ Admin
View Detailed Restaurant Menu
UC-59 X
Restaurant Detail/ Admin
Restaurant Combo
Detail/ Admin
Restaurant Service
Detail

Admin New
UC-60 Approve Restaurant X
Restaurants

SWP490_G35 31/303
FBS - Software Requirement Specification v2.0

Admin New
UC-61 Cancel Restaurant X
Restaurants

Admin List
UC-62 Block Restaurant X
Restaurants

Admin List
UC-63 Unblock Restaurant X
Restaurants

View Notifications
UC-64 Admin Notification X
For Admin

UC-65 View All Reports Admin Report X

Admin Restaurant
Menu Detail/
Deactivate Item In Admin Restaurant
UC-66 X
Restaurant Combo Detail/
Admin Restaurant
Service Detail

Admin Wallet
UC-67 View FBS Wallet X
Information

Admin Wallet
UC-68 Search Transaction X
Information

Search Money Admin Pay In/

UC-69 X
Processing Admin Withdrawal

Accept Money Admin Pay In/

UC-70 X
Processing Admin Withdrawal

Cancel Money Admin Pay In/

UC-71 X
Processing Admin Withdrawal

Recharge
UC-72 Recharge Processing X
Processing

UC-73 Search User Admin Customers X

Admin Customer
UC-74 View User Profile X
Profile

UC-75 Block User Admin Customer X

UC-76 Unblock User Admin Customer X

Table 3-2: Security Matrix

3.3 Entity Description

3.3.1 Entity Relationship Diagram

SWP490_G35 32/303
FBS - Software Requirement Specification v2.0

Figure 3-2: Entity Relationship Diagram

Entities List

# Entity Description

1 Customer Registered user on the system

Registered user and completed registration as a supplier who

2 Provider
owns the restaurant on the system

3 Admin System manager of the FBS

4 Notification Notifications of registered user

5 Order Order of user

6 FBS Wallet Wallet of the user in the system

7 Feedback Rate, comment, and report of the user for a restaurant

8 Combo Dish combo of the restaurant

9 Promotion Promotion of the restaurant

SWP490_G35 33/303
FBS - Software Requirement Specification v2.0

10 Service Service of restaurant

11 Dish Dish of restaurant

12 Restaurant The restaurant is registered by the provider

Table 3-3: Entity List

3.3.2 Entity Details

1. Customer

# Attribute name PK Type Mandatory Description

1 ID x Long Yes ID of customer

The phone number that the

2 Phone Login String Yes
customer uses to log in

The password that the customer to

3 Password String Yes
login with

4 Name String No Username of customer

The phone number that the

5 Phone Number String Yes
customer uses to contact

6 Gender Boolean No Gender of customer

7 Date Of Birth Date No Date of birth of the customer ser

8 Address String No The specific address of customer

9 Email String No Email of the customer

10 Status String Yes Status of the customer’s account

11 Last Modified Date Date Yes The last time the customer logged in

12 Avatar Image No Avatar of the customer

Customer's FBS wallet account

13 Balance Float Yes
balance

Table 3-4: Customer Detail

2. Provider

# Attribute name PK Type Mandatory Description

1 ID x Long Yes ID of provider

SWP490_G35 34/303
FBS - Software Requirement Specification v2.0

The phone number that the provider

2 Phone Login String Yes
uses to log in

The password that the provider to

3 Password String Yes
login with

4 Name String No Username of provider

The phone number that the provider

5 Phone Number String Yes
uses to contact

6 Gender Boolean No Gender of provider

7 Date Of Birth Date No Date of birth of the provider

8 Address String No The specific address of the provider

9 Email String No Email of the provider

10 Status String Yes Status of the provider’s account

11 Last Modified Date Date Yes The last time the provider logged in

12 Avatar Image No Avatar of the provider

Provider's FBS wallet account

13 Balance Float Yes
balance

Table 3-5: Provider Detail

3. Admin

# Attribute name PK Type Mandatory Description

1 ID x Long Yes ID of provider

The phone number that the admin

2 Phone Login String Yes
uses to log in

The password that the admin to

3 Password String Yes
login with

4 Status String Yes Status of the admin’s account

5 Last Modified Date Date Yes The last time the admin logged in

Table 3-6: Admin Detail

4. Notification

# Attribute name PK Type Mandatory Description

SWP490_G35 35/303
FBS - Software Requirement Specification v2.0

1 ID x Long Yes ID of the notification

2 Content String Yes Content of the notification

Indicates this notification of which

3 Customer String No
customer

Indicates this notification of which

4 Provider String No
provider

The date on which the notice was

5 Date Date Yes
sent

Indicates whether this notification is

6 For Admin Boolean Yes
for the admin or not

7 Status String Yes Status of the notification

Indicate whether the notification has

8 Is Read Boolean Yes
been viewed or not

9 Type String Yes Type of notification

Table 3-7: Notification Detail

5. Order

# Attribute name PK Type Mandatory Description

1 ID x Long Yes ID of the order

2 Amount Float Yes The total amount of the order

The session when the feast will take

3 Time String Yes
place

4 Order Date Date Yes Order creation date

Indicate which restaurant this order

5 Restaurant String Yes
from

Indicate which customer this order

6 Customer String Yes
belongs to

7 Status String Yes Status of the order

8 Promotion String Yes Promotion is applicable for the order

9 Order Code String Yes Code of the order

SWP490_G35 36/303
FBS - Software Requirement Specification v2.0

Price of each dish, service, or combo

10 Price Float Yes
in order

Quantity of each dish, service, or

11 Quantity Int Yes
combo in order

12 Dish String No The dish that the customer chooses

The combo that the customer

13 Combo String No
chooses

The service that the customer

14 Service String No
chooses

Feast table style, can be 6 seater

15 Table Type Int Yes
table or 8 seater table

The estimated number of guests for

16 Number Of Guests Int Yes
the feast

17 Note String Yes Note for restaurant

18 Organize Date Date Yes Date to organize feast

19 Organize Address String No Specific address to organize feast

20 Organize Ward String No Ward to organize feast

21 Organize District String No District to organize feast

22 Organize Province String No Province to organize feast

Table 3-8: Order Detail

6. FBS Wallet

# Attribute name PK Type Mandatory Description

1 ID x Long Yes Id of the wallet

2 User String Yes The owner of the wallet

Change of account maybe add or

3 Balance Change Float Yes
subtract

The amount is transferred to which

4 From To User String Yes
user and to which user

5 Current Balance Float Yes Current account balance

6 Date Of Change Date Yes Date of execution of transaction

7 Description String No Description of transaction

SWP490_G35 37/303
FBS - Software Requirement Specification v2.0

8 Status String Yes Status of account wallet

9 Payment Code String No Code of payment

10 Payment Type String Yes Type of payment

Table 3-9: FBS Wallet Detail

7. Feedback

# Attribute name PK Type Mandatory Description

1 ID x Long Yes Id of the feedback/report

2 Feedback Content String Yes Content of feedback/report

The date on which the

3 Feedback Date Date Yes
feedback/report was made

Rate of feedback, if it is report, rate

4 Rate Float Yes
is 0

Indicates this feedback/report from

5 Customer String Yes
which customer

Indicates this feedback/report to

6 Restaurant String Yes
which restaurant

7 Status String Yes Status of feedback/report

Table 3-10: Feedback Detail

8. Combo

# Attribute name PK Type Mandatory Description

1 ID x Long Yes Id of the combo

2 Name String Yes Name of the combo

3 Description String Yes Description about the combo

4 Price Float Yes Sale price of the combo

Indicates this combo of which

5 Restaurant String Yes
restaurant

6 Status String Yes Status of the combo

7 Dish String Yes Dishes of the combo

8 Avatar Image Yes Avatar of the combo

SWP490_G35 38/303
FBS - Software Requirement Specification v2.0

Table 3-11: Combo Detail

9. Promotion

# Attribute name PK Type Mandatory Description

1 Id x Long Yes Id of the promotion

2 Name String Yes Name of the promotion

3 Description String Yes Detail description of the promotion

Discount Discount percentage of the

4 Float Yes
Percentage promotion

5 Start Date Date Yes Start date of the promotion

6 End Date Date Yes End date of the promotion

7 Status String Yes Status of the promotion

8 Avatar Image Yes Avatar of the promotion

Indicate this promotion of which

9 Restaurant String Yes
restaurant

Table 3-12: Promotion Detail

10. Service

# Attribute name PK Type Mandatory Description

1 ID x Long Yes Id of the service

2 Name String Yes Name of the service

3 Description String Yes Detailed description of the service

4 Status String Yes Status of the service

5 Price Float Yes Sale price of the service

Indicates this service of which

6 Restaurant String Yes
restaurant

7 Service Category String Yes Category of the service

8 Avatar Image Yes Avatar of the service

Table 3-13: Service Detail

11. Dish

SWP490_G35 39/303
FBS - Software Requirement Specification v2.0

# Attribute name PK Type Mandatory Description

1 ID x Long Yes Id of the dish

2 Name String Yes Name of the dish

3 Description String Yes Detailed description of the dish

4 Price String Yes Sale price of the dish

Indicates this dish of which

5 Restaurant String Yes
restaurant

6 Menu Category String Yes Category of the dish

7 Status String Yes Status of the dish

8 Avatar Image Yes Avatar of the dish

Table 3-14: Dish Detail

12. Restaurant

# Attribute name PK Type Mandatory Description

1 ID x Long Yes Id of the restaurant

2 Restaurant Name String Yes Name of the restaurant

Indicates this restaurant of which

3 Provider String Yes
user

4 Province String Yes Province/City of the restaurant

5 District String Yes District of the restaurant

The specific address of the

6 Address String Yes
restaurant

The phone number that the

7 Phone Number String Yes
restaurant uses to contact

8 Status String Yes Status of the restaurant

9 Description String Yes Description of the restaurant

The number of guests the restaurant

10 Size Int Yes
can accommodate

11 Restaurant Type String Yes Type of the restaurant

The business license number of the

12 Business License Id String Yes
restaurant

SWP490_G35 40/303
FBS - Software Requirement Specification v2.0

Images of food hygiene and safety

13 Certificate Image Image Yes
for catering of the restaurant

14 Avatar Image No Avatar of the restaurant

15 Description Image Image No Description images of restaurant

Table 3-15: Restaurant Detail

3.4 Common Business Rules

ID Rule Definition

BR-01 Each phone is only registered for one user.

Users have to wait for the OTP code to be sent to their phone and re-enter the code to
BR-02
be able to register an account.

All users after having an account can log in, log out, change passwords, retrieve
BR-03
passwords when forgotten.

BR-04 Password and re-password must be matched.

BR-05 Only registered users can successfully log in and make party bookings on the web.

BR-06 Only users who have been verified after an add restaurant step can become providers.

BR-07 The FBS system only supports the Vietnamese language.

There are 4 roles in the FBS system: guest (who only views the system), customer (who
BR-08 has successfully registered), provider (who has completed the additional step of
registering as a provider), and admin (who is system management).

Guest can view the information on the website and add items to cart but can not
BR-09
complete order

Customers can view the website, place an order on the website, and register as a
BR-10
provider.

BR-11 Customers must deposit the amount required by the restaurant.

The customer has the right to cancel the order placed before the delivery date. But
BR-12 when the customer cancels the order, they have to pay compensation according to the
regulations of the restaurant and the system

Customers can order the party to be delivered at home or the locations provided by the
BR-13
restaurant.

Providers have full roles as customers and have additional management functions to
BR-14
view, add, edit, delete products, manage orders and manage promotions

SWP490_G35 41/303
FBS - Software Requirement Specification v2.0

The provider has the right to accept or cancel the order but must handle it on the day of
BR-15
the order.

Admin has permission to views orders, revenue of systems, accounts, and restaurants of
BR-16
the system

BR-17 Restaurants are only displayed when approved by the admin.

BR-18 All items in an order must be delivered to the same location.

BR-19 All items in an order must be paid for with the same payment method.

Order price is calculated as the sum of each food item price times the quantity of that
BR-20 food item ordered, plus a delivery charge if a meal is delivered outside the free delivery
zone and subtract promotion.

If the customer has deposited in advance, the final payment price must be deducted
BR-21
from the deposit amount.

If a customer orders items from multiple restaurants, multiple invoices must be issued,
BR-22
each for a separate restaurant, and billed separately.

BR-23 The provider can register multiple restaurants with the same login account.

The provider can choose the active or inactive status. When a restaurant is inactive, all
BR-24
items will be hidden from customers.

BR-25 Email must be in the correct format (email@domain.com).

BR-26 Phone number must enter the number.

BR-27 The price must enter the positive integer and be greater than or equal to 1,000 (VNĐ).

BR-28 The number of guests of order must enter the positive integer.

BR-29 The quantity of the dish of order must enter the positive integer.

BR-30 The quantity of the combo of order must enter the positive integer.

BR-31 The quantity of service of order must enter the positive integer.

BR-32 Discount percentage of promotion must enter the positive integer.

BR-33 The number of guests the restaurant can accommodate must be a positive integer.

BR-34 The year of the feast is within one year from the year of the order date.

BR-35 Even if the restaurant wasn't accepted by Admin, they can still add items.

Dishes, combos, and services require name, picture, price, category, and description to
BR-36
add to the restaurant.

BR-37 The item's name in a restaurant is unique.

BR-38 The restaurant must have at least one picture to add in.

SWP490_G35 42/303
FBS - Software Requirement Specification v2.0

Restaurants are required to have a business license and a certificate of food hygiene and
BR-39
safety to be allowed to register on the system.

BR-40 Providers can not edit the category of dishes and services

The system automatically deducts the commission and refunds the deposit to the
provider after the order is completed. In addition, if the customer cancels the order, the
BR-41
deposit will also be refunded according to the regulations and based on the time of
cancellation

The number of items in the cart will be equal to the number of guests divided by the
BR-42
number of seats at the table

Customers must pay for the cart at this restaurant before going to another restaurant to
BR-43
choose

BR-44 Promotion name in a restaurant is unique

BR-45 Order code in FBS system is unique

BR-46 Transaction code in FBS system is unique

Only when the order is approved will the customer and the restaurant know each
BR-47
other's phone numbers and specific addresses

BR-48 Once the order has been completed and the customer has successfully paid for the
restaurant, the provider can mark the order status as completed

BR-49 When a customer makes a deposit request, the admin must accept it before the money
is transferred to the FBS wallet

BR-50 When a customer makes a withdrawal request, the admin must accept it before the
customer can receive the money

BR-51 After the customer gives cash, the admin will deposit it into the customer's wallet

BR-52 The amount entered for depositing or withdrawing must be a positive integer and must
be at least 10000 VND

Table 3-16: Common Business Rules

3.5 Detailed Functional Specification

SWP490_G35 43/303
FBS - Software Requirement Specification v2.0

Figure 3-3: Actor Relationship Diagram

3.5.1 Guest Functions
3.5.1.1 Use Case diagram

SWP490_G35 44/303
FBS - Software Requirement Specification v2.0

Figure 3-4: Guest Functions Use case Diagram

Use Case ID User case Name Description

Allow users to search restaurants by

UC-01 Search Restaurants province/city, county/district, by organizing a
roving feast, or organizing a restaurant feast.

View Restaurant Services Allow the user to view all services of the
UC-02
restaurant.

Allow the user to view detailed information

UC-03 View Restaurant Infor
about the restaurant.

Allow the user to view all combos of the

UC-04 View Restaurant Combo
restaurant.

Allow the user to search dishes of the

UC-05 Search Restaurant Dishes
restaurant by keywords.

SWP490_G35 45/303
FBS - Software Requirement Specification v2.0

Allow the user to view all dishes of the

UC-06 View Restaurant Dishes
restaurant.

Allow the user to view detailed information of

UC-07 View Detail Item
items in the restaurant.

Allow the user to view all coming and ongoing

UC-08 View All Promotions promotions of all restaurants on the FBS
system.

Allow the user who does not have an account in

UC-09 Register Account
the system to register a new account.

Allow the user to chat with FBS’s page in

UC-10 Chat With System
Facebook via Facebook Messenger

Table 3-17: Guest Functions Use case List

3.5.1.2 UC-01 - Search Restaurant

3.5.1.2.1 Screen Design

SWP490_G35 46/303
FBS - Software Requirement Specification v2.0

Figure 3-5: Screen Design of Search Restaurant

Table 3-18: Search Restaurant screen Definition

SWP490_G35 47/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Header

Image
1 Logo Image Link to Home screen
Card

2 Trang chủ Hyperlink Link to Home screen

Link to View All

3 Ưu đãi hôm nay Hyperlink
Promotion screen

Link to Add
4 Đăng ký nhà hàng Hyperlink
Restaurant screen

5 Đăng nhập Hyperlink Button to sign in

6 Đăng ký Hyperlink Button to sign up

Main

Combo
1 Tỉnh/ Thành phố No List of province
box

Combo List districts of

2 Quận/ Huyện No
box selected province

Choose the type of

3 Tiệc lưu động Checkbox No
feast

Trung tâm tổ chức sự Choose the type of

4 Checkbox No
kiện feast

The textbox to enter

5 Từ khóa hoặc tên Textbox No search keywords or
restaurant’s name

6 Tìm kiếm Button The button to trigger

Search function

The card display

restaurant
7 Restaurant Card Card information that
matches the search
terms

8 Restaurant Photo Image Avatar of the

restaurant

9 ABC Place Label Restaurant's name

SWP490_G35 48/303
FBS - Software Requirement Specification v2.0

This button links to

10 Xem ngay Button Restaurant Detail
screen

11 Pagination Hyperlink This hyperlink links to

page of results

Footer

1 Theo dõi chúng tôi trên Label

Link to FBS’s Twitter

2 Twitter Logo Hyperlink
account

Link to FBS’s Facebook

3 Facebook Logo Hyperlink
account

Link to FBS’s Youtube

4 Youtube Logo Hyperlink
channel

5 Về Feast Booking Label

Guide on how to book

6 Cách đặt tiệc Hyperlink a feast at the FBS
system

How to contact the

7 Liên hệ với chúng tôi Hyperlink
system

Recruitment news of
8 Tuyển dụng Hyperlink
FBS

Introduce to FBS
9 Về chúng tôi Hyperlink
system

10 Trợ giúp Label

11 Trung tâm trợ giúp Hyperlink User support

Frequently asked
12 Câu hỏi thường gặp Hyperlink
questions by users

13 Chính sách bảo mật Hyperlink Privacy policy

14 Điều khoản sử dụng Hyperlink Terms of use

3.5.1.2.2 Use case Specification

SWP490_G35 49/303
FBS - Software Requirement Specification v2.0

Use Case ID UC-01 Use Case Name Search Restaurant

Author TrangTLH Version 2.0 Date 07/06/2021

Actor Guest, FBSCustomer, FBSProvider

This function allows the user to search restaurants by province/city,

Description
county/district, by organizing a roving feast, or organizing a restaurant feast.

PRE-01: User has been authorized to Home screen

Precondition
PRE-02: User is in Home screen

TRG-01: User has been authorized to Home screen

Trigger TRG-02: User is in Home screen
TRG-03: User enters search information and clicks “Tìm kiếm” button

POS-01: Query by search condition in the database.

Post-Condition POS-02: Users will search successfully and redirect to the search result
screen.

Main flows

Step Actor Action

1 User Type URL into location field of internet browser and then press enter

2 FBS Display Home screen

Select the province/city at “Tỉnh/Thành phố” combo box and select the
city/district at “Quận/Huyện” combo box
Or: Select organizing a roving feast at “Tiệc lưu động” or organizing a
3 User
restaurant feast at “Trung tâm tổ chức sự kiện” or both
Or: Enter keywords or restaurant name at “Từ khóa hoặc tên” textbox
Or do nothing

4 User Click the “Tìm kiếm” button

5 FBS Validate the entered keywords and then display Search Result screen

Table 3-19: Search Restaurant Use case Specification

SWP490_G35 50/303
FBS - Software Requirement Specification v2.0

3.5.1.3 UC-02 - View Restaurant Services

3.5.1.3.1 Screen Design

Figure 3-6: Screen Design of View Restaurant Services

SWP490_G35 51/303
FBS - Software Requirement Specification v2.0

Table 3-20: View Restaurant Services screen Description

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Search Restaurant screen)

Main

This hyperlink links to

1 Cửa hàng Hyperlink Restaurant Detail
screen

This hyperlink links to

2 Thực đơn Hyperlink
View Dish screen

This hyperlink links to

3 Combo Hyperlink
View Combo screen

This hyperlink links to

4 Dịch vụ Hyperlink
View Service screen

This button links to

5 Cart Icon Button
View Cart screen

6 Category Title
Title of Service
category
Value: Trang trí, Ban
Label nhạc, Vũ đoàn, Ca sĩ,
MC (Dẫn chương
trình), Quay phim -
Chụp ảnh

7 Services Slideshow Slideshow Slideshow of services

Card display
8 Service Card Card
information of service

9 Service Image Image Avatar of service

10 Service Name Label Name of service

11 Service Price Label Sale price of service

The button to add

12 Đặt ngay Button
service to the cart

The button to view

13 Information Icon Button detailed information
of service

Footer (same as footer of Search Restaurant screen)

SWP490_G35 52/303
FBS - Software Requirement Specification v2.0

3.5.1.3.2 Use case Specification

Use Case ID UC-02 Use Case Name View Restaurant Services

Author TrangTLH Version 2.0 Date 07/06/2021

Actor Guest, FBSCustomer, FBSProvider

Description This function allows the user to view all services of the restaurant

PRE-01: User has been authorized to Restaurant Detail screen

Precondition
PRE-02: User is in Restaurant Detail screen

TRG-01: User has been authorized to Restaurant Detail screen

Trigger TRG-02: User is in Restaurant Detail screen
TRG-03: User clicks the menu bar “Dịch vụ” on Restaurant Detail screen

Post-Condition POS-01: User can view all services in restaurants

Main flows

Step Actor Action

1 User Click “Dịch vụ” at menu bar

2 FBS Display Restaurant Services screen

3 User View all services in the restaurant

Table 3-21: View Restaurant Services Use case Specification

SWP490_G35 53/303
FBS - Software Requirement Specification v2.0

3.5.1.4 UC-03 - View Restaurant Infor

3.5.1.4.1 Screen Design

Figure 3-7: Screen Design of View Restaurant Information

Table 3-22: View Restaurant Infor screen Definition

SWP490_G35 54/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Search Restaurant screen)

Main

This hyperlink links to

1 Cửa hàng Hyperlink Restaurant Detail
screen

This hyperlink links to

2 Thực đơn Hyperlink
View Dish screen

This hyperlink links to

3 Combo Hyperlink
View Combo screen

This hyperlink links to

4 Dịch vụ Hyperlink
View Service screen

This button links to

5 Cart Icon Button
View Cart screen

Slideshow of
Restaurant Image
6 Slideshow restaurant’s
Slideshow
description image

This hyperlink links to

7 Report Flag Hyperlink
the report form

8 Restaurant Name Label Name of restaurant

9 Restaurant Province Label Province of restaurant

Restaurant Detail description of

10 Label
Description the restaurant

Card of restaurant’s
promotion
Value: Promotion
name, Promotion
11 Promotion Card Card image, Promotion
description,
Promotion start, and
end date, Promotion
status

Textarea to enter
12 Enter Feedback Text Textarea Yes 250
feedback/report

This rating to user

13 Star Rate Rating Yes insert rate, if it is
report, rate is 0

SWP490_G35 55/303
FBS - Software Requirement Specification v2.0

Add feedback or
14 Đánh giá Button
report

15 Rate Link Hyperlink Filter feedback by rate

Detailed information
of each feedback
Value: User avatar,
16 Feedback Card Card
Username, star rate,
Feedback content,
Feedback date

This hyperlink links to

17 Feedback Pagination Hyperlink
page of feedback
Footer (same as footer of Search Restaurant screen)

3.5.1.4.2 Use case Specification

Use Case ID UC-03 Use Case Name View Restaurant Infor

Author TrangTLH Version 2.0 Date 07/06/2021

Actor Guest, FBSCustomer, FBSProvider

This function allows the user to view detailed information about the
Description
restaurant

PRE-01: User has been authorized to Home screen

Precondition
PRE-02: User is in Home screen

TRG-01: User has been authorized to Home screen

Trigger TRG-02: User is in Home screen
TRG-02: User clicks “Xem thêm” button on a specific restaurant

Post-Condition POS-01: User can view all information in restaurants

Main flows

Step Actor Action

1 User Click “Xem thêm” button on a specific restaurant

1 FBS Display Restaurant Detail screen

2 User View all information in the restaurant

Table 3-23: View Restaurant Infor Use case Specification

3.5.1.5 UC-04 - View Restaurant Combo

3.5.1.5.1 Screen Design

SWP490_G35 56/303
FBS - Software Requirement Specification v2.0

Figure 3-8: Screen Design of View Restaurant Combo

Table 3-24: View Restaurant Combo screen Definition

SWP490_G35 57/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length
Header (same as header of Search Restaurant screen)
Main
This hyperlink links to
1 Cửa hàng Hyperlink Restaurant Detail
screen

This hyperlink links to

2 Thực đơn Hyperlink
View Dish screen

This hyperlink links to

3 Combo Hyperlink
View Combo screen

This hyperlink links to

4 Dịch vụ Hyperlink
View Service screen

This button links to

5 Cart Icon Button
View Cart screen

Card display
8 Combo Card Card
information of combo

9 Combo Name Label Name of combo

10 Combo’s Dishes List List dishes of combo

Sale price of the

11 Combo Price Label
combo

The button to add the

12 Đặt ngay Button
combo to the cart

This hyperlink links to

13 Pagination Hyperlink
page of combos

The button to view

14 Information Icon Button
information of combo

Footer (same as footer of Search Restaurant screen)

3.5.1.5.2 Use case Specification

Use Case ID UC-04 Use Case Name View Restaurant Combos

SWP490_G35 58/303
FBS - Software Requirement Specification v2.0

Author TrangTLH Version 2.0 Date 07/06/2021

Actor Guest, FBSCustomer, FBSProvider

Description This function allows the user to view all combos of the restaurant

PRE-01: User has been authorized to Restaurant Detail screen

Precondition
PRE-02: User is in Restaurant Detail screen

TRG-01: User has been authorized to Restaurant Detail screen

Trigger TRG-02: User is in Restaurant Detail screen
TRG-03: User clicks the menu bar “Combo” on the Restaurant Detail screen

Post-Condition POS-01: User can view all combo in restaurants

Main flows

Step Actor Action

1 User Click “Combo” at the menu bar

2 FBS Display Restaurant Combo screen

3 User View all combos in the restaurant

Table 3-25: View Restaurant Combo Use case Specification

3.5.1.6 UC-05 - Search Restaurant Dishes

3.5.1.6.1 Screen Design

SWP490_G35 59/303
FBS - Software Requirement Specification v2.0

Figure 3-9: Screen Design of Search Restaurant Dishes

Table 3-26: Search Restaurant Dishes screen Definition

SWP490_G35 60/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length
Header (same as header of Search Restaurant screen)
Main
This hyperlink links to
1 Cửa hàng Hyperlink Restaurant Detail
screen

This hyperlink links to

2 Thực đơn Hyperlink
View Dish screen

This hyperlink links to

3 Combo Hyperlink
View Combo screen

This hyperlink links to

4 Dịch vụ Hyperlink
View Service screen

This button links to

5 Cart Icon Button
View Cart screen

Tìm kiếm món ăn

6 Label
theo tên

The textbox to enter

7 Search Text Textbox Yes
search keywords

This card displays the

8 Dish Card Card
information of dish

9 Dish Image Image Image of dish

10 Dish Name Label Name of dish

11 Dish Price Label Sale price of dish

The button to add the

12 Đặt ngay Button
dish to the cart

This hyperlink links to

13 Pagination Hyperlink
page of dish

The button to view

14 Information Icon Button detailed information
of dish

Footer (same as footer of Search Restaurant screen)

3.5.1.6.2 Use case Specification

SWP490_G35 61/303
FBS - Software Requirement Specification v2.0

Use Case ID UC-05 Use Case Name Search Restaurant Dishes

Author TrangTLH Version 1.0 Date 09/07/2021

Actor Guest, FBSCustomer, FBSProvider

This function allows the user to search dishes of the restaurant by keywords
Description
name

PRE-01: User has been authorized to Restaurant Menu screen

Precondition
PRE-02: User is in Restaurant Menu screen

TRG-01: User has been authorized to Restaurant Menu screen

Trigger TRG-02: User is in Restaurant Detail screen
TRG-03: User enters keywords in Search text and presses Enter

POS-01: Query by search condition in the database.

Post-Condition POS-02: Users will search successfully and redirect to the search dish result
screen.

Main flows

Step Actor Action

1 User Click “Thực đơn” at the menu bar

2 FBS Display Restaurant Dish screen

3 User Enters keywords in Search text and presses Enter to search dishes by name

4 FBS Validate the entered keywords and then display the search dish result screen.

Table 3-27: Search Restaurant Dishes Use case Specification

3.5.1.7 UC-06 - View Restaurant Dishes

3.5.1.7.1 Screen Design

SWP490_G35 62/303
FBS - Software Requirement Specification v2.0

Figure 3-10: Screen Design of View Restaurant Dishes

Table 3-28: View Restaurant Dishes screen Definition

SWP490_G35 63/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length
Header (same as header of Search Restaurant screen)
Main
This hyperlink links to
1 Cửa hàng Hyperlink Restaurant Detail
screen

This hyperlink links to

2 Thực đơn Hyperlink
View Dish screen

This hyperlink links to

3 Combo Hyperlink
View Combo screen

This hyperlink links to

4 Dịch vụ Hyperlink
View Service screen

This button links to

5 Cart Icon Button
View Cart screen

Tìm kiếm món ăn

6 Label
theo tên

The textbox to enter

7 Search Text Textbox No
search keywords

Title of Dish category

Value: Khai vị, Món
8 Category Title Label
chính, Tráng miệng,
Đồ uống

9 Dishes Slideshow Slideshow Slideshow of dishes

This card displays the

10 Dish Card Card
information of dish

11 Dish Image Image Image of dish

12 Dish Name Label Name of dish

13 Dish Price Label Sale price of dish

The button to add the

14 Đặt ngay Button
dish to the cart

The button to view

15 Information Icon Button detailed information
of dish
Footer (same as footer of Search Restaurant screen)
3.5.1.7.2 Use case Specification

SWP490_G35 64/303
FBS - Software Requirement Specification v2.0

Use Case ID UC-06 Use Case Name View Restaurant Dishes

Author TrangTLH Version 2.0 Date 07/06/2021

Actor Guest, FBSCustomer, FBSProvider

Description This function allows the user to view all dishes of the restaurant

PRE-01: User has been authorized to Restaurant Detail screen

Precondition
PRE-02: User is in Restaurant Detail screen

TRG-01: User has been authorized to Restaurant Detail screen

Trigger TRG-02: User is in Restaurant Detail screen
TRG-03: User clicks the menu bar “Thực đơn” on Restaurant Detail screen

Post-Condition POS-01: User can view all dishes in restaurants

Main flows

Step Actor Action

1 User Click “Thực đơn” at the menu bar

2 FBS Display Restaurant Dishes screen

3 User View all dishes in the restaurant

Table 3-29: View Restaurant Dishes Use case Specification

3.5.1.8 UC-07 - View Detail Item

3.5.1.8.1 Screen Design

Figure 3-11: Screen Design of View Detail Item

Table 3-30: View Detail Item Screen Definition

SWP490_G35 65/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Main

1 Title Chi tiết món ăn Label

2 Dish Image Image Avatar of dish

3 Tên món ăn Label Name of dish

4 Loại món ăn Label Category of dish

5 Trạng thái Label Status of dish

6 Giá món ăn Label Sale price of dish

7 Mô tả Label Description of dish

8 Trở lại Button Button to close Item

Detail screen

9 Close Button Button to close Item

Detail screen

3.5.1.8.2 Use case Specification

Use Case ID UC-07 Use Case Name View Detail Item

Author TrangTLH Version 1.0 Date 21/07/2021

Commented [9]: 1. User has been authorized to
Restaurant Menu ..
Actor FBSGuest 2. User is in Restaurant Menu
3. User click on Information icon button....
The function allows the user to view detailed information of items in the
Description Commented [10R9]: _Marked as resolved_
restaurant
Commented [11R9]: _Re-opened_
PRE-01: User has been authorized to Restaurant Menu/ Restaurant Combo/ Commented [12]: 1. User has been authorized to
Restaurant Service screen Restaurant Menu ..
Precondition 2. User is in Restaurant Menu
PRE-02: User is in Restaurant Menu/ Restaurant Combo/ Restaurant Service
screen Commented [13R12]: _Marked as resolved_
Commented [14R12]: _Re-opened_
TRG-01: User has been authorized to Restaurant Menu/ Restaurant Combo/
Commented [15]: 1. User has been authorized to
Restaurant Service screen Restaurant Menu ..
Trigger TRG-02: User is in Restaurant Menu/ Restaurant Combo/ Restaurant Service 2. User is in Restaurant Menu
screen Commented [16R15]: _Marked as resolved_
TRG-03: User clicks Information Icon button at the item that wants to view
Commented [17R15]: _Re-opened_

SWP490_G35 66/303
FBS - Software Requirement Specification v2.0

Post-Condition POS-01: User views detail information of item successfully

Main flows

Step Actor Action

1 User Go to Restaurant Menu/ Restaurant Combo/ Restaurant Service screen

2 FBS Display Restaurant Menu/ Restaurant Combo/ Restaurant Service screen

3 User Click Information Icon button on the item that want to view

4 FBS Display Item Detail screen

5 User View Item Detail screen

Table 3-31: View Item Detail Use case Specification

SWP490_G35 67/303
FBS - Software Requirement Specification v2.0

3.5.1.9 UC-08 - View All Promotions

3.5.1.9.1 Screen Design

Figure 3-12: Screen Design of View All Promotions

SWP490_G35 68/303
FBS - Software Requirement Specification v2.0

Table 3-32: View All Promotions screen Definition

Max
# Field Name Type Mandatory Description
Length
Header (same as header of Search Restaurant screen)
Main
1 Thông tin ưu đãi Label

The card display

2 Promotion Card Card promotions
information

3 Promotion Photo Image Avatar of the

promotion

4 Promotion Name Label Name of promotion

5 Promotion Description Label Short description of

the promotion

6 Promotion Status Label Status of the

promotion

This hyperlink links to

7 Đi đến nhà hàng Hyperlink Restaurant Detail
page that has this
promotion

8 Pagination Hyperlink This hyperlink links to

page of promotions
Footer (same as footer of Search Restaurant screen)

3.5.1.9.2 Use case Specification

Use Case ID UC-08 Use Case Name View All Promotions

Author TrangTLH Version 1.0 Date 09/07/2021

Actor Guest, FBSCustomer, FBSProvider

This function allows the user to view all coming and ongoing promotions of all
Description
restaurants on the FBS system

PRE-01: User has been authorized to Home screen

Precondition
PRE-02: User is in Home screen

TRG-01: User has been authorized to Home screen

Trigger
TRG-02: User is in Home screen

SWP490_G35 69/303
FBS - Software Requirement Specification v2.0

TRG-03: User clicks the “Ưu đãi hôm nay” hyperlink in header

POS-01: User can view all coming and ongoing promotions of all restaurants
Post-Condition
on Promotion screen

Main flows

Step Actor Action

1 User Click the “Ưu đãi hôm nay” hyperlink in header

Display Promotion page with all coming and ongoing promotions of all
2 FBS
restaurants

3 User View all promotions

Table 3-33: View All Promotions Use case Specification

3.5.1.10 UC-09 - Register Account

3.5.1.10.1 Screen Design

Figure 3-13: Screen Design of Register Account

Table 3-34: Register Account screen Definition

SWP490_G35 70/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length
Header (same as header of Search Restaurant screen)
Main

1 Đăng nhập Hyperlink This hyperlink links to

Login screen

2 Title Đăng ký Label

3 Họ và tên Textbox Yes 100 Enter username

4 Số điện thoại Textbox Yes 10 Enter phone to sign

up

Enter a password,
5 Mật khẩu Textbox Yes 32 display "*" instead of
a clear character

Enter re-password,
6 Nhập lại mật khẩu Textbox Yes 32 display "*" instead of
a clear character

Enter the OTP sent to

7 Nhập mã OTP Textbox Yes the phone number
entered above

Tôi đồng ý với Điều

khoản sử dụng và Agree to the Terms of
10 Checkbox Use and Privacy Policy
Chính sách bảo mật
của FBS of FBS

12 Điều khoản sử dụng Hyperlink This hyperlink links to

Terms of Use screen

This hyperlink links to

13 Chính sách bảo mật Hyperlink the Privacy Policy
screen

14 Đăng ký Button The button to trigger

Sign up function

3.5.1.10.2 Use case Specification

Use Case ID UC-09 Use Case Name Register Account

Author ThaoHTP Version 2.0 Date 03/06/2021

Actor Guest

SWP490_G35 71/303
FBS - Software Requirement Specification v2.0

This function allows the user who does not have an account in the system to
Description
register a new account

PRE-01: User has been authorized to Home screen

Precondition
PRE-02: User is in Home screen

TRG-01: User has been authorized to Home screen

TRG-02: User is in Home screen
TRG-03: User clicks “Đăng ký” hyperlink in the header
TRG-04: User fills in the registration information, and clicks the “Đăng ký”
Trigger
button.
TRG-05: A verification OTP code is sent to the phone number used to register.
TRG-06: User fills the OTP code in the “Nhập mã OTP” textbox and clicks
“Đăng ký” button

POS-01. A new account is created and saved in the database.

Post-Condition
POS-02. Users will receive a successful message.

Main flows

Step Actor Action

1 User Click the “Đăng ký” button in header

2 FBS Display Register screen

3 User Enter username or full name in the “Họ và tên” textbox

4 User Enter phone used to login in the “Số điện thoại” textbox

5 User Enter password in the “Mật khẩu” textbox

6 User Enter re-password in the “Nhập lại mật khẩu” textbox

Click “Tôi đồng ý với Điều khoản sử dụng và Chính sách bảo mật của FBS”
7 User
checkbox

8 User Click“Đăng ký” button

9 FBS Send OTP code to the phone number used to register

10 User Enter an OTP code

11 User Click “Đăng ký” button

Validate the entered username, phone number, password, re-password, and

12 FBS
OTP code and then display a message “Đăng ký thành công”

Table 3-35: Register Account Use case Specification

Alternative flows

SWP490_G35 72/303
FBS - Software Requirement Specification v2.0

AT1 At step 3 in the main flows, if the username is not entered

Sub-step Actor Action

3.1 FBS Display a message “Vui lòng nhập họ và tên”

Table 3-36: Alternative flows of Register Account Use case

AT2 At step 4 in the main flows, if the phone number is not entered

Sub-step Actor Action

4.1 FBS Display a message “Vui lòng nhập số điện thoại”

Table 3-37: Alternative flows of Register Account Use case

AT3 At step 4 in the main flows, if the phone number entered is already registered

Sub-step Actor Action

4.2 FBS Display a message “Số điện thoại đã tồn tại”

Table 3-38: Alternative flows of Register Account Use case

AT4 At step 4 in the main flows, if the phone number is not correct format

Sub-step Actor Action

4.3 FBS Display a message “Số điện thoại không đúng định dạng”

Table 3-39: Alternative flows of Register Account Use case

AT5 At step 5 in the main flows, if the password is not entered

Sub-step Actor Action

5.1 FBS Display a message “Vui lòng nhập mật khẩu”

Table 3-40: Alternative flows of Register Account Use case

AT6 At step 5 in the main flows, if the password is not between 3-32 characters

Sub-step Actor Action

SWP490_G35 73/303
FBS - Software Requirement Specification v2.0

5.2 FBS Display a message “Vui lòng nhập mật khẩu từ 3-32 ký tự”

Table 3-41: Alternative flows of Register Account Use case

AT7 At step 6 in the main flows, if the password and re-password are not the same

Sub-step Actor Action

6.1 FBS Display a message “Mật khẩu không khớp”

Table 3-42: Alternative flows of Register Account Use case

AT8 At step 7 in the main flows, if the terms of use checkbox has not been clicked

Sub-step Actor Action

7.1 FBS Display a message “Vui lòng đồng ý với điều khoản sử dụng”

Table 3-43: Alternative flows of Register Account Use case

AT9 At step 9 in the main flows, if there is an internal error in the system

Sub-step Actor Action

9.1 FBS Display a message “Lỗi hệ thống”

Table 3-44: Alternative flows of Register Account Use case

AT10 At step 10 in the main flows, if the OTP code is not entered

Sub-step Actor Action

10.1 FBS Display a message “Vui lòng nhập mã OTP”

Table 3-45: Alternative flows of Register Account Use case

AT11 At step 10 in the main flows, if the OTP code entered is not correct

Sub-step Actor Action

9.2 FBS Display a message “Đăng ký thất bại”

Table 3-46: Alternative flows of Register Account Use case

SWP490_G35 74/303
FBS - Software Requirement Specification v2.0

Business Rules

# Rule Description

BR01 Each phone is only registered for one user.

Users have to wait for the OTP code to be sent to their phone and re-enter the code to
BR02
be able to register an account.

BR04 Password and re-password must be matched.

Table 3-47: Business Rules of Register Account

3.5.1.11 UC-10 – Chat With System

3.5.1.11.1 Screen Design

Use Case ID UC-10 Use Case Name Chat With System

Author TrangTLH Version 1.0 Date 21/07/2021

Actor FBSGuest, FBSCustomer, FBSProvider

This function allows the user to chat with FBS’s page in Facebook via
Description
Facebook Messenger

PRE-01: User has been authorized to Home screen

Precondition
PRE-02: User is in Home screen

TRG-01: User has been authorized to Home screen

Trigger TRG-02: User is in Home screen
TRG-03: User clicks on Messenger icon and chats with FBS’s page

Post-Condition POS-01: The message will be sent to the FBS page

Main flows

Step Actor Action

1 User Access FBS system

2 User Click Messenger icon and chat

Table 3-48: Chat With System Use case Specification

3.5.2 Customer Functions

3.5.2.1 Use Case diagram

SWP490_G35 75/303
FBS - Software Requirement Specification v2.0

Figure 3-14: Customer Functions Use case Diagram

Use Case ID User case Name Description

Allow the authorized user to reset the

UC-11 Reset Password
password.

SWP490_G35 76/303
FBS - Software Requirement Specification v2.0

Allow the authorized user to sign in to

UC-12 Sign In
FBS.

Allow the authorized user to view

UC-13 View Profile
his/her profile.

Allow the authorized user to update

UC-14 Update Profile
his/her information.

Allow the authorized user to change the

UC-15 Change Password
password.

Allow the authorized user to top up their

UC-16 Charge Account
accounts on the FBS system.

Allow the authorized user to review all

UC-17 View Transaction Infor
transactions history.

Allows the authorized user to withdraw

UC-18 Withdraw
funds from their FBS system accounts.

Allow the authorized user to rate and

UC-19 Rate and Comment Restaurant
comment on a restaurant.

Allow the authorized user to report

UC-20 Report Restaurant dishes, combos, or services of the
restaurant to the admin.

Allow the authorized user to create a

UC-21 Create Feast Order feast order by choosing the menu and
services, and fill in some information.

Allow the authorized user to view order

history such as pending orders,
UC-22 View Order History
preparing orders, accomplish orders, and
canceled orders.

Allow the authorized user to view

UC-23 View Order Detail
detailed information on orders.

Allow the authorized user to cancel the

UC-24 Cancel Feast Order
order.

Allow the authorized user to add a new

UC-25 Add Restaurant
restaurant into the FBS system.

Allow the authorized user to view

UC-26 View Notifications
notifications

Allow the authorized user to sign out to

UC-27 Sign Out
FBS.

Table 3-49: Customer Functions Use case List

SWP490_G35 77/303
FBS - Software Requirement Specification v2.0

3.5.2.2 UC-11 - Reset Password

3.5.2.2.1 Screen Design

Figure 3-15: Screen Design of Reset Password

Table 3-50: Reset Password screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Search Restaurant screen)

Main

1 Title Quên mật khẩu Label

2 Số điện thoại Textbox Yes 10 Enter phone login

Enter a new
3 Mật khẩu mới Textbox Yes 32 password, display "*"
instead of a clear
character

Enter re-password,
4 Nhập lại mật khẩu Textbox Yes 32 display "*" instead of
clear character

Enter the OTP sent to

5 Nhập mã OTP Textbox Yes the phone number
entered above

SWP490_G35 78/303
FBS - Software Requirement Specification v2.0

6 Gửi mã OTP Button The button to send

OTP

7 Xác nhận Button The button to reset

password

3.5.2.2.2 Use case Specification

Use Case ID UC-11 Use Case Name Reset Password

Author TrangTLH Version 2.0 Date 07/06/2021

Actor FBSCustomer, FBSProvider

Description This function allows the authorized user to reset the password

TRG-01: User has been authorized to Login screen

Precondition
TRG-02: User is in Login screen

TRG-01: User has been authorized to Login screen

TRG-02: User is in Login screen
TRG-03: User clicks “Quên mật khẩu” hyperlink
TRG-04: User is in Forget Password screen, fills in the phone used to log in,
Trigger
password and re-password, and clicks the “Gửi mã OTP” button.
TRG-05: A OTP code is sent to the phone number used to register.
TRG-06: User fills the OTP code in the “Nhập mã OTP” textbox and clicks “Xác
nhận” button

Post-Condition POS-01: Users performed password reset successfully

Main flows

Step Actor Action

1 User Clicks the “Quên mật khẩu” hyperlink in Login screen

2 FBS Display Forget Password screen

3 User Enter phone used to login in the “Số điện thoại” textbox

4 User Enter new password in the “Mật khẩu mới” textbox

5 User Enter re-password in the “Nhập lại mật khẩu” textbox

6 User Click “Gửi mã OTP” button

7 FBS Send OTP code to the phone number used to login

8 User Enter an OTP code

9 User Click “Xác nhận” button

SWP490_G35 79/303
FBS - Software Requirement Specification v2.0

Validate the entered phone number, password, re-password, and OTP code
10 FBS
and then display a message “Đổi mật khẩu thành công”

Table 3-51: Reset Password Use case Specification

Alternative flows

AT1 At step 3 in the main flows, if the phone number is not entered

Sub-step Actor Action

3.1 FBS Display a message “Vui lòng nhập số điện thoại”

Table 3-52: Alternative flows of Reset Password Use case

AT2 At step 3 in the main flows, if the phone number entered is not registered

Sub-step Actor Action

3.2 FBS Display a message “Số điện thoại không đúng”

Table 3-53: Alternative flows of Reset Password Use case

AT3 At step 3 in the main flows, if the phone number entered is not correct format

Sub-step Actor Action

3.3 FBS Display a message “Số điện thoại không đúng định dạng”

Table 3-54: Alternative flows of Reset Password Use case

AT4 At step 4 in the main flows, if the password is not entered

Sub-step Actor Action

4.1 FBS Display a message “Vui lòng nhập mật khẩu”

Table 3-55: Alternative flows of Reset Password Use case

AT5 At step 4 in the main flows, if the password is not between 3-127 characters

Sub-step Actor Action

4.2 FBS Display a message “Vui lòng nhập mật khẩu từ 3-127 ký tự”

SWP490_G35 80/303
FBS - Software Requirement Specification v2.0

Table 3-56: Alternative flows of Reset Password Use case

AT6 At step 5 in the main flows, if the password and re-password are not the same

Sub-step Actor Action

5.1 FBS Display a message “Mật khẩu không khớp”

Table 3-57: Alternative flows of Reset Password Use case

AT7 At step 7 in the main flows, if there is an internal error in the system
Sub-step Actor Action
7.1 FBS Display a message “Lỗi hệ thống”

Table 3-58: Alternative flows of Reset Password Use case

AT8 At step 8 in the main flows, if the OTP code is not entered

Sub-step Actor Action

8.1 FBS Display a message “Vui lòng nhập mã OTP”

Table 3-59: Alternative flows of Reset Password Use case

AT9 At step 8 in the main flows, if the OTP code entered is not correct

Sub-step Actor Action

8.2 FBS Display a message “Đổi mật khẩu không thành công”

Table 3-60: Alternative flows of Reset Password Use case

Business Rules

# Rule Description

Users have to wait for the OTP code to be sent to their phone and re-enter the code to
BR02
be able to register an account.

All users after having an account can log in, log out, change passwords, retrieve
BR03
passwords when forgotten.

BR04 Password and re-password must be matched.

BR26 Phone number must enter the number.

SWP490_G35 81/303
FBS - Software Requirement Specification v2.0

Table 3-61: Business Rules of Reset Password Use case

3.5.2.3 UC-12 - Sign In

3.5.2.3.1 Screen Design

Figure 3-16: Screen Design of Sign In

Table 3-62: Sign In screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Search Restaurant screen)

Main

1 Title Đăng nhập Label

2 Số điện thoại Textbox Yes 10 Enter phone to login

Enter a password,
3 Mật khẩu Textbox Yes 32 display "*" instead of
a clear character

4 Xác nhận Button The button to trigger

Sign in function

SWP490_G35 82/303
FBS - Software Requirement Specification v2.0

5 Tạo tài khoản Hyperlink Link to Register screen

6 Quên mật khẩu Hyperlink Link to Forget

Password screen

3.5.2.3.2 Use case Specification

Use Case ID UC-12 Use Case Name Sign In

Author TrangTLH Version 2.0 Date 07/06/2021

Actor FBSCustomer, FBSProvider, FBSAdmin

Description This function allows the authorized user to sign in to FBS

PRE-01: User has been authorized to Home screen

Precondition
PRE-02: User is in Home screen

TRG-01: User has been authorized to Home screen

TRG-02: User is in Home screen
Trigger TRG-03: User clicks “Đăng nhập” hyperlink in header and is in Login screen
TRG-04: User fills in the phone used to log in, password, and clicks the “Đăng
nhập” button.

Post-Condition POS-01: User logins successfully in FBS system and goes to Home screen

Main flows

Step Actor Action

1 User Click the “Đăng nhập” hyperlink on Home page

Display Login screen with the following fields:

- Số điện thoại
2 FBS
- Mật khẩu
- “Đăng nhập” button

3 User Enter phone used to login in the “Số điện thoại” textbox

4 User Enter password in the “Mật khẩu” textbox

5 User Click “Đăng nhập” button

6 FBS Validate the entered phone number, password and then display Home screen

Table 3-63: Sign In Use case Specification

Alternative flows

AT1 At step 3 in the main flows, if the phone number is not entered

SWP490_G35 83/303
FBS - Software Requirement Specification v2.0

Sub-step Actor Action

3.1 FBS Display a message “Vui lòng nhập số điện thoại”

Table 3-64: Alternative flows of Sign In Use case

AT2 At step 3 in the main flows, if the phone number entered is not registered

Sub-step Actor Action

3.2 FBS Display a message “Số điện thoại hoặc mật khẩu không đúng”

Table 3-65: Alternative flows of Sign In Use case

AT3 At step 4 in the main flows, if the password is not entered

Sub-step Actor Action

4.1 FBS Display a message “Vui lòng nhập mật khẩu”

Table 3-66: Alternative flows of Sign In Use case

AT4 At step 4 in the main flows, if the password is not correct

Sub-step Actor Action

4.2 FBS Display a message “Số điện thoại hoặc mật khẩu không đúng”

Table 3-67: Alternative flows of Sign In Use case

Business Rules

# Rule Description
All users after having an account can log in, log out, change passwords, retrieve
BR03
passwords when forgotten.

BR26 Phone number must enter the number.

Table 3-68: Business Rules of Sign In Use case

3.5.2.4 UC-13 - View Profile

3.5.2.4.1 Screen Design

SWP490_G35 84/303
FBS - Software Requirement Specification v2.0

Figure 3-17: Screen Design of View Profile

Table 3-69: View Profile screen Definition

SWP490_G35 85/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Header

Image
1 Logo Image Link to Home screen
Card

2 Trang chủ Hyperlink Link to Home screen

Link to View All

3 Ưu đãi hôm nay Hyperlink
Promotion screen

Link to Add
4 Đăng ký nhà hàng Hyperlink
Restaurant screen

Icon Button to view

5 Bell Icon
Button notifications

Link links to User

6 Username Hyperlink
Profile screen

This hyperlink links to

7 Đăng xuất Hyperlink trigger Sign out
function

Sidebar

1 User Image Image Avatar of user

2 Username Label Username of user

Link to User Profile

3 Hồ sơ của tôi Hyperlink
screen

Link to User Profile

4 Đơn đặt tiệc của tôi Hyperlink
Order screen

Link to Wallet
5 Ví FBS Hyperlink
Information screen

Link to My Restaurant
6 Nhà hàng của tôi Hyperlink
screen

Main

Title Thông tin người

1 Label
dùng

2 User Image Image Avatar of user

3 Username Label Username of user

SWP490_G35 86/303
FBS - Software Requirement Specification v2.0

4 Chọn ảnh Button Button to change

avatar

5 Email Label Email of user

6 Số điện thoại Label Phone number to

contact of the user

Password of the user,

7 Mật khẩu Label display "*" instead of
a clear character

8 Giới tính Label Gender of user

9 Ngày sinh Label Date of birth of user

10 Địa chỉ Label Address of user

11 Chỉnh sửa Button Display Update Profile

screen

12 Thay đổi mật khẩu Button Display Change

Password screen

Footer (same as footer of Search Restaurant screen)

3.5.2.4.2 Use case Specification

Use Case ID UC-13 Use Case Name View Profile

Author TrangTLH Version 2.0 Date 07/06/2021

Actor FBSCustomer, FBSProvider

Description This function allows the authorized user to view his/her profile

PRE-01: User has been authorized to Home screen

Precondition
PRE-02: User is in Home screen

TRG-01: User has been authorized to Home screen

TRG-02: User is in Home screen
Trigger
TRG-03: User clicks Username hyperlink in the header and goes to User
Profile screen

POS-01: Screen redirects to the User Profile screen

Post-Condition
POS-02: User view all detailed information in the profile

Main flows

Step Actor Action

SWP490_G35 87/303
FBS - Software Requirement Specification v2.0

1 User Click Username link

2 FBS Display User Profile screen

3 User View all detailed information in the profile

Table 3-70: View Profile Use case Specification

3.5.2.5 UC-14 - Update Profile

3.5.2.5.1 Screen Design

Figure 3-18: Screen Design of Update Profile

Table 3-71: Update Profile screen Definition

SWP490_G35 88/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Main

1 Title Chỉnh sửa Label

2 Tên người dùng Textbox Yes 100 Username of user

Phone number to
3 Số điện thoại Textbox Yes 10
contact of user

4 Email Textbox No 100 Email of user

5 Địa chỉ Textbox No 100 Address of user

Gender of user
6 Giới tính Combo box Value: Name - Male,
Nữ - Female, Khác -
Other

7 Ngày sinh Date picker Date of birth of user

8 Lưu Button Button to save change

9 Quay lại Button Button to close User

Profile Update form

10 Close Label Button to close User

Profile Update form

3.5.2.5.2 Use case Specification

Use Case ID UC-14 Use Case Name Update Profile

Author TrangTLH Version 2.0 Date 07/06/2021

Actor FBSCustomer, FBSProvider

This function allows the authorized user to update his/her information in the
Description
profile

PRE-01: User has been authorized to User Profile screen

Precondition
PRE-02: User is in User Profile screen

TRG-01: User has been authorized to User Profile screen

Trigger TRG-02: User is in User Profile screen
TRG-03: User clicks “Chỉnh sửa” button

SWP490_G35 89/303
FBS - Software Requirement Specification v2.0

TRG-04: User goes to User Profile Update screen, changes information, and
clicks “Lưu” button

POS-01: Query by information in the database and change to new info.

Post-Condition
POS-02: Users will change profile successfully and back to User Profile screen

Main flows

Step Actor Action

1 User Click Username hyperlink in header

2 FBS Display User Profile screen

3 User Click “Chỉnh sửa” button

4 FBS Display User Profile Update screen

Enter the information that needs to be changed, username and phone

5 User number is required, choose gender in combo box and date of birth at date
picker

6 User Click “Lưu” button

7 FBS Validate entered information and then display confirm dialog

8 User Click “Đồng ý” button

Table 3-72: Update Profile Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if the username is not entered

Sub-step Actor Action

5.1 FBS Display a message “Vui lòng nhập tên người dùng”

Table 3-73: Alternative flows of Update Profile Use case

AT2 At step 5 in the main flows, if the phone number is not entered

Sub-step Actor Action

5.2 FBS Display a message “Vui lòng nhập số điện thoại”

Table 3-74: Alternative flows of Update Profile Use case

AT3 At step 5 in the main flows, if the email is not correct format

Sub-step Actor Action

SWP490_G35 90/303
FBS - Software Requirement Specification v2.0

5.3 FBS Display a message “Vui lòng nhập email đúng định dạng (bao gồm '@' và '.')”

Table 3-75: Alternative flows of Update Profile Use case

AT4 At step 6 in the main flows, if the user clicks “Quay lại” button or Close button

Sub-step Actor Action

6.1 FBS Close User Profile Update screen and not save change

Table 3-76: Alternative flows of Update Profile Use case

AT5 At step 6 in the main flows, if the user clicks “Quay lại” button or Close button

Sub-step Actor Action

6.1 FBS Close User Profile Update screen and not save change

Table 3-77: Alternative flows of Update Profile Use case

AT6 At step 8 in the main flows, if the user clicks “Quay lại” button

Sub-step Actor Action

8.1 FBS Back to User Profile Update screen and not save change

Table 3-78: Alternative flows of Update Profile Use case

Business Rules

# Rule Description

All users after having an account can log in, log out, change passwords, retrieve
BR03
passwords when forgotten.

BR25 Email must be in correct format (email@domain.com)

BR26 Phone number must enter the number.

Table 3-79: Business Rules of Update Profile Use case

3.5.2.6 UC-15 - Change Password

3.5.2.6.1 Screen Design

SWP490_G35 91/303
FBS - Software Requirement Specification v2.0

Figure 3-19: Screen Design of Change Password

Table 3-80: Change Password screen Definition

Max
# Field Name Type Mandatory Description
Length

Main

1 Title Đổi mật khẩu Label

Enter an old
2 Mật khẩu hiện tại Textbox Yes 32 password, display "*"
instead of a clear
character

Enter a new
3 Mật khẩu mới Textbox Yes 32 password, display "*"
instead of a clear
character

Enter re-password,
4 Xác nhận mật khẩu Textbox Yes 32 display "*" instead of
clear character

5 Xác nhận Button The button to reset

password

3.5.2.6.2 Use case Specification

Use Case ID UC-15 Use Case Name Change Password

SWP490_G35 92/303
FBS - Software Requirement Specification v2.0

Author TrangTLH Version 1.0 Date 09/07/2021

Actor FBSCustomer, FBSProvider

Description This function allows the authorized user to change the password

PRE-01: User has been authorized to User Profile Update screen

Precondition PRE-02: User is in User Profile Update screen
PRE-02: User clicks “Thay đổi mật khẩu” button

TRG-01: User has been authorized to Restaurant Detail screen

TRG-02: User is in Restaurant Detail screen
Trigger TRG-03: User clicks “Thay đổi mật khẩu” button
TRG-04: User goes to User Profile Update screen, entered old password, new
password, re-password and clicks “Lưu” button

POS-01: Query by information in the database and change to a new

password.
Post-Condition
POS-02: Users will change password successfully and back to User Profile
screen

Main flows

Step Actor Action

1 User Click Username hyperlink in header

2 FBS Display User Profile screen

3 User Click “Thay đổi mật khẩu” button

4 User Display User Profile Change Password screen

5 User Enter old password in the “Mật khẩu hiện tại” textbox

6 User Enter new password in the “Mật khẩu mới” textbox

7 User Enter re-password in the “Xác nhận mật khẩu” textbox

8 User Click “Xác nhận” button

Validate the entered old password, new password, re-password, and then
9 FBS
display a confirm dialog

10 User Click “Đồng ý” button and back to User Profile screen

Table 3-81: Change Password Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if the old password is not entered

Sub-step Actor Action

SWP490_G35 93/303
FBS - Software Requirement Specification v2.0

5.1 FBS Display a message “Vui lòng nhập mật khẩu”

Table 3-82: Alternative flows of Change Password Use case

AT2 At step 5 in the main flows, if the old password entered is not true

Sub-step Actor Action

5.2 FBS Display a message “Mật khẩu không đúng”

Table 3-83: Alternative flows of Change Password Use case

AT3 At step 5 in the main flows, if the password is not between 3-127 characters

Sub-step Actor Action

5.3 FBS Display a message “Vui lòng nhập mật khẩu từ 3-127 ký tự”

Table 3-84: Alternative flows of Change Password Use case

AT4 At step 6 in the main flows, if the new password is not entered

Sub-step Actor Action

6.1 FBS Display a message “Vui lòng nhập mật khẩu”

Table 3-85: Alternative flows of Change Password Use case

AT5 At step 6 in the main flows, if the password is not between 3-127 characters

Sub-step Actor Action

6.2 FBS Display a message “Vui lòng nhập mật khẩu từ 3-127 ký tự”

Table 3-86: Alternative flows of Change Password Use case

AT6 At step 7 in the main flows, if the password and re-password are not the same

Sub-step Actor Action

7.1 FBS Display a message “Mật khẩu không khớp”

Table 3-87: Alternative flows of Change Password Use case

SWP490_G35 94/303
FBS - Software Requirement Specification v2.0

AT7 At step 10 in the main flows, if the user clicks “Quay lại” button

Sub-step Actor Action

10.1 FBS Back to User Profile Change Password screen and not save change

Table 3-88: Alternative flows of Change Password Use case

Business Rules

# Rule Description

All users after having an account can log in, log out, change passwords, retrieve
BR03
passwords when forgotten.

BR04 Password and re-password must be matched.

BR26 Phone number must enter the number

Table 3-89: Business Rules of Change Password Use case

3.5.2.7 UC-16 - Charge Account

3.5.2.7.1 Screen Design

SWP490_G35 95/303
FBS - Software Requirement Specification v2.0

Figure 3-20: Screen Design of Charge Account

Table 3-90: Charge Account screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of User Profile screen)

Sidebar (same as sidebar of User Profile screen)

Menu bar

SWP490_G35 96/303
FBS - Software Requirement Specification v2.0

1 Thông tin tài khoản Hyperlink Link to Wallet

Information screen

2 Nạp tiền Hyperlink Link to Pay In screen

3 Rút tiền Hyperlink Link to Withdrawal

screen

Main

Title Chọn phương

1 Label
thức nạp tiền vào ví

Top up by bank
Nạp tiền bằng cách transfer to the
Radio
2 chuyển khoản qua system's account with
Button
ngân hàng the content as given
by the system

Radio Top up FBS wallet

3 Nạp tiền bằng ví PayPal
Button with PayPal wallet

Number Enter the amount to

4 Số tiền nạp Yes top up into the FBS
stepper
wallet

5 Nạp tiền Button Button to trigger Top-

up function

Footer (same as footer of User Profile screen)

3.5.2.7.2 Use case Specification

Use Case ID UC-16 Use Case Name Charge Account

Author TrangTLH Version 1.0 Date 20/07/2021

Actor FBSCustomer, FBSProvider

This function allows the authorized user to top up their accounts on the FBS
Description
system

PRE-01: User has been authorized to Wallet Information screen

Precondition
PRE-02: User is in Wallet Information screen

TRG-01: User has been authorized to Wallet Information screen

Trigger TRG-02: User is in Wallet Information screen
TRG-03: User clicks “Nạp tiền” at the menu bar

SWP490_G35 97/303
FBS - Software Requirement Specification v2.0

TRG-04: User selects a method of top-up money into the wallet, enters the
amount, and clicks “Nạp tiền” button

POS-01: The top-up request will be sent to the admin

Post-Condition
POS-02: Admin will process the request and top up the FBS wallet for the user

Main flows

Step Actor Action

1 User Go to User Profile screen

2 FBS Display User Profile screen

3 User Click “Ví FBS” hyperlink at the sidebar

4 FBS Display Wallet Information screen

5 User Click “Nạp tiền” hyperlink at the menu bar

6 FBS Display Pay In screen

Select method of top up money into the wallet in “Chọn phương thức nạp
7 User
tiền vào ví”

8 User Enter amount at “Số tiền nạp” number stepper

9 User Click “Nạp tiền” button

10 FBS Display confirm dialog

11 User Click “Đồng ý” button

Table 3-91: Charge Account Use case Specification

Alternative flows

At step 7 in the main flows, if the user selects top-up to FBS wallet with PayPal wallet
AT1
method

Sub-step Actor Action

7.1 FBS Redirect to PayPal website

Table 3-92: Alternative flows of Charge Account Use case

AT2 At step 8 in the main flows, if the amount is not entered

Sub-step Actor Action

SWP490_G35 98/303
FBS - Software Requirement Specification v2.0

8.1 FBS Display message “Vui lòng nhập số tiền cần nạp”

Table 3-93: Alternative flows of Charge Account Use case

AT3 At step 8 in the main flows, if the amount is not positive

Sub-step Actor Action

8.2 FBS Display message “Vui lòng nhập số tiền là số lớn hơn 0”

Table 3-94: Alternative flows of Charge Account Use case

AT4 At step 11 in the main flows, if the user clicks “Quay lại” button or Close button

Sub-step Actor Action

11.1 FBS Close confirm button and not save change

Table 3-95: Alternative flows of Charge Account Use case

3.5.2.8 UC-17 - View Transaction Infor

3.5.2.8.1 Screen Design

SWP490_G35 99/303
FBS - Software Requirement Specification v2.0

Figure 3-21: Screen Design of View Transaction Infor

Table 3-96: View Transaction Info screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of User Profile screen)

Sidebar (same as sidebar of User Profile screen)

Menu bar (same as menu bar of Charge Account screen)

Main

SWP490_G35 100/303
FBS - Software Requirement Specification v2.0

1 Tổng số dư Label Current balance

2 Title Lịch sử giao dịch Label

3 Nhập mã giao dịch Textbox Enter transaction code

to search

Date Search transaction

4 Từ
picker history from what date

Date Search transaction

5 Đến
picker history to what date

6 Search Icon Button Button to trigger

Search function

Filter transaction by
status of transactions
Value: Tất cả - All,
7 Trạng thái Hyperlink Thành công -
Successful, Đang xử lý -
Processing, Thất bại -
Failure

8 Transaction Table Table Display transaction

information

9 Mã giao dịch Label Transaction code

10 Thời gian Label Transaction date

11 Loại Label Type of transaction

12 Số tiền (VNĐ) Label Transaction amount

13 Ghi chú Label Note of transaction

14 Trạng thái Label Status of transaction

15 Transaction Pagination Hyperlink This hyperlink links to

page of transactions

Footer (same as Search Restaurant screen)

3.5.2.8.2 Use case Specification

Use Case ID UC-17 Use Case Name View Transaction Infor

Author TrangTLH Version 1.0 Date 20/07/2021

SWP490_G35 101/303
FBS - Software Requirement Specification v2.0

Actor FBSCustomer, FBSProvider

Description This function allows the authorized user to review all transactions history

PRE-01: User has been authorized to User Profile screen

Precondition
PRE-02: User is in User Profile screen

TRG-01: User has been authorized to User Profile screen

Trigger TRG-02: User is in User Profile screen
TRG-03: User clicks “Ví FBS” at the sidebar

Post-Condition POS-01: Users will view transaction history successfully

Main flows

Step Actor Action

1 User Go to User Profile screen

2 FBS Display User Profile screen

3 User Click “Ví FBS” hyperlink at the sidebar

4 FBS Display Wallet Information screen

7 User View transaction history

Table 3-97: View Transaction Infor Use case Specification

3.5.2.9 UC-18 - Withdraw

3.5.2.9.1 Screen Design

SWP490_G35 102/303
FBS - Software Requirement Specification v2.0

Figure 3-22: Screen Design of Withdraw

Table 3-98: Withdraw Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of User Profile screen)

Sidebar (same as sidebar of User Profile screen)

Menu bar (same as menu bar of Charge Account screen)

SWP490_G35 103/303
FBS - Software Requirement Specification v2.0

Main

Title Chọn phương

1 Label
thức rút tiền

Radio Withdraw cash

2 Rút tiền mặt trực tiếp directly at the specific
Button
address of the system

Withdraw by bank
Rút tiền bằng cách transfer to the user's
Radio
3 chuyển khoản qua account with the
Button
ngân hàng content as given by
the system

Enter the bank

account information
Nhập thông tin tài from which the
4 Textarea Yes
khoản ngân hàng amount will be
withdrawn according
to the system's form

Number Enter the amount to

5 Số tiền rút Yes withdraw into the FBS
stepper
wallet

6 Rút tiền Button Button to trigger

Withdraw function

Footer (same as footer of User Profile screen)

3.5.2.9.2 Use case Specification

Use Case ID UC-18 Use Case Name Withdraw

Author TrangTLH Version 1.0 Date 20/07/2021

Actor FBSCustomer, FBSProvider

This function allows the authorized user to withdraw funds from the FBS
Description
system wallet

PRE-01: User has been authorized to Wallet Information screen

Precondition
PRE-02: User is in Wallet Information screen

TRG-01: User has been authorized to Wallet Information screen

TRG-02: User is in Wallet Information screen
Trigger TRG-03: User clicks “Rút tiền” at the menu bar
TRG-04: User selects a method of withdrawing money from the wallet, enters
the amount, and clicks “Rút tiền” button

SWP490_G35 104/303
FBS - Software Requirement Specification v2.0

POS-01: The withdrawal request will be sent to the admin

Post-Condition
POS-02: Admin will process the request and transfer money to the user

Main flows

Step Actor Action

1 User Go to User Profile screen

2 FBS Display User Profile screen

3 User Click “Ví FBS” hyperlink at the sidebar

4 FBS Display Wallet Information screen

5 User Click “Rút tiền” hyperlink at the menu bar

6 FBS Display Withdraw screen

7 User Select method of withdraw money in “Chọn phương thức rút tiền”

8 User Enter amount at “Số tiền rút” number stepper

9 User Click “Rút tiền” button

10 FBS Display confirm dialog

11 User Click “Đồng ý” button

Table 3-99: Withdraw Use case Specification

Alternative flows

At step 7 in the main flows, if the user selects withdraw by bank transfer to the user's
AT1
account

Sub-step Actor Action

Display “Nhập thông tin tài khoản” text area for user to enter the bank
7.1 FBS
account information

Table 3-100: Alternative flows of Withdraw Use case

AT2 At step 8 in the main flows, if the amount is not entered

Sub-step Actor Action

8.1 FBS Display message “Vui lòng nhập số tiền cần rút”

Table 3-101: Alternative flows of Withdraw Use case

SWP490_G35 105/303
FBS - Software Requirement Specification v2.0

AT3 At step 8 in the main flows, if the amount is not positive

Sub-step Actor Action

8.2 FBS Display message “Vui lòng nhập số tiền là số lớn hơn 0”

Table 3-102: Alternative flows of Withdraw Use case

AT4 At step 11 in the main flows, if the user clicks “Quay lại” button or Close button

Sub-step Actor Action

11.1 FBS Close confirm button and not save change

Table 3-103: Alternative flows of Withdraw Use case

SWP490_G35 106/303
FBS - Software Requirement Specification v2.0

3.5.2.10 UC-19 - Rate and Comment Restaurant

3.5.2.10.1 Screen Design

Figure 3-23: Screen Design of Rate and Comment Restaurant

SWP490_G35 107/303
FBS - Software Requirement Specification v2.0

Table 3-104: Rate and Comment Restaurant Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of User Profile screen)

Main (described in UC-01)

Footer (same as footer of Search Restaurant screen)

3.5.2.10.2 Use case Specification

Use Case ID UC-19 Use Case Name Rate and Comment Restaurant

Author TrangTLH Version 2.0 Date 07/06/2021

Actor FBSCustomer, FBSProvider

This function allows the authorized user to rate and comment about the
Description
restaurant

PRE-01: User has been authorized to Restaurant Detail screen

Precondition
PRE-02: User is in Restaurant Detail screen

TRG-01: User has been authorized to Restaurant Detail screen

TRG-02: User is in Restaurant Detail screen
Trigger
TRG-03: User chooses the number of star rating and write a comment
TRG-04: User clicks “Đánh giá” button

POS-01: User will rate and comment successfully.

Post-Condition POS-02: The rating and the content of the rating are saved in the database
POS-03: The feedback will display on the Restaurant Detail screen

Main flows

Step Actor Action

1 User Go to Restaurant Detail screen of a restaurant

2 FBS Display Restaurant Detail screen

3 User Choose the number of star rating

4 User Write comment

5 User Click “Đánh giá” button

6 FBS Display the feedback at the “Bài đánh giá ABC Palace từ khách hàng”

Table 3-105: Rate and Comment Restaurant Use case Specification

SWP490_G35 108/303
FBS - Software Requirement Specification v2.0

Alternative flows

AT1 At step 4 in the main flows, if the comment is not entered

Sub-step Actor Action

4.1 FBS Display a message “Vui lòng nhập nội dung đánh giá”

Table 3-106: Alternative flows of Rate and Comment Restaurant Use case

AT2 At step 4 in the main flows, if the report content is more than 250 characters

Sub-step Actor Action

5.1 FBS Display a message “Nội dung đánh giá phải ít hơn 250 ký tự”

Table 3-107: Alternative flows of Rate and Comment Restaurant Use case

Business Rules

# Rule Description

Rate and comment must choose the number of stars

Table 3-108: Business Rules of Rate and Comment Restaurant Use case

3.5.2.11 UC-20 - Report Restaurant

3.5.2.11.1 Screen Design

Figure 3-24: Screen Design of Report Restaurant

SWP490_G35 109/303
FBS - Software Requirement Specification v2.0

Table 3-109: Report Restaurant Screen Definition

Max
# Field Name Type Mandatory Description
Length

Main

1 Title Báo cáo Label

2 Nội dung báo cáo Textarea Yes 250 Enter report content

3 Gửi Button Button to send report

Button to back
4 Trở lại Button Restaurant Detail
screen

5 Đóng Button Button to close Report

Restaurant form

3.5.2.11.2 Use case Specification

Use Case ID UC-20 Use Case Name Report Restaurant

Author TrangTLH Version 1.0 Date 10/07/2021

Actor FBSCustomer, FBSProvider

This function allows the authorized user to report dishes, combos, or services
Description
of the restaurant to the admin

PRE-01: User has been authorized to Restaurant Detail screen

Precondition PRE-02: User is in Restaurant Detail screen
PRE-02: User clicks “Báo cáo” link

TRG-01: User has been authorized to Restaurant Detail screen

TRG-02: User is in Wallet Information screen
Trigger
TRG-03: User clicks “Báo cáo” link and goes to Report Restaurant popup
TRG-04: User writes a report and clicks “Gửi” button

POS-01: User will report successfully.

Post-Condition POS-02: The report is saved in the database
POS-03: Admin receives the notification of customer's report

Main flows

Step Actor Action

1 User Go to Restaurant Detail screen of a restaurant

SWP490_G35 110/303
FBS - Software Requirement Specification v2.0

2 FBS Display Restaurant Detail screen

3 User Click “Báo cáo” link

4 FBS Display Report Restaurant popup

5 User Write report

6 User Click “Gửi” button

Display a message “Bạn đã báo cáo thành công” and send a notification to the
7 FBS
admin about the customer's report

Table 3-110: Report Restaurant Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if the report content is not entered

Sub-step Actor Action

5.1 FBS Display a message “Vui lòng nhập nội dung báo cáo”

Table 3-111: Alternative flows of Report Restaurant Use case

AT2 At step 6 in the main flows, if the user clicks “Trở lại” button or Close button

Sub-step Actor Action

6.1 FBS Back to Restaurant Detail screen and not save change

Table 3-112: Alternative flows of Report Restaurant Use case

Business Rules

# Rule Description

Report must have content

Table 3-113: Business Rules of Report Restaurant Use case

SWP490_G35 111/303
FBS - Software Requirement Specification v2.0

3.5.2.12 UC-21 - Create Feast Order

3.5.2.12.1 Screen Design

Figure 3-25: Screen Design of Create Feast Order

Table 3-114: Create Feast Order Screen Definition

SWP490_G35 112/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Main

1 Title Giỏ hàng Label

2 Close Button Button to close Cart

screen

Select table type

3 Loại bàn Combo box Yes Value: Bàn 6 – Type 6
people, Bàn 8 – Type 8
people

Select session to
organize feast
4 Buổi Combo box Yes
Value: Trưa – noon,
Tối – evening

Number Enter the number of

5 Số lượng khách Yes 10
stepper guests

6 Chọn ngày Date picker Yes Select feast date

7 Ghi chú Textarea No 2000 Note for restaurant

8 Category Title
Category of items
Value: Thực đơn –
Label Menu, Combo món ăn
– Combo, Dịch vụ -
Service

9 Item Name Label Name of selected item

10 Item Price Label Sale price of selected

item

Number Quantity of selected

11 Item Quantity 5
stepper item

12 Xóa Button Button to remove

item

13 Tổng Label Total amount of feast

order

14 Thanh toán Button Button to book feast

order

SWP490_G35 113/303
FBS - Software Requirement Specification v2.0

Button to back
15 Trở lại Button Restaurant Detail
screen

3.5.2.12.2 Use case Specification

Use Case ID UC-21 Use Case Name Create Feast Order

Author TrangTLH Version 2.0 Date 08/06/2021

Actor FBSCustomer, FBSProvider

This function allows the authorized user to create a feast order by choosing
Description
the menu and services, and fill in some information

PRE-01: User has been authorized to Restaurant Menu/ Restaurant Combo/

Restaurant Service screen Commented [18]: 1. User has been authorized to
Precondition Restaurant Menu ..
PRE-02: User is in Restaurant Menu/ Restaurant Combo/ Restaurant Service
2. User is in Restaurant Menu
screen
Commented [19R18]: _Marked as resolved_

TRG-01: User has been authorized to Restaurant Menu/ Restaurant Combo/ Commented [20R18]: _Re-opened_

Restaurant Service screen Commented [21]: 1. User has been authorized to

Restaurant Menu ..
TRG-02: User is in Restaurant Menu/ Restaurant Combo/ Restaurant Service 2. User is in Restaurant Menu
Trigger screen Commented [22R21]: _Marked as resolved_
TRG-03: User selects dishes, combos, or services Commented [23R21]: _Re-opened_
TRG-04: User clicks Cart icon, goes to Cart screen, and enters order info
Commented [24]: 1. User has been authorized to
TRG-05: User clicks “Thanh toán” button Restaurant Menu ..
2. User is in Restaurant Menu
POS-01: The feast will be successfully added to the database
Commented [25R24]: _Marked as resolved_
POS-02: Users create a feast order successfully.
POS-03: System display a message “Bạn đã tạo đơn hàng thành công” and Commented [26R24]: _Re-opened_
Post-Condition clear cart Commented [27]: 1. User has been authorized to
POS-04: The money in the user's wallet will be deducted by the amount of Restaurant Menu ..
2. User is in Restaurant Menu
the deposit
POS-05: Provider receives the notification of customer's order Commented [28R27]: _Marked as resolved_
Commented [29R27]: _Re-opened_
Main flows

Step Actor Action

1 User Go to Restaurant Detail screen of a restaurant

2 FBS Display Restaurant Detail screen

3 User Click “Thực đơn”, “Combo”, “Dịch vụ” hyperlink on menu bar

4 FBS Display Restaurant Menu, Restaurant Combo, and Restaurant Service screen

5 User Select dishes, combos, or services and add them to the cart

SWP490_G35 114/303
FBS - Software Requirement Specification v2.0

6 FBS Add items to cart

7 User Click Cart icon

8 FBS Display Cart screen

Enter order detailed information about table type, session to organize feast,
9 User
number of guests, feast date and note for restaurant and number of items

10 User Click button “Thanh toán”

11 FBS Display message “Bạn đã tạo đơn hàng thành công”

Table 3-115: Create Feast Order Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if the user doesn't select any item

Sub-step Actor Action

5.1 FBS Cart displays “Giỏ hàng trống”

Table 3-116: Alternative flows of Create Feast Order Use case

AT2 At step 9 in the main flows, if the required fields are not entered

Sub-step Actor Action

9.1 FBS Display a message “Vui lòng nhập thông tin đơn hàng”

Table 3-117: Alternative flows of Create Feast Order Use case

At step 9 in the main flows, if the year of the feast is exceeded 1 year from the year of
AT3
the order date

Sub-step Actor Action

9.2 FBS Display a message “Ngày tổ chức phải là dd/mm/yyyy” hoặc sớm hơn”

Table 3-118: Alternative flows of Create Feast Order Use case

AT4 At step 10 in the main flows, if the user clicks “Trở lại” button or Close button

Sub-step Actor Action

10.1 FBS Back to Restaurant Detail screen

SWP490_G35 115/303
FBS - Software Requirement Specification v2.0

Table 3-119: Alternative flows of Create Feast Order Use case

Business Rules

# Rule Description

BR05 Only registered users can successfully log in and make party bookings on the web.

BR28 The number of guests of order must enter the number

BR29 The quantity of dish of order must enter the number

BR30 The quantity of combo of order must enter the number

BR31 The quantity of service of order must enter the number

Must select at least one item before booking a feast

Table 3-120: Business Rules of Create Feast Order Use case

.
3.5.2.13 UC-22 - View Order History
3.5.2.13.1 Screen Design

SWP490_G35 116/303
FBS - Software Requirement Specification v2.0

Figure 3-26: Screen Design of View Order History

Table 3-121: View Order History Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as User Profile screen)

Sidebar (same as User Profile screen)

Main

SWP490_G35 117/303
FBS - Software Requirement Specification v2.0

Menu for the user to

1 Status Of The Order
select the order status
they want to see
Menu bar Value: Chờ duyệt -
Pending, Chưa diễn ra
- Preparing, Đã diễn ra
- Accomplished, Đã
hủy - Canceled

2 Order Card Card Display some key

information of order

3 Restaurant Image Image Avatar of restaurant

4 Mã số đặt Label Order code

5 ABC Palace Label Name of restaurant

6 Ngày đặt Label Order date

Type of organization:
Tiệc cưới tại nhà
7 hàng/Tiệc cưới lưu Label Value: Feast at
động restaurant / Feast at
home

8 Ngày diễn ra Label Feast session and date

9 Xem chi tiết Button Button to view order

detail

10 Order Pagination Hyperlink This hyperlink links to

page of orders

Footer (same as Search Restaurant screen)

3.5.2.13.2 Use case Specification

Use Case ID UC-22 Use Case Name View Order History

Author TrangTLH Version 2.0 Date 08/06/2021

Actor FBSCustomer, FBSProvider

This function allows the authorized user to view order history such as
Description
pending orders, preparing orders, accomplish orders, and canceled orders

PRE-01: User has been authorized to User Profile screen

Precondition
PRE-02: User is in User Profile screen

SWP490_G35 118/303
FBS - Software Requirement Specification v2.0

TRG-01: User has been authorized to User Profile screen

TRG-02: User is in User Profile screen
Trigger
TRG-03: User clicks “Đơn đặt tiệc của tôi” at the sidebar
TRG-04: User clicks the links in the menu bar to view orders by status

Post-Condition POS-01: Users will view order history successfully.

Main flows

Step Actor Action

1 User Go to User Profile screen

2 FBS Display User Profile screen

3 User Click “Đơn đặt tiệc của tôi” hyperlink at the sidebar

4 FBS Display User Profile Order screen

Select “Chờ duyệt” in menu bar to view the orders that waiting for the
5 User restaurant to approve, or “Chưa diễn ra” - the orders that are being
prepared, “Đã diễn ra” - Completed orders, “Đã hủy” - Canceled orders

6 FBS Display User Profile Order screen by order status

7 User View orders

Table 3-122: View Order History Use case Specification

3.5.2.14 UC-23 - View Order Detail

3.5.2.14.1 Screen Design

SWP490_G35 119/303
FBS - Software Requirement Specification v2.0

Figure 3-27: Screen Design of View Order Detail

Table 3-123: View Order Detail Screen Definition

SWP490_G35 120/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Header (same as User Profile screen)

Sidebar (same as User Profile screen)

Main

1 ABC Palace Label Name of restaurant

2 Ha Noi Label Province of restaurant

3 Restaurant Image Image Avatar of restaurant

Type of organization
4 Loại hình Label Value: Tại cơ sở - Feast
at restaurant, Lưu
động - Feast at home

5 Mã số đơn đặt Label Order code

6 Ngày đặt Label Order date

7 Ngày diễn ra Label Feast session and date

8 Status order Label Status of order

9 Email Label Email of customer

10 Số điện thoại Label Phone number to

contact of customer

11 Số lượng khách Label Number of guests

12 Loại bàn Label Type of table

13 Ghi chú Label Note for restaurant

Include name, sale

14 Table Items Table price, quantity of
selected items

Total amount of each

15 Tổng Label type: Menu, Combo,
Service

16 Tổng tiền cần thanh toán Label Total amount of order

Chương trình khuyến

17 Label Name of promotion
mãi

SWP490_G35 121/303
FBS - Software Requirement Specification v2.0

18 Tiền đặt cọc Label Deposits of order

19 Hủy đặt Button Button to cancel the

order

Footer (same as Search Restaurant screen)

3.5.2.14.2 Use case Specification

Use Case ID UC-23 Use Case Name View Order Detail

Author TrangTLH Version 2.0 Date 08/06/2021

Actor FBSCustomer, FBSProvider

This function allows the authorized user to view detailed information on

Description
orders

PRE-01: User has been authorized to Pending Order/ Preparing Order/

Accomplished Order/ Canceled Order screen
Precondition
PRE-02: User is in Pending Order/ Preparing Order/ Accomplished Order/
Canceled screen

TRG-01: User has been authorized to Pending Order/ Preparing Order/

Accomplished Order/ Canceled Order screen
Trigger TRG-02: User is in Pending Order/ Preparing Order/ Accomplished Order/
Canceled Order screen
TRG-03: User clicks “Xem chi tiết” link

Post-Condition POS-01: Users will view order detail successfully.

Main flows

Step Actor Action

1 User Go to User Profile Order screen

2 User Click “Xem chi tiết” hyperlink in the order card that want to view

3 FBS Display User Profile Order Detail screen

4 User View order detail

Table 3-124: View Order Detail Use case Specification

SWP490_G35 122/303
FBS - Software Requirement Specification v2.0

3.5.2.15 UC-24 - Cancel Feast Order

3.5.2.15.1 Screen Design

Figure 3-28: Screen Design of Cancel Feast Order

Figure 3-29: Screen Design of Confirm Dialog

Table 3-125: Cancel Feast Order Screen Definition

SWP490_G35 123/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Confirm Dialog

1 Title Thông báo Label

2 Close Button Button to close

confirm dialog

Nhập mật khẩu của

3 Textbox Yes 32 Enter password
bạn

4 Xác nhận Button Button to accept to

cancel the order

Button to back to User

5 Trở lại Button Profile Order Detail
screen

3.5.2.15.2 Use case Specification

Use Case ID UC-24 Use Case Name Cancel Feast Order

Author TrangTLH Version 2.0 Date 08/06/2021

Actor FBSCustomer, FBSProvider

Description This function allows the authorized user to cancel his/her order

PRE-01: User has been authorized to Pending Order/ Preparing Order screen
Precondition
PRE-02: User is in Pending Order/ Preparing Order screen

PRE-01: User has been authorized to Pending Order/ Preparing Order screen
Trigger PRE-02: User is in Pending Order/ Preparing Order screen
TRG-03: User clicks “Hủy đặt” button
TRG-04: User enters password and clicks “Xác nhận” button at confirm dialog

POS-01: User will cancel the order successfully

POS-02: The order will successfully update status in the database
Post-Condition POS-03: If the order has been accepted and the cancellation time is not
within the specified time, the customer's deposit will be transferred to the
restaurant

Main flows

Step Actor Action

1 User Go to User Profile Order Detail screen

2 FBS Display User Profile Order Detail screen

SWP490_G35 124/303
FBS - Software Requirement Specification v2.0

3 User Click “Hủy đặt” button

4 FBS Display Confirm Dialog

5 User Enter password in the “Nhập mật khẩu của bạn” textbox

6 User Click “Xác nhận” button

Validate entered password and display message “Bạn đã hủy đơn hàng thành
7 FBS
công”

Table 3-126: Cancel Feast Order Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if password is not entered or wrong

Sub-step Actor Action

5.1 FBS Display a message “Mật khẩu không đúng”

Table 3-127: Alternative flows of Cancel Feast Order Use case

AT2 At step 6 in the main flows, if the user clicks “Trở lại” button or Close button

Sub-step Actor Action

6.1 FBS Back to User Profile Order Detail screen and not save change

Table 3-128: Alternative flows of Cancel Feast Order Use case

Business Rules

# Rule Description

The customer has the right to cancel the order placed before the delivery date. But
BR12 when the customer cancels the order, they have to pay compensation according to the
regulations of the restaurant and the system.

Customers can order the party to be delivered at home or the locations provided by the
BR13
restaurant.

Table 3-129: Business Rules of Cancel Feast Order Use case

SWP490_G35 125/303
FBS - Software Requirement Specification v2.0

3.5.2.16 UC-25 - Add Restaurant

3.5.2.16.1 Screen Design

Figure 3-30: Screen Design of Add Restaurant

Table 3-130: Add Restaurant Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of User Profile screen)

Main

1 Title Đăng ký nhà hàng Label

2 Tên nhà hàng Textbox Yes 100 Name of restaurant

SWP490_G35 126/303
FBS - Software Requirement Specification v2.0

Type of restaurant
Value: Tổ chức sự kiện
lưu động - Organizing
Combo a roving feast, Tổ
3 Loại hình Yes
box chức sự kiện tại cơ sở
- Organizing a
restaurant feast, Cả
hai - Both

4 Mô tả Textarea Yes 2000 Detailed description

about restaurant

Combo Province/City of
5 Tỉnh/Thành phố Yes
box restaurant

Combo
6 Quận/Huyện Yes District of restaurant
box

7 Địa chỉ Textbox Yes 100 Specific address of the

restaurant

8 Số điện thoại Textbox Yes 10 Phone number to

contact of restaurant

The number of guests

9 Sức chứa Textbox Yes 10 the restaurant can
accommodate

The business license

Mã giấy phép kinh
10 Textbox Yes 100 number of the
doanh
restaurant

Button to open popup

Giấy chứng nhận vệ to select Images of
11 sinh an toàn thực Button Yes food hygiene and
phẩm safety for catering of
the restaurant

Tôi đồng ý với các điều Checkbox to accept

12 Checkbox Yes
khoản with terms of system

Link to Terms of
13 điều khoản Hyperlink
system

Button to add a new

14 Hoàn tất Button
restaurant

Footer (same as Search Restaurant screen)

SWP490_G35 127/303
FBS - Software Requirement Specification v2.0

3.5.2.16.2 Use case Specification

Use Case ID UC-25 Use Case Name Add Restaurant

Author TrangTLH Version 2.0 Date 10/06/2021

Actor FBSCustomer, FBSProvider

This function allows the authorized user to add a new restaurant into the FBS
Description
system

PRE-01: User has been authorized to Home screen

Precondition
PRE-02: User is in Home screen

TRG-01: User has been authorized to Home screen

TRG-02: User is in Home screen
Trigger TRG-03: User clicks “Đăng ký nhà hàng” in header to go to Add Restaurant
screen
TRG-04: User enters some information about the new restaurant, and clicks
“Hoàn tất” button

POS-01: User registered new restaurants successfully.

Post-Condition POS-02: The new restaurant has been successfully added to the database
POS-03: Admin will receive a notification and view restaurant to approval

Main flows

Step Actor Action

1 User Click “Đăng ký nhà hàng” in header

2 FBS Display Add Restaurant screen

3 User Enter restaurant name in the “Tên nhà hàng” textbox

4 User Select restaurant type at “Loại hình” combo box

5 User Enter detailed description about restaurant in the “Mô tả” text area

6 User Select province/city at “Tỉnh/Thành phố” combo box

7 User Select district at “Quận/Huyện” combo box

8 User Enter specific address of restaurant in the “Địa chỉ” textbox

9 User Enter phone number used to contact of restaurant in the “Số điện thoại”

10 User Enter number of guests the restaurant can accommodate in the “Sức chứa”

SWP490_G35 128/303
FBS - Software Requirement Specification v2.0

Enter the business license number of the restaurant in the “Mã giấy phép
11 User
kinh doanh” textbox

Click “Thêm ảnh” button to open popup to select Images of food hygiene and
12 User
safety for catering of the restaurant

13 User Click “Tôi đồng ý với các điều khoản” checkbox

14 User Click “Hoàn tất” button

15 FBS Validate entered information and display confirm dialog

16 User Click “Có” button

Display a message “Đăng ký nhà hàng thành công” and redirect to My

17 FBS
Restaurant screen

Table 3-131: Add Restaurant Use case Specification

Alternative flows

AT1 At step 3 in the main flows, if restaurant name is not entered

Sub-step Actor Action

3.1 FBS Display a message “Tên nhà hàng không được để trống”

Table 3-132: Alternative flows of Add Restaurant Use case

AT2 At step 5 in the main flows, if description is not entered

Sub-step Actor Action

5.1 FBS Display a message “Mô tả không được để trống”

Table 3-133: Alternative flows of Add Restaurant Use case

AT3 At step 8 in the main flows, if address is not entered

Sub-step Actor Action

8.1 FBS Display a message “Địa chỉ không được để trống”

Table 3-134: Alternative flows of Add Restaurant Use case

AT4 At step 9 in the main flows, if phone number is not entered

SWP490_G35 129/303
FBS - Software Requirement Specification v2.0

Sub-step Actor Action

9.1 FBS Display a message “Số điện thoại không được để trống”

Table 3-135: Alternative flows of Add Restaurant Use case

AT5 At step 9 in the main flows, if phone number is wrong format

Sub-step Actor Action

9.2 FBS Display a message “Số điện thoại sai định dạng”

Table 3-136: Alternative flows of Add Restaurant Use case

AT6 At step 10 in the main flows, if number of guests is not entered

Sub-step Actor Action

10.1 FBS Display a message “Sức chứa không được để trống”

Table 3-137: Alternative flows of Add Restaurant Use case

AT7 At step 11 in the main flows, if business license number is not entered

Sub-step Actor Action

11.1 FBS Display a message “Mã giấy phép kinh doanh không được để trống”

Table 3-138: Alternative flows of Add Restaurant Use case

AT8 At step 12 in the main flows, if image is not entered

Sub-step Actor Action

12.1 FBS Display a message “Vui lòng thêm giấy chứng nhận của nhà hàng”

Table 3-139: Alternative flows of Add Restaurant Use case

AT9 At step 13 in the main flows, if checkbox is not checked

Sub-step Actor Action

13.1 FBS Display a message “Vui lòng đồng ý với điều khoản của FBS”

SWP490_G35 130/303
FBS - Software Requirement Specification v2.0

Table 3-140: Alternative flows of Add Restaurant Use case

AT10 At step 16 in the main flows, if user clicks “Trở lại” button or Close button

Sub-step Actor Action

16.1 FBS Back to Add Restaurant screen and not save

Table 3-141: Alternative flows of Add Restaurant Use case

Business Rules

# Rule Description

BR06 Only users who have been verified after an add restaurant step can become providers.

Customers can view the website, place an order on the website, and register as a
BR10
provider.

BR23 Provider can register multiple restaurants with the same login account.

BR33 The number of guests the restaurant can accommodate must enter the positive integer

Table 3-142: Business Rules of Add Restaurant Use case

3.5.2.17 UC-26 - View Notifications

3.5.2.17.1 Screen Design

Figure 3-31: Screen Design of View Notifications

Table 3-143: View Notifications Screen Definition

SWP490_G35 131/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Notification

1 Title Thông báo Label

Notification
2 Notifications List List of notification
list

3 Notification Content Hyperlink Yes Content of

notification

3.5.2.17.2 Use case Specification

Use Case ID UC-26 Use Case Name View Notification

Author TrangTLH Version 1.0 Date 11/07/2021

Actor FBSCustomer, FBSProvider

Description This function allows the authorized user to view notifications

PRE-01: User has been authorized to Home screen

Precondition
PRE-02: User is in Home screen

TRG-01: User has been authorized to Home screen

Trigger TRG-02: User is in Home screen
TRG-03: User clicks Bell icon link to view notification

Post-Condition POS-01: User view all notifications

Main flows

Step Actor Action

1 User Click the bell icon in header

2 FBS Display Notification

3 User View all notifications

Table 3-144: View Notifications Use case Specification

Alternative flows

AT1 At step 2 in the main flows, if user does not have a notification

Sub-step Actor Action

SWP490_G35 132/303
FBS - Software Requirement Specification v2.0

2.1 FBS Notification displays “Không có thông báo nào”

Table 3-145: Alternative flows of View Notifications Use case

3.5.2.18 UC-27 - Sign Out

3.5.2.18.1 Use case Specification

Use Case ID UC-27 Use Case Name Sign Out

Author TrangTLH Version 2.0 Date 08/06/2021

Actor FBSCustomer, FBSProvider, FBSAdmin

Description This function allows the authorized user to sign out to FBS

Precondition PRE-01: User successfully logged into the FBS system

TRG-01: User successfully logged into the FBS system

Trigger
TRG-02: User clicks “Đăng xuất” hyperlink in header to sign out

Post-Condition POS-01: Users will log out successfully and redirect to the Login screen

Main flows

Step Actor Action

1 User Click “Đăng xuất” hyperlink in header to sign out

2 FBS Display confirm dialog

3 User Click “Đồng ý” button

4 FBS Sign out successfully and redirect to Login screen

Table 3-146: Sign Out Use case Specification

Alternative flows

AT1 At step 3 in the main flows, if user clicks “Quay lại” button or Close button

Sub-step Actor Action

3.1 FBS Close confirm dialog and not sign out

Table 3-147: Alternative flows of Sign Out Use case

SWP490_G35 133/303
FBS - Software Requirement Specification v2.0

3.5.3 UC-28 - Refund

3.5.3.1 Use case Specification

Use Case ID UC-27 Use Case Name Refund

Author TrangTLH Version 1.0 Date 21/07/2021

Actor

The system automatically deducts the commission and refunds the deposit to
the provider after the order is completed. In addition, if the customer cancels
Description
the order, the deposit will also be refunded according to the regulations and
based on the time of cancellation

Precondition PRE-01: User creates a feast order

TRG-01: User creates a feast order

Trigger
TRG-02: User cancels a feast order

Post-Condition POS-01: Refund according to system policies and regulations

Main flows

Step Actor Action

1 FBS Refund according to system policies and regulations

Table 3-148: Refund Use case Specification

3.5.4 UC-29 - Authorize User

3.5.4.1 Use case Specification

Use Case ID UC-27 Use Case Name Authorize User

Author TrangTLH Version 2.0 Date 08/06/2021

Actor

Description This function allows verifying the user's role

Precondition PRE-01: User created an account in the FBS system

TRG-01: User created an account in the FBS system

Trigger
TRG-02: User login successfully with account

Post-Condition POS-01: Authorized user to check what functions the user can perform

Main flows

SWP490_G35 134/303
FBS - Software Requirement Specification v2.0

Step Actor Action

1 FBS Check what functions the user can perform

Table 3-149: Authorize User Use case Specification

3.5.5 Provider Functions

3.5.5.1 Use Case diagram

SWP490_G35 135/303
FBS - Software Requirement Specification v2.0

Figure 3-32: Provider Functions Use case Diagram

SWP490_G35 136/303
FBS - Software Requirement Specification v2.0

Use Case ID User case Name Description

Allow the authorized user to view all

UC-30 View List All Restaurants
restaurants that he/she has.

Allow the authorized user to update

UC-31 Update Restaurant Profile
restaurant detailed information.

Allow the authorized user to view the list

UC-32 View List All Orders
of all orders from customers.

Allow the authorized user to search the

UC-33 Search Order
order from customers by order code.

Allow the authorized user to view the

UC-34 View Order detailed information of the order from
the customer.

Allow the authorized user to accept

UC-35 Accept Order
orders from the customers.

Allow the authorized user to cancel the

UC-36 Cancel Order
order from the customer.

Allow the authorized user to complete

UC-37 Complete Order
the order from the customer.

Allow the authorized user to view the list

UC-38 View List All Combos
of all combos of own restaurant

Allow the authorized user to add a new

UC-39 Add Combo
combo into the restaurant.

Allow the authorized user to update

UC-40 Update Combo detailed information about a combo of
the restaurant.

Allow the authorized user to view the list

UC-41 View List All Dishes
of all dishes of own restaurant

Allow the authorized user to search the

UC-42 Search Dish dish of his/her restaurant by keywords
name and dish’s category.

Allow the authorized user to add a new

UC-43 Add Dish
dish to the restaurant.

Allow the authorized user to update

UC-44 Update Dish detailed information about a dish of the
restaurant.

SWP490_G35 137/303
FBS - Software Requirement Specification v2.0

Allow the authorized user to view the list

UC-45 View List All Services
of all services of own restaurant

Allow the authorized user to search the

UC-46 Search Service service of his/her restaurant by
keywords name and service’s category.

Allow the authorized user to add a new

UC-47 Add Service
service to the restaurant.

Allow the authorized user to update

UC-48 Update Service detailed information about a service of
the restaurant.

Allow the authorized user to view the list

UC-49 View List All Promotions
of all promotions of own restaurant

Allow the authorized user to add a new

UC-50 Add Promotion
promotion to the restaurant.

Allow the authorized user to update

UC-51 Update Promotion detailed information about a promotion
of the restaurant.

Allow the authorized user to add a

UC-52 Add Restaurant Image
description image for the restaurant.

Allow the authorized user to delete a

UC-53 Delete Restaurant Image
description image of the restaurant.

Table 3-150: Provider Functions Use case List

SWP490_G35 138/303
FBS - Software Requirement Specification v2.0

3.5.5.2 UC-30 - View List All Restaurants

3.5.5.2.1 Screen Design

SWP490_G35 139/303
FBS - Software Requirement Specification v2.0

Figure 3-33: Screen Design of View List All Restaurants

Table 3-151: View List All Restaurants Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of User Profile screen)

Sidebar (same as sidebar of User Profile screen)

Main

1 Title Trạng thái
Status of restaurant
Value: Chờ duyệt -
Restaurant is waiting
Label for approval, Đang
hoạt động -
Restaurant is active,
Ngừng hoạt động -
Restaurant is inactive

Display some
2 Restaurant Card Card information of
restaurant

3 Restaurant Image Image Avatar of restaurant

4 ABC Palace Label Name of restaurant

5 Star Rating Rating Rate of restaurant

6 Province Label Province of restaurant

7 Mô hình Label Type of restaurant

Number of guests that

8 Sức chứa Label restaurant can
accommodate

9 Xem chi tiết Button Button to view detail

of the restaurant

Footer (same as footer of Search Restaurant screen)

SWP490_G35 140/303
FBS - Software Requirement Specification v2.0

3.5.5.2.2 Use case Specification

Use Case ID UC-29 Use Case Name View List All Restaurants

Author TrangTLH Version 1.0 Date 14/07/2021

Actor FBSProvider

This function allows the authorized user to view all restaurants that he/she
Description
has

PRE-01: User has been authorized to User Profile screen

Precondition
PRE-02: User is in User Profile screen

TRG-01: User has been authorized to User Profile screen

Trigger TRG-02: User is in User Profile screen
TRG-03: User clicks “Nhà hàng của tôi” hyperlink at the sidebar

Post-Condition POS-01: User will view the list of all restaurants successfully

Main flows

Step Actor Action

1 User Go to User Profile screen

2 FBS Display User Profile screen

3 User Click “Nhà hàng của tôi” hyperlink at the sidebar

4 FBS Display My Restaurant screen

5 User View list all restaurants

Table 3-152: View List All Restaurants Use case Specification

SWP490_G35 141/303
FBS - Software Requirement Specification v2.0

3.5.5.3 UC-31 - Update Restaurant Profile

3.5.5.3.1 Screen Design

Figure 3-34: Screen Design of Update Restaurant Profile

SWP490_G35 142/303
FBS - Software Requirement Specification v2.0

Table 3-153: Update Restaurant Profile Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of User Profile screen)

Menu bar

Link to My Restaurant
1 Thông tin Hyperlink
Detail screen

Link to My Restaurant
2 Ảnh Hyperlink
Image screen

Link to My Restaurant
3 Thực đơn Hyperlink
Menu screen

Link to My Restaurant
4 Combo món ăn Hyperlink
Combo screen

Link to My Restaurant
5 Dịch vụ Hyperlink
Service screen

Link to My Restaurant
6 Khuyến mãi Hyperlink
Promotion screen

Link to My Restaurant
7 Đơn hàng Hyperlink
Order screen

Main

1 Restaurant Image Image Avatar of restaurant

Hyperlink to open
2 Thay đổi ảnh Hyperlink popup to update new
avatar of the
restaurant

Images of food
Giấy chứng nhận vệ
hygiene and safety for
3 sinh an toàn thực Image
catering of the
phẩm
restaurant

4 Tên nhà hàng Textbox Yes 100 Name of restaurant

5 Loại hình Combo box Yes Type of restaurant

6 Mô tả Textarea Yes 2000 Detailed description

about restaurant

7 Tỉnh/Thành phố Combo box Yes Province/City of

restaurant

SWP490_G35 143/303
FBS - Software Requirement Specification v2.0

8 Quận/Huyện Combo box Yes District of restaurant

9 Địa chỉ Textbox Yes 100 Specific address of the

restaurant

10 Số điện thoại Textbox Yes 10 Phone number to

contact of restaurant

The number of guests

11 Sức chứa Textbox Yes 10 the restaurant can
accommodate

The business license

Mã giấy phép kinh
12 Textbox Fixed number of the
doanh
restaurant

13 Trạng thái hoạt động Combo box Yes Status of restaurant

Button to trigger
14 Cập nhật Button Yes
Update function

Footer (same as Search Restaurant screen)

3.5.5.3.2 Use case Specification

Use Case ID UC-31 Use Case Name Update Restaurant Profile

Author TrangTLH Version 1.0 Date 14/07/2021

Actor FBSProvider

This function allows the authorized user to update restaurant detailed

Description
information

PRE-01: User has been authorized to My Restaurant screen

PRE-02: User is in My Restaurant screen
Precondition
PRE-03: User selects the restaurant that wants to update to go to My
Restaurant Detail Screen

TRG-01: User has been authorized to My Restaurant screen

TRG-02: User is in My Restaurant screen
TRG-03: User selects the restaurant that wants to update to go to My
Trigger
Restaurant Detail Screen
TRG-04: User goes to My Restaurant Detail screen, changes information, and
clicks “Cập nhật” button

SWP490_G35 144/303
FBS - Software Requirement Specification v2.0

POS-01: Query by information in the database and change to new

Post-Condition information.
POS-02: User will change restaurant profile successfully

Main flows

Step Actor Action

1 User Go to My Restaurant screen

2 FBS Display My Restaurant screen

3 User Click “Xem thêm” button at the restaurant you want to update

4 FBS Display My Restaurant Detail screen

5 User Click “Thay đổi ảnh” hyperlink if user want to update the image

6 FBS Display popup to select an image

7 User Select new avatar for restaurant

8 FBS Display confirm button

9 User Click “Lưu” button

10 FBS Update and display the new avatar of restaurant

11 User Enter the information that needs to be changed

12 User Click “Cập nhật” button

13 FBS Validate entered information and then display confirm dialog

14 User Click “Đồng ý” button

15 FBS Display message “Cập nhật nhà hàng thành công”

Table 3-154: Update Restaurant Profile Use case Specification

Alternative flows

AT1 At step 9 in the main flows, if user clicks “Hủy” button

Sub-step Actor Action

9.1 FBS Not save change and display old avatar

Table 3-155: Alternative flows of Update Restaurant Profile Use case

AT2 At step 11 in the main flows, if restaurant name is not entered

SWP490_G35 145/303
FBS - Software Requirement Specification v2.0

Sub-step Actor Action

11.1 FBS Display a message “Tên nhà hàng không được để trống”

Table 3-156: Alternative flows of Update Restaurant Profile Use case

AT3 At step 11 in the main flows, if description is not entered

Sub-step Actor Action

11.2 FBS Display a message “Mô tả không được để trống”

Table 3-157: Alternative flows of Update Restaurant Profile Use case

AT4 At step 11 in the main flows, if address is not entered

Sub-step Actor Action

11.3 FBS Display a message “Địa chỉ không được để trống”

Table 3-158: Alternative flows of Update Restaurant Profile Use case

AT5 At step 11 in the main flows, if phone number is not entered

Sub-step Actor Action

11.4 FBS Display a message “Số điện thoại không được để trống”

Table 3-159: Alternative flows of Update Restaurant Profile Use case

AT6 At step 11 in the main flows, if phone number is wrong format

Sub-step Actor Action

11.5 FBS Display a message “Số điện thoại sai định dạng”

Table 3-160: Alternative flows of Update Restaurant Profile Use case

AT7 At step 11 in the main flows, if number of guests is not entered

Sub-step Actor Action

11.6 FBS Display a message “Sức chứa không được để trống”

Table 3-161: Alternative flows of Update Restaurant Profile Use case

SWP490_G35 146/303
FBS - Software Requirement Specification v2.0

AT8 At step 14 in the main flows, if user click “Trở lại” button or Close button

Sub-step Actor Action

11.1 FBS Back to My Restaurant Detail screen and not save change

Table 3-162: Alternative flows of Update Restaurant Profile Use case

3.5.5.4 UC-32 - View List All Orders

3.5.5.4.1 Screen Design

SWP490_G35 147/303
FBS - Software Requirement Specification v2.0

Figure 3-35: Screen Design of View List All Orders

Table 3-163: View List All Orders Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of User Profile screen)

Menu bar (same as menu bar of Update Restaurant screen)

Main

Title Danh sách đơn

1 Label
hàng

2 Mã đơn hàng Textbox Yes Enter order code to

search

Button to trigger
3 Tìm kiếm Button Search order by order
code

4 Order Table Table Table contains order

information

5 Mã đơn Label Code of order

6 Ngày đặt Label Order date

7 Tổng tiền Label Total amount of order

8 Trạng thái Label Status of order

9 Chi tiết Button Link to My Restaurant

Order Detail screen

10 Order Pagination Hyperlink This hyperlink links to

page of orders

Footer (same as footer of Search Restaurant screen)

3.5.5.4.2 Use case Specification

Use Case ID UC-32 Use Case Name View List All Orders

Author TrangTLH Version 1.0 Date 14/07/2021

SWP490_G35 148/303
FBS - Software Requirement Specification v2.0

Actor FBSProvider

This function allows the authorized user to view the list of all orders from
Description
customers

PRE-01: User has been authorized to My Restaurant Detail screen

Precondition
PRE-02: User is in My Restaurant Detail screen

TRG-01: User has been authorized to My Restaurant Detail screen

Trigger TRG-02: User is in My Restaurant Detail screen
TRG-03: User clicks “Đơn hàng” hyperlink in the menu bar

Post-Condition POS-01: User will view the list of all orders successfully

Main flows

Step Actor Action

1 User Go to My Restaurant Detail screen

2 FBS Display My Restaurant Detail screen

3 User Click “Đơn hàng” hyperlink in the menu bar

4 FBS Display My Restaurant Order screen

5 User View list all orders of a restaurant

Table 3-164: View List All Orders Use case Specification

Business Rules

# Rule Description

BR14 Providers have full roles as customers and have additional management functions to
view, add, edit, delete products, manage orders and manage promotions

Table 3-165: Business Rules of View List All Orders Use case

SWP490_G35 149/303
FBS - Software Requirement Specification v2.0

3.5.5.5 UC-33 - Search Order

3.5.5.5.1 Screen Design

Figure 3-36: Screen Design of Search Order

Table 3-166: Search Order Screen Definition

Max
# Field Name Type Mandatory Description
Length

Reference to UC-32

3.5.5.5.2 Use case Specification

Use Case ID UC-33 Use Case Name Search Order

SWP490_G35 150/303
FBS - Software Requirement Specification v2.0

Author TrangTLH Version 1.0 Date 14/07/2021

Actor FBSProvider

This function allows the authorized user to search the order from customers
Description
by order code

PRE-01: User has been authorized to My Restaurant Order screen

Precondition
PRE-02: User is in My Restaurant Order screen

TRG-01: User has been authorized to My Restaurant Order screen

Trigger TRG-02: User is in My Restaurant Order screen
TRG-03: User enters order code and clicks “Tìm kiếm” button

POS-01: Query by search condition in the database.

Post-Condition
POS-02: Users will search successfully and view order

Main flows

Step Actor Action

1 User Go to My Restaurant Order screen

2 FBS Display My Restaurant Order screen

3 User Enter order code at “Mã đơn hàng” textbox

4 User Click “Tìm kiếm” button

5 FBS Validate entered order code and display result at My Restaurant Order screen

Table 3-167: Search Order Use case Specification

Alternative flows

AT1 At step 3 in the main flows, if order code is not entered

Sub-step Actor Action

3.1 FBS Display all orders of restaurant

Table 3-168: Alternative flows of Search Order Use case

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

SWP490_G35 151/303
FBS - Software Requirement Specification v2.0

Table 3-169: Business Rules of Search Order Use case

3.5.5.6 UC-34 - View Order

3.5.5.6.1 Screen Design

Figure 3-37: Screen Design of View Order

SWP490_G35 152/303
FBS - Software Requirement Specification v2.0

Table 3-170: View Order Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as User Profile screen)

Menu bar (same as My Restaurant Order screen)

Main

1 Title Thông tin đơn hàng Label

2 Mã số đơn đặt Label Order code

3 Ngày đặt Label Order date

4 Ngày diễn ra Label Feast session and date

5 Loại hình Label Type of organization

6 Status order Label Status of order

7 Tên khách đặt Label Name of customer

8 Số lượng khách Label Number of guests

9 Loại bàn Label Type of table

10 Ghi chú Label Note for restaurant

Include name, sale

11 Table Items Table price, quantity of
selected items

Total amount of each

12 Tổng Label type: Menu, Combo,
Service

13 Tổng tiền cần thanh toán Label Total amount of order

Chương trình khuyến

14 Label Name of promotion
mãi

15 Tiền đặt cọc Label Deposits of order

16 Nhận đơn Button Button to accept

order

17 Hủy đơn Button Button to cancel order

SWP490_G35 153/303
FBS - Software Requirement Specification v2.0

Footer (same as Search Restaurant screen)

3.5.5.6.2 Use case Specification

Use Case ID UC-34 Use Case Name View Order

Author TrangTLH Version 2.0 Date 09/06/2021

Actor FBSProvider

This function allows the authorized user to view the detailed information of
Description
the order from the customer

PRE-01: User has been authorized to My Restaurant Order screen

Precondition
PRE-02: User is in My Restaurant Order screen

TRG-01: User has been authorized to My Restaurant Order screen

Trigger TRG-02: User is in My Restaurant Order screen
TRG-03: User clicks “Chi tiết” button at the order that wants to view

Post-Condition POS-01: User will view detailed information of the order successfully

Main flows

Step Actor Action

1 User Go to My Restaurant Order screen

2 FBS Display My Restaurant Order screen

3 User Click “Chi tiết” button at the order that want to view

4 FBS Display My Restaurant Order Detail screen

5 User View detailed information of the order

Table 3-171: View Order Use case Specification

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions.

Table 3-172: Business Rules of View Order Use case

SWP490_G35 154/303
FBS - Software Requirement Specification v2.0

3.5.5.7 UC-35 - Accept Order

3.5.5.7.1 Screen Design

Figure 3-38: Screen Design of Accept Order

SWP490_G35 155/303
FBS - Software Requirement Specification v2.0

Figure 3-39: Screen Design of Confirm Dialog

Table 3-173: Accept Order Screen Definition

Max
# Field Name Type Mandatory Description
Length

Confirm Dialog

1 Title Thông báo Label

2 Close Button Button to close

confirm dialog

Nhập mật khẩu của

3 Textbox Yes 32 Enter password
bạn

4 Xác nhận Button Button to accept to

cancel the order

Button to back to User

5 Trở lại Button Profile Order Detail
screen

3.5.5.7.2 Use case Specification

Use Case ID UC-35 Use Case Name Accept Order

Author TrangTLH Version 2.0 Date 15/07/2021

Actor FBSProvider

Description This function allows the authorized user to accept orders from the customers

PRE-01: User has been authorized to My Restaurant Order Detail screen of

Precondition pending orders
PRE-02: User is in My Restaurant Order Detail screen of pending orders

SWP490_G35 156/303
FBS - Software Requirement Specification v2.0

TRG-01: User has been authorized to My Restaurant Order Detail screen of

pending orders
Trigger TRG-02: User is in My Restaurant Order Detail screen of pending orders
TRG-03: User clicks “Nhận đơn” button
TRG-04: User enters password and clicks “Xác nhận” button at confirm dialog

POS-01: User will accept the order successfully

POS-02: The order will successfully update status in the database
Post-Condition
POS-03: The money in the restaurant's wallet will be deducted by the amount
of the deposit

Main flows

Step Actor Action

1 User Go to My Restaurant Order Detail screen

2 FBS Display My Restaurant Order Detail screen

3 User Click “Nhận đơn” button

4 FBS Display Confirm Dialog

5 User Enter password in the “Nhập mật khẩu của bạn” textbox

6 User Click “Xác nhận” button

Validate entered password and display message “Bạn đã nhận đơn hàng
7 FBS
thành công”

Table 3-174: Accept Order Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if password is not entered or wrong

Sub-step Actor Action

5.1 FBS Display a message “Mật khẩu không đúng”

Table 3-175: Alternative flows of Accept Order Use case

AT2 At step 6 in the main flows, if the user clicks “Trở lại” button or Close button

Sub-step Actor Action

6.1 FBS Back to My Restaurant Order Detail screen and not save change

Table 3-176: Alternative flows of Accept Order Use case

SWP490_G35 157/303
FBS - Software Requirement Specification v2.0

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

The provider has the right to accept or cancel the order but must handle it on the day
BR15
of the order.

Table 3-177: Business Rules of Accept Order Use case

SWP490_G35 158/303
FBS - Software Requirement Specification v2.0

3.5.5.8 UC-36 - Cancel Order

3.5.5.8.1 Screen Design

Figure 3-40: Screen Design of Cancel Order

SWP490_G35 159/303
FBS - Software Requirement Specification v2.0

Figure 3-41: Screen Design of Confirm Dialog

Table 3-178: Cancel Order Screen Definition

Max
# Field Name Type Mandatory Description
Length

Confirm Dialog

1 Title Thông báo Label

2 Close Button Button to close

confirm dialog

3 Nhập mật khẩu của bạn Textbox Yes 32 Enter password

4 Xác nhận Button Button to accept to

cancel the order

Button to back to User

5 Trở lại Button Profile Order Detail
screen

3.5.5.8.2 Use case Specification

Use Case ID UC-36 Use Case Name Cancel Order

Author TrangTLH Version 2.0 Date 15/07/2021

Actor FBSProvider

This function allows the authorized user to cancel the order from the
Description
customers

PRE-01: User has been authorized to My Restaurant Order Detail screen of

Precondition
pending orders or preparing orders

SWP490_G35 160/303
FBS - Software Requirement Specification v2.0

PRE-02: User is in My Restaurant Order Detail screen of pending orders or

preparing orders

TRG-01: User has been authorized to My Restaurant Order Detail screen of

pending orders or preparing orders
TRG-02: User is in My Restaurant Order Detail screen of pending orders or
Trigger
preparing orders
TRG-03: User clicks “Hủy đơn” button
TRG-04: User enters password and clicks “Xác nhận” button at confirm dialog

POS-01: User will cancel the order successfully

Post-Condition POS-02: The order will successfully update status in the database
POS-03: The customer's deposit will be refunded to the customer's wallet

Main flows

Step Actor Action

1 User Go to My Restaurant Order Detail screen

2 FBS Display My Restaurant Order Detail screen

3 User Click “Hủy đơn” button

4 FBS Display Confirm Dialog

5 User Enter password in the “Nhập mật khẩu của bạn” textbox

6 User Click “Xác nhận” button

Validate entered password and display message “Bạn đã hủy đơn hàng thành
7 FBS
công”

Table 3-179: Cancel Order Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if password is not entered or wrong

Sub-step Actor Action

5.1 FBS Display a message “Mật khẩu không đúng”

Table 3-180: Alternative flows of Cancel Order Use case

AT2 At step 6 in the main flows, if the user clicks “Trở lại” button or Close button

SWP490_G35 161/303
FBS - Software Requirement Specification v2.0

Sub-step Actor Action

6.1 FBS Back to My Restaurant Order Detail screen and not save change

Table 3-181: Alternative flows of Cancel Order Use case

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

The provider has the right to accept or cancel the order but must handle it on the day
BR15
of the order.

Table 3-182: Business Rules of Cancel Order Use case

SWP490_G35 162/303
FBS - Software Requirement Specification v2.0

3.5.5.9 UC-37 - Complete Order

3.5.5.9.1 Screen Design

Figure 3-42: Screen Design of Complete Order

SWP490_G35 163/303
FBS - Software Requirement Specification v2.0

Figure 3-43: Screen Design of Confirm Dialog

Table 3-183: Complete Order Screen Definition

Max
# Field Name Type Mandatory Description
Length

Confirm Dialog

1 Title Thông báo Label

2 Close Button Button to close

confirm dialog

3 Nhập mật khẩu của bạn Textbox Yes 32 Enter password

4 Xác nhận Button Button to accept to

complete the order

Button to back to User

5 Trở lại Button Profile Order Detail
screen

3.5.5.9.2 Use case Specification

Use Case ID UC-37 Use Case Name Complete Order

Author TrangTLH Version 2.0 Date 15/07/2021

Actor FBSProvider

This function allows the authorized user to complete the order from the
Description
customers

PRE-01: User has been authorized to My Restaurant Order Detail screen of

Precondition preparing orders
PRE-02: User is in My Restaurant Order Detail screen of preparing order

SWP490_G35 164/303
FBS - Software Requirement Specification v2.0

TRG-01: User has been authorized to My Restaurant Order Detail screen of

preparing orders
Trigger TRG-02: User is in My Restaurant Order Detail screen of preparing orders
TRG-03: User clicks “Hoàn thành” button
TRG-04: User enters password and clicks “Xác nhận” button at confirm dialog

POS-01: User will complete the order successfully

POS-02: The order will successfully update status in the database
Post-Condition
POS-03: The customer's payment will be refunded to the provider’s wallet
after the system minus commission

Main flows

Step Actor Action

1 User Go to My Restaurant Order Detail screen

2 FBS Display My Restaurant Order Detail screen

3 User Click “Hoàn thành” button

4 FBS Display Confirm Dialog

5 User Enter password in the “Nhập mật khẩu của bạn” textbox

6 User Click “Xác nhận” button

Validate entered password and display message “Bạn đã hoàn thành đơn
7 FBS
hàng thành công”

Table 3-184: Complete Order Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if password is not entered or wrong

Sub-step Actor Action

5.1 FBS Display a message “Mật khẩu không đúng”

Table 3-185: Alternative flows of Complete Order Use case

AT2 At step 6 in the main flows, if the user clicks “Trở lại” button or Close button

Sub-step Actor Action

6.1 FBS Back to My Restaurant Order Detail screen and not save change

Table 3-186: Alternative flows of Complete Order Use case

Business Rules

SWP490_G35 165/303
FBS - Software Requirement Specification v2.0

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

Once the order has been completed and the customer has successfully paid for the
BR48
restaurant, the provider can mark the order status as completed

Table 3-187: Business Rules of Complete Order Use case

3.5.5.10 UC-38 - View List All Combos

3.5.5.10.1 Screen Design

Figure 3-44: Screen Design of View List All Combos

Table 3-188: View List All Combos Screen Definition

SWP490_G35 166/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Header (same as User Profile screen)

Menu bar (same as My Restaurant Order screen)

Main

Title Danh sách combo

1 Label
món ăn

2 Thêm combo Button Button to add a new

combo

3 Combo Table Table Table contains combos

information

4 Tên combo Label Name of combo

5 Giá Label Sale price of combo

6 Trạng thái Label Status of combo

7 Sửa Button Button to update a

combo

8 Combo Pagination Hyperlink This hyperlink links to

page of combo

Footer (same as footer of Search Restaurant screen)

3.5.5.10.2 Use case Specification

Use Case ID UC-38 Use Case Name View List All Combos

Author TrangTLH Version 2.0 Date 15/07/2021

Actor FBSProvider

This function allows the authorized user to view the list of all combos of own
Description
restaurant

PRE-01: User has been authorized to My Restaurant Detail screen

Precondition
PRE-02: User is in My Restaurant Detail screen

TRG-01: User has been authorized to My Restaurant Detail screen

Trigger TRG-02: User is in My Restaurant Detail screen
TRG-03: User clicks “Combo món ăn” hyperlink in the menu bar

SWP490_G35 167/303
FBS - Software Requirement Specification v2.0

Post-Condition POS-01: User will view the list of all combos successfully

Main flows

Step Actor Action

1 User Go to My Restaurant Detail screen

2 FBS Display My Restaurant Detail screen

3 User Click “Combo món ăn” hyperlink in the menu bar

4 FBS Display My Restaurant Combo screen

5 User View list all combos successful

Table 3-189: View List All Combos Use case Specification

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

Table 3-190: Business Rules of View List All Combos Use case

3.5.5.11 UC-39 - Add Combo

3.5.5.11.1 Screen Design

SWP490_G35 168/303
FBS - Software Requirement Specification v2.0

Figure 3-45: Screen Design of Add Combo

Table 3-191: Add Combo Screen Definition

Max
# Field Name Type Mandatory Description
Length

Main

1 Title Thêm combo Label

Button to open popup

2 Chọn hoặc đổi ảnh Hyperlink to select an avatar for
combo

3 Tên combo Textbox Yes 100 Name of combo

4 Giá combo Textbox Yes 10 Sale price of combo

5 Mô tả Textarea Yes 2000 Description of

promotion

6 Lưu Button Button to save a new

promotion

7 Trở lại Button Button to back to the

previous page

8 Close Button Button to close screen

SWP490_G35 169/303
FBS - Software Requirement Specification v2.0

3.5.5.11.2 Use case Specification

Use Case ID UC-39 Use Case Name Add Combo

Author TrangTLH Version 2.0 Date 16/07/2021

Actor FBSProvider

This function allows the authorized user to add a new combo into the
Description
restaurant

PRE-01: User has been authorized to My Restaurant Combo screen

Precondition
PRE-02: User is in My Restaurant Combo screen

TRG-01: User has been authorized to My Restaurant Combo screen

TRG-02: User is in My Restaurant Combo screen
Trigger TRG-03: User clicks “Thêm combo” button and goes to Add Combo screen
TRG-04: User enters some information about the new combo
TRG-05: User clicks “Lưu” button

POS-01: User will add a new combo successfully.

Post-Condition POS-02: The new combo has been successfully added to the database and
display on FBS system

Main flows

Step Actor Action

1 User Go to My Restaurant Combo screen and clicks “Thêm combo” button

2 FBS Display My Restaurant Add Combo screen

3 User Click “Chọn hoặc đổi ảnh” button to open popup to select avatar of combo

4 User Enter combo name in the “Tên combo” textbox

5 User Enter sale price of combo in the “Giá combo”

6 User Enter description in “Mô tả” text area

7 User Click “Lưu” button

Validate entered information, display a message and display new combo in

8 FBS
My Restaurant Combo screen

Table 3-192: Add Combo Use case Specification

Alternative flows

AT1 At step 3 in the main flows, if promotion image is not entered

SWP490_G35 170/303
FBS - Software Requirement Specification v2.0

Sub-step Actor Action

3.1 FBS Display a message “Vui lòng thêm ảnh cho combo”

Table 3-193: Alternative flows of Add Combo Use case

AT2 At step 4 in the main flows, if combo name is not entered

Sub-step Actor Action

4.1 FBS Display a message “Vui lòng nhập tên combo”

Table 3-194: Alternative flows of Add Combo Use case

AT3 At step 5 in the main flows, if combo price is not entered

Sub-step Actor Action

5.1 FBS Display a message “Vui lòng nhập giá bán”

Table 3-195: Alternative flows of Add Combo Use case

AT4 At step 5 in the main flows, if combo price is not a positive integer

Sub-step Actor Action

5.2 FBS Display a message “Giá bán phải là số nguyên dương”

Table 3-196: Alternative flows of Add Combo Use case

AT5 At step 6 in the main flows, if description is not entered

Sub-step Actor Action

6.1 FBS Display a message “Vui lòng mô tả cho combo”

Table 3-197: Alternative flows of Add Combo Use case

AT6 At step 7 in the main flows, if user clicks “Trở lại” button or Close button

Sub-step Actor Action

SWP490_G35 171/303
FBS - Software Requirement Specification v2.0

7.1 FBS Back to My Restaurant Combo screen and not save

Table 3-198: Alternative flows of Add Combo Use case

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

BR27 The price must enter the positive integer and be greater than or equal to 1,000 (VNĐ).

Table 3-199: Business Rules of Add Combo Use case

3.5.5.12 UC-40 - Update Combo

3.5.5.12.1 Screen Design

Figure 3-46: Screen Design of Update Combo

SWP490_G35 172/303
FBS - Software Requirement Specification v2.0

Figure 3-47: Screen Design of Add Dish To Combo

Table 3-200: Update Combo Screen Definition

Max
# Field Name Type Mandatory Description
Length

My Restaurant Update Combo

1 Title Cập nhật combo Label

2 Combo Image Image Avatar of combo

Button to open popup

3 Thay đổi ảnh Hyperlink to update avatar for
combo

4 Tên combo Textbox Yes 100 Name of combo

5 Giá combo Textbox Yes 10 Sale price of combo

Combo
6 Trạng thái Status of combo
box

SWP490_G35 173/303
FBS - Software Requirement Specification v2.0

7 Mô tả Textarea Yes 2000 Description of

promotion

8 Lưu Button Button to update

promotion

9 Trở lại Button Button to back to the

previous page

10 Close Button Button to close screen

Display information
11 Dishes Table Table about dishes of
combo

12 STT Label Ordinal number

13 Tên món ăn Label Name of dish

14 Loại Label Category of dish

15 Xóa Button Button to remove dish

from combo

Thêm món ăn vào Button to display

16 Button popup add dish to
combo
combo

17 Tổng tiền các món Label Provisional total price

of selected dishes

My Restaurant Combo Dish

Title Thêm món ăn vào

1 Label
combo

Display information
2 Dishes Table Table about dishes of the
restaurant

3 STT Label Ordinal number

4 Tên món ăn Label Name of dish

5 Loại Label Category of dish

6 Xóa Button Button to add dish to

combo

SWP490_G35 174/303
FBS - Software Requirement Specification v2.0

Button to close My
7 OK Button Restaurant Combo
Dish screen

Vertical
8 Scroll
Scroll Bar

3.5.5.12.2 Use case Specification

Use Case ID UC-40 Use Case Name Update Combo

Author TrangTLH Version 2.0 Date 16/07/2021

Actor FBSProvider

This function allows the authorized user to update detailed information

Description
about a combo of the restaurant

PRE-01: User has been authorized to My Restaurant Combo screen

Precondition PRE-02: User is in My Restaurant Combo screen
PRE-01: User clicks “Sửa” button at combo that wants to update

TRG-01: User has been authorized to My Restaurant Combo screen

TRG-02: User is in My Restaurant Combo screen
Trigger
TRG-03: User clicks “Sửa” button at combo that wants to update
TRG-04: User changes information about combo and clicks “Lưu” button

POS-01: Query by information in the database and change My Restaurant

Post-Condition Combo Dish screen information.
POS-02: Users will change combo successfully

Main flows

Step Actor Action

Go to My Restaurant Combo screen and click “Sửa” button at combo that

1 User
want to update

2 FBS Display My Restaurant Update Combo screen

3 User Click “Thay đổi ảnh” button to open popup to select avatar of combo

4 User Enter combo name in the “Tên combo” textbox

5 User Enter sale price of combo in the “Giá combo” textbox

6 User Select status of combo in “Trạng thái” combo box

7 User Enter description in “Mô tả” text area

8 User Click “Xóa” button at dish that want to remove from combo

SWP490_G35 175/303
FBS - Software Requirement Specification v2.0

9 FBS Delete dish from combo and display message “Xóa món ăn thành công”

10 User Click “Thêm món ăn vào combo” to add dish to combo

11 FBS Display My Restaurant Combo Dish screen

12 User Click “Thêm” button at dish that want to add to combo

13 FBS Add dish to combo and display message “Thêm món ăn thành công”

14 User Click “OK” button to close My Restaurant Combo Dish screen

15 User Click “Lưu” button

16 FBS Validate entered information, display a message, and close screen

Table 3-201: Update Combo Use case Specification

Alternative flows

AT1 At step 4 in the main flows, if combo name is not entered

Sub-step Actor Action

4.1 FBS Display a message “Tên combo không được để trống”

Table 3-202: Alternative flows of Update Combo Use case

AT2 At step 5 in the main flows, if combo price is not entered

Sub-step Actor Action

5.1 FBS Display a message “Giá bán không được để trống”

Table 3-203: Alternative flows of Update Combo Use case

AT3 At step 5 in the main flows, if combo price is not a positive integer

Sub-step Actor Action

5.2 FBS Display a message “Giá bán phải là số nguyên dương”

Table 3-204: Alternative flows of Update Combo Use case

AT4 At step 7 in the main flows, if description is not entered

Sub-step Actor Action

SWP490_G35 176/303
FBS - Software Requirement Specification v2.0

6.1 FBS Display a message “Mô tả không được để trống”

Table 3-205: Alternative flows of Update Combo Use case

AT5 At step 14 in the main flows, if user clicks “Trở lại” button or Close button

Sub-step Actor Action

7.1 FBS Back to My Restaurant Combo screen and not save

Table 3-206: Alternative flows of Update Combo Use case

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

The provider can choose the active or inactive status. When a restaurant is inactive, all
BR24
items will be hidden from customers.

BR27 The price must enter the positive integer and be greater than or equal to 1,000 (VNĐ).

Table 3-207: Business Rules of Add Combo Use case

3.5.5.13 UC-41 - View List All Dishes

3.5.5.13.1 Screen Design

SWP490_G35 177/303
FBS - Software Requirement Specification v2.0

Figure 3-48: Screen Design of View List All Dishes

Table 3-208: View list All Dishes Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of User Profile screen)

Menu bar (same as My Restaurant Order screen)

Main

1 Title Danh sách món ăn Label

SWP490_G35 178/303
FBS - Software Requirement Specification v2.0

2 Tên món ăn Textbox Enter keywords name

of dish to search

3 Loại Combo box Category of dishes

Button to trigger
4 Search Icon Button Search dish by
keywords name

5 Thêm món ăn Button Button to add a new

dish

6 Dishes Table Table Table contains dishes

information

7 Tên món ăn Label Name of dish

8 Loại Label Category of dish

9 Giá bán Label Sale price of dish

10 Trạng thái Label Status of dish

11 Sửa Button Button to update dish

12 Dish Pagination Hyperlink This hyperlink links to

page of dishes

Footer (same as footer of Search Restaurant screen)

3.5.5.13.2 Use case Specification

Use Case ID UC-41 Use Case Name View List All Dishes

Author TrangTLH Version 1.0 Date 17/07/2021

Actor FBSProvider

This function allows the authorized user to view the list of all dishes of own
Description
restaurant

PRE-01: User has been authorized to My Restaurant Detail screen

Precondition
PRE-02: User is in My Restaurant Detail screen

TRG-01: User has been authorized to My Restaurant Detail screen

TRG-02: User is in My Restaurant Detail screen
Trigger
TRG-03
User clicks “Thực đơn” hyperlink in the menu bar

SWP490_G35 179/303
FBS - Software Requirement Specification v2.0

Post-Condition POS-01: User will view the list of all dishes successfully

Main flows

Step Actor Action

1 User Go to My Restaurant Detail screen

2 FBS Display My Restaurant Detail screen

3 User Click “Thực đơn” hyperlink in the menu bar

4 FBS Display My Restaurant Dish screen

5 User View list all dishes of the restaurant

Table 3-209: View List All Dishes Use case Specification

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

Table 3-210: Business Rules of View List All Dishes Use case

3.5.5.14 UC-42 - Search Dishes

3.5.5.14.1 Screen Design

SWP490_G35 180/303
FBS - Software Requirement Specification v2.0

Figure 3-49: Screen Design of Search Dishes

Table 3-211: Search Dishes Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of User Profile screen)

Menu bar (same as My Restaurant Order screen)

Main

1 Title Danh sách món ăn Label

SWP490_G35 181/303
FBS - Software Requirement Specification v2.0

2 Tên món ăn Textbox Enter keywords name

of dish to search

3 Loại Combo box Category of dishes

Button to trigger
4 Search Icon Button Search dish by
keywords name

5 Thêm món ăn Button Button to add a new

dish

6 Dishes Table Table Table contains dishes

information

7 Tên món ăn Label Name of dish

8 Loại Label Category of dish

9 Giá bán Label Sale price of dish

10 Trạng thái Label Status of dish

11 Sửa Button Button to update dish

12 Dish Pagination Hyperlink This hyperlink links to

page of dishes

Footer (same as footer of Search Restaurant screen)

3.5.5.14.2 Use case Specification

Use Case ID UC-42 Use Case Name Search Dishes

Author TrangTLH Version 1.0 Date 17/07/2021

Actor FBSProvider

This function allows the authorized user to search the dish of his/her
Description
restaurant by keywords name and dish’s category

PRE-01: User has been authorized to My Restaurant Dish screen

Precondition
PRE-02: User is in My Restaurant Dish screen

TRG-01: User has been authorized to My Restaurant Dish screen

TRG-02: User is in My Restaurant Dish screen
Trigger
TRG-03: User enters keywords name, select category and clicks “Tìm kiếm”
button

Post-Condition POS-01: Query by search condition in the database.

SWP490_G35 182/303
FBS - Software Requirement Specification v2.0

POS-02: Users will search successfully and view the list of dishes

Main flows

Step Actor Action

1 User Go to My Restaurant Dish screen

2 FBS Display My Restaurant Dish screen

3 User Enter keywords name at “Tên món ăn” textbox

4 User Select category of dishes in “Loại” combo box

5 User Click search icon

Validate entered keywords name and display result at My Restaurant Dish

6 FBS
screen

Table 3-212: Search Dishes Use case Specification

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

Table 3-213: Business Rules of Search Dishes Use case

3.5.5.15 UC-43 - Add Dish

3.5.5.15.1 Screen Design

SWP490_G35 183/303
FBS - Software Requirement Specification v2.0

Figure 3-50: Screen Design of Add Dish

Table 3-214: Add Dish Screen Definition

Max
# Field Name Type Mandatory Description
Length

Main

1 Title Thêm món ăn Label

Button to open popup

2 Chọn hoặc đổi ảnh Hyperlink to select an avatar for
dish

3 Tên món ăn Textbox Yes 100 Name of dish

Combo
4 Loại món ăn Yes Category of dish
box

5 Giá món ăn Textbox Yes 10 Sale price of dish

6 Mô tả Textarea Yes 2000 Description of dish

7 Lưu Button Button to save a new

dish

SWP490_G35 184/303
FBS - Software Requirement Specification v2.0

8 Trở lại Button Button to back to the

previous page

9 Close Button Button to close screen

3.5.5.15.2 Use case Specification

Use Case ID UC-43 Use Case Name Add Dish

Author TrangTLH Version 2.0 Date 17/07/2021

Actor FBSProvider

Description This function allows the authorized user to add a new dish to the restaurant

PRE-01: User has been authorized to My Restaurant Dish screen

Precondition
PRE-02: User is in My Restaurant Dish screen

TRG-01: User has been authorized to My Restaurant Dish screen

TRG-02: User is in My Restaurant Dish screen
Trigger TRG-03: User clicks “Thêm món ăn” button
TRG-04: User enters some information about the new dish and clicks “Lưu”
button

POS-01: User will add a new dish successfully.

Post-Condition POS-02: The new dish has been successfully added to the database and
display on FBS system

Main flows

Step Actor Action

1 User Go to My Restaurant Dish screen and clicks “Thêm món ăn” button

2 FBS Display My Restaurant Add Dish screen

3 User Click “Chọn hoặc đổi ảnh” button to open popup to select avatar of dish

4 User Enter dish name in the “Tên món ăn” textbox

5 User Select category of dish in the “Loại món ăn” combo box

6 User Enter sale price of dish in the “Giá món ăn” textbox

7 User Enter description in “Mô tả” text area

8 User Click “Lưu” button

Validate entered information, display a message and display new dish in My

9 FBS
Restaurant Dish screen

Table 3-215: Add Dish Use case Specification

SWP490_G35 185/303
FBS - Software Requirement Specification v2.0

Alternative flows

AT1 At step 3 in the main flows, if dish image is not entered

Sub-step Actor Action

3.1 FBS Display a message “Vui lòng thêm ảnh cho món ăn”

Table 3-216: Alternative flows of Add Dish Use case

AT2 At step 4 in the main flows, dish name is not entered

Sub-step Actor Action

4.1 FBS Display a message “Vui lòng nhập tên món ăn”

Table 3-217: Alternative flows of Add Dish Use case

AT3 At step 6 in the main flows, if sale price is not entered

Sub-step Actor Action

6.1 FBS Display a message “Vui lòng nhập giá bán”

Table 3-218: Alternative flows of Add Dish Use case

AT4 At step 6 in the main flows, if sale price is not a positive integer

Sub-step Actor Action

6.2 FBS Display a message “Giá bán phải là số nguyên dương”

Table 3-219: Alternative flows of Add Dish Use case

AT5 At step 7 in the main flows, if description is not entered

Sub-step Actor Action

7.1 FBS Display a message “Vui lòng mô tả cho món ăn”

Table 3-220: Alternative flows of Add Dish Use case

SWP490_G35 186/303
FBS - Software Requirement Specification v2.0

AT6 At step 8 in the main flows, if user clicks “Trở lại” button or Close button

Sub-step Actor Action

8.1 FBS Back to My Restaurant Dish screen and not save

Table 3-221: Alternative flows of Add Dish Use case

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

BR27 The price must enter the positive integer and be greater than or equal to 1,000 (VNĐ).

Table 3-222: Business Rules of Add Dish Use case

3.5.5.16 UC-44 - Update Dish

3.5.5.16.1 Screen Design

SWP490_G35 187/303
FBS - Software Requirement Specification v2.0

Figure 3-51: Screen Design of Update Dish

Table 3-223: Update Dish Screen Definition

Max
# Field Name Type Mandatory Description
Length

Main

1 Title Cập nhật món ăn Label

2 Dish Image Image Avatar of dish

Button to open the

3 Thay đổi ảnh Hyperlink popup to update
avatar for dish

4 Tên món ăn Textbox Yes 100 Name of dish

Combo
5 Loại món ăn Yes Category of dish
box

SWP490_G35 188/303
FBS - Software Requirement Specification v2.0

Combo
6 Trạng thái Status of dish
box

7 Giá món ăn Textbox Yes 10 Sale price of dish

8 Mô tả Textarea Yes 2000 Description of dish

9 Lưu Button Button to save a new

dish

10 Trở lại Button Button to back to the

previous page

11 Close Button Button to close screen

3.5.5.16.2 Use case Specification

Use Case ID UC-44 Use Case Name Update Dish

Author TrangTLH Version 2.0 Date 17/07/2021

Actor FBSProvider

This function allows the authorized user to update detailed information

Description
about a dish of the restaurant

PRE-01: User has been authorized to My Restaurant Dish screen

Precondition
PRE-02: User is in My Restaurant Dish screen

TRG-01: User has been authorized to My Restaurant Dish screen

TRG-02: User is in My Restaurant Dish screen
Trigger
TRG-03: User clicks “Sứa” button at the dish that wants to update
TRG-04: User changes information about dish and clicks “Lưu” button

POS-01: Query by information in the database and change My Restaurant

Post-Condition Dish screen information.
POS-02: User will change dish successfully

Main flows

Step Actor Action

Go to My Restaurant Dish screen and click “Sửa” button at dish that want to
1 User
update

2 FBS Display My Restaurant Update Dish screen

3 User Click “Thay đổi ảnh” button to open popup to select avatar of dish

4 User Enter dish name in the “Tên món ăn” textbox

SWP490_G35 189/303
FBS - Software Requirement Specification v2.0

5 User Select category of dish in “Loại món ăn” combo box

6 User Select status of dish in “Trạng thái” combo box

7 User Enter sale price of dish in the “Giá món ăn” textbox

8 User Enter description in “Mô tả” text area

9 User Click “Lưu” button

Validate entered information, display a message, and back to My Restaurant

10 FBS
Dish screen

Table 3-224: Update Dish Use case Specification

Alternative flows

AT1 At step 4 in the main flows, dish name is not entered

Sub-step Actor Action

4.1 FBS Display a message “Tên món ăn không được để trống”

Table 3-225: Alternative flows of Update Dish Use case

AT2 At step 7 in the main flows, if sale price is not entered

Sub-step Actor Action

7.1 FBS Display a message “Giá bán không được để trống”

Table 3-226: Alternative flows of Update Dish Use case

AT3 At step 7 in the main flows, if sale price is not a positive integer

Sub-step Actor Action

7.2 FBS Display a message “Giá bán phải là số nguyên dương”

Table 3-227: Alternative flows of Update Dish Use case

AT4 At step 8 in the main flows, if description is not entered

Sub-step Actor Action

8.1 FBS Display a message “Vui lòng mô tả cho món ăn”

Table 3-228: Alternative flows of Update Dish Use case

SWP490_G35 190/303
FBS - Software Requirement Specification v2.0

AT5 At step 9 in the main flows, if user clicks “Trở lại” button or Close button

Sub-step Actor Action

9.1 FBS Back to My Restaurant Dish screen and not save

Table 3-229: Alternative flows of Update Dish Use case

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

The provider can choose the active or inactive status. When a restaurant is inactive, all
BR24
items will be hidden from customers.

BR27 The price must enter the positive integer and be greater than or equal to 1,000 (VNĐ).

Table 3-230: Business Rules of Update Dish Use case

3.5.5.17 UC-45 - View List All Services

3.5.5.17.1 Screen Design

SWP490_G35 191/303
FBS - Software Requirement Specification v2.0

Figure 3-52: Screen Design of View List All Services

Table 3-231: View List All Services Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of User Profile screen)

Menu bar (same as My Restaurant Order screen)

Main

1 Title Danh sách dịch vụ Label

SWP490_G35 192/303
FBS - Software Requirement Specification v2.0

2 Tên dịch vụ Textbox 100 Enter keywords name

of service to search

3 Loại Combo box Category of services

Button to trigger
4 Search Icon Button Search service by
keywords name

5 Thêm dịch vụ Button Button to add a new

service

6 Services Table Table Table contains

services information

7 Tên dịch vụ Label Name of service

8 Loại Label Category of service

9 Giá bán Label Sale price of service

10 Trạng thái Label Status of service

11 Sửa Button Button to update

service

12 Service Pagination Hyperlink This hyperlink links to

page of services

Footer (same as footer of Search Restaurant screen)

3.5.5.27.2 Use case Specification

Use Case ID UC-45 Use Case Name View List All Services

Author TrangTLH Version 1.0 Date 17/07/2021

Actor FBSProvider

This function allows the authorized user to view the list of all services of own
Description
restaurant

PRE-01: User has been authorized to My Restaurant Detail screen

Precondition
PRE-02: User is in My Restaurant Detail screen

TRG-01: User has been authorized to My Restaurant Detail screen

Trigger TRG-02: User is in My Restaurant Detail screen
TRG-03: User clicks “Dịch vụ” hyperlink in the menu bar

Post-Condition POS-01: User will view list of all services successfully

SWP490_G35 193/303
FBS - Software Requirement Specification v2.0

Main flows

Step Actor Action

1 User Go to My Restaurant Detail screen

2 FBS Display My Restaurant Detail screen

3 User Click “Dịch vụ” hyperlink in the menu bar

4 FBS Display My Restaurant Service screen

5 User View list all services of restaurant

Table 3-232: View List All Services Use case Specification

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

Table 3-233: Business Rules of View List All Services Use case

3.5.5.18 UC-46 - Search Services

3.5.5.18.1 Screen Design

SWP490_G35 194/303
FBS - Software Requirement Specification v2.0

Figure 3-53: Screen Design of Search Services

Table 3-234: Search Services Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of User Profile screen)

Menu bar (same as My Restaurant Order screen)

Main

1 Title Danh sách dịch vụ Label

SWP490_G35 195/303
FBS - Software Requirement Specification v2.0

2 Tên dịch vụ Textbox Enter keywords name

of service to search

3 Loại Combo box Category of services

Button to trigger
4 Search Icon Button Search service by
keywords name

5 Thêm dịch vụ Button Button to add a new

service

6 Services Table Table Table contains

services information

7 Tên dịch vụ Label Name of service

8 Loại Label Category of service

9 Giá bán Label Sale price of service

10 Trạng thái Label Status of service

11 Sửa Button Button to update

service

12 Service Pagination Hyperlink This hyperlink links to

page of services

Footer (same as footer of Search Restaurant screen)

3.5.5.18.2 Use case Specification

Use Case ID UC-45 Use Case Name Search Services

Author TrangTLH Version 1.0 Date 17/07/2021

Actor FBSProvider

This function allows the authorized user to search the service of his/her
Description
restaurant by keywords name and service’s category

PRE-01: User has been authorized to My Restaurant Service screen

Precondition
PRE-02: User is in My Restaurant Service screen

TRG-01: User has been authorized to My Restaurant Service screen

TRG-02: User is in My Restaurant Service screen
Trigger
TRG-03: User enters keywords name, select category and clicks “Tìm kiếm”
button

SWP490_G35 196/303
FBS - Software Requirement Specification v2.0

POS-01: Query by search condition in the database.

Post-Condition
POS-02: Users will search successfully and view the list of services

Main flows

Step Actor Action

1 User Go to My Restaurant Service screen

2 FBS Display My Restaurant Service screen

3 User Enter keywords name at “Tên dịch vụ” textbox

4 User Select category of services in “Loại” combo box

5 User Click search icon

Validate entered keywords name and display result at My Restaurant Service

6 FBS
screen

Table 3-235: Search Services Use case Specification

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

Table 3-236: Business Rules of Search Services Use case

SWP490_G35 197/303
FBS - Software Requirement Specification v2.0

3.5.5.19 UC-47 - Add Service

3.5.5.19.1 Screen Design

Figure 3-54: Screen Design of Add Service

Table 3-237: Add Service Screen Definition

Max
# Field Name Type Mandatory Description
Length

Main

1 Title Thêm dịch vụ Label

Button to open popup

2 Chọn hoặc đổi ảnh Hyperlink to select an avatar for
service

3 Tên dịch vụ Textbox Yes 100 Name of service

Combo
4 Loại dịch vụ Yes Category of service
box

5 Giá dịch vụ Textbox Yes 10 Sale price of service

SWP490_G35 198/303
FBS - Software Requirement Specification v2.0

6 Mô tả Textarea Yes 2000 Description of service

8 Lưu Button Button to save a new

service

9 Trở lại Button Button to back to the

previous page

10 Close Button Button to close screen

3.5.5.19.2 Use case Specification

Use Case ID UC-47 Use Case Name Add Service

Author TrangTLH Version 2.0 Date 17/07/2021

Actor FBSProvider

This function allows the authorized user to add a new service to the
Description
restaurant

PRE-01: User has been authorized to My Restaurant Service screen

Precondition PRE-02: User is in My Restaurant Service screen

TRG-01: User has been authorized to My Restaurant Service screen

TRG-02: User is in My Restaurant Service screen
Trigger TRG-03: User clicks “Thêm dịch vụ” button
TRG-04: User enters some information about new service and clicks “Lưu”
button

POS-01: User will add a new service successfully.

Post-Condition POS-02: The new service has been successfully added to the database and
display on FBS system

Main flows

Step Actor Action

1 User Go to My Restaurant Service screen and clicks “Thêm dịch vụ” button

2 FBS Display My Restaurant Add Service screen

3 User Click “Chọn hoặc đổi ảnh” button to open popup to select avatar of service

4 User Enter service name in the “Tên dịch vụ” textbox

5 User Select category of service in the “Loại dịch vụ” combo box

6 User Enter sale price of service in the “Giá dịch vụ” textbox

7 User Enter description in “Mô tả” text area

SWP490_G35 199/303
FBS - Software Requirement Specification v2.0

8 User Click “Lưu” button

Validate entered information, display a message and display new service in

9 FBS
My Restaurant Service screen

Table 3-238: Add Service Use case Specification

Alternative flows

AT1 At step 3 in the main flows, if service image is not entered

Sub-step Actor Action

3.1 FBS Display a message “Vui lòng thêm ảnh cho dịch vụ”

Table 3-239: Alternative flows of Add Service Use case

AT2 At step 4 in the main flows, service name is not entered

Sub-step Actor Action

4.1 FBS Display a message “Vui lòng nhập tên dịch vụ”

Table 3-240: Alternative flows of Add Service Use case

AT3 At step 6 in the main flows, if sale price is not entered

Sub-step Actor Action

6.1 FBS Display a message “Vui lòng nhập giá bán”

Table 3-241: Alternative flows of Add Service Use case

AT4 At step 6 in the main flows, if sale price is not a positive integer

Sub-step Actor Action

6.2 FBS Display a message “Giá bán phải là số nguyên dương”

Table 3-242: Alternative flows of Add Service Use case

AT5 At step 7 in the main flows, if description is not entered

SWP490_G35 200/303
FBS - Software Requirement Specification v2.0

Sub-step Actor Action

7.1 FBS Display a message “Vui lòng mô tả cho dịch vụ”

Table 3-243: Alternative flows of Add Service Use case

AT6 At step 8 in the main flows, if user clicks “Trở lại” button or Close button

Sub-step Actor Action

8.1 FBS Back to My Restaurant Service screen and not save

Table 3-244: Alternative flows of Add Service Use case

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

BR27 The price must enter the positive integer and be greater than or equal to 1,000 (VNĐ).

Table 3-245: Business Rules of Add Service Use case

SWP490_G35 201/303
FBS - Software Requirement Specification v2.0

3.5.5.20 UC-48 - Update Service

3.5.5.20.1 Screen Design

Figure 3-55: Screen Design of Update Service

Table 3-246: Update Service Screen Definition

Max
# Field Name Type Mandatory Description
Length

Main

1 Title Cập nhật dịch vụ Label

SWP490_G35 202/303
FBS - Software Requirement Specification v2.0

2 Service Image Image Avatar of service

Button to open popup

3 Thay đổi ảnh Hyperlink to update avatar for
service

4 Tên dịch vụ Textbox Yes 100 Name of service

5 Loại dịch vụ Combo box Yes Category of service

6 Trạng thái Combo box Status of service

7 Giá dịch vụ Textbox Yes 10 Sale price of service

8 Mô tả Textarea Yes 2000 Description of service

9 Lưu Button Button to save a new

service

10 Trở lại Button Button to back to the

previous page

11 Close Button Button to close screen

3.5.5.20.2 Use case Specification

Use Case ID UC-48 Use Case Name Update Service

Author TrangTLH Version 2.0 Date 17/07/2021

Actor FBSProvider

This function allows the authorized user to update detailed information

Description
about a service of the restaurant

PRE-01: User has been authorized to My Restaurant Service screen

Precondition PRE-02: User is in My Restaurant Service screen

TRG-01: User has been authorized to My Restaurant Service screen

TRG-02: User is in My Restaurant Service screen
Trigger
TRG-03: User clicks “Sứa” button at service that wants to update
TRG-04: User changes information about service and clicks “Lưu” button

POS-01: Query by information in the database and change My Restaurant

Post-Condition Service screen information.
POS-02: Users will change service successfully

Main flows

SWP490_G35 203/303
FBS - Software Requirement Specification v2.0

Step Actor Action

Go to My Restaurant Service screen and click “Sửa” button at service that

1 User
want to update

2 FBS Display My Restaurant Update Service screen

3 User Click “Thay đổi ảnh” button to open popup to select avatar of service

4 User Enter service name in the “Tên dịch vụ” textbox

5 User Select category of service in “Loại dịch vụ” combo box

6 User Select status of service in “Trạng thái” combo box

7 User Enter sale price of service in the “Giá dịch vụ” textbox

8 User Enter description in “Mô tả” text area

9 User Click “Lưu” button

Validate entered information, display a message, and back to My Restaurant

10 FBS
Dish screen

Table 3-247: Update Service Use case Specification

Alternative flows

AT1 At step 4 in the main flows, dish name is not entered

Sub-step Actor Action

4.1 FBS Display a message “Tên món ăn không được để trống”

Table 3-248: Alternative flows of Update Service Use case

AT2 At step 7 in the main flows, if sale price is not entered

Sub-step Actor Action

7.1 FBS Display a message “Giá bán không được để trống”

Table 3-249: Alternative flows of Update Service Use case

SWP490_G35 204/303
FBS - Software Requirement Specification v2.0

AT3 At step 7 in the main flows, if sale price is not a positive integer

Sub-step Actor Action

7.2 FBS Display a message “Giá bán phải là số nguyên dương”

Table 3-250: Alternative flows of Update Service Use case

AT4 At step 8 in the main flows, if description is not entered

Sub-step Actor Action

8.1 FBS Display a message “Vui lòng mô tả cho món ăn”

Table 3-251: Alternative flows of Update Service Use case

AT5 At step 9 in the main flows, if user clicks “Trở lại” button or Close button

Sub-step Actor Action

9.1 FBS Back to My Restaurant Dish screen and not save

Table 3-252: Alternative flows of Update Service Use case

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

The provider can choose the active or inactive status. When a restaurant is inactive, all
BR24
items will be hidden from customers.

BR27 The price must enter the positive integer and be greater than or equal to 1,000 (VNĐ).

Table 3-253: Business Rules of Update Service Use case

SWP490_G35 205/303
FBS - Software Requirement Specification v2.0

3.5.5.21 UC-49 - View List All Promotions

3.5.5.21.1 Screen Design

Figure 3-56: Screen Design of View List All Promotions

Table 3-254: View List All Promotions Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as User Profile screen)

Menu bar (same as My Restaurant Order screen)

Main

Title Danh sách khuyến

1 Label
mãi

2 Thêm khuyến mãi Button Button to add a new

promotion

SWP490_G35 206/303
FBS - Software Requirement Specification v2.0

3 Promotion Table Table Table contains

promotion information

4 Tên chương trình Label Name of promotion

5 Ngày bắt đầu Label Start date

6 Ngày kết thúc Label End date

7 Trạng thái Label Status of promotion

8 Sửa Button Button to update a

promotion

9 Promotion Pagination Hyperlink This hyperlink links to

page of promotions

Footer (same as footer of Search Restaurant screen)

3.5.5.2.2 Use case Specification

Use Case ID UC-49 Use Case Name View List All Promotions

Author TrangTLH Version 2.0 Date 15/07/2021

Actor FBSProvider

This function allows the authorized user to view the list of all promotions of
Description
his/her restaurant

PRE-01: User has been authorized to My Restaurant Detail screen

Precondition PRE-02: User is in My Restaurant Detail screen

TRG-01: User has been authorized to My Restaurant Detail screen

Trigger TRG-02: User is in My Restaurant Detail screen
TRG-03: User clicks “Khuyến mãi” hyperlink in the menu bar

Post-Condition POS-01: User will view the list of all promotions successfully

Main flows

Step Actor Action

1 User Go to My Restaurant Detail screen

2 FBS Display My Restaurant Detail screen

3 User Click “Khuyến mãi” hyperlink in the menu bar

SWP490_G35 207/303
FBS - Software Requirement Specification v2.0

4 FBS Display My Restaurant Promotion screen

5 User View list all promotions successfully

Table 3-255: View List All Promotions Use case Specification

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

Table 3-256: Business Rules of View List All Promotions Use case

3.5.5.22 UC-50 - Add Promotion

3.5.5.22.1 Screen Design

Figure 3-57: Screen Design of Add Promotion

SWP490_G35 208/303
FBS - Software Requirement Specification v2.0

Table 3-257: Add Promotion Screen Definition

Max
# Field Name Type Mandatory Description
Length

Main

1 Title Thêm khuyến mãi Label

Button to open popup

2 Chọn hoặc đổi ảnh Hyperlink to select an avatar for
promotion

3 Tên khuyến mãi Textbox Yes 100 Name of promotion

Number Discount percentage

4 Phần trăm khuyến mãi Yes 3
stepper of promotion

Date Start date of

5 Ngày bắt đầu Yes
picker promotion

Date End date of

6 Ngày kết thúc Yes
picker promotion

7 Mô tả Textarea Yes 2000 Description of

promotion

8 Lưu Button Button to save a new

promotion

9 Trở lại Button Button to back to the

previous page

10 Close Button Button to close screen

3.5.5.22.2 Use case Specification

Use Case ID UC-50 Use Case Name Add Promotion

Author TrangTLH Version 2.0 Date 15/07/2021

Actor FBSProvider

This function allows the authorized user to add a new promotion to the
Description
restaurant

PRE-01: User has been authorized to My Restaurant Promotion screen

Precondition PRE-02: User is in My Restaurant Promotion screen

SWP490_G35 209/303
FBS - Software Requirement Specification v2.0

TRG-01: User has been authorized to My Restaurant Promotion screen

TRG-02: User is in My Restaurant Promotion screen
Trigger TRG-03: User clicks “Thêm khuyến mãi” button
TRG-04: User enters some information about the new promotion and clicks
“Lưu” button

POS-01: User will add a new promotion successfully.

Post-Condition POS-02: The new promotion has been successfully added to the database and
display on FBS system

Main flows

Step Actor Action

1 User Go to My Restaurant Promotion screen and clicks “Thêm khuyến mãi” button

2 FBS Display My Restaurant Add Promotion screen

Click “Chọn hoặc đổi ảnh” button to open popup to select avatar of
3 User
promotion

4 User Enter promotion name in the “Tên khuyến mãi” textbox

5 User Enter discount percentage in the “Phần trăm khuyến mãi”

6 User Select start date in “Ngày bắt đầu”

7 User Select end date in “Ngày kết thúc”

8 User Enter description in “Mô tả” text area

9 User Click “Lưu” button

Validate entered information, display a message and display new promotion

10 FBS
in My Restaurant Promotion screen

Table 3-258: Add Promotion Use case Specification

Alternative flows

AT1 At step 3 in the main flows, if promotion image is not entered

Sub-step Actor Action

3.1 FBS Display a message “Vui lòng thêm ảnh cho khuyến mãi”

Table 3-259: Alternative flows of Add Promotion Use case

SWP490_G35 210/303
FBS - Software Requirement Specification v2.0

AT2 At step 4 in the main flows, if promotion name is not entered

Sub-step Actor Action

4.1 FBS Display a message “Vui lòng nhập tên khuyến mãi”

Table 3-260: Alternative flows of Add Promotion Use case

AT3 At step 5 in the main flows, if discount percentage is not a positive integer

Sub-step Actor Action

5.1 FBS Display a message “Phần trăm khuyến mãi phải là số nguyên dương”

Table 3-261: Alternative flows of Add Promotion Use case

AT4 At step 6 in the main flows, if start date is not entered

Sub-step Actor Action

6.1 FBS Display a message “Vui lòng chọn ngày bắt đầu”

Table 3-262: Alternative flows of Add Promotion Use case

AT5 At step 6 in the main flows, if start date is smaller than create promotion date

Sub-step Actor Action

6.2 FBS Display a message “Vui lòng chọn ngày lớn hơn hoặc bằng ngày hôm nay”

Table 3-263: Alternative flows of Add Promotion Use case

AT6 At step 7 in the main flows, if end date is not entered

Sub-step Actor Action

7.1 FBS Display a message “Vui lòng chọn ngày kết thúc”

Table 3-264: Alternative flows of Add Promotion Use case

SWP490_G35 211/303
FBS - Software Requirement Specification v2.0

AT7 At step 7 in the main flows, if end date is smaller than create promotion date

Sub-step Actor Action

7.2 FBS Display a message “Vui lòng chọn ngày lớn hơn hoặc bằng ngày hôm nay”

Table 3-265: Alternative flows of Add Promotion Use case

AT8 At step 8 in the main flows, if description is not entered

Sub-step Actor Action

8.1 FBS Display a message “Vui lòng mô tả cho khuyến mãi”

Table 3-266: Alternative flows of Add Promotion Use case

AT9 At step 10 in the main flows, if user clicks “Trở lại” button or Close button

Sub-step Actor Action

10.1 FBS Back to My Restaurant Promotion screen and not save

Table 3-267: Alternative flows of Add Promotion Use case

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

BR32 Discount percentage of promotion must enter the positive integer

Table 3-268: Business Rules of Add Promotion Use case

SWP490_G35 212/303
FBS - Software Requirement Specification v2.0

3.5.5.23 UC-51 - Update Promotion

3.5.5.23.1 Screen Design

Figure 3-58: Screen Design of Update Promotion

Table 3-269: Update Promotion Screen Definition

SWP490_G35 213/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Main

Title Cập nhật khuyến

1 Label
mãi

2 Promotion Image Image Avatar of promotion

Button to open popup

3 Thay đổi ảnh Hyperlink to update avatar for
promotion

4 Tên khuyến mãi Textbox Yes 100 Name of promotion

Number Discount percentage

5 Phần trăm khuyến mãi Yes 3
stepper of promotion

Date Start date of

6 Ngày bắt đầu Yes
picker promotion

Date End date of

7 Ngày kết thúc Yes
picker promotion

Combo
8 Trạng thái Fixed Status of promotion
box

9 Mô tả Textarea Yes 2000 Description of

promotion

10 Lưu Button Button to update a

promotion

11 Trở lại Button Button to back to the

previous page

12 Close Button Button to close screen

3.5.5.23.2 Use case Specification

Use Case ID UC-51 Use Case Name Update Promotion

Author TrangTLH Version 2.0 Date 16/07/2021

Actor FBSProvider

This function allows the authorized user to update detailed information

Description
about a promotion of the restaurant

SWP490_G35 214/303
FBS - Software Requirement Specification v2.0

PRE-01: User has been authorized to My Restaurant Promotion screen

Precondition PRE-02: User is in My Restaurant Promotion screen

TRG-01: User has been authorized to My Restaurant Promotion screen

TRG-02: User is in My Restaurant Promotion screen
Trigger
TRG-03: User clicks “Sửa” button at promotion that wants to update
TRG-04: User changes information about promotion and clicks “Lưu” button

POS-01: Query by information in the database and change to new

Post-Condition information.
POS-02: User will change promotion successfully

Main flows

Step Actor Action

Go to My Restaurant Promotion screen and “Sửa” button at promotion that

1 User
want to update

2 FBS Display My Restaurant Update Promotion screen

3 User Click “Thay đổi ảnh” button to open popup to update avatar of promotion

4 User Enter promotion name in the “Tên khuyến mãi” textbox

5 User Enter discount percentage in the “Phần trăm khuyến mãi”

6 User Select start date in “Ngày bắt đầu”

7 User Select end date in “Ngày kết thúc”

8 User Enter description in “Mô tả” text area

9 User Click “Lưu” button

10 FBS Validate entered information and then display confirm dialog

11 User Click “Đồng ý” button

12 FBS Display message “Cập nhật nhà hàng thành công”

Table 3-270: Update Promotion Use case Specification

Alternative flows

AT1 At step 4 in the main flows, if promotion name is not entered

SWP490_G35 215/303
FBS - Software Requirement Specification v2.0

Sub-step Actor Action

4.1 FBS Display a message “Tên khuyến mãi không được để trống”

Table 3-271: Alternative flows of Update Promotion Use case

AT2 At step 5 in the main flows, if discount percentage is not a positive integer

Sub-step Actor Action

5.1 FBS Display a message “Phần trăm khuyến mãi phải là số nguyên dương”

Table 3-272: Alternative flows of Update Promotion Use case

AT3 At step 6 in the main flows, if start date is not entered

Sub-step Actor Action

6.1 FBS Display a message “Vui lòng chọn ngày bắt đầu”

Table 3-273: Alternative flows of Update Promotion Use case

AT4 At step 6 in the main flows, if start date is smaller than create promotion date

Sub-step Actor Action

6.2 FBS Display a message “Vui lòng chọn ngày lớn hơn hoặc bằng ngày hôm nay”

Table 3-274: Alternative flows of Update Promotion Use case

AT5 At step 7 in the main flows, if end date is not entered

Sub-step Actor Action

7.1 FBS Display a message “Vui lòng chọn ngày kết thúc”

Table 3-275: Alternative flows of Update Promotion Use case

AT6 At step 7 in the main flows, if end date is smaller than create promotion date

Sub-step Actor Action

SWP490_G35 216/303
FBS - Software Requirement Specification v2.0

7.2 FBS Display a message “Vui lòng chọn ngày lớn hơn hoặc bằng ngày hôm nay”

Table 3-276: Alternative flows of Update Promotion Use case

AT7 At step 8 in the main flows, if description is not entered

Sub-step Actor Action

8.1 FBS Display a message “Mô tả không được để trống”

Table 3-277: Alternative flows of Update Promotion Use case

AT8 At step 9 in the main flows, if user clicks “Trở lại” button or Close button

Sub-step Actor Action

10.1 FBS Back to My Restaurant Promotion screen and not save

Table 3-278: Alternative flows of Update Promotion Use case

AT9 At step 11 in the main flows, if user clicks “Trở lại” button or Close button

Sub-step Actor Action

10.1 FBS Back to My Restaurant Update Promotion screen and not save

Table 3-279: Alternative flows of Update Promotion Use case

Business Rules

# Rule Description

Providers have full roles as customers and have additional management functions to
BR14
view, add, edit, delete products, manage orders and manage promotions

BR32 Discount percentage of promotion must enter the positive integer

Table 3-280: Business Rules of Update Promotion Use case

3.5.5.24 UC-52 - Add Restaurant Image

3.5.5.24.1 Screen Design

SWP490_G35 217/303
FBS - Software Requirement Specification v2.0

Figure 3-59: Screen Design of Add Restaurant Image

Table 3-281: Add Restaurant Image Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as User Profile screen)

Menu bar (same as My Restaurant Order screen)

Main

SWP490_G35 218/303
FBS - Software Requirement Specification v2.0

1 Title Ảnh của nhà hàng Label

Button to open popup

2 Thêm ảnh Button to select description
image for restaurant

3 Image Card Card Card display image

4 Delete Icon Button Button to delete

image

5 Description Image Image Description image

6 Image Pagination Hyperlink This hyperlink links to

page of images

Footer (same as footer of Search Restaurant screen)

3.5.5.24.2 Use case Specification

Use Case ID UC-52 Use Case Name Add Restaurant Image

Author TrangTLH Version 1.0 Date 18/07/2021

Actor FBSProvider

This function allows the authorized user to add a description image for the
Description
restaurant

PRE-01: User has been authorized to My Restaurant Image screen

Precondition
PRE-02: User is in My Restaurant Image screen

TRG-01: User has been authorized to My Restaurant Image screen

TRG-02: User is in My Restaurant Image screen
Trigger TRG-03: User clicks “Thêm ảnh” button
TRG-04: User clicks on image that wants to add and clicks“Đồng ý” button in
confirm dialog

POS-01: User will add a new image successfully.

Post-Condition POS-02: The new image has been successfully added to the database and
display on FBS system

Main flows

Step Actor Action

1 User Go to My Restaurant Detail screen and clicks “Ảnh” hyperlink

2 FBS Display My Restaurant Image screen

SWP490_G35 219/303
FBS - Software Requirement Specification v2.0

Click “Thêm ảnh” button to open popup to select description image of

3 User
restaurant

4 FBS Display popup to select file image

5 User Select image and click Open button

6 FBS Display confirm dialog

7 User Click “Đồng ý” button

8 FBS Display new image in My Restaurant Image screen

Table 3-282: Add Restaurant Image Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if user clicks Close button

Sub-step Actor Action

5.1 FBS Close popup and back to My Restaurant Image screen

Table 3-283: Alternative flows of Add Restaurant Image Use case

AT2 At step 7 in the main flows, if user clicks “Quay lại” button

Sub-step Actor Action

7.1 FBS Close confirm dialog and back to My Restaurant Image screen

Table 3-284: Alternative flows of Add Restaurant Image Use case

Business Rules

# Rule Description

BR38 The restaurant must have at least one picture to add in.

Table 3-285: Business Rules of Add Restaurant Image Use case

3.5.5.25 UC-53 - Delete Restaurant Image

3.5.5.25.1 Screen Design

SWP490_G35 220/303
FBS - Software Requirement Specification v2.0

Figure 3-60: Screen Design of Delete Restaurant Image

Table 3-286: Delete Restaurant Image Screen Definition

SWP490_G35 221/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Reference to UC-52

3.5.5.25.2 Use case Specification

Use Case ID UC-52 Use Case Name Delete Restaurant Image

Author TrangTLH Version 1.0 Date 18/07/2021

Actor FBSProvider

This function allows the authorized user to delete a description image of the
Description
restaurant

PRE-01: User has been authorized to My Restaurant Image screen

Precondition
PRE-02: User is in My Restaurant Image screen

TRG-01: User has been authorized to My Restaurant Image screen

TRG-02: User is in My Restaurant Image screen
Trigger
TRG-03: User clicks Delete icon in image that wants to delete and clicks
button “Đồng ý” in confirm dialog

POS-01: User will delete a new image successfully.

Post-Condition POS-02: The new image has been successfully deleted in the database and
not displayed on FBS system

Main flows

Step Actor Action

1 User Go to My Restaurant Image screen

2 FBS Display My Restaurant Image screen

3 User Click Delete icon in image that want to delete

4 FBS Display confirm dialog

5 User Click “Đồng ý” button

6 FBS Not displayed image in My Restaurant Image screen

Table 3-287: Delete Restaurant Image Use case Specification

Alternative flows

SWP490_G35 222/303
FBS - Software Requirement Specification v2.0

AT1 At step 5 in the main flows, if user clicks “Quay lại” button

Sub-step Actor Action

5.1 FBS Close confirm dialog and back to My Restaurant Image screen

Table 3-288: Alternative flows of Delete Restaurant Image Use case

Business Rules

# Rule Description

BR38 The restaurant must have at least 1 picture to add in.

Table 3-289: Business Rules of Delete Restaurant Image Use case

3.5.6 Admin Functions

3.5.6.1 Use Case diagram

SWP490_G35 223/303
FBS - Software Requirement Specification v2.0

Figure 3-61: Admin Functions Use case Diagram

SWP490_G35 224/303
FBS - Software Requirement Specification v2.0

Use Case ID User case Name Description

Allow the authorized user to view the

UC-54 View Dashboard
dashboard in the days.

Allow the authorized user to search

UC-55 Search Order For Admin
orders of the system.

Allow the authorized user to view

UC-56 View Order Information
detailed information about the system.

Allow the authorized user to search

UC-57 Search Restaurant For Admin
restaurants on the system.

Allow the authorized user to view the list

UC-58 View Pending Restaurants
of all pending restaurants of the system.

Allow the authorized user to view the

UC-59 View Detailed Restaurant detailed information restaurant of the
system.

Allow the authorized user to approve a

UC-60 Approve Restaurant
new restaurant.

Allow the authorized user to change the

UC-61 Cancel Restaurant
status of restaurants to cancel.

Allow the authorized user to block the

UC-62 Block Restaurant
reported restaurant.

Allow the authorized user to unblock the

UC-63 Unblock Restaurant
restaurant.

Allow the authorized user to view

UC-64 View Notifications For Admin
notifications.

Allow the authorized user to view the list

UC-65 View All Reports
of all reports of the system.

Allow the authorized user to deactivate

UC-66 Deactivate Item In Restaurant the reported dish, combo, or service of
the restaurants

Allow the authorized user to view all

UC-67 View FBS Wallet
transactions history.

Allow the authorized user to search

UC-68 Search Transaction
transaction history.

Allow the authorized user to search

UC-69 Search Money Processing money processing including recharge
manager, withdrawal management.

SWP490_G35 225/303
FBS - Software Requirement Specification v2.0

Allows the authorized user to confirm

UC-70 Accept Money Processing deposit and withdrawal requests from
customers.

Allows the authorized user to cancel

UC-71 Cancel Money Processing deposit and withdrawal requests from
customers.

Allow authorized users to top up FBS

UC-72 Recharge Processing wallets for customers after receiving
customer’s cash.

Allow the authorized user to search for

UC-73 Search User
users of the system.

Allow the authorized user to view the

UC-74 View User Profile
profile of the user of the system.

Allow the authorized user to block the

UC-75 Block User
violated user.

Allow the authorized user to unblock the

UC-76 Unblock User
user.

Table 3-290: Admin Functions Use case List

SWP490_G35 226/303
FBS - Software Requirement Specification v2.0

3.5.6.2 UC-54 - View Dashboard

3.5.6.2.1 Screen Design

Figure 3-62: Screen Design of View Dashboard

Table 3-291: View Dashboard Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header

Icon Button to view

1 Bell Icon
Button notifications

This hyperlink links to

2 Đăng xuất Hyperlink trigger Sign out
function

Sidebar

SWP490_G35 227/303
FBS - Software Requirement Specification v2.0

1 Feast Booking System Label

2 Trang chủ Hyperlink Link to Admin screen

Link to Admin Order

3 Đơn hàng Hyperlink
screen

Link to Admin Wallet

4 Ví FBS Hyperlink
Information screen

Link to Admin
5 Nhà hàng Hyperlink
Restaurant screen

Link to Admin Report

6 Report Hyperlink
screen

Link to Admin User

7 Người dùng Hyperlink
screen

Main

Total number of
1 Số người dùng Label accounts in the FBS
system

The number of visits

2 Lượt truy cập hôm nay Label to FBS system today at
the current time

Đơn hàng theo thời Chart showing

3 Pie Chart number of orders by
gian
search date

4 Order Status Label Status of order

The system's revenue

5 Doanh thu trong tháng Label this month at the
current time

Date Find the number of

6 Từ
Picker orders from what date

Date Find the number of

7 Đến
Picker orders to what date

Tổng số nhà hàng trong Column Total number of

8 restaurants in the FBS
hệ thống Chart
system

9 Restaurant Status Label Status of restaurant

SWP490_G35 228/303
FBS - Software Requirement Specification v2.0

3.5.6.2.2 Use case Specification

Use Case ID UC-54 Use Case Name View Dashboard

Author TrangTLH Version 1.0 Date 17/07/2021

Actor FBSAdmin

Description This function allows the authorized user to view the dashboard in the days

PRE-01: User has been authorized to Admin screen

Precondition
PRE-02: User is in Admin screen

TRG-01: User has been authorized to Admin screen

Trigger TRG-02: User is in Admin screen
TRG-03: User views dashboard of FBS system

Post-Condition POS-01: User will view dashboard

Main flows

Step Actor Action

1 User Sign in FBS system with admin role

2 FBS Validate phone number, password and display Admin screen

3 User View dashboard

Table 3-292: View Dashboard Use case Specification

Business Rules

# Rule Description

Admin has permission to views orders, revenue of system, accounts, and restaurants of
BR16
system

Table 3-293: Business Rules of View Dashboard Use case

3.5.6.3 UC-55 - Search Order For Admin

3.5.6.3.1 Screen Design

SWP490_G35 229/303
FBS - Software Requirement Specification v2.0

Figure 3-63: Screen Design of Search Order For Admin

Table 3-294: Search Order For Admin Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as sidebar of Admin screen)

Main

1 Nhập mã đơn hàng Textbox Enter order coder to

search

Date Find the number of

2 Từ
Picker orders from what date

SWP490_G35 230/303
FBS - Software Requirement Specification v2.0

Date Find the number of

3 Đến
Picker orders to what date

Combo
4 Order Status Select status of orders
box

5 Search Button Button Button to trigger

Search function

6 Order Table Table Table contains order

information

7 Mã đơn Label Code of order

8 Ngày đặt Label Order date

9 Tổng tiền Label Total amount of order

10 Trạng thái Label Status of order

11 Chi tiết Button Link to Admin Order

Detail screen

12 Order Pagination Hyperlink This hyperlink links to

page of orders

3.5.6.3.2 Use case Specification

Use Case ID UC-55 Use Case Name Search Order For Admin

Author TrangTLH Version 1.0 Date 17/07/2021

Actor FBSAdmin

Description The function allows the authorized user to search the order of the system

PRE-01: User has been authorized to Admin screen

Precondition
PRE-02: User is in Admin screen

TRG-01: User has been authorized to Admin screen

TRG-02: User is in Admin screen
Trigger TRG-03: User clicks “Đơn hàng” hyperlink on sidebar
TRG-04: User enters order code or selects from date to date or selects status
of orders and clicks Search button

POS-02: Query in database with entered information

Post-Condition
POS-01: User views list of orders that want to view successfully

SWP490_G35 231/303
FBS - Software Requirement Specification v2.0

Main flows

Step Actor Action

1 User Go to Admin screen

2 FBS Display Admin screen

3 User Click “Đơn hàng” hyperlink on sidebar

4 User Enter order code or select from date to date or select status of orders

5 User Click Search button

6 FBS Display list of orders in Admin Order screen

7 FBS View list of orders

Table 3-295: Search Order For Admin Use case Specification

Business Rules

# Rule Description

Admin has permission to views orders, revenue of system, accounts, and restaurants of
BR16
system

Table 3-296: Business Rules of Search Order For Admin Use case

3.5.6.4 UC-56 - View Order Information

3.5.6.4.1 Screen Design

SWP490_G35 232/303
FBS - Software Requirement Specification v2.0

Figure 3-64: Screen Design of View Order Information

Table 3-297: View Order Information Screen Definition

Max
# Field Name Type Mandatory Description
Length

Main

1 Title Thông tin đơn hàng Label

2 Nhà hàng Label Name of restaurant

3 Địa chỉ Label Specific address of

restaurant

4 Số điện thoại Label Phone number of

restaurant

SWP490_G35 233/303
FBS - Software Requirement Specification v2.0

5 Loại hình Label Type of restaurant

6 Mã số đơn đặt Label Order code

7 Ngày đặt Label Order date

8 Ngày diễn ra Label Feast session and date

9 Loại hình Label Type of organization

10 Tình trạng Label Status of order

11 Tên khách hàng Label Name of customer

12 Email Label Email of customer

13 Số điện thoại Label Phone number to

contact of customer

14 Số lượng khách Label Number of guests

15 Loại bàn Label Type of table

16 Ghi chú Label Note for restaurant

Include name, sale

17 Table Items Table price, quantity of
selected items

Total amount of each

18 Tổng Label type: Menu, Combo,
Service

19 Tổng tiền cần thanh toán Label Total amount of order

Chương trình khuyến

20 Label Name of promotion
mãi

21 Tiền đặt cọc Label Deposits of order

22 Trở lại Button Button to back to

Admin Order screen

23 Close Button Button to back to

Admin Order screen

3.5.6.5.2 Use case Specification

SWP490_G35 234/303
FBS - Software Requirement Specification v2.0

Use Case ID UC-56 Use Case Name View Order Information

Author TrangTLH Version 1.0 Date 17/07/2021

Actor FBSAdmin

This function allows the authorized user to view detailed information about
Description
the system

PRE-01: User has been authorized to Admin Order screen

Precondition
PRE-02: User is in Admin Order screen

TRG-01: User has been authorized to Admin screen

Trigger TRG-02: User is in Admin screen
TRG-03: User clicks “Chi tiết” button at the order that wants to view

Post-Condition POS-01: User will view detailed information of the order successfully

Main flows

Step Actor Action

1 User Go to Admin Order screen

2 FBS Display Admin Order screen

3 User Click “Chi tiết” button at the order that want to view

4 FBS Display Admin Order Detail screen

5 User View detailed information of the order

Table 3-298: View Order Information Use case Specification

Business Rules

# Rule Description

Admin has permission to views orders, revenue of system, accounts, and restaurants of
BR16
system

Table 3-299: Business Rules of View Order Information Use case

3.5.6.5 UC-57 - Search Restaurant For Admin

3.5.6.5.1 Screen Design

SWP490_G35 235/303
FBS - Software Requirement Specification v2.0

Figure 3-65: Screen Design of Search Restaurant For Admin

Table 3-300: Search Restaurant For Admin Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as sidebar of Admin screen)

Menu bar

Link to Admin List

1 Tất cả nhà hàng Hyperlink
Restaurants screen

Nhà hàng đang chờ Link to Admin New

2 Hyperlink
duyệt Restaurants screen

Main

SWP490_G35 236/303
FBS - Software Requirement Specification v2.0

1 Nhập tên nhà hàng Textbox Enter keywords name

to search

2 Restaurant Status Combo box Status of Restaurant

3 Search Button Button Button to trigger

Search function

Table contains
4 Restaurant Table Table restaurant
information

5 Tên nhà hàng Label Name of restaurant

6 Loại hình Label Type of restaurant

7 Địa chỉ Label Province of restaurant

8 Trạng thái Label Status of restaurant

Link to Admin
9 Chi tiết Button Restaurant Detail
screen

10 Chặn Button Button to block

restaurant

11 Bỏ chặn Button Button to unblock

restaurant

12 Restaurant Pagination Hyperlink This hyperlink links to

page of restaurants

3.5.6.5.2 Use case Specification

Use Case ID UC-57 Use Case Name Search Restaurant For Admin

Author TrangTLH Version 1.0 Date 20/07/2021

Actor FBSAdmin

Description The function allows the authorized user to search restaurants on the system.

PRE-01: User has been authorized to Admin screen

Precondition
PRE-02: User is in Admin screen

TRG-01: User has been authorized to Admin screen

Trigger
TRG-02: User is in Admin screen

SWP490_G35 237/303
FBS - Software Requirement Specification v2.0

TRG-03: User clicks “Nhà hàng” hyperlink on sidebar and clicks “Tất cả nhà
hàng” hyperlink in menu bar
TRG-04: User enters keyword name or selects status of restaurant and clicks
Search button

POS-01: Query in database with entered information

Post-Condition
POS-02: User views list of restaurants successfully

Main flows

Step Actor Action

1 User Go to Admin screen

2 FBS Display Admin screen

3 User Click “Nhà hàng” hyperlink on sidebar

4 FBS Display Admin Pending Restaurant screen

5 User Click “Tất cả nhà hàng” hyperlink in menubar

6 FBS Display Admin List Restaurant screen

7 User Enter keyword name or selects status of restaurant

8 User Click Search button

9 FBS Display list of restaurants in Admin List Restaurant screen

10 User View list of restaurants

Table 3-301: Search Restaurant For Admin Use case Specification

Business Rules

# Rule Description

Admin has permission to views orders, revenue of system, accounts, and restaurants of
BR16
system

Table 3-302: Business Rules of Search Restaurant For Admin Use case

SWP490_G35 238/303
FBS - Software Requirement Specification v2.0

3.5.6.6 UC-58 - View Pending Restaurants

3.5.6.6.1 Screen Design

Figure 3-66: Screen Design of View Pending Restaurants

Table 3-303: View Pending Restaurants Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as sidebar of Admin screen)

Menu bar (same as menu bar of Admin List Restaurant screen)

Main

1 Restaurant Table Table Table contains

restaurant information

2 Tên nhà hàng Label Name of the restaurant

SWP490_G35 239/303
FBS - Software Requirement Specification v2.0

3 Loại hình Label Type of the restaurant

4 Địa chỉ Label Province of the

restaurant

Link to Admin
5 Chi tiết Button Restaurant Detail
screen

6 Duyệt Button Button to approve the

restaurant

7 Hủy Button Button to cancel the

restaurant

8 Restaurant Pagination Hyperlink This hyperlink links to

page of restaurants

3.5.6.7.2 Use case Specification

Use Case ID UC-58 Use Case Name View Pending Restaurants

Author TrangTLH Version 1.0 Date 20/07/2021

Actor FBSAdmin

The function allows the authorized user to view the list of all pending
Description
restaurants of the system.

PRE-01: User has been authorized to Admin screen

Precondition
PRE-02: User is in Admin screen

TRG-01: User has been authorized to Admin screen

Trigger TRG-02: User is in Admin screen
TRG-03: User clicks “Nhà hàng” hyperlink on sidebar

POS-01: User views list of restaurants waiting to be approved of FBS system

Post-Condition
successfully

Main flows

Step Actor Action

1 User Click “Nhà hàng” hyperlink on sidebar

4 FBS Display Admin Pending Restaurant screen

5 User View list of restaurants waiting to be approved of FBS system

Table 3-304: View Pending Restaurants Use case Specification

SWP490_G35 240/303
FBS - Software Requirement Specification v2.0

Business Rules

# Rule Description

Admin has permission to views orders, revenue of system, accounts, and restaurants of
BR16
system

Table 3-305: Business Rules of View Pending Restaurants Use case

3.5.6.7 UC-59 - View Detail Restaurant

3.5.6.7.1 Screen Design

Figure 3-67: Screen Design of View Detail Restaurant

Table 3-306: View Detail Restaurant Screen Definition

SWP490_G35 241/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as sidebar of Admin screen)

Menu bar

Link to Admin
1 Thông tin Hyperlink Restaurant
Information screen

Link to Admin
2 Ảnh Hyperlink Restaurant Image
screen

Link to Admin
3 Thực đơn Hyperlink Restaurant Menu
screen

Link to Admin
4 Combo món ăn Hyperlink Restaurant Combo
screen

Link to Admin
5 Dịch vụ Hyperlink Restaurant Service
screen

Main

1 Restaurant Image Image Avatar of restaurant

Images of food
Giấy chứng nhận vệ
hygiene and safety for
2 sinh an toàn thực Image
catering of the
phẩm
restaurant

3 Tên nhà hàng Label Name of restaurant

4 Loại hình Label Type of restaurant

5 Mô tả Label Detailed description

about restaurant

6 Tỉnh/Thành phố Label Province/City of

restaurant

7 Quận/Huyện Label District of restaurant

8 Địa chỉ Label Specific address of

restaurant

SWP490_G35 242/303
FBS - Software Requirement Specification v2.0

9 Số điện thoại Label Phone number to

contact of restaurant

The number of guests

10 Sức chứa Label the restaurant can
accommodate

The business license

Mã giấy phép kinh
11 Label number of the
doanh
restaurant

12 Trạng thái hoạt động Label Status of restaurant

3.5.6.7.2 Use case Specification

Use Case ID UC-59 Use Case Name View Detail Restaurant

Author TrangTLH Version 1.0 Date 20/07/2021

Actor FBSAdmin

This function allows the authorized user to view the detailed information
Description
restaurant of the system

PRE-01: User has been authorized to Admin List Restaurants or Admin

Pending Restaurants screen
Precondition
PRE-02: User is in Admin List Restaurants or Admin Pending Restaurants
screen

TRG-01: User has been authorized to Admin List Restaurants or Admin

Pending Restaurants screen
Trigger TRG-02: User is in Admin List Restaurants or Admin Pending Restaurants
screen
TRG-03: User clicks “Chi tiết” button at the restaurant that wants to view

Post-Condition POS-01: User views detailed information of restaurant successfully

Main flows

Step Actor Action

1 User Go to Admin List Restaurants or Admin Pending Restaurants screen

2 FBS Display Admin List Restaurants/Admin Pending Restaurants screen

3 User Click “Chi tiết” button at the restaurant that want to view

4 FBS Display Admin Restaurant Information screen

SWP490_G35 243/303
FBS - Software Requirement Specification v2.0

5 User View detailed information of restaurant

Table 3-307: View Detail Restaurant Use case Specification

Business Rules

# Rule Description

Admin has permission to views orders, revenue of system, accounts, and restaurants of
BR16
system

Table 3-308: Business Rules of View Detail Restaurant Use case

3.5.6.8 UC-60 - Approve Restaurant

3.5.6.8.1 Screen Design

SWP490_G35 244/303
FBS - Software Requirement Specification v2.0

Figure 3-68: Screen Design of Approve Restaurant

Figure 3-69: Screen Design of Confirm Dialog

Table 3-309: Approve Restaurant Screen Definition

SWP490_G35 245/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as sidebar of Admin screen)

Menu bar (described at UC-55)

Main (described at UC-56)

Confirm Dialog

1 Title Thông báo Label

Bạn có muốn lưu thay

2 Label Message
đổi không

3 Lưu Button Button to save change

4 Trở lại Button Button to close

confirm dialog

5 Close Button Button to close

confirm dialog

3.5.6.8.2 Use case Specification

Use Case ID UC-60 Use Case Name Approve Restaurant

Author TrangTLH Version 1.0 Date 20/07/2021

Actor FBSAdmin

Description This function allows the authorized user to approve a new restaurant

PRE-01: User has been authorized to Admin Pending Restaurant screen

Precondition
PRE-02: User is in Admin Pending Restaurant screen

TRG-01: User has been authorized to Admin Pending Restaurant screen

Trigger TRG-02: User is in Admin Pending Restaurant screen
TRG-03: User clicks “Duyệt” button at the restaurant that wants to approve

POS-01: Status of restaurant in database will change to Active

Post-Condition
POS-02: The restaurant will be displayed on the system for user to view

Main flows

Step Actor Action

1 User Go to Admin Pending Restaurants screen

SWP490_G35 246/303
FBS - Software Requirement Specification v2.0

2 FBS Display Admin Pending Restaurants screen

3 User Click “Duyệt” button

4 FBS Display Confirm dialog

5 User Click “Lưu” button

Approve restaurant, notify for provider and display new restaurant on the
6 FBS
system

Table 3-310: Approve Restaurant Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if user clicks “Trở lại” or Close button

Sub-step Actor Action

5.1 FBS Back to Admin Pending Restaurants screen and not save change

Table 3-311: Alternative flows of Approve Restaurant Use case

3.5.6.9 UC-61 - Cancel Restaurant

3.5.6.9.1 Screen Design

SWP490_G35 247/303
FBS - Software Requirement Specification v2.0

Figure 3-70: Screen Design of Cancel Restaurant

Figure 3-71: Screen Design of Confirm Dialog

Table 3-312: Cancel Restaurant Screen Definition

SWP490_G35 248/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as sidebar of Admin screen)

Menu bar (described at UC-55)

Main (described at UC-56)

Confirm Dialog (same as confirm dialog of Approve Restaurant screen)

3.5.6.9.2 Use case Specification

Use Case ID UC-61 Use Case Name Cancel Restaurant

Author TrangTLH Version 1.0 Date 20/07/2021

Actor FBSAdmin

This function allows the authorized user to change the status of restaurants
Description
to cancel

PRE-01: User has been authorized to Admin Pending Restaurant screen

Precondition
PRE-02: User is in Admin Pending Restaurant screen

TRG-01: User has been authorized to Admin Pending Restaurant screen

Trigger TRG-02: User is in Admin Pending Restaurant screen
TRG-03: User clicks “Hủy” button at the restaurant that wants to cancel

Post-Condition POS-01: Status of restaurant in database will change to Cancel

Main flows

Step Actor Action

1 User Go to Admin Pending Restaurants screen

2 FBS Display Admin Pending Restaurants screen

3 User Click “Hủy” button

4 FBS Display Confirm dialog

5 User Click “Lưu” button

6 FBS Cancel restaurant and notify for provider

Table 3-313: Cancel Restaurant Use case Specification

SWP490_G35 249/303
FBS - Software Requirement Specification v2.0

Alternative flows

AT1 At step 5 in the main flows, if user clicks “Trở lại” or Close button

Sub-step Actor Action

5.1 FBS Back to Admin Pending Restaurants screen and not save change

Table 3-314: Alternative flows of Cancel Restaurant Use case

3.5.6.10 UC-62 - Block Restaurant

3.5.6.10.1 Screen Design

Figure 3-72: Screen Design of Block Restaurant

SWP490_G35 250/303
FBS - Software Requirement Specification v2.0

Figure 3-73: Screen Design of Confirm Dialog

Table 3-315: Block Restaurant Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as sidebar of Admin screen)

Menu bar (described at UC-55)

Main (described at UC-55)

Confirm Dialog

1 Title Thông báo Label

Bạn có muốn lưu thay

2 Label Message
đổi không

3 Lưu Button Button to save change

4 Trở lại Button Button to close

confirm dialog

5 Close Button Button to close

confirm dialog

3.5.6.10.2 Use case Specification

Use Case ID UC-62 Use Case Name Block Restaurant

Author TrangTLH Version 1.0 Date 20/07/2021

Actor FBSAdmin

Description This function allows the authorized user to block the reported restaurant

SWP490_G35 251/303
FBS - Software Requirement Specification v2.0

PRE-01: User has been authorized to Admin List Restaurant screen

Precondition
PRE-02: User is in Admin List Restaurant screen

TRG-01: User has been authorized to Admin List Restaurant screen

Trigger TRG-02: User is in Admin List Restaurant screen
TRG-03: User clicks “Chặn” button at the restaurant that wants to block

POS-01: Status of restaurant in database will change to Banned

Post-Condition
POS-02: The restaurant will be hidden on the system for user

Main flows

Step Actor Action

1 User Go to Admin List Restaurants screen

2 FBS Display Admin List Restaurants screen

3 User Click “Chặn” button

4 FBS Display Confirm dialog

5 User Click “Lưu” button

6 FBS Block restaurant, notify for provider, and hide restaurant on the system

Table 3-316: Block Restaurant Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if user clicks “Trở lại” or Close button

Sub-step Actor Action

5.1 FBS Back to Admin List Restaurants screen and not save change

Table 3-317: Alternative flows of Block Restaurant Use case

SWP490_G35 252/303
FBS - Software Requirement Specification v2.0

3.5.6.11 UC-63 - Unblock Restaurant

3.5.6.11.1 Screen Design

Figure 3-73: Screen Design of Unblock Restaurant

Figure 3-75: Screen Design of Confirm Dialog

SWP490_G35 253/303
FBS - Software Requirement Specification v2.0

Table 3-318: Unblock Restaurant Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as sidebar of Admin screen)

Menu bar (described at UC-55)

Main (described at UC-55)

Confirm Dialog

1 Title Thông báo Label

Bạn có muốn lưu thay

2 Label Message
đổi không

3 Lưu Button Button to save change

4 Trở lại Button Button to close

confirm dialog

5 Close Button Button to close

confirm dialog

3.5.6.11.2 Use case Specification

Use Case ID UC-63 Use Case Name Unblock Restaurant

Author TrangTLH Version 1.0 Date 20/07/2021

Actor FBSAdmin

Description This function allows the authorized user to unblock the reported restaurant

PRE-01: User has been authorized to Admin List Restaurant screen

Precondition
PRE-02: User is in Admin List Restaurant screen

TRG-01: User has been authorized to Admin List Restaurant screen

Trigger TRG-02: User is in Admin List Restaurant screen
TRG-01: User clicks “Bỏ chặn” button at the restaurant that wants to unblock

POS-01: Status of restaurant in database will change to Active

Post-Condition
POS-02: The restaurant will be displayed on the system for user

Main flows

Step Actor Action

SWP490_G35 254/303
FBS - Software Requirement Specification v2.0

1 User Go to Admin List Restaurants screen

2 FBS Display Admin List Restaurants screen

3 User Click “Bỏ chặn” button

4 FBS Display Confirm dialog

5 User Click “Lưu” button

Unblock restaurant, notify for provider, and display restaurant again on the
6 FBS
system

Table 3-319: Unblock Restaurant Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if user clicks “Trở lại” or Close button

Sub-step Actor Action

5.1 FBS Back to Admin List Restaurants screen and not save change

Table 3-320: Alternative flows of Unblock Restaurant Use case

3.5.6.12 UC-64 - View Notifications For Admin

3.5.6.12.1 Screen Design

Figure 3-76: Screen Design of View Notifications For Admin

Table 3-321: View Notifications For Admin Screen Definition

SWP490_G35 255/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Notification

1 Title Thông báo Label

Notification
2 Notifications List List of notification
list

3 Notification Content Hyperlink Yes Content of

notification

3.5.6.12.2 Use case Specification

Use Case ID UC-64 Use Case Name View Notifications For Admin

Author TrangTLH Version 1.0 Date 18/07/2021

Actor FBSAdmin

Description This function allows the authorized user to view notifications

PRE-01: User has been authorized to Admin screen

Precondition
PRE-02: User is in Admin screen

TRG-01: User has been authorized to Admin screen

Trigger TRG-02: User is in Admin screen
TRG-03: User clicks Bell icon link to view notification

Post-Condition POS-01: User view all notifications

Main flows

Step Actor Action

1 User Click the bell icon in header

2 FBS Display Admin Notification

3 User View all notifications

Table 3-322: View Notifications For Admin Use case Specification

Alternative flows

SWP490_G35 256/303
FBS - Software Requirement Specification v2.0

AT1 At step 2 in the main flows, if user does not have a notification

Sub-step Actor Action

2.1 FBS Notification displays “Không có thông báo nào”

Table 3-323: Alternative flows of View Notifications For Admin Use case

3.5.6.13 UC-65 - View All Reports

3.5.6.13.1 Screen Design

Figure 3-77: Screen Design of View All Reports

Table 3-324: View All Reports Screen Definition

SWP490_G35 257/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as sidebar of Admin screen)

Main

Title Danh sách báo

1 Label
cáo

2 Reports Table Table Display information of

report

3 Nội dung Label Content of report

4 Thời gian Label The time the report

was created

Button to redirect to
5 Đi đến nhà hàng Button the restaurant was
reported

6 Xong Button Button to check that

report was resolved

7 Reports Pagination Hyperlink This hyperlink links to

page of reports

3.5.6.13.2 Use case Specification

Use Case ID UC-65 Use Case Name View All Reports

Author TrangTLH Version 1.0 Date 18/07/2021

Actor FBSAdmin

This function allows the authorized user to view the list of all reports of the
Description
system

PRE-01: User has been authorized to Admin screen

Precondition
PRE-02: User is in Admin screen

TRG-01: User has been authorized to Admin screen

Trigger TRG-02: User is in Admin screen
TRG-03: User clicks “Báo cáo” hyperlink in sidebar

Post-Condition POS-01: User view all reports successfully

SWP490_G35 258/303
FBS - Software Requirement Specification v2.0

Main flows

Step Actor Action

1 User Go to Admin screen

2 FBS Display Admin screen

3 User Click “Báo cáo” hyperlink in sidebar

4 FBS Display Admin Report screen

Table 3-325: View All Reports Use case Specification

3.5.6.14 UC-66 - Deactivate Item In Restaurant

3.5.6.14.1 Screen Design

Figure 3-78: Screen Design of Deactivate Item In Restaurant

SWP490_G35 259/303
FBS - Software Requirement Specification v2.0

Figure 3-79: Screen Design of Item Detail

Table 3-326: Deactivate Item In Restaurant Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as Admin screen)

Menu bar

Link to Admin
1 Thông tin Hyperlink Restaurant
Information screen

Link to Admin
2 Ảnh Hyperlink Restaurant Image
screen

Link to Admin
3 Thực đơn Hyperlink Restaurant Menu
screen

Link to Admin
4 Combo món ăn Hyperlink Restaurant Combo
screen

Link to Admin
5 Dịch vụ Hyperlink Restaurant Service
screen

Main

SWP490_G35 260/303
FBS - Software Requirement Specification v2.0

1 Title Danh sách món ăn Label

2 Dishes Table Table Display information of

dishes

3 Tên món ăn Label Name of dish

4 Loại Label Dish category

5 Giá bán Label Sale price of dish

6 Trạng thái Label Status of dish

7 Xem thêm Button Button to view detail

of dish

8 Dishes Pagination Hyperlink This hyperlink links to

page of dishes

Admin Restaurant Menu Detail

1 Title Chi tiết món ăn Label

2 Dish Image Image Avatar of dish

3 Tên món ăn Label Name of dish

4 Loại món ăn Label Category of dish

5 Trạng thái Label Status of dish

6 Giá món ăn Label Sale price of dish

7 Mô tả Label Description of dish

8 Gỡ Button Button to trigger Block

item function

Button to back to
9 Trở lại Button Admin Restaurant
Menu screen

SWP490_G35 261/303
FBS - Software Requirement Specification v2.0

Button to back to
10 Close Button Admin Restaurant
Menu screen

3.5.6.14.2 Use case Specification

Use Case ID UC-66 Use Case Name Deactivate Item In Restaurant

Author TrangTLH Version 1.0 Date 21/07/2021

Actor FBSAdmin

The function allows the authorized user to deactivate the dish, combo, or
Description
service of the restaurants that are reported or violate the terms of the system

PRE-01: User has been authorized to Admin Restaurant Information screen

Precondition
PRE-02: User is in Admin Restaurant Information screen

TRG-01: User has been authorized to Admin Restaurant Information screen

TRG-02: User is in Admin Restaurant Information screen
Trigger TRG-03: User clicks “Thực đơn”/ “Combo món ăn”/ “Dịch vụ” in sidebar
TRG-04: User clicks “Xem thêm” button at the item that wants to deactivate
TRG-05: User clicks “Gỡ” button

POS-01: Status of item in database will change to Banned

Post-Condition POS-02: The item will be hidden on the system for user and provider will
receive a notification

Main flows

Step Actor Action

1 User Go to Admin Restaurant Information screen

2 FBS Display Admin Restaurant Information screen

3 User Click “Thực đơn”/ “Combo món ăn”/ “Dịch vụ” hyperlink in sidebar

Display Admin Restaurant Menu/ Admin Restaurant Combo / Admin

4 FBS
Restaurant Service screen

5 User Click “Xem thêm” button on item that want to deactivate

Display Admin Restaurant Menu Detail/ Admin Restaurant Combo Detail/

6 FBS
Admin Restaurant Service Detail popup

7 User Click “Gỡ” button

SWP490_G35 262/303
FBS - Software Requirement Specification v2.0

8 FBS Display confirm dialog

9 User Click “Đồng ý” button to deactivate item

10 FBS Deactivate item, hide this in system and send a notification to provider

Table 3-327: Deactivate Item In Restaurant Use case Specification

Alternative flows

AT1 At step 9 in the main flows, if user clicks “Trở lại” or Close button

Sub-step Actor Action

Back to Admin Restaurant Menu/ Admin Restaurant Combo / Admin

9.1 FBS
Restaurant Service screen and not save change

Table 3-328: Alternative flows of Deactivate Item In Restaurant Use case

3.5.6.15 UC-67 - View FBS Wallet

3.5.6.15.1 Screen Design

SWP490_G35 263/303
FBS - Software Requirement Specification v2.0

Figure 3-80: Screen Design of View FBS Wallet

Table 3-329: View FBS Wallet Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as sidebar of Admin screen)

Menu bar

1 Lịch sử giao dịch Hyperlink Link to Admin Wallet

Information

2 Quản lý nạp tiền Hyperlink Link to Admin Pay In

screen

SWP490_G35 264/303
FBS - Software Requirement Specification v2.0

3 Quản lý rút tiền Hyperlink Link to Admin

Withdraw screen

Main

1 Tổng số dư Label Current balance

2 Title Lịch sử giao dịch Label

3 Nhập mã giao dịch Text Enter transaction code

to search

Date Search transaction

4 Từ
picker history from what date

Date Search transaction

5 Đến
picker history to what date

6 Search Icon Button Button to trigger

Search function

Filter transaction by
status of transactions
Value: Tất cả - All,
7 Trạng thái Hyperlink Thành công –
Successful, Đang xử lý
– Processing, Thất bại –
Failure

8 Transaction Table Table Display transaction

information

9 Mã giao dịch Label Transaction code

10 Thời gian Label Transaction date

11 Loại Label Type of transaction

12 Số tiền (VNĐ) Label Transaction amount

13 Ghi chú Label Note of transaction

14 Trạng thái Label Status of transaction

15 Transaction Pagination Hyperlink This hyperlink links to

page of transactions

3.5.6.15.2 Use case Specification

SWP490_G35 265/303
FBS - Software Requirement Specification v2.0

Use Case ID UC-67 Use Case Name View FBS Wallet

Author TrangTLH Version 1.0 Date 21/07/2021

Actor FBSAdmin

This function allows the authorized user to view all transactions history of the
Description
system

PRE-01: User has been authorized to Admin screen

Precondition
PRE-02: User is in Admin screen

TRG-01: User has been authorized to Admin screen

Trigger TRG-02: User is in Admin screen
TRG-03: User clicks “Ví FBS” at the sidebar

Post-Condition POS-01: Users will view transaction history successfully

Main flows

Step Actor Action

1 User Go to Admin screen

2 FBS Display Admin screen

3 User Click “Ví FBS” hyperlink at the sidebar

4 FBS Display Admin Wallet Information screen

5 User View transaction history

Table 3-330: View FBS Wallet Use case Specification

Business Rules

# Rule Description

Admin has permission to views orders, revenue of system, accounts, and restaurants of
BR16
system

Table 3-331: Business Rules of View FBS Wallet Use case

3.5.6.16 UC-68 - Search Transaction

3.5.6.16.1 Screen Design

SWP490_G35 266/303
FBS - Software Requirement Specification v2.0

Figure 3-81: Screen Design of Search Transaction

Table 3-332: Search Transaction Screen Definition

Max
# Field Name Type Mandatory Description
Length

Reference to UC-67

3.5.6.16.2 Use case Specification

Use Case ID UC-68 Use Case Name Search Transaction

Author TrangTLH Version 1.0 Date 21/07/2021

SWP490_G35 267/303
FBS - Software Requirement Specification v2.0

Actor FBSAdmin

This function allows the authorized user to search transactions history of the
Description
system

PRE-01: User has been authorized to Admin Wallet Information screen

Precondition
PRE-02: User is in Admin Wallet Information screen

TRG-01: User has been authorized to Admin Wallet Information screen

Trigger TRG-02: User is in Admin Wallet Information screen
TRG-03: User enters information and clicks Search button

POS-01: Query in database with entered information

Post-Condition
POS-02: User views list of transactions successfully

Main flows

Step Actor Action

1 User Go to Admin Wallet Information screen

2 FBS Display Admin Wallet Information screen

3 User Enter transaction code or select date or select transaction status

4 User Click Search button

5 FBS Display list of transactions in Admin Wallet Information screen

6 User View list of transactions

Table 3-333: Search Transaction Use case Specification

Business Rules

# Rule Description

Admin has permission to views orders, revenue of system, accounts, and restaurants of
BR16
system

Table 3-334: Business Rules of Search Transaction Use case

3.5.6.17 UC-69 - Search Money Processing

3.5.6.17.1 Screen Design

SWP490_G35 268/303
FBS - Software Requirement Specification v2.0

Figure 3-82 Screen Design of Search Money Processing

Table 3-335: Search Money Processing Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as sidebar of Admin screen)

Menu bar (same as menu bar of View FBS Wallet screen)

Main

1 Title Quản lý nạp tiền Label

SWP490_G35 269/303
FBS - Software Requirement Specification v2.0

Enter transaction code

2 Nhập mã giao dịch Text
to search

Date Search transaction

3 Từ
picker history from what date

Date Search transaction

4 Đến
picker history to what date

Button to trigger
5 Search Icon Button
Search function

Button to open
6 Xử lý nạp tiền Button Recharge Processing
screen

Display transaction
7 Transaction Table Table
information

8 Mã giao dịch Label Transaction code

9 Thời gian Label Transaction date

10 Loại Label Type of transaction

11 Số tiền (VNĐ) Label Transaction amount

12 Ghi chú Label Note of transaction

13 Trạng thái Label Status of transaction

Button to accept
14 Xác nhận Label money processing
request

Button to cancel
15 Hủy Label money processing
request

This hyperlink links to

16 Transaction Pagination Hyperlink
page of transactions

3.5.6.17.2 Use case Specification

Use Case ID UC-69 Use Case Name Search Money Processing

Author TrangTLH Version 1.0 Date 21/07/2021

Actor FBSAdmin

This function allows the authorized user to search money processing, include:
Description
recharge manager, withdrawal management

SWP490_G35 270/303
FBS - Software Requirement Specification v2.0

PRE-01: User has been authorized to Admin Pay In Information/ Admin

Withdrawal Information screen
Precondition
PRE-02: User is in Admin Pay In Information/ Admin Withdrawal Information
screen

TRG-01: User has been authorized to Admin Pay In Information/ Admin

Withdrawal Information screen
Trigger TRG-02: User is in Admin Pay In Information/ Admin Withdrawal Information
screen
TRG-03: User enters information and clicks Search button

POS-01: Query in database with entered information

Post-Condition
POS-02: User views list of transactions successfully

Main flows

Step Actor Action

1 User Go to Admin Pay In Information/ Admin Withdrawal Information screen

2 FBS Display Admin Wallet Information/ Admin Withdrawal Information screen

3 User Enter transaction code or select date

4 User Click Search button

Display list of transactions in Admin Pay In Information/ Admin Withdrawal

5 FBS
Information screen

6 User View list of transactions

Table 3-336: Search Money Processing Use case Specification

Business Rules

# Rule Description

Admin has permission to views orders, revenue of system, accounts, and restaurants of
BR16
system

Table 3-337: Business Rules of Search Money Processing Use case

3.5.6.18 UC-70 - Accept Money Processing

3.5.6.18.1 Screen Design
Reference to UC-69

SWP490_G35 271/303
FBS - Software Requirement Specification v2.0

3.5.6.18.2 Use case Specification

Use Case ID UC-70 Use Case Name Accept Money Processing

Author TrangTLH Version 1.0 Date 21/07/2021

Actor FBSAdmin

This function allows to confirmation deposit and withdrawal requests from

Description
customers

PRE-01: User has been authorized to Admin Pay In Information/ Admin

Withdrawal Information screen
Precondition
PRE-02: User is in Admin Pay In Information/ Admin Withdrawal Information
screen

TRG-01: User has been authorized to Admin Pay In Information/ Admin

Withdrawal Information screen
Trigger TRG-02: User is in Admin Pay In Information/ Admin Withdrawal Information
screen
TRG-03: User clicks “Xác nhận” button at the transaction that wants to accept

POS-01: The request will be fulfilled, the funds will be added to the
Post-Condition customer's wallet or withdrawn from the customer's wallet
POS-02: Transaction will be removed from the Transaction table in screen

Main flows

Step Actor Action

1 User Go to Admin Pay In Information/ Admin Withdrawal Information screen

2 FBS Display Admin Wallet Information/ Admin Withdrawal Information screen

3 User Click “Xác nhận” button at the transaction that want to accept

4 FBS Display Confirm dialog

5 User Click “Đồng ý” button

Display dialog, complete request, deposit or withdraw money for customer,

6 FBS
send notification to customer and hide request from screen

Table 3-338: Accept Money Processing Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if user clicks “Trở lại” or Close button

Sub-step Actor Action

SWP490_G35 272/303
FBS - Software Requirement Specification v2.0

Back to Admin Wallet Information/ Admin Withdrawal Information screen

5.1 FBS
and not save change

Table 3-339: Alternative flows of Accept Money Processing Use case

Business Rules

# Rule Description

When a customer makes a deposit request, the admin must accept it before the money
BR49
is transferred to the FBS wallet

When a customer makes a withdrawal request, the admin must accept it before the
BR50
customer can receive the money

Table 3-340: Business Rules of Accept Money Processing Use case

3.5.6.19 UC-71 - Cancel Money Processing

3.5.6.19.1 Screen Design
Reference to UC-79

3.5.6.19.2 Use case Specification

Use Case ID UC-71 Use Case Name Cancel Money Processing

Author TrangTLH Version 1.0 Date 21/07/2021

Actor FBSAdmin

This function allows canceling deposit and withdrawal requests from

Description
customers

PRE-01: User has been authorized to Admin Pay In Information/ Admin

Withdrawal Information screen
Precondition
PRE-02: User is in Admin Pay In Information/ Admin Withdrawal Information
screen

TRG-01: User has been authorized to Admin Pay In Information/ Admin

Withdrawal Information screen
Trigger TRG-02: User is in Admin Pay In Information/ Admin Withdrawal Information
screen
TRG-03: User clicks “Hủy” button at the transaction that wants to cancel

POS-01: The request will be canceled

Post-Condition
POS-02: Transaction will be removed from the Transaction table in screen

Main flows

SWP490_G35 273/303
FBS - Software Requirement Specification v2.0

Step Actor Action

1 User Go to Admin Pay In Information/ Admin Withdrawal Information screen

2 FBS Display Admin Wallet Information/ Admin Withdrawal Information screen

3 User Click “Hủy” button at the transaction that want to accept

4 FBS Display Confirm dialog

5 User Click “Đồng ý” button

Display dialog, cancel request, send a notification to customer, and hide

6 FBS
request from screen

Table 3-341: Cancel Money Processing Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if user clicks “Trở lại” or Close button

Sub-step Actor Action

Back to Admin Wallet Information/ Admin Withdrawal Information screen

5.1 FBS
and not save change

Table 3-342: Alternative flows of Cancel Money Processing Use case

3.5.6.20 UC-72 - Recharge Processing

3.5.6.20.1 Screen Design

SWP490_G35 274/303
FBS - Software Requirement Specification v2.0

Figure 3-83 Screen Design of Recharge Processing

Table 3-343: Recharge Processing Screen Definition

Max
# Field Name Type Mandatory Description
Length

Main

1 Title Nạp tiền Label

2 Nhập số tiền Textbox Yes Enter amount of

money

Số điện thoại (tài Enter phone number of

3 Textbox Yes the user who wants to
khoản) nạp tiền
recharge

Button to check if the

4 Kiểm tra Button provided phone
number matches the
user information

Tên người nạp tiền Enter recharger's name

5 Textbox No if top-up on behalf of
(nếu nạp hộ)
the user

Enter recharger's
Số điện thoại người phone number if top-
6 Textbox No
nạp tiền (nếu nạp hộ) up on behalf of the
user

SWP490_G35 275/303
FBS - Software Requirement Specification v2.0

7 Nạp tiền Button Button to recharge

Button to close
8 Trở lại Button Recharge Processing
screen

Button to close
9 Close Button Recharge Processing
screen

3.5.6.20.2 Use case Specification

Use Case ID UC-72 Use Case Name Recharge Processing

Author TrangTLH Version 1.0 Date 21/07/2021

Actor FBSAdmin

This function allows the authorized user to top up FBS wallets for customers
Description
after receiving customer’s cash

PRE-01: User receives customer’s cash

Precondition PRE-01: User has been authorized to Admin Pay In Information screen
PRE-02: User is in Admin Pay In Information screen

TRG-01: User has been authorized to Admin Pay In Information screen

Trigger TRG-02: User is in Admin Pay In Information screen
TRG-03: User enters information and clicks “Nạp tiền” button

POS-01: The money is loaded into the client's wallet and the customer will
Post-Condition
receive a notification

Main flows

Step Actor Action

1 User Go to Admin Pay In Information screen

2 FBS Display Admin Wallet Information screen

3 User Click “Xử lý nạp tiền” button

4 FBS Display Recharge Processing screen

5 User Enter amount of money at “Nhập số tiền” textbox

Enter phone number of the user who want to recharge at “Số điện thoại (tài
6 User
khoản) nạp tiền” textbox

Click “Kiểm tra” button to check if the provided phone number matches the
7 User
user information

SWP490_G35 276/303
FBS - Software Requirement Specification v2.0

8 User Enter recharger's name if top-up on behalf of the user (not require)

9 User Enter recharger's phone number if top-up on behalf of the user (not require)

10 User Click “Nạp tiền” button

11 FBS Display Confirm dialog

12 User Click “Đồng ý” button

Display message, recharge customer wallet and send a notification to

13 FBS
customer

Table 3-344: Search Money Processing Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if amount of money is not entered

Sub-step Actor Action

5.1 FBS Display a message “Vui lòng nhập số tiền hoặc số tiền không hợp lệ”

Table 3-345: Alternative flows of Recharge Processing Use case

AT2 At step 5 in the main flows, if amount of money is not a positive integer

Sub-step Actor Action

5.2 FBS Display a message “Vui lòng nhập số tiền hoặc số tiền không hợp lệ”

Table 3-346: Alternative flows of Recharge Processing Use case

AT3 At step 5 in the main flows, if amount of money is less than 10,000 VND

Sub-step Actor Action

5.3 FBS Display a message “Số tiền tối thiểu có thể nạp hoặc rút là 10,000 VND”

Table 3-347: Alternative flows of Recharge Processing Use case

AT4 At step 6 in the main flows, if phone number is not entered or wrong format

Sub-step Actor Action

6.1 FBS Display a message “Số điện thoại không hợp lý”

SWP490_G35 277/303
FBS - Software Requirement Specification v2.0

Table 3-348: Alternative flows of Recharge Processing Use case

AT5 At step 6 in the main flows, if phone number is not in the system

Sub-step Actor Action

6.2 FBS Display a message “Số điện thoại không có trong hệ thống”

Table 3-349: Alternative flows of Recharge Processing Use case

AT6 At step 7 in the main flows, if phone number is not in the system

Sub-step Actor Action

7.1 FBS Display a message “Không có thông tin”

Table 3-350: Alternative flows of Recharge Processing Use case

AT7 At step 12 in the main flows, if user clicks “Trở lại” or Close button

Sub-step Actor Action

12.1 FBS Back to Recharge Processing screen and not save change

Table 3-351: Business Rules of Recharge Processing Use case

Business Rules

# Rule Description

BR51 After the customer gives cash, the admin will deposit to the customer's wallet

The amount entered for depositing or withdrawing must be a positive integer and must
BR52
be at least 10000 VND

Table 3-352: Business Rules of Recharge Processing Use case

3.5.6.21 UC-73 - Search User

3.5.6.21.1 Screen Design

SWP490_G35 278/303
FBS - Software Requirement Specification v2.0

Figure 3-84: Screen Design of Search User

Table 3-353: Search User Screen Definition

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as sidebar of Admin screen)

Main

Title Quản lý người

1 Label
dùng

2 Nhập tên người dùng Textbox Enter keywords name

to search

SWP490_G35 279/303
FBS - Software Requirement Specification v2.0

3 Nhập số điện thoại Textbox Enter phone login to

search

4 User Status Combo box Status of User

5 Search Button Button Button to trigger

Search function

6 User Table Table Table contains user

information

7 Tên người dùng Label Name of user

8 Số điện thoại Label Phone login of user

9 Vai trò Label Role of user

10 Trạng thái Label Status of user

11 Chi tiết Button Link to Admin User

Profile screen

12 Chặn Button Button to block user

13 Bỏ chặn Button Button to unblock

user

14 User Pagination Hyperlink This hyperlink links to

page of users

3.5.6.21.2 Use case Specification

Use Case ID UC-73 Use Case Name Search User

Author TrangTLH Version 1.0 Date 21/07/2021

Actor FBSAdmin

Description This function allows the authorized user to search for users of the system

PRE-01: User has been authorized to Admin screen

Precondition
PRE-02: User is in Admin screen

TRG-01: User has been authorized to Admin screen

TRG-02: User is in Admin screen
Trigger TRG-03: User clicks “Người dùng” hyperlink on sidebar
TRG-04: User enters keywords name or phone login or selects status of user
and clicks Search button

Post-Condition POS-01: Query in database with entered information

SWP490_G35 280/303
FBS - Software Requirement Specification v2.0

POS-02: User views list of users successfully

Main flows

Step Actor Action

1 User Go to Admin screen

2 FBS Display Admin screen

3 User Click “Người dùng” hyperlink on sidebar

4 FBS Display Admin List Users screen

5 User Enter keywords name or phone login or select status of user

6 User Click Search button

7 FBS Display list of user in Admin List Users screen

8 User View list of users

Table 3-354: Search User Use case Specification

Business Rules

# Rule Description

Admin has permission to views orders, revenue of systems, accounts, and restaurants of
BR16
system

Table 3-355: Business Rules of Search User Use case

3.5.6.22 UC-74 - View User Profile

3.5.6.22.1 Screen Design

SWP490_G35 281/303
FBS - Software Requirement Specification v2.0

Figure 3-85: Screen Design of View User Profile

Table 3-356: View User Profile Screen Definition

Max
# Field Name Type Mandatory Description
Length

Main

1 User Image Image Avatar of user

2 Tên người dùng Label Name of user

3 Số điện thoại Label Phone login of user

4 Ngày sinh Label Date of birth of user

5 Email Label Email of user

Specific address of
6 Địa chỉ Label
user

Button to back to
7 Trở lại Button Admin List User
screen

Button to close Admin

8 Close Button
User Profile Popup

3.5.6.22.2 Use case Specification

Use Case ID UC-75 Use Case Name View User Profile

SWP490_G35 282/303
FBS - Software Requirement Specification v2.0

Author TrangTLH Version 1.0 Date 21/07/2021

Actor FBSAdmin

This function allows the authorized user to view the profile of the user of the
Description
system

PRE-01: User has been authorized to Admin List Users screen

Precondition
PRE-02: User is in Admin List Users screen

TRG-01: User has been authorized to Admin List Users screen

Trigger TRG-02: User is in Admin List Users screen
TRG-03: User clicks “Chi tiết” button at the user that wants to view

Post-Condition POS-01: User views profile of restaurant successfully

Main flows

Step Actor Action

1 User Go to Admin List Users screen

2 FBS Display Admin List Users screen

3 User Click “Chi tiết” button at the user that want to view

4 FBS Display Admin User Profile screen

5 User View profile of the restaurant

Table 3-357: View User Profile Use case Specification

Business Rules

# Rule Description

Admin has permission to views orders, revenue of system, accounts, and restaurants of
BR16
system

Table 3-358: Business Rules of View User Profile Use case

3.5.6.23 UC-75 - Block User

3.5.6.23.1 Screen Design

SWP490_G35 283/303
FBS - Software Requirement Specification v2.0

Figure 3-86: Screen Design of Block User

Figure 3-87: Screen Design of Confirm Dialog

Table 3-359: Block User Screen Definition

SWP490_G35 284/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Header (same as header of Admin screen)

Sidebar (same as sidebar of Admin screen)

Main (described at UC-66)

Confirm Dialog

1 Title Thông báo Label

Bạn có muốn lưu thay

2 Label Message
đổi không

3 Lưu Button Button to save change

Button to close
4 Trở lại Button
confirm dialog

Button to close
5 Close Button
confirm dialog

3.5.6.23.2 Use case Specification

Use Case ID UC-68 Use Case Name Block User

Author TrangTLH Version 1.0 Date 21/07/2021

Actor FBSAdmin

Description This function allows the authorized user to block the violated user

PRE-01: User has been authorized to Admin List Users screen

Precondition
PRE-02: User is in Admin List Users screen

TRG-01: User has been authorized to Admin List Users screen

Trigger TRG-02: User is in Admin List Users screen
TRG-01: User clicks “Chặn” button at the user that wants to block

POS-01: Status of user in database will change to Banned

Post-Condition
POS-02: The user will be hidden on the system and can not sign in system

Main flows

Step Actor Action

1 User Go to Admin List User screen

2 FBS Display Admin List User screen

3 User Click “Chặn” button

SWP490_G35 285/303
FBS - Software Requirement Specification v2.0

4 FBS Display Confirm dialog

5 User Click “Lưu” button

6 FBS Block user and hide user on the system

Table 3-360: Block User Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if user clicks “Trở lại” or Close button

Sub-step Actor Action

5.1 FBS Back to Admin List Users screen and not save change

Table 3-361: Alternative flows of Block User Use case

3.5.6.24 UC-76 - Unblock User

3.5.6.24.1 Screen Design

SWP490_G35 286/303
FBS - Software Requirement Specification v2.0

Figure 3-88: Screen Design of Unblock User

Figure 3-80: Screen Design of Confirm Dialog

Table 3-362: Unblock User Screen Definition

SWP490_G35 287/303
FBS - Software Requirement Specification v2.0

Max
# Field Name Type Mandatory Description
Length

Reference to UC-75

3.5.6.24.2 Use case Specification

Use Case ID UC-76 Use Case Name Unblock User

Author TrangTLH Version 1.0 Date 21/07/2021

Actor FBSAdmin

Description This function allows the authorized user to unblock the user

PRE-01: User has been authorized to Admin List Users screen

Precondition
PRE-02: User is in Admin List Users screen

TRG-01: User has been authorized to Admin List Users screen

Trigger TRG-02: User is in Admin List Users screen
TRG-03: User clicks “Bỏ chặn” button at the user that wants to unblock

POS-01: Status of user in database will change to Active

Post-Condition
POS-02: The user will be displayed on the system and user can sign-in system

Main flows

Step Actor Action

1 User Go to Admin List User screen

2 FBS Display Admin List User screen

3 User Click “Bỏ chặn” button

4 FBS Display Confirm dialog

5 User Click “Lưu” button

6 FBS Unblock user and display user on the system

Table 3-363: Unblock User Use case Specification

Alternative flows

AT1 At step 5 in the main flows, if user clicks “Trở lại” or Close button

SWP490_G35 288/303
FBS - Software Requirement Specification v2.0

Sub-step Actor Action

5.1 FBS Back to Admin List Users screen and not save change

Table 3-364: Alternative flows of Unblock User Use case

4 Non-Functional Requirements
4.1 External Interfaces
4.1.1 User Interfaces

UI-1: The system shall provide instructions and regulations when canceling the order from FBS
when the user creates and cancels the order to explain the compensation policy when canceling the
application as well as why the deposit is required.
UI-2: The system shall provide a term of use link from FBS to explain mandatory terms when using
FBS.
UI-3: The webpages shall permit using the keyboard in some cases, in addition to using mouse
alone
UI-4: Standard user interface:
● Font-family: sans serif
● Font-size: 16px
● Icon: Font Awesome 5
● Colors: The main color of this system is: #198754
UI-5: Screen resolution: This system supports responsiveness for candidate’s screens: mobiles,
desktops, tablets, laptops.

4.1.2 Software Interfaces

4.1.2.1 Microsoft SQL Server Commented [30]: Cần mô tả cấu trúc dữ liệu của giao
diện
Transfer protocol: TCP/IP Commented [31R30]: _Marked as resolved_
Commented [32R30]: _Re-opened_
4.1.2.2 FireBase
Commented [33]: Nếu định nghĩa các interface này thì
chia thành các mục nhỏ cho mỗi một interface
Firebase Phone Authentication shall send an OTP to the phone number used to register the account. xem ví dụ
If the user does not provide the correct OTP code, the account cannot be registered
Commented [34R33]: _Marked as resolved_

4.1.2.3 Facebook Messenger Commented [35R33]: _Re-opened_

User will chat with FBS system via Facebook Messenger

4.1.2.4 PayPal

To allow users to top up the system

SWP490_G35 289/303
FBS - Software Requirement Specification v2.0

4.1.3 Communications Interfaces

CI-1: Transfer protocol: HTTP

4.2 Quality Attributes

4.2.1 Usability

The FBS conforms to common usability standards and provides a friendly interface for those who use
it for the first time.
● User interface should be clear and easy to use
● Main functions are organized into tabs for easier access.
● Alternative attributes are provided for non-text elements, such as images.
● Links, buttons, checkboxes are easily clickable.
● The search box is wide enough for users to see what they have typed.
● Links are easily recognizable, clickable. Items that are not links do not look clickable, for
example, underlining text is avoided.
● Important commands are displayed as buttons with distinct background colors.

Commented [36]: Xem lại cấu trúc trong temlate và

sắp xếp lại
4.2.2 Reliability Mục 4.2.2.1 Availability và 4.2.3.3 Scalability không
để bên trong Reliability
The mean time between two failures is at least 1 month. Commented [37R36]: _Marked as resolved_
Commented [38R36]: _Re-opened_
4.2.3 Availability
Commented [39]: Phần này mô tả khả năng sẵn sàng
của hệ thống thường là VD
- The system is deployed to the server, ensures 24/7 operation. User can access the system at 1. Hệ thống luôn sẵn sàng 24/7
any time hoặc thể hiện chỉ số sô yêu cầu được đáp ứng /tổng số
yêu cầu của người dùng
- Meeting more than 90% of user’s requirements
- In the case of unplanned system downtime, all features will be available again in the shortest Phần thông tin đã mô tả thể hiện là yêu cầu phần
time possible cứng/yêu cầu phần mềm

4.2.4 Performance

● Processing time:
Pages are categorized into different levels: low, medium, complex, and very complex. Depending on
the type of page that occupies the CPU differently.
Below are the two requirements for the performance of web, with the assumption that in normal
cases, there will be less than or equal to 1000 concurrent users:

# Level of page Time to load

1 Low 3 second or less

SWP490_G35 290/303
FBS - Software Requirement Specification v2.0

2 Medium 5 seconds or less

3 Complex 6-8 seconds or less

4 Very complex 10 seconds or more

Table 4-1: Processing time

● Cost performance:
- Hardware references to 4.4
- FBS uses 10% CPU, 700MB RAM, and 700MB Memory
- Every month needed 500MB on the hard drive

4.2.5 Security

● The HTTP protocol will be used to facilitate communications between the client and server
and for all FBS functions. Basic password authentication and role-based security mechanisms
will be used to protect FBS site from unauthorized access.
● Token-Based Authentication relies on a signed token that is sent to the server on each
request.
● Sign in as the phone number.
● The server must authenticate every request accessing the restricted Web pages.
● After authenticating the browser, the server must determine whether that browser is
authorized (i.e., has necessary privileges) to access the requested restricted Web pages.
● Firebase Phone Authentication to verify phone login when register an account

4.2.6 Safety

● The password is encrypted using the BCrypt password encoder.

4.2.7 Supportability

● The naming convention for back-end using camel-case convention.

● Front-end app follows a standard single-page application structure to ensure maintainability.
● REST API standard for connecting between front-end and back-end.
● Maintainable source code and easy deployment since we follow a single coding convention
and a high maintainability architecture design.
4.2.8 Design Constraints

This system should be compiled with the following items below:

SWP490_G35 291/303
FBS - Software Requirement Specification v2.0

● End-user environment: Any web browser that users have been installed on their personal
computer like Google Chrome, Edge.
● Java extension:
● Operating System that is used for running judge host daemon has at least 4GB RAM.
● Every process in this system must be less than 3s, and not exceed 1 second with the best
condition of the Internet.
● ReactJS, Spring boot framework
Design requirements:
● FBS Server-side: Layer architecture
● FBS Client-side: MVC architecture

4.2.9 Support Documents

When handing over, must hand over:

- Project Introduction
- Term of service of FBS system
- Software User Guides

5 Other Requirements
5.1 Appendix1 - Messages List

Message Message
# Context Content
code Type

Under the Input-required phone

1 MSG01 Vui lòng nhập số điện thoại
text box number is empty

Under the Input-required password is

2 MSG02 Vui lòng nhập mật khẩu
text box empty

Toast Username or password is not Số điện thoại hoặc mật khẩu

3 MSG03
message correct when clicking sign-in không chính xác

Under the Input-required name is

4 MSG04 Vui lòng nhập tên đầy đủ
text box empty

Under the Input-required new password

5 MSG05 Vui lòng nhập mật khẩu mới
text box is empty

Toast
6 MSG06 Password is not true Vui lòng nhập lại mật khẩu
message

Toast Password and re-password is

7 MSG07 Mật khẩu không khớp
message not match

SWP490_G35 292/303
FBS - Software Requirement Specification v2.0

Toast The phone number entered is

8 MSG08 Số điện thoại sai định dạng
message wrong format

Toast Bạn đăng ký không thành

9 MSG09 Account registration failed
message công

Toast Account registration

10 MSG10 Đăng ký thành công
message successful

Toast Reset/ Change password

11 MSG11 Đổi mật khẩu thành công
message successful

Input-required amount to
Toast
12 MSG12 deposit into the wallet is Vui lòng nhập số tiền cần nạp
message
empty

13 MSG13 Dialog Cart is empty Giỏ hàng trống [Quay lại]

Perform the functions that Bạn phải đăng nhập để thực

14 MSG14 Dialog need to be logged in but not hiện chức năng này [Đăng
logged in nhập]/[Quay lại]

Toast Input-required content of Vui lòng nhập nội dung đánh

15 MSG15
message feedback is empty giá

Confirm whether the user

Bạn có chắc chắn xóa ảnh
16 MSG16 Dialog wants to delete the image or
này? [Có]/ [Trở lại]
not

Requires a password of 3-32 Vui lòng nhập mật khẩu từ 3-

Toast
17 MSG17 characters and does not 32 ký tự và không bao gồm
message
include spaces khoảng trắng

Perform the functions that

Toast Vui lòng đăng nhập để thực
18 MSG18 need to be logged in but not
message hiện chức năng này
logged in

The phone number used to

Toast
19 MSG19 register already exists in the Số điện thoại đã tồn tại
message
system

Confirm user about logging Bạn có chắc chắn muốn thoát

20 MSG20 Dialog
out khỏi hệ thống FBS?

Under the Input-required name of Tên nhà hàng không được để

21 MSG21
text box restaurant is empty trống

Input-required number value

Under the Giá trị phải lớn hơn hoặc bằng
22 MSG22 must be greater than or
text box 0
equal to 0

SWP490_G35 293/303
FBS - Software Requirement Specification v2.0

Under the Date is required to be current Giá trị phải là [Ngày hiện tại]
23 MSG23
text box date or later hoặc muộn hơn

Toast Input-required image of Vui lòng thêm ảnh của khuyến

24 MSG24
message promotion is empty mãi

Under the Input-required address of

25 MSG25 Địa chỉ không được để trống
text box restaurant is empty

Input-required number of
Toast guests the restaurant can Vui lòng nhập sức chứa hoặc
26 MSG26
message accommodate is empty or sức chứa không hợp lệ
wrong format

Under the Input-required business Mã giấy phép kinh doanh

27 MSG27
text box license code is empty không được để trống

Under the Input-required description is

28 MSG28 Mô tả không được để trống
text box empty

Input-required image of Vui lòng thêm giấy chứng

Toast
29 MSG29 restaurant food safety nhận an toàn thực phẩm của
message
certificate is empty nhà hàng

Haven't clicked on the

Toast Vui lòng chấp nhận điều
30 MSG30 checkbox to agree to the
message khoản của FBS
terms of the FBS system

Toast Restaurant registration

31 MSG31 Đăng ký nhà hàng thành công
message successful

Toast Input-required name is

32 MSG32 Vui lòng nhập tên đầy đủ
message empty

The number of characters in

Toast Mã giấy phép kinh doanh quá
33 MSG33 the business license code is
message dài
longer than specified

Toast
34 MSG34 Email is wrong format Email sai định dạng
message

Under the Date of birth must be less Ngày sinh phải nhỏ hơn ngày
35 MSG35
text box than today hiện tại

Toast Restaurant name longer than Tên nhà hàng quá dài (nhỏ
36 MSG36
message 100 characters hơn 100 ký tự)

Under the Input-required combo name

37 MSG37 Vui lòng nhập tên combo
text box is empty

Under the Input-required combo price is

38 MSG38 Vui lòng nhập giá combo
text box empty

SWP490_G35 294/303
FBS - Software Requirement Specification v2.0

The number of guests the

Toast
39 MSG39 restaurant can accommodate Sức chứa quá lớn
message
is greater than specified

Toast Combo price is greater than

40 MSG40 Giá combo phải ít hơn 10 ký tự
message 10 characters

Toast The combo name already Tên combo đã tồn tại trong
41 MSG41
message exists in the restaurant nhà hàng

Under the Input-required dish name is

42 MSG42 Vui lòng nhập tên món ăn
text box empty

Under the Input-required dish price is

43 MSG43 Vui lòng nhập giá món ăn
text box empty

Toast The dish name already exists Tên món ăn đã tồn tại trong
44 MSG44
message in the restaurant nhà hàng

Under the Input-required service name

45 MSG45 Vui lòng nhập tên dịch vụ
text box is empty

Under the Input-required service price is

46 MSG46 Vui lòng nhập giá dịch vụ
text box empty

Toast The service name already Tên dịch vụ đã tồn tại trong
47 MSG47
message exists in the restaurant nhà hàng

Under the Input-required promotion

48 MSG48 Vui lòng nhập tên khuyến mãi
text box name is empty

Under the Promotion value must be less Giá trị phải bé hơn hoặc bằng
49 MSG49
text box than or equal to 100 100

Under the Input-required promotion Vui lòng nhập phần trăm

50 MSG50
text box percentage is empty khuyến mãi

Under the Input-required promotion Vui lòng nhập ngày bắt đầu
51 MSG51
text box start date is empty khuyến mại

Under the Input-required promotion Vui lòng nhập ngày kết thúc
52 MSG52
text box end date is empty khuyến mại

Promotion end date must be

Under the Giá trị phải là [Ngày bắt đầu]
53 MSG53 equal to or greater than start
text box hoặc muộn hơn
date

Under the Input-required old password

54 MSG54 Vui lòng nhập mật khẩu cũ
text box is empty

Toast
55 MSG55 Old password is not correct Mật khẩu cũ không đúng
message

SWP490_G35 295/303
FBS - Software Requirement Specification v2.0

Toast
56 MSG56 Update combo successfully Cập nhật combo thành công
message

Toast Input-required content of Vui lòng nhập nội dung báo

57 MSG57
message report is empty cáo

Toast
58 MSG58 Send report successfully Gửi báo cáo thành công
message

Under the Input-required number of

59 MSG59 Vui lòng nhập số lượng khách
text box guests is empty

Under the Number of guest must be Số lượng khách phải lớn hơn
60 MSG60
text box greater or equal than 1 hoặc bằng 1

Under the Input-required feast organize

61 MSG61 Vui lòng chọn ngày tổ chức
text box date is empty

Toast
62 MSG62 Password is not correct Mật khẩu không đúng
message

Toast
63 MSG63 Accept order successfully Nhận đơn thành công
message

Toast
64 MSG64 Cancel order successfully Hủy đơn thành công
message

Confirm about saving Lưu thay đổi? [Đồng ý]/ [Quay

65 MSG65 Dialog
changes lại]

Toast
66 MSG66 Name is longer than specified Tên của bạn quá dài
message

Toast Content of feedback must be Nội dung đánh giá phải ít hơn
67 MSG67
message less than 250 characters 250 ký tự

Toast Value must be earlier than Giá trị phải sớm hơn
68 MSG68
message today + 1 (dd/mm/yyyy + 1)

Toast
69 MSG69 Quantity is too much Số lượng quá lớn
message

Toast The number of guests is too

70 MSG70 Số lượng khách quá lớn
message large

Toast Description must be less than Mô tả phải nhỏ hơn 2000 ký

71 MSG71
message 2000 characters tự

Toast Address must be less than Tên địa chỉ quá dài (nhỏ hơn
72 MSG72
message 100 character 100 ký tự)

SWP490_G35 296/303
FBS - Software Requirement Specification v2.0

Toast Confirm about updating Bạn có chắc chắn cập nhật

73 MSG73
message information thông tin [Có]/ [Trở lại]

Toast
74 MSG74 Update successfully Cập nhật thành công
message

Toast Combo price must be less Tên combo phải ít hơn 100 ký
75 MSG75
message than 100 characters tự

Toast
76 MSG76 Input value must be numeric Vui lòng nhập số
message

Toast Combo description must be Mô tả combo phải nhỏ hơn

77 MSG77
message less than 2000 characters 2000 ký tự

Under the Input-required combo

78 MSG78 Vui lòng nhập mô tả combo
text box description is empty

Toast
79 MSG79 Add combo successfully Thêm combo thành công
message

Toast
80 MSG80 Add successfully Thêm thành công
message

Toast Dish name must be less than Tên món ăn phải ít hơn 100 ký
81 MSG81
message 100 characters tự

Toast Dish price must be less than Giá món ăn phải ít hơn 10 ký
82 MSG82
message 10 characters tự

Toast
83 MSG83 Add dish successfully Thêm món ăn thành công
message

Toast
84 MSG84 Update dish successfully Cập nhật món ăn thành công
message

Toast Input-required image of Bạn vui lòng thêm ảnh của

85 MSG85
message service is empty dịch vụ

Toast Thanh toán đơn hàng thành

86 MSG86 Order payment successful
message công

Toast Input-required image of

87 MSG87 Vui lòng thêm ảnh của combo
message combo is empty

Toast Input-required image of dish

88 MSG88 Vui lòng thêm ảnh của món ăn
message is empty

Toast
89 MSG89 Update service successfully Cập nhật dịch vụ thành công
message

SWP490_G35 297/303
FBS - Software Requirement Specification v2.0

Toast Promotion name must be less Tên khuyến mãi phải ít hơn
90 MSG90
message than 100 characters 100 ký tự

Toast Promotion description must Mô tả khuyến mãi phải ít hơn

91 MSG91
message be less than 2000 characters 2000 ký tự

Toast Promotion percentage must Phần trăm khuyến mãi phải ít

92 MSG92
message be less than 3 characters hơn 3 ký tự

Toast The promotion name already

93 MSG93 Khuyến mãi này đã tồn tại
message exists in the restaurant

Toast Update promotion Cập nhật khuyến mãi thành

94 MSG94
message successfully công

Bạn có chắc chắn muốn gỡ

95 MSG95 Dialog Confirm about removing dish món ăn này ? [Đồng ý]/ [Quay
lại]

Bạn có chắc chắn muốn gỡ

Confirm about removing
96 MSG96 Dialog combo món ăn này ? [Đồng
combo
ý]/ [Quay lại]

Bạn có chắc chắn muốn gỡ

Confirm about removing
97 MSG97 Dialog dịch vụ này ? [Đồng ý]/ [Quay
service
lại]

Toast
98 MSG98 Remove the dish successfully Gỡ món ăn thành công
message

Toast Remove the combo

99 MSG99 Gỡ combo thành công
message successfully

Toast Remove the service

100 MSG100 Gỡ dịch vụ thành công
message successfully

Input-required amount of
Toast Vui lòng nhập số tiền hoặc số
101 MSG101 money is empty or wrong
message tiền không hợp lệ
format

Toast Input-required phone Số điện thoại không được để

102 MSG102
message number is empty trống

Toast The phone number is not in Số điện thoại không có trong

103 MSG103
message the system hệ thống

Bạn có chắc chắn muốn nạp

104 MSG104 Dialog Confirm customer recharge
tiền ? [Đồng ý]/ [Quay lại]

Successfully deposited
105 MSG105 Dialog Nạp tiền vào ví thành công
money into the wallet

SWP490_G35 298/303
FBS - Software Requirement Specification v2.0

The minimum amount that

Toast Số tiền tối thiểu có thể nạp
106 MSG106 can be deposited or
message hoặc rút là 10000VNĐ
withdrawn is 10000 VND

Bạn có chắc chắn đăng ký?

107 MSG107 Dialog Confirmation of registration
[Có]/ [Quay lại]

Bạn có chắc muốn nạp tiền ?

108 MSG108 Dialog Confirm about the deposit
[Đồng ý]/ [Quay lại]

Yêu cầu nạp tiền của bạn đã

Toast Deposit request submitted được gửi lên hệ thống, chúng
109 MSG109
message successfully tôi sẽ xem xét và xử lý sớm
nhất

Toast Input-required amount of

110 MSG110 Vui lòng nhập số tiền cần rút
message money to withdraw is empty

Bạn có chắc muốn rút tiền ?

111 MSG111 Dialog Confirm about the withdraw
[Đồng ý]/ [Quay lại]

Yêu cầu rút tiền của bạn đã

Toast Withdraw request submitted được gửi lên hệ thống, chúng
112 MSG112
message successfully tôi sẽ xem xét và xử lý sớm
nhất

Bạn có chắc chắn thanh toán

Confirm about payment the
113 MSG113 Dialog đơn hàng này ? [Đồng ý]/
order
[Quay lại]

Toast The amount in your wallet is Số tiền trong ví của bạn không
114 MSG114
message not enough đủ

Under the Value must be greater or Giá trị phải lớn hơn hoặc bằng
115 MSG115
text box equal than 1000 1000

Toast Input-required bank account Vui lòng nhập thông tin tài
116 MSG116
message information is empty khoản ngân hàng của bạn

Under the
117 MSG117 Input-required field is empty Vui lòng điền vào trường này
text box

Under the Input-required address is

118 MSG118 Vui lòng nhập địa chỉ cụ thể
text box empty

Toast
119 MSG119 Successful confirmation Xác nhận thành công
message

Toast Customer cancels the order

120 MSG120 Hủy thành công
message successfully

SWP490_G35 299/303
FBS - Software Requirement Specification v2.0

Toast Nạp tiền vào ví không thành

121 MSG121 Wallet recharge failed
message công

Haven't completed the order Bạn phải hoàn tất thanh toán
Toast
122 MSG122 at this restaurant, went to của nhà hàng khác trước khi
message
another restaurant to choose thêm vào giỏ hàng

Đơn hàng đã quá hạn để

Toast Order confirmation but the
123 MSG123 nhận, chúng tôi đã chuyển
message order is overdue
đơn hàng này thành "Đã hủy"

Toast Đồng ý hoàn thành đơn hàng

124 MSG124 Complete order successfully
message thành công

Table 5-1: Message List of FBS system

5.2 Appendix2 - Firebase

Figure 5-1: Firebase send OTP after enter register info

- User enters OTP in the Register screen, if the OTP entered is the same as the OTP sent to the
phone number, the system will display a successful login message. Otherwise, the system
will display an error message

● Forget Password:

- After the user enters phone login, password, re-password and the system checks that the
information is valid, Firebase will send a message containing the OTP to the phone number

SWP490_G35 300/303
FBS - Software Requirement Specification v2.0

Figure 5-3: Firebase send OTP after enter info to reset password
- User enters OTP in the Forget Password screen, if the OTP entered is the same as the OTP
sent to the phone number, the system will display a successful login message. Otherwise, the
system will display an error message

5.3 Appendix3 - Facebook Messenger

- User chats with FBS system via Facebook Messenger

- The message will be sent to the message box of the FBS page. The system will reply via the
FBS page on Facebook

SWP490_G35 301/303
FBS - Software Requirement Specification v2.0

Figure 5-4: Popup chat via Messenger

5.4 Appendix4 - PayPal

- After selecting the deposit method or pay by PayPal, the system will redirect to the PayPal
page
- User fills in the information and makes a transaction on the PayPal page, the money will be
transferred to the system's FBS wallet

SWP490_G35 302/303
FBS - Software Requirement Specification v2.0

Figure 5-5: Transactions with PayPal

SWP490_G35 303/303