VIETNAM NATIONAL UNIVERSITY, HO CHI MINH CITY

UNIVERSITY OF TECHNOLOGY
FACULTY OF COMPUTER SCIENCE AND ENGINEERING

SOFTWARE ENGINEERING (CO3001)

PROJECT REPORT
Assignment 1: RESTAURANT POS 2.0
Task 1: Requirement elicitation

Lecturers: Quản Thành Thơ

Bùi Công Tuấn
Group name: Eternals
Students: Phan Anh Tú - 1915822 (Leader)
Huỳnh Tuấn Đạt - 1913026
Trần Quốc Việt - 1915919
Nguyễn Văn Quốc - 1914864
Nguyễn Việt Đức - 1913167

HO CHI MINH CITY, SEPTEMBER 2021

 University of Technology, Ho Chi Minh City
Faculty of Computer Science and Engineering

Contents
1 Workload 2

2 Task 1: Requirement elicitation 3

2.1 Task 1.1: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Task 1.2: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.1 Functional requirements for system: . . . . . . . . . . . . . . . . . . . . . 4
2.2.2 Use-case diagram for the whole system: . . . . . . . . . . . . . . . . . . . 5
2.2.3 Non-Functional requirements for system: . . . . . . . . . . . . . . . . . . . 5
2.2.3.a General non-functional requirement for whole system: . . 5
2.2.3.b Specific non-function requirement for feature: . . . . . . . 6
2.3 Task 1.3: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3.1 Use-case: Order Food . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3.2 Use-case: Send Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3.3 Use-case: Pay for the order . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Assignment for Software Engineering - Academic year 2021 - 2022 Page 1/11
 University of Technology, Ho Chi Minh City
Faculty of Computer Science and Engineering

1 Workload

No. Fullname Student ID Problems

1 Phan Anh Tú 1915822 Task 1.3: Use-case Send Feedback.
2 Huỳnh Tuấn Đạt 1913026 Task 1.2
Functional requirements for system
Use-case diagram for the whole system
3 Trần Quốc Việt 1915919 Task 1.3
Use-case: Order Food
Use-case: Pay for the order.
4 Nguyễn Văn Quốc 1914864 Task 1.2: Non-Functional requirements for system.
5 Nguyễn Việt Đức 1913167 Task 1.1.

Assignment for Software Engineering - Academic year 2021 - 2022 Page 2/11
 University of Technology, Ho Chi Minh City
Faculty of Computer Science and Engineering

2 Task 1: Requirement elicitation

2.1 Task 1.1:
Require: Identify the context of this project. Who are relevant stakeholders? What are expected
to be done? What are the scope of the project?
• Context: This application offers customers a system to order food at the restaurants by
scanning the QR code provided on each table which takes them to the website of the app.
Hence, the app not only facilitates the food ordering process, but it also helps customers
be safe in the COVID-19 pandemic by maintaining physical distancing between them and
the clerks.
• Relevant stakeholders of this project are restaurant owners, customers, clerks, and kitchen.

• Features expected to be done include a menu screen for customers to choose the food they
want, a detail screen showing relevant information of the food, a cart for customers to
adjust and place order, online payment screen using credit card, notification of the food
status, recording transactions and getting feedback from users.
• Scope: This project is being undertaken for restaurant owners for the purpose of creating
a method for their customers to order food without direct contact with the staff.
+ This project will be run by a chain restaurant.
+ Operates in business hours.
+ Support pre-order.
+ Support take-away options.
+ Allow Visa and Mastercard only as a main payment method.
+ Should allow non-direct contact between clerks and customers.
+ Implemented using Web technologies and QR code for getting URL.
+ The website must be responsive to be available on mobile device, tablet device and
PC/laptop.
+ Capable of handling up to 300 transactions per day.
+ Comply with the regulations of the Ministry of Health of Vietnam.
+ Users can only send one feedback each transaction.

Assignment for Software Engineering - Academic year 2021 - 2022 Page 3/11
 University of Technology, Ho Chi Minh City
Faculty of Computer Science and Engineering

