Các bước tiến hành xây dựng một module của một phần mềm

1. SFCS - Smart Food Court System
Version 1.0
Metor: Quản Thành Thơ
Author: Phùng Chí Minh Quang
ID: 1612786

2. 1. Member List:
2. Document History:
3. Introduction to project:
4. Use case of the project:
5. Project features in general:

3. Feature 1: Customers can order food without going directly to the
food stall.
By using the machine with touch screen around the food count or
mobile app, customers can order food without going directly to the
food stall. On the screen of the touch screen machine will appear
the type of food and their price. Customers choose food and
payment. When the payment is made, the order is confirm and will
be put in the order list at the food stall kitchen.
Feature 2: Notify customers when food is ready.
When the food is ready, the system will notify customers by the
pager calling or mobile app.
Feature 3: Make payments.
Customer can pay by online wallets like Momo wallet, Samsung
Pay, Apple Pay and re-charge the app and use app account to make
payment for ordered food.
Feature 4: Manage the system.
Managers are able to view the online report for the whole food
court.Vendors can view their online report for their stall, add new
food into the menu or add new discounts. The cook can view
orders and inform the ready of food or inform the system that some
food is out-of-order. The IT staff can shutdown all online service
to upload new feature or fix bugs.
6. Non-functional features:
7. Log in function:
7.1: Use case tabular
Use-case name Log in
Actor Customer, staff, manager, vendor (user)
Description The user have to log in to use the app
Preconditions App must be opened

4. Normal Flow 1. App display “log in screen” attached “register
option”.
+A: user choose to log in.
+B: user choose to register.
Case A:
2. user write id and pass
3. If id and pass are correct, lead user into the app
feature.
Case B:
4. App display 2 choice: “sign up new account” or “sign
up with google account”
+B1: user choose “sign up new account”
+B2: user choose “sign up with Google account”
Case B1:
5. Guide user to write id/pass(2 times)
6. Return to step 1
Case B2:
8. open google app to customer can log in by their
google account.
9. lead user to the app feature.
Exceptions No exception
Alternative Flows Alternative1:
3.1 If id/pass is incorrect, display “id or pass is
incorrect” and return to step 1.
Alternative2:
5.1 If writing password (2 time) is unsuccessful, display
“password is not the same” and let user fill again
Note: Functions in app feature is depent on what kind of user (
vendor will have report function but customer will not)
7.2: Usecase diagram

5. 7.3: Non-functional requirements
- Time to “log in” (if id and pass are correct): <2s
- Once user successfully log in, app will start a active session time
(it means you don’t need to “log in” again in active session time).
Active session time is 2 weeks.
- Time for new account can be use to “log in” is less than 1s.