2.2 Task 1.2:

Require: Describe all functional and non-functional requirements of the desired system. Draw a
use-case diagram for the whole system

2.2.1 Functional requirements for system:

• Order food : Select the foods on the menu screen and put it in the cart

• View/Edit food : View ordered foods, and edit (add, delete, ..) ordered foods
• Place an order : Confirm the order with the items already placed in the cart
• Check out (Payment function): users can add the payment method to pay for their order
(additional).

• Feedback : Evaluation of the food as well as the quality of service and application
• Login: Authentication and authorization
• Manage staff : Manage staff in restaurant

• Manage customer : Manage customers who have ordered food at the restaurant
• View report: View all the information about the restaurant’s business ( such as invoices,
orders,...)
• Adjust foods menu: View invoices: View all invoices with filters date, orders,....

• Summary invoices: Select suitable field and print report about invoice for manager’s restau-
rant
• Update status food : Update food with status received when customer received the food
• Notify status food : Kitchen update food is available for clerk and customer

• Update available ingredient: Update status and available ingredient in inventory

• Check available ingredient: Check available ingredient for order’s customer and notify for
customer
• Record : Logs for data of system

• Maintain system: Maintain and update system

Assignment for Software Engineering - Academic year 2021 - 2022 Page 4/11
 University of Technology, Ho Chi Minh City
Faculty of Computer Science and Engineering

2.2.2 Use-case diagram for the whole system:

2.2.3 Non-Functional requirements for system:

2.2.3.a General non-functional requirement for whole system:
• The system only works from 6am to 10pm on weekdays.
• The system must follow the client-server model with customer and business information
stored on a server licensed by the government according to the Cybersecurity Law dated
January 1, 2019.

• The system development team complies with Circular No. 45/2017/TT-BTTTT of the
Ministry of Information and Communications.
• The system responds to user queries in a maximum of 2 seconds. If the query time is larger,
the system displays the message "The request is in progress".
• The system is allowed to fail once in 100 requests processing times.

Assignment for Software Engineering - Academic year 2021 - 2022 Page 5/11
 University of Technology, Ho Chi Minh City
Faculty of Computer Science and Engineering

• The system runs on platforms: IOS, Android

• User’s password must be hashed with Argon2
• All user data is encrypted with 1024bit SSL
• The system is maintained at least once in 3 months.
• Each periodic system upgrade should not last more than 30 minutes.
• The system is not subject to downtime of any 3rd party products.
• The system does not reveal the user’s personal information except name and user name.
• Users will be able to use the system after 2g of training.

2.2.3.b Specific non-function requirement for feature:

1. Use case: Order food
• If the user orders many dishes at the same time, the system will arrange the dishes
according to the order
• The system is capable of processing 200 orders at the same time
2. Use case: Checkout (payment)
• E-wallet service receiving system: MoMo, ZaloPay, AirPay and Mocha.
• E-wallet response time must be less than 1s.
• The system allows users to pay orders up to 5,000,000 VND once.
• Client transactions are secure and can only be accessed by the user.
3. Use case: Place an order
• If too many orders are sent at once, the system will use the queue to confirm each
order
4. Use case: Feedback
• The system can store up to 10000 customer reviews
• The system will automatically update new reviews on top of older reviews on the
forum.
• The maximum length of the review is 1000 words
5. Use case: View list invoice
• Invoices will be sent and arranged in chronological order
6. Use case: Adjust list food
• Update dishes according to customers’ tastes (the number of dishes that customers
choose more will be added ingredients)
• Update age-appropriate dishes
7. Use case: View report system (order, invoice)

Assignment for Software Engineering - Academic year 2021 - 2022 Page 6/11
 University of Technology, Ho Chi Minh City
Faculty of Computer Science and Engineering

• Reports to view are archived for 1 year..

• View unlimited reports.

8. Use case: Maintain system

• The system records errors and saves those errors as a list and sends them to technical
staff.
• Through customer reviews when using the system, technical staff upgrade to best
serve customer requirements.

2.3 Task 1.3:

Require: Choose one specific feature, i.e. food ordering, table reservation, customer management.
Draw its use-case diagram and describe the use-case using a table format

2.3.1 Use-case: Order Food

1. Use-case diagram

Assignment for Software Engineering - Academic year 2021 - 2022 Page 7/11
 University of Technology, Ho Chi Minh City
Faculty of Computer Science and Engineering

2. Table format

Name Order Food

Actor Customer
Customers can order lots of food they want to eat. They can know
Description about the feedback of the others about those food. They also have
two options: take-away or dine-in.
Preconditions Customers need to access to home page.
1. Customers go to home page of website by URL or the QR code.
Normal flow 2. System displays a menu list.
3. Customers can choose a Menu.
4. System displays a Menu screen.
5. Customers select the dish they want.
6. System pops up a window that allows the customer to enter
the quantity and note for that dish.
7. Customers enter the quantity and note for that dish.
8. Customers click “Shopping” button.
9. System returns Menu screen and updates the sum-up cart.
10. Customers can update their cart (adjust the number of dishes
or modify notes to their dishes).
11. Customers select options (take-away, dine-in) on the cart.
12. Customers click “Payment” button to complete order.
13. System stores order data and sends it to clerk.
Exception 1: at step 9
Exceptions 9a. System notifies “Please select the number of dishes again” if the
number of dishes the customer enters is greater than the number of
dishes that the kitchen can provide.
9b. System shows the number of dishes that can be served.
Return step 7 in normal flow.
Exception 2: at step 13
13a. System notifies “Please add the dish to the cart” if the cart is
empty.
Return step 2 in normal flow.
Alternative 1: at step 4
Alternative flow 4a. Customers click “Back to Home”.
4b. System navigates to Home Page.
Alternative 2: at step 7
7a. Customers click “Close” button.
7b. System clears the information that customer enters and close
the window.
Return step 4 in normal flow.

Assignment for Software Engineering - Academic year 2021 - 2022 Page 8/11
 University of Technology, Ho Chi Minh City
Faculty of Computer Science and Engineering

2.3.2 Use-case: Send Feedback

1. Use-case diagram

2. Table format

Name Send Feedback

Actor Customer
After users receiving the food and enjoy the meal, users can send a
Description
feedback to the restaurant through the website
Preconditions Customers need to access to home page
1. Customers go to home page of website by URL or the QR code.
Normal flow 2. System displays a menu list and feedback link.
3. Customers click feedback link.
4. Customers are redirected to feedback page.
5. Systems displays feedback screen with text fields for name,
feedback.
6. Customers fill in these text fields.
7. Customers press “Send” button.
8. The feedback is stored and displayed in the feedback page.
Exception: at step 7
Exceptions Can’t click “Send” button due to missing field name or feedback
System display “You must fill in the name and feedback”.
Alternative flow None

Assignment for Software Engineering - Academic year 2021 - 2022 Page 9/11
 University of Technology, Ho Chi Minh City
Faculty of Computer Science and Engineering

2.3.3 Use-case: Pay for the order

1. Use-case diagram

2. Table format

Name Pay for the order

Actor Customer
Description Customers pay for the order.
Preconditions Customers completed the order.
1. System displays order information.
Normal flow 2. Customers check order information.
3. Customers enter the discount code if they have.
4. System updates total order price.
5. Customers choose e-wallets to pay.
6. Customers click “Confirm” to pay the order.
7. System displays “Payment Success”.

Assignment for Software Engineering - Academic year 2021 - 2022 Page 10/11
 University of Technology, Ho Chi Minh City
Faculty of Computer Science and Engineering

Exception 1: at step 7
Exceptions System displays “The amount is not enough. Please add more
money to the wallet” if the customer does not have enough money
to pay.
Return step 1 in normal flow.
Exception 2: at step 7
System displays “Unexpected Error” if system catchs unexpected
error (e.g., Internet problem, Invalid Account).
Return step 1 in normal flow.
Alternative flow None

Assignment for Software Engineering - Academic year 2021 - 2022 Page 11/11