Group4 CoffeeChain Report

MINISTRY OF EDUCATION AND TRAINING
FPT UNIVERSITY
Capstone Project Document

Coffee Chain
SEP490_G3
Nguyen Tuan Duong - Leader - HE150423
Le Nguyen Anh Tuan - Member - HE150485
Group Members Pham Duc Anh - Member - HE 150529
Phuong Thanh Huyen - Member - HE150576
Phan Duc Manh - Member - HE151290
Supervisor Tran Dinh Tri

Ext Supervisor None
Capstone Project
CC
code
- Hanoi, April 2023 -
1
Table of Contents
Definition and Acronyms ....................................................................................................................... 12
CHAPTER 1: ............................................................................................................................................ 13
PROJECT INTRODUCTION....................................................................................................................... 13
1.1. Overview ..................................................................................................................................... 13
1.1.1. Project Information ................................................................................................................. 13
1.1.2 Project Team ............................................................................................................................. 13
1.2. Product Background ................................................................................................................... 13
1.3. Existing Systems .......................................................................................................................... 14
1.3.1 Chuk Tea and Coffee ................................................................................................................. 14
1.3.1.1. Description ............................................................................................................................ 14
1.3.1.2. Functions............................................................................................................................... 14
1.3.1.3. Pros & cons ........................................................................................................................... 14
1.3.2 Twitter Beans Coffee ................................................................................................................ 15
1.3.2.1. Description ............................................................................................................................ 15
1.3.2.2. Functions............................................................................................................................... 15
1.3.2.3. Pros & cons ........................................................................................................................... 15
1.4. Business Opportunity.................................................................................................................. 15
1.5. Software Product Vision ............................................................................................................. 16
1.6. Project Scope & Limitations........................................................................................................ 16
1.6.2. Out of scope ............................................................................................................................. 16
1.6.3. Limitations & Exclusions .......................................................................................................... 16
CHAPTER 2: ............................................................................................................................................ 17
PROJECT MANAGEMENT PLAN .............................................................................................................. 17
2.1. Overview ..................................................................................................................................... 17
2.1.1. Scope & Estimation .................................................................................................................. 17
2.1.2. Project Objectives .................................................................................................................... 17
2.1.3. Project Risks ............................................................................................................................. 18
2.2. Management Approach .............................................................................................................. 19
2.2.1. Project Process......................................................................................................................... 19
2.2.2. Quality Management ............................................................................................................... 19
2.2.2.1. Document ............................................................................................................................. 19
2.2.2.2. Coding ................................................................................................................................... 19
2.2.2.3. Testing................................................................................................................................... 19
2
2.2.3. Training Plan ............................................................................................................................ 20
2.3. Project Deliverables .................................................................................................................... 20
2.4. Responsibility Assignments ........................................................................................................ 21
2.4.1 Role ........................................................................................................................................... 21
2.4.2. Responsibility Assignments ..................................................................................................... 22
2.5. Project Communications............................................................................................................. 22
2.6. Configuration Management ....................................................................................................... 23
2.6.1. Document Management .......................................................................................................... 23
2.6.1.1. Convention............................................................................................................................ 23
2.6.1.2. Management ........................................................................................................................ 23
2.6.2. Source Code Management ...................................................................................................... 23
2.6.2.1. Convention............................................................................................................................ 23
2.6.2.2. Management ........................................................................................................................ 23
2.6.3. Tools & Infrastructures ............................................................................................................ 23
CHAPTER 3: ............................................................................................................................................ 25
SOFTWARE REQUIREMENT SPECIFICATION .......................................................................................... 25
3.1. Product Overview ....................................................................................................................... 25
3.2. User Requirements ..................................................................................................................... 25
3.2.1. Actors ....................................................................................................................................... 25
3.2.2. Major Features......................................................................................................................... 26
3.2.2.1. Guest ..................................................................................................................................... 26
3.2.2.2. Customer .............................................................................................................................. 26
3.2.2.3. Administrator ........................................................................................................................ 27
3.2.2.4. Branch Manager ................................................................................................................... 28
3.2.2. Use Cases ................................................................................................................................. 29
3.2.2.1. Diagram(s) ............................................................................................................................. 29
3.2.2.2. Descriptions .......................................................................................................................... 33
3.3. Functional Requirements............................................................................................................ 38
3.3.1. System Functional Overview ................................................................................................... 38
3.3.1.1. Screens Flow ......................................................................................................................... 38
3.3.1.2. Screen Descriptions .............................................................................................................. 38
3.3.1.3. Screen Authorization ............................................................................................................ 40
3.3.1.4. Entity Relationship Diagram ................................................................................................. 42
3.3.2. Feature Description ................................................................................................................. 43
3.2.1. Register .................................................................................................................................... 43
3.2.2. View the menu ......................................................................................................................... 44
3
3.2.3. View information of Coffee Chain ........................................................................................... 45
3.2.4. View all posts from Coffee Chain ............................................................................................. 46
3.2.5. View information (location, phone number) of each branch.................................................. 47
3.2.6. Login ......................................................................................................................................... 48
3.2.7. Logout ...................................................................................................................................... 50
3.2.8. Forget Password ...................................................................................................................... 51
3.2.9. Change Password ..................................................................................................................... 52
3.2.10. Profile Management: View personal information ................................................................. 53
3.2.11. Profile Management: Update personal information ............................................................. 54
3.2.12. Place an order: Add products to your cart ............................................................................ 56
3.2.13. Place an order: Delete the product in your cart .................................................................... 57
3.2.14. Place an order: Change quantity ........................................................................................... 58
3.2.15. Place an order: Apply voucher ............................................................................................... 59
3.2.16. Place an order: Checkout ....................................................................................................... 60
3.2.17. Cancel order ........................................................................................................................... 62
3.2.18. View all orders ....................................................................................................................... 63
3.2.19. View order details .................................................................................................................. 64
3.2.20. User Management: View all user .......................................................................................... 65
3.2.21. User Management: Enable/disable user account ................................................................. 67
3.2.22. Order Management: View order detail ................................................................................. 68
3.2.23. Branch Management: View all branch .................................................................................. 69
3.2.24. Branch Management: Add branch ........................................................................................ 70
3.2.25. Branch Management: Update Branch ................................................................................... 72
3.2.26. Branch Management: Enable/Disable branch ....................................................................... 73
3.2.27. Product Management: View product .................................................................................... 74
3.2.28. Product Management: Add product...................................................................................... 75
3.2.29. Product Management: Edit product ...................................................................................... 77
3.2.30. Product Management: Enable/Disable product .................................................................... 78
3.2.31. Category Management: View all category ............................................................................ 79
3.2.32. Category Management: Add category .................................................................................. 80
3.2.33. Category Management: Edit category ................................................................................... 82
3.2.34. Category Management: Enable/Disable category................................................................. 83
3.2.35. Post Management: View post ............................................................................................... 84
3.2.36. Post Management: Edit post ................................................................................................. 85
3.2.37. Post Management: Upload post ............................................................................................ 86
3.2.38. Post Management: Delete post ............................................................................................. 87
4
3.2.41. User Management: Add branch manager ............................................................................. 89
3.2.42. Request Management: View request .................................................................................... 90
3.2.43. Request Management: Accept/decline request.................................................................... 91
3.2.44. View orders of their branch ................................................................................................... 92
3.2.45. Receive orders from customers that ordered to their branch .............................................. 94
3.2.46. Approve an order ................................................................................................................... 95
3.2.47. Cancel an order ...................................................................................................................... 96
3.2.48. View information of customers ordering (phone number, name, address) ......................... 97
3.2.49. Branch-self Management: View information of their branch ............................................... 99
3.2.50 Branch product management: Enable/Disable product in the menu of their branch ......... 100
3.2.51. Branch Request Management: Create request ................................................................... 101
3.2.52. Branch Request Management: Edit request ....................................................................... 102
3.2.53. Branch Request Management: Send request ...................................................................... 104
3.2.54. Branch Request Management: Cancel request ................................................................... 105
3.2.55. Branch Request Management: View request detail............................................................ 107
3.2.56. Branch Request Management: Completed request ............................................................ 108
3.2.57. Completed an order ............................................................................................................. 109
3.4. Non-Functional Requirements.................................................................................................. 110
3.4.1 External Interfaces .................................................................................................................. 110
3.4.1.1. User Interfaces .................................................................................................................... 110
3.4.1.2. External Interfaces .............................................................................................................. 111
3.4.2. Quality Attributes .................................................................................................................. 111
3.4.2.1. Usability .............................................................................................................................. 111
3.4.2.2. Reliability ............................................................................................................................ 111
3.4.2.4. Security ............................................................................................................................... 111
3.5. Requirement Appendix ............................................................................................................. 111
3.5.1. Business Rules ........................................................................................................................ 111
3.5.2. Common Requirements ......................................................................................................... 112
3.5.3. Application Messages List ...................................................................................................... 112
CHAPTER 4: .......................................................................................................................................... 114
SOFTWARE DESIGN DESCRIPTION ....................................................................................................... 114
4.1. System Design ........................................................................................................................... 114
4.1.1. System Architecture .............................................................................................................. 114
4.1.2. Component Architecture ....................................................................................................... 115
4.1.2. Package Diagram ................................................................................................................... 117
4.1.3.1. Back-end Package Diagram................................................................................................. 117
5
4.1.2.2. Front-end Package Diagram ............................................................................................... 118
4.2. Database Design ....................................................................................................................... 120
4.2.1. Table Descriptions ................................................................................................................. 120
4.2.1.1. Entity ................................................................................................................................... 120
4.2.1.2. Attribute ............................................................................................................................. 121
4.2.1.2.1. Table Branch .................................................................................................................... 121
4.2.1.2.2. News Branch .................................................................................................................... 122
4.2.1.2.3. Image Info Storage........................................................................................................... 122
4.2.1.2.4. Table Internal User .......................................................................................................... 123
4.2.1.2.5. Table Orders .................................................................................................................... 123
4.2.1.2.6. Table Order Detail............................................................................................................ 124
4.2.1.2.7. Table App Param.............................................................................................................. 124
4.2.1.2.8. Table Category ................................................................................................................. 125
4.2.1.2.9. Table Goods ..................................................................................................................... 125
4.2.1.2.10. Table Coupon ................................................................................................................. 126
4.2.1.2.11. Table Request ................................................................................................................ 126
4.2.1.2.12. Table Request Detail ...................................................................................................... 127
4.2.1.2.13. Table Branch goods disable ........................................................................................... 128
4.3. Detailed Design ......................................................................................................................... 128
4.3.1. Class Diagram ......................................................................................................................... 128
4.3.2. Sequence Diagram ................................................................................................................. 129
4.3.2.1. Login.................................................................................................................................... 129
4.3.2.2. Logout ................................................................................................................................. 130
4.3.2.3. Update personal information ............................................................................................. 130
4.3.2.4. View personal information ................................................................................................. 131
4.3.2.5. Register ............................................................................................................................... 131
4.3.2.6. Add Product ........................................................................................................................ 131
4.3.2.7. Edit Product ........................................................................................................................ 132
4.3.2.8. View Product....................................................................................................................... 132
4.3.2.9. Enable/Disable Product ...................................................................................................... 132
4.3.2.10. Add Category .................................................................................................................... 133
4.3.2.11. Edit Category .................................................................................................................... 133
4.3.2.12. View Category ................................................................................................................... 133
4.3.2.13. Enable/Disable Category .................................................................................................. 134
4.3.2.14. Upload Post....................................................................................................................... 134
4.3.2.15. View Post .......................................................................................................................... 134
6
4.3.2.16. Edit Post ............................................................................................................................ 135
4.3.2.17. Delete Post ........................................................................................................................ 135
4.3.2.18. View Branch ...................................................................................................................... 135
4.3.2.19. Add Branch ....................................................................................................................... 136
4.3.2.20. Enable/Disable Branch...................................................................................................... 136
4.3.2.21. Update Branch .................................................................................................................. 136
4.3.2.22. View Request .................................................................................................................... 137
4.3.2.23. Accept/Decline Request ................................................................................................... 137
4.3.2.24. Completed Request .......................................................................................................... 137
4.3.2.25. Create Request ................................................................................................................. 138
4.3.2.26. Edit Request ...................................................................................................................... 138
4.3.2.27. Send Request .................................................................................................................... 138
4.3.2.28. View information of their branch ..................................................................................... 139
4.3.2.29. Checkout (Create Order) .................................................................................................. 139
4.3.2.30. Cancel an order ................................................................................................................. 139
4.3.2.31. Order management: View order detail ............................................................................ 140
4.3.2.32. Approve an order .............................................................................................................. 140
4.3.2.33. Completed an order.......................................................................................................... 140
4.3.2.34. Receive orders from customers that ordered to their branch ......................................... 141
4.3.2.35. Branch Product management: Enable product in the menu of their branch .................. 141
4.3.2.36. Branch Product management: Disable product in the menu of their branch ................. 141
4.3.2.37. View all orders .................................................................................................................. 142
4.3.2.38. View all orders of their branch ......................................................................................... 142
4.3.2.39. View the menu .................................................................................................................. 142
4.3.2.40. View all posts from Coffee Chain...................................................................................... 143
4.3.2.41. View information (location, phone number) of each branch .......................................... 143
4.3.2.42. Forget Password ............................................................................................................... 143
4.3.2.43. Change Password .............................................................................................................. 144
4.3.2.44. Customer management: View customer .......................................................................... 144
4.3.2.45. Customer management: Enable customer account ......................................................... 145
4.3.2.46. Customer management: Disable customer account ........................................................ 145
CHAPTER 5: .......................................................................................................................................... 146
SOFTWARE TESTING DOCUMENTATION ............................................................................................. 146
5.1. Scope of Testing ........................................................................................................................ 146
5.1.1. Testing Targets ....................................................................................................................... 146
5.1.1.1. Feature, Functional ............................................................................................................. 146
7
5.1.1.2. Non - Functional ................................................................................................................. 146
5.1.1.2.1. User Interface .................................................................................................................. 146
5.1.1.2.2. Security Requirements .................................................................................................... 146
5.1.1.2.3. Usability Requirements ................................................................................................... 146
5.1.1.2.4. Maintainability Requirements ......................................................................................... 146
5.1.2. Testing Levels ......................................................................................................................... 146
5.2. Test Strategy ............................................................................................................................. 147
5.2.1. Testing Types ......................................................................................................................... 149
5.2.2. Test Levels.............................................................................................................................. 151
5.2.3. Supporting Tools .................................................................................................................... 151
5.3. Test Plan .................................................................................................................................... 152
5.3.1. Human Resources .................................................................................................................. 152
5.3.2. Test Environment................................................................................................................... 152
5.3.3. Test Milestones ...................................................................................................................... 152
5.4. Test Cases ................................................................................................................................. 153
5.4.1. Unit Test ................................................................................................................................. 153
5.4.2. Integration Test ..................................................................................................................... 189
5.4.3. System Test ............................................................................................................................ 190
5.5. Test Reports .............................................................................................................................. 201
5.5.1. Unit Test Report ..................................................................................................................... 201
5.5.2. Integration Test Report ......................................................................................................... 202
5.5.3. System Test Report ................................................................................................................ 202
5.5.4. Acceptance Test Report ......................................................................................................... 203
CHAPTER 6: .......................................................................................................................................... 204
RELEASE PACKAGE & USER GUIDES ..................................................................................................... 204
6.1. Deliverable Package .................................................................................................................. 204
6.2. Installation Guides .................................................................................................................... 205
6.2.1. System Requirements ............................................................................................................ 205
6.2.2. Installation Instruction ........................................................................................................... 205
6.2.2.1. Install MySQL ...................................................................................................................... 205
6.2.2.2. Install Coffee Chain Front-end ............................................................................................ 205
6.2.2.2.1. For Development ............................................................................................................. 205
6.2.2.2.2. For Production ................................................................................................................. 206
6.2.2.3. Install Coffee Chain Backend .............................................................................................. 206
6.2.2.3.1. For Development ............................................................................................................. 206
6.2.2.3.2. For Production ................................................................................................................. 208
8
6.3. User Manual .............................................................................................................................. 208
6.3.1. Guest guideline ...................................................................................................................... 208
6.3.1.1. Register ............................................................................................................................... 208
6.3.1.2. View the menu .................................................................................................................... 210
6.3.1.3. About us (View information of Coffee Chain) .................................................................... 211
6.3.1.4. View all posts from Coffee Chain........................................................................................ 212
6.3.1.5. View information (location, phone number) of each branch ............................................ 214
6.3.1.6. Shopping Now ..................................................................................................................... 216
6.3.1.7. Check out ............................................................................................................................ 217
6.3.2. Customer guideline ................................................................................................................ 221
6.3.2.1. Log in ................................................................................................................................... 221
6.3.2.2. Log out ................................................................................................................................ 222
6.3.2.3. Forgot password ................................................................................................................. 223
6.3.2.4. Change Password ................................................................................................................ 225
6.3.2.5. Profile Management ........................................................................................................... 226
6.3.2.5.1. View personal information .............................................................................................. 226
6.3.2.5.2. Update personal information .......................................................................................... 227
6.3.2.6. View the menu .................................................................................................................... 229
6.3.2.7. About us (View information of Coffee Chain) .................................................................... 231
6.3.2.8. View all posts from Coffee Chain........................................................................................ 232
6.3.2.9. View information (location, phone number) of each branch ............................................ 233
6.3.2.11. Check out .......................................................................................................................... 237
6.3.1.12. Order ................................................................................................................................. 240
6.3.3. Administrator guideline ......................................................................................................... 241
6.3.3.1. Log in ................................................................................................................................... 241
6.3.3.2. Log out ................................................................................................................................ 242
6.3.3.3. Forget password ................................................................................................................. 243
6.3.3.4. Change Password ................................................................................................................ 244
6.3.3.6. Order Management ............................................................................................................ 247
6.3.3.6.1. View list of orders ............................................................................................................ 247
6.3.3.7. Customer Management ...................................................................................................... 248
6.3.3.7.1. View list of customers...................................................................................................... 248
6.3.3.7.2. View detail information customer account ..................................................................... 248
6.3.3.8. Branch Management .......................................................................................................... 250
9
6.3.3.8.1. View list of branches........................................................................................................ 250
6.3.3.8.2. Add branch....................................................................................................................... 251
6.3.3.8.3.Enable/Disable branch...................................................................................................... 252
6.3.3.8.4. Update Branch ................................................................................................................. 253
6.3.3.9. Product Management: ....................................................................................................... 255
6.3.3.9.1. View list of products ........................................................................................................ 255
6.3.3.9.2. Add product ..................................................................................................................... 256
6.3.3.9.3.Enable/Disable product .................................................................................................... 257
6.3.3.9.4. Edit product ..................................................................................................................... 258
6.3.3.10. Category Management: ................................................................................................... 260
6.3.3.10.1. View list of a category ................................................................................................... 260
6.3.3.10.2. Add category .................................................................................................................. 261
6.3.3.10.3. Enable/Disable category ................................................................................................ 262
6.3.3.10.4. Edit category .................................................................................................................. 263
6.3.3.11. Post Management: .......................................................................................................... 265
6.3.3.11.1. View list of posts ............................................................................................................ 265
6.3.3.11.2. Add post ......................................................................................................................... 266
6.3.3.11.3. Edit post ......................................................................................................................... 267
6.3.3.12. Branch Manager Management: ....................................................................................... 270
6.3.3.12.1. View list of branch managers ........................................................................................ 270
6.3.3.12.2. Add a branch manager .................................................................................................. 270
6.3.3.12.3. Enable/disable branch manager .................................................................................... 272
6.3.3.13 Request Management ....................................................................................................... 273
6.3.3.13.1. View list of requests ...................................................................................................... 273
6.3.3.13.2 Approve request ............................................................................................................. 274
6.3.3.13.3 Cancel request ................................................................................................................ 276
6.3.4. Branch Manager guideline ..................................................................................................... 278
6.3.4.1 Login..................................................................................................................................... 278
6.3.4.2. Log out ................................................................................................................................ 279
6.3.4.3. Forget password ................................................................................................................. 280
6.3.3.4. Change Password ................................................................................................................ 282
6.3.4.6. Orders Management .......................................................................................................... 284
6.3.4.6.1 View orders of their branch .............................................................................................. 284
6.3.4.6.2. Approve an order ............................................................................................................. 285
10
6.3.4.6.3. Completed an order......................................................................................................... 287
6.3.4.6.4. Cancel an order ................................................................................................................ 289
6.3.4.7. Branch-self Management ................................................................................................... 291
6.3.4.7.1 View information of their branch ..................................................................................... 291
6.3.4.8. Branch product management ............................................................................................. 292
6.3.4.8.1. Enable/Disable product in the menu of their branch ..................................................... 292
6.3.4.9. Branch Request Management ............................................................................................ 293
6.3.4.9.1. Create request ................................................................................................................. 293
6.3.4.9.2. Edit request...................................................................................................................... 295
6.3.4.9.3. Send request .................................................................................................................... 297
6.3.4.9.4. Cancel request ................................................................................................................. 299
6.3.4.9.5. View request detail .......................................................................................................... 302
6.3.4.9.6. Completed request .......................................................................................................... 303
11
Definition and Acronyms
Acronym Definition
CC Coffee Chain
BA Business Analysis
BR Business Rule
ERD Entity Relationship Diagram
GUI Graphical User Interface
PM Project Manager
SDD Software Design Description
SPMP Software Project Management Plan
SRS Software Requirement Specification
UAT User Acceptance Test
UC Use Case
API Application Program Interface
12
CHAPTER 1:
PROJECT INTRODUCTION
1.1. Overview
1.1.1. Project Information
• Project name: Coffee chain
• Project code: CC
• Group name: SEP490-G3
• Software type: Website
1.1.2 Project Team

Full Name Role Email Mobile
Tran Dinh Tri Lecturer tritd@fe.edu.vn 0913091952
Nguyen Tuan Duong Leader duongnthe150423@fpt.edu.vn 0934455456
Le Nguyen Anh Tuan Member tuanlnahe150485@fpt.edu.vn 0399420013
Pham Duc Anh Member anhpdhe150529@fpt.edu.vn 0975516981
Phuong Thanh Huyen Member huyenpthe150576@fpt.edu.vn 0975122951
Phan Duc Manh Member manhpdhe151290@fpt.edu.vn 0338622864
Table 1.1. Project Team
1.2. Product Background

Vietnam is a country that has strong growth F&B market. According to the latest report of
iPOS.vn, a technology management solution provider for the F&B industry, the number of new coffee
shop openings increased by 24.37% over the same period last year. According to the report, the
number of new coffee shops opened in April 2022 is mainly in two big cities, Hanoi and Ho Chi Minh
City. The estimated average daily, number of newly opened shops is about 139.67. Therefore, the
demand for a website to advertise and managing for an F&B brand is increasing highly, with this
demand, our team is going to develop a website that can solve this problem. The website will be
designed to cater to the needs of all stakeholders, including customers, branch managers, and
administrators. One key feature of the website is the request function, which allows branch managers
to send import goods requests directly to the administrator. This feature ensures that each branch has
access to the necessary supplies and ingredients, reducing the risk of stockouts or delays in service. By
streamlining the supply chain, the Coffee Chain can improve efficiency, reduce waste and enhance
profitability.
13
1.3. Existing Systems
1.3.1 Chuk Tea and Coffee
1.3.1.1. Description
Figure 1.1. Description
1.3.1.2. Functions
• Homepage
• Product List, product details
• Order Product
• Shop news, event
• Discount detail
• List Shop detail
• Contact Info page
• Membership
• User Management
1.3.1.3. Pros & cons

● Props
o Easy to use
o Eye-catching UI
● Cons
o Cannot order when shops are closed
o No information of the most seller product
o Product info is insufficient.
14
1.3.2 Twitter Beans Coffee
1.3.2.1. Description
Figure 1.2. Description
1.3.2.2. Functions
• Homepage
• Product List, product details
• Order Product
• Shop news, event
• Discount detail
• List Shop detail
• Contact Info page
• Membership
• Franchise offer
1.3.2.3. Pros & cons

● Props
o Eye-catching UI
● Cons
o Have no account function (Log in, log out…)
o Bad UX (Cannot see many components at once. Ex: cannot view the cart when order
a product), map is not working.
1.4. Business Opportunity

For those who want to franchise their brand, to be able to manage branches easier. This
website will help beverage service chains to advertise their products, help customers understand the
products easily, find branches near their locations, buy long shelf-life products online. It makes it easier
for customers to find your chain's branches near them, as well as makes it easier for customers to
know and understand your products. For chain managers, they can easily update the menu, as well as
post changes, so that customers can more easily update information, receive requests from each
branch. Moreover, the manager of each branch can get order online to make order and contact to the
shipping unit, create an import request to the admin.
15
1.5. Software Product Vision
Instead of searching each branch of a coffee chain in google and comparing which branch is
the nearest branch by their place and searching the opening hours of this branch, now the Coffee
Chain will help them to find the nearest branch, check if the branch is opening or not and give the
phone number of the branch easily. This website accepts buying long life-shelf products and shipping
to their place or the location that they want so that they don’t need to go out to buy just a cup of
drink. Moreover, customers can also check the menu for new updates, or find the information about
the coffee chain they need without contacting the brand or branches. For branch managers, Coffee
Chain provides a streamlined system for ordering and importing goods from the chain's storage.
Branch managers can easily send a request for goods through the platform, which is then reviewed
and approved by the administrator. This ensures that all branches have the necessary supplies
1.6. Project Scope & Limitations

Our team will build a software system, a web-based application called Coffee Chain
After researching and discussing, we decided that there are four groups of users in the
system: guest, customer, administrator, branch manager. Each role has a different level of
access to the system.
• Guest role: allowed to register, view information of Coffee Chain, view the menu and post of
Coffee Chain, add goods to the cart.
• Customer role: allowed to log in/log out, view information of Coffee Chain, view the menu
and post of Coffee Chain, add goods to the cart and checkout, view their orders and order
detail.
• Administrator role: allowed to log in/log out, manage user, manage product, manage
category, manage branch, manage order, approve/decline request, manage news.
• Branch manager role: allowed to login/log out, receive order from the customer, manage
their branch product, create request.
1.6.2. Out of scope

Due to the limitation of time and ability, CC will not contain these following functions:
• Manage storage
• Translate website into English
1.6.3. Limitations & Exclusions
LI-1: The price for each size is fixed and increases in percentages
LI-2: Choose the branch to order only can choose the branch in the same district
LI-3: Products have only two types which are having size and not having size
LI-4: Customers cannot make notes for each product or order
16
CHAPTER 2:
PROJECT MANAGEMENT PLAN
2.1. Overview
2.1.1. Scope & Estimation
Figure 2.1. Scope & Estimation
2.1.2. Project Objectives

• Timeliness (%): 80%
• Defect Distribution:
Testing Stage Test Coverage No. of Defects % of Defect Notes

#
1 Reviewing 100% 250 71.43%
2 Unit Test 100% 52 14.86%
3 Integration Test 100% 33 9.43%
4 System Test 100% 15 4.28%
5 Acceptance Test 100% 0 0%
Table 2.1. Quality
• Project management
17
# Objectives
1 All Iteration objectives have been completed
2 Project will be finished before April 16 2023
Table 2.2. Project management
• Allocated Effort
# Members Weekdays Weekends
1 Nguyễn Tuấn Dương 6 hours 6 hours
2 Lê Nguyễn Anh Tuấn 6 hours 6 hours
3 Phạm Đức Anh 6 hours 6 hours
4 Phương Thanh Huyền 6 hours 6 hours
5 Phan Đức Mạnh 6 hours 6 hours
Table 2.3. Allocated Effort
2.1.3. Project Risks

# Risk Description Impact Possibility Response Plans
The project team Working overtime to complete task on
1 High High
misses the deadline time
Technical professional needs to support
Having difficulty team members in a group to increase
2 using new Medium Medium required skill and knowledge. Review
technologies complete tasks to make comments for
team members
A team member can do work after busy
Team member is
times with more effort or other members
3 sick or busy with High Medium
can assist in completing the unfinished
personal work
functions
The members
Discuss with customer to clear
4 misunderstood the High Medium
requirement
requirement
Change in The supervisor and the entire team must
5 High High
requirements review any new updates to requirements
Table 2.4. Project Risks
18
2.2. Management Approach
2.2.1. Project Process
Figure 2.2. Iterative and Incremental model
In this project, we apply Iterative and Incremental model as development process model. Iterative
and Incremental model is a process where creating requirements, designing, building and testing a
system in small parts. This help to make modules very easily. In this model, the module passes
through some phases like planning, requirements, analysis and design, coding, testing and
evaluation.
The reasons that we choose Iterative and Incremental model are:

- Can develop prioritized requirements first.
- Initial product delivery is faster.
- Requirement changes can be easily accommodated.
- Easier to test and debug during a smaller iteration.
- Less risky, handle risk easily because creating software in parts.
2.2.2. Quality Management

2.2.2.1. Document
1. The document must follow the template of the project document
2. Portions of the document will be carefully reviewed and evaluated by the leadership of each
role
3. The document is public so that all team members can know the content of each part of the
document
2.2.2.2. Coding
1. All members must code according to standard Coding conventions to make the code easy to
read and understand, thus easier to manage and maintain.
2. Use Java8 and ReactJS programming languages for best coding practice.
2.2.2.3. Testing
1. Integration testing and System testing after implementing key functions.
2. The person in charge has to prepare test cases suitable for the system, design the
architecture and cover all those cases.
19
3. After completing each iteration, the customer will conduct an inspection and evaluation.
2.2.3. Training Plan

Training Area Participants When, Duration Waiver Criteria
Java Spring Boot Nguyen Tuan Duong During project Mandatory
Git, Github All members During project Mandatory
NextJs Phan Duc Manh During project Mandatory

Table 2.5. Training Plan
2.3. Project Deliverables

# Deliverable name Delivery date Verified Notes
by
Initiation Phase
1. Report 1 - Project Introduction 02/03/2023 Instructor
Planning Phase
2. Report 2 - Project Management We 1/31/23 Instructor

Plan
Iteration 1
3. Report 3 - Software Su 2/5/23 Instructor

Requirement Specification v1.0
4. Report 4 - Software Design Tu 2/7/23 Instructor

Document v1.0
5. Test plan v1.0 Th 3/9/2023 Instructor
6. Test case v1.0 Sa 3/11/2023 Instructor
7. Report of test result Mo 3/13/2023 Instructor
Iteration 2
8. Report 3 - Software Th 3/16/2023 Instructor

Requirement Specification v1.5
9. Report 4 - Software Design Fr 3/17/2023 Instructor

Document v1.5
10. Test plan v1.5 Sun 4/2/2023 Instructor
11. Test case v1.5 Mo 4/3/2023 Instructor
20
12. Report of test result We 4/5/2023 Instructor
Table 2.6. Project Deliverables
2.4. Responsibility Assignments

2.4.1 Role
Figure 2.3. Role
Organization structure above includes 4 sub-teams: Documentation sub-team, Analysis & Design
sub-team, Coding sub-team and Testing sub-team. Each sub-team has a sub-team leader and team
members.
This is the detail description about role and responsibility of each role in the organization structure:
Role Name Responsibility
Give instruction for the project team

Supervisor Tran Dinh Tri Verify deliverables
Supervise project team’s status
Have overall responsibility of the
project
Assign task to members
Project Manager Nguyen Tuan Duong
Tracking member’s work
Report working status to the
instructor
21
Documentation Sub-team Responsible for the progress of the
Nguyen Tuan Duong
Leader document
Analysis and Design Sub-team Responsible for create/design
Phan Duc Manh
Leader database design
Decide technique and tools to be used
Train other members about web
Coding Sub-team Leader Le Nguyen Anh Tuan development
Keeping track of development work
done by other members
Create test plan
Testing Sub-team Leader Phuong Thanh Huyen
Responsible for test plan
Table 2.7. Role and Responsibility
2.4.2. Responsibility Assignments

D~Do; R~Review; S~Support; I~Informed; <blank>- Omitted
DuongNT HuyenPT
TuanLNA AnhPD ManhPD
Responsibility HE15042 HE15057
HE150485 HE150529 HE51290
3 6
Project Planning &
D D, R S S I
Tracking
Prepare Project
Introduction D S S D, R S
Document
Prepare SRS
Document R D S S R
(Overview Part)
Prepare SRS
Document (User D R S S R
Requirements)
Code Back-End S D, R D I I
Code Front-End I R D I D
Prepare Test
Document and D S S D, R S
Report
Prepare User
D, R S, R S D S
Guides
Prepare Final
Report (all
D, R S, R I D I
document and
presentation slide)
Table 2.8. Responsibility Assignments
2.5. Project Communications

When, Type, Tool,
Communication Item Who/ Target Purpose
Frequency Method(s)
22
All team 10:00 am
Weekly meeting with Review report and Offline - At
members every
Supervisor document school
Supervisor Friday
8:00 pm on
every Online -
Review and create a
All team Tuesday, Google
Daily team meeting work plan for the next
members Thursday meet
day
and
Saturday
Online -
All team When
Discuss and solve Google
members anyone has
Unscheduled meeting important problems or meet
Supervisor important
new requirement Offline - At
problems
school
Table 2.9. Project Communications
2.6. Configuration Management

2.6.1. Document Management
2.6.1.1. Convention
1. The name of all reports must begin with SWP490_G3.
2. All documents must have a name that represents the content of the document.
3. If the document is edited, it will be marked with each version (Ex: version 1.x - x is the
version of the document).
4. The content of all documents must begin with the school's logo and name.
2.6.1.2. Management
5. Tools: OneDrive, Google Drive, Jira Software
6. Documents and reports sent to the supervisor via email and link drive.
2.6.2. Source Code Management

2.6.2.1. Convention
1. The source code is managed by GitHub
2. All members building the functionality need to fork their own branch from the master
branch
3. The merging of code into the master branch must be carefully reviewed by the developers
4. All developers must perform unit tests and code reviews before creating a merge request.
2.6.2.2. Management
1. Deployment management on Netlify Platform
2. Only team members have the permission to deploy code
2.6.3. Tools & Infrastructures

Logo
Category Tools / Infrastructure
NextJS/Tailwind (Front-End), Java Spring Boot

Technology
(Back-End)
23
Database MySQL
IDEs/Editors Visual Studio Code, IntelliJ, MySQL workbench
Diagramming Astah, DrawIO
Documentation Ms Office
GitHub (Source Codes), Google Drive/OneDrive

Version Control
(Documents)
Deployment
Netlify Platform
server
Project Google Calendar (Schedule), Jira Software (Tasks,
management Defects)
Communication
Messenger, Google meet, Gmail
tools
Table 2.10. Tools & Infrastructures
24
CHAPTER 3:
SOFTWARE REQUIREMENT SPECIFICATION
3.1. Product Overview
The Coffee Chain (CC) is a website that helps customers easily find information about the
coffee chain as well as order online. The context diagram below illustrates the external entities and
system interfaces for release 1.0. The system is expected to fully support the customer to place an
order online and find information about the coffee chain
Figure 3.1. Coffee Chain Context Diagram
3.2. User Requirements

3.2.1. Actors
# Actor Description
1 Guest User not login in system
2 Customer User login system by an account as customer
3 Administrator User login system by an account who manage all the system
4 Branch Manager User login system by an account who manage a branch of coffee chain
Table 3.1. Actors
25
3.2.2. Major Features
3.2.2.1. Guest
FE-1: Register
FE-2: View the menu
FE-3: View information of Coffee Chain
FE-4: View all posts from Coffee Chain
FE-5: View information (location, phone number) of each branch
FE-6: Place an order: Add products to your cart
FE-7: Delete the product in your cart
FE-8: Change quantity
FE-9: Apply voucher
3.2.2.2. Customer
FE-10: Log in
FE-11: Log out
FE-12: Forget Password
FE-13: Change Password
FE-14: Profile Management: View personal information
FE-15: Update personal information
FE-16: View the menu
FE-17: View information of Coffee Chain
FE-18: View all posts from Coffee Chain
FE-19: View information (location, phone number) of each branch
FE-20: Place an order: Add products to your cart
FE-21: Delete the product in your cart
FE-22: Change quantity
FE-23: Apply voucher
FE-24: Checkout
FE-25: Cancel order
FE-26: View all orders
FE-27: View order details
26
3.2.2.3. Administrator
FE-28: Log in
FE-29: Log out
FE-33: Order Management: View order detail
FE-34: User Management: View all user
FE-35: Enable/disable user account
FE-36: Add user branch manager role
FE-37: Branch Management: View all branch
FE-38: Add branch
FE-39: Enable/Disable branch
FE-40: Update Branch
FE-41: Product Management: View all product
FE-42: Add product
FE-43: Enable/Disable product
FE-44: Edit product
FE-45: Category Management: View all category
FE-46: Add category
FE-47: Enable/Disable category
FE-48: Edit category
FE-49: Post Management: View all post
FE-50: Edit post
FE-51: Upload post
FE-52: Delete post
FE-53: Request Management: View all request
FE-54: Accept/decline request
27
3.2.2.4. Branch Manager
FE-55: Log in
FE-56: Log out
FE-60: View orders of their branch
FE-61: Receive orders from customers that ordered to their branch
FE-62: Approve an order
FE-63: Completed an order
FE-64: Cancel an order
FE-65: View information of customers ordering (phone number, name, address)
FE-66: Branch-self Management: View information of their branch
FE-67: Branch product management: Enable/Disable product in the menu of their branch
FE-68: Branch Request Management: Create request
FE-69: Edit request
FE-70: Send request
FE-71: Cancel request
FE-72: View request detail
FE-73: Completed request
28
3.2.2. Use Cases
3.2.2.1. Diagram(s)
Figure 3.2. Use Cases Diagram
29
Figure 3.3. Use Cases Diagram – Guest Use Case
30
Figure 3.4. Use Cases Diagram – Customer Use Case
31
Figure 3.5. Use Cases Diagram – Administrator Use Case
32
Figure 3.6. Use Cases Diagram – Branch Manager Use Case
3.2.2.2. Descriptions
ID Use Case Actors Use Case Description
1 Register Guest User registers to have an account
2 View the menu Guest, Customer User can view the menu of Coffee
Chain
3 View information of the Coffee Guest, Customer User can view the information of
Chain Coffee Chain
4 View all posts from Coffee Guest, Customer User can view all posts from Coffee
Chain Chain
33
5 View information (location, Guest, Customer User can view all information of each
phone number) of each branch branch of Coffee Chain
6 Log in Customer, User can login to the system

Administrator,
Branch Manager
7 Log out Customer, User can logout of the system

Administrator,
Branch Manager
8 Forget Password Customer User can reset the password of their

account if they forget the password
9 Change Password Customer, User can change their password

Administrator,
Branch Manager
10 Profile management: View Customer, Customer can view their personal

personal information Administrator, information
Branch Manager
11 Profile management: Update Customer, Customer can update their personal

personal information Administrator, information
Branch Manager
12 Place an order: Add products Guest, Customer User can add products to their cart
to your cart
13 Place an order: Delete the Guest, Customer User can delete products in their cart
product in your cart
14 Place an order: Change Guest, Customer User can change the quantity of each
quantity product in their cart
15 Place an order: Apply voucher Guest, Customer User can apply voucher
16 Place an order: Checkout Customer Customer can check out the products
they chose after filling all the needed
information
34
17 Cancel order Customer, Branch Customer can cancel orders within 2
Manager hours after payment
18 View all orders Customer Customer can view all of their orders
19 View order details Customer Customers can view the order details
of each order
20 Product management: View Administrator Administrator can view product of

product Coffee Chain
21 Category management: View Administrator Administrator can view all category of

all category Coffee Chain
22 Branch management: View all Administrator Administrator can view all branch of
branch Coffee Chain
23 Post management: View all Administrator Administrator can view all post of
post Coffee Chain
24 Order management: View Administrator Administrator can view order detail of

order detail any order
25 User management: View all Administrator Administrator can view all users of
user Coffee Chain
26 User management: Administrator Administrator can enable or disable

Enable/Disable user account user account
27 Branch Management: Add Administrator Administrator can add a new branch

branch
28 Branch Management: Administrator Administrator can enable or disable

Enable/Disable branch branch
29 Product Management: Add Administrator Administrator can add a new product

product
30 Product Management: Administrator Administrator can enable or disable

Enable/Disable product product
31 Product Management: Edit Administrator Administrator can edit product

product
35
32 Category Management: Add Administrator Administrator can add a new category
category
33 Category Management: Administrator Administrator can enable or disable

Enable/Disable category category
34 Category Management: Edit Administrator Administrator can edit category

category
35 Post Management: Upload Administrator Administrator can upload a new post

post
36 Post Management: Edit post Administrator Administrator can edit post
37 Post Management: Delete post Administrator Administrator can delete post
38 User Management: Add branch Administrator Administrator can add a new branch
manager manager
39 Request Management: View Administrator, Administrator can view the request

request detail Branch Manager from branch managers
40 Request Management: Administrator Administrator can accept or decline

Accept/decline request export request from branch managers
41 View orders of their branch Branch Manager Branch Manager can view order of
their Coffee Chain branch
42 Receive orders from customers Branch Manager Branch Manager can receive orders
that ordered to their branch from customers that ordered to their
branch
43 View information of customers Branch Manager Branch Manager can view information
ordering (phone number, of customers ordering of their Coffee
name, address) Chain branch
44 Request Management: Update Administrator Administrator can edit information of

branch any branch
45 Branch-self management: view Branch Manager Branch Manager can view information
information of their branch of their Coffee Chain branch
36
46 Branch Product management: Branch Manager Branch Manager can enable or disable
Enable/Disable product in the product in the menu their Coffee
menu of their branch Chain branch
47 Branch Request Management: Branch Manager Branch Manager can create export
Create request request
48 Branch Request Management: Branch Manager Branch Manager can edit their
Edit request request before sent it
49 Branch Request Management: Branch Manager Branch Manager can send their export
Send request request
50 Branch Request Management: Branch Manager Branch Manager can cancel their
Cancel request request
51 Branch Request Management: Branch Manager Branch Manager confirm that they
Completed request received the goods
52 Approve An Order Branch Manager Branch Manager approve that order

already done and ready to ship
53 Completed An Order Branch Manager Branch Manager change the status of

order to completed
Table 3.2. Descriptions
37
3.3. Functional Requirements
3.3.1. System Functional Overview
3.3.1.1. Screens Flow
Figure 3.7. Screen flow
3.3.1.2. Screen Descriptions

# Screen Description
1 Landing Page Marketing page of Coffee Chain
2 Login Screen for user can login (only for customer role)
3 Forget Password Screen for user reset their password
4 Register Screen for user create a new account
5 Menu Menu page of Coffee Chain
6 Post Post of Coffee Chain
7 About Us Information about the Coffee Chain
8 All Branch Screen view information of each branch and find the branch
nearby
9 Profile View your personal information
10 Change Password Screen for user can change their password
11 Update personal Update your personal information

information
38
12 Orders View list of your orders
13 Order Details View order details of an order
14 Checkout Customer cart checkout screen
15 Admin Dashboard Dashboard of admin
16 Branch Manager Dashboard of branch manager

Dashboard
17 Order Management View list of all orders
18 View order View order details of an order
19 User Management View list of Users
20 View user View information of a user
21 Branch Management View list of branches
22 Add branch Add a new branch
23 View branch View information of a branch
24 Product Management View list of products
25 View product View information of a product
26 Edit product Edit information of a product
27 Add product Add a new product
28 Category Management View list of categories

29 View category View information of a category
30 Edit category Edit information of a category
31 Add category Add a new category
32 Post Management View list of posts
33 View post View detail of a post
34 Edit post Edit a post
35 Upload post Upload new post
36 Branch order View list of orders of your branch

management
37 Receive order Receive order from customer
38 View branch’s order View order details of an order
39 View information of View information of the customer who placed that order
order
40 Branch Profile Information of your branch
39
41 Edit branch Edit any branch information
42 Branch’s product View list of your branch product

Management
43 View branch’s product View information of a product
44 Branch Request View list of requests in your branch storage

Management
45 Create new request Create a new request
46 View created requests View created request
47 Edit request Edit a request
48 Request Management View the list of requests sent to the admin
49 View all request View a list of requests from branch manager
50 View detail of a View detail of a request

request
51 Internal User Login Screen for user can login (only for administrator and Branch
manager)
Table 3.3. Screen Descriptions
3.3.1.3. Screen Authorization

# Branch
Customer Administrator Manager
Screen Guest
1 Landing Page x
x
2 x x x
Login
3 Forget Password x
4 Register x
5 Menu x x
6 Post x x
7 About Us x x
8 All Branch x x
9 Profile x x x
10 Change Password x x x
11 Update personal
information x x x
12 Orders x
13 Order Details x
40
14 Checkout x
15 Admin Dashboard x
16 Branch Manager
Dashboard x
17 Order Management x
18 View order detail x
19 User Management x
20 View user x
21 Branch Management x
22 Add branch x
23 View branch x
24 Product Management x
25 View product x
26 Edit product x
27 Add product x
28 Category
Management x
29 View category x
30 Edit category x
31 Add category x
32 Post Management x
33 View post x
34 Edit post x
35 Upload post x
36 Branch order
management x
37 Receive order x
38 View branch’s order x
39 View information of
orderer x
40 Branch Profile x
41 Edit branch x
41
42 Branch’s product
Management x
43 View branch’s product x
44 Branch Request
Management x
45 Create new request x
46 View created requests x
47 Edit request x
48 Request Management x
49 View all request x
50 View detail of a
request x x
51 Internal User Login x

Table 3.4. Screen Authorization
3.3.1.4. Entity Relationship Diagram
Figure 3.8. Entity Relationship Diagram
Entities Description
# Entity Description
01 branch Description branch
02 internal_user Description internal user account’s information
03 orders Description of the customer's order
04 order_detail Description order detail of order
42
05 app_param Description configuration
06 category Description categories
07 goods Description goods
08 coupon Description coupon
09 request Description requests from branch
10 request_detail Description request detail of request
11 news Description news
12 image_info Description image info
13 branch_goods_disable Description branch goods disable
Table 3.5. Entities Description
3.3.2. Feature Description

3.2.1. Register
USE CASE-01
Use-case No. <UC01> Use-case Version <1.1>
Use-case Name Register
Author DuongNT
Date 4/2/2023 Priority High
Actor Guest
Description User registers to have an account
Triggers Click “Login” button
Click “Register” button
Preconditions User accesses to the website
Post Conditions User registers successfully to the website and go to log in screen
User’s account is saved to the database
Main Success Scenario
Step Actor Event System response
1 Click “Login” tab on the

header
2 Redirect to “Login” page
43
3 Click “Register” button
4 Redirect to “Register” page
5 Fill in all the required

information and then click
the “register” button
6 User profile saved in the database
Alternative Scenario
# Action Use case
N/A
Exceptions Exception Message Caught

code
400 Bad request Can't connect to database
Business Rules Code Rule
BR-1 The email used for register must match the email format
BR-2 Each registered account will correspond to only 1 of their mail
Table 3.6. Register
3.2.2. View the menu

USE CASE-02
Use-case Name View the menu
Author HuyenPT
Actor Guest, Customer
Description User can view the menu of Coffee Chain
Click “Menu” button
Post Conditions User accesses to “Menu” page
44
1 Click “Menu” button on the

header
2 Redirect to “Menu” page
# Action Use case
N/A

code
N/A
Table 3.7. View the menu
3.2.3. View information of Coffee Chain

USE CASE-03
Use-case Name View information of the coffee chain
Author DuongNT
Date 4/2/2023 Priority Low
Description User can view information of the coffee chain
Triggers Click “About Us” button
Post Conditions User accesses to “About Us” page
45
1 Click “About Us” button on
the header
2 Redirect to “About Us” page
# Action Use case
N/A

code
N/A
Table 3.8. View information of Coffee Chain
3.2.4. View all posts from Coffee Chain

USE CASE-04
Use-case Name View all posts from Coffee Chain
Author DuongNT
Description User can view all posts from the Coffee Chain
Triggers User accesses to the “News” page
Click any posts in “News” page
Post Conditions User see all the posts of Coffee Chain
1 Click “News” tab on the

header
46
2 Redirect to “News” page
3 Click any posts in “News”

page
4 Redirect to “News Detail” page and list all
information of post detail
# Action Use case
N/A

code
N/A
Table 3.9. View all posts from Coffee Chain
3.2.5. View information (location, phone number) of each branch

USE CASE-05
Use-case Name View information (location, phone number) of each branch
Author DuongNT
Description User can view information of each branch
Triggers Click “Branch” button
Click the branch in the branch list that they want to see the information
Post Conditions User can view all the information of the branch
47
1 Click “Branch List” tab on the
header
2 Redirect to “Branch List” page
3 Click the branch in “Branch

List” that they want to see the
information
4 A pop-up box appears above the node that
they clicked (included name of the branch,
phone number, address, ...)
5 Click “Detail” button in the

pop-up box
6 Redirect to the detail page of that branch that

have all the information
# Action Use case
N/A

code
401 Unauthorized User has not logged in yet
N/A
Table 3.10. View information (location, phone number) of each branch
3.2.6. Login
USE CASE-06
Use-case Name View information (location, phone number) of each branch
Author DuongNT
Actor Customer, Administrator, Chain Manager, Branch Manager
48
Description User logs in to system
Triggers Click button “Login”
User has an account
User hasn’t logged in to the system yet
Post Conditions User logs in successfully and go to homepage screen or dashboard (base on
actor)
1 Click “Login” button
2 Use email to login
3 Get into the homepage or dashboard screen

(base on actor)
# Action Use case
N/A

code
401 Unauthorized Invalid token
403 Forbidden Users do not have permission on this page
BR-4 Check account:
-Check username format
-Check password format
Table 3.11. Login
49
3.2.7. Logout
USE CASE-07
Use-case Name Logout
Author DuongNT
Actor Customer, Administrator, Chain Manager, Branch Manager
Description User log out the system
Triggers Click the “logout” button
Preconditions User has logged into the system
Post Conditions Log out successfully and go to homepage screen
1 Click avatar icon
2 Select "Logout"
3 Return to the Homepage screen
# Action Use case
N/A

code
N/A
50
Table 3.12. Logout
3.2.8. Forget Password

USE CASE-08
Use-case Name Forget Password
Author DuongNT
Actor Customer
Description User forgets their password and wants to reset password
Triggers Click “Login” tab
Click “Forget Password” button
User has an account
Post Conditions Reset password successfully and go to log in screen
New password is saved to the database
1 Click “Login” tab on the

header
3 Click “Forget Password”

button
4 Redirect to “Forget Password” page
5 Enter your email and click

“Get your password”
6 Redirect to “Login” page and send user an email

includes reset password link
7 User clicks the link in mail
8 Redirect to “Reset Password” page
51
9 User enter “new password”
and “re-enter password”
then click “change
password”
# Action Use case
N/A

code
BR-5 Users need to verify the owner of the mail that they have
registered
Table 3.13. Forget Password
3.2.9. Change Password

USE CASE-09
Use-case Name Change Password
Author DuongNT
Actor Customer, Administrator, Branch Manager
Description User can change their password
Triggers Click avatar icon
Click “Change Password” tab
Post Conditions User change password successfully
52
1 Click avatar icon
2 Redirect to “My Personal Information” page
3 Click “Change Password” tab
4 Redirect to “Change Password” page
5 Enter “Old Password”, “New

Password” and “Re-enter
New Password” then click the
“Change Password” button
6 New Password saved in the database
# Action Use case
N/A

code
BR-22 The user needs to enter the correct old password
BR-6 User have to confirm by email
Table 3.14. Change Password
3.2.10. Profile Management: View personal information

USE CASE-10
Use-case Name View personal information
53
Author DuongNT
Description Customer can view their profile
Triggers Click avatar icon or “My Personal Information” tab
Post Conditions Show all information of user
1 Click avatar icon
# Action Use case
N/A

code
BR-7 User information must be strictly confidential
Table 3.15. Profile Management: View personal information
3.2.11. Profile Management: Update personal information

USE CASE-11
Use-case Name Update personal information
Author HuyenPT
54
Description Customer can update profile
Triggers Click avatar icon or “My Personal Information” tab
Post Conditions Information’s customer change and update
1 Click avatar icon
3 Edit, update information

then clicks button “Update”
4 Update profile’s user to database
5 Return new profile
# Action Use case
N/A

code
BR-23 Check user information:
- If the information is not in the correct format or has an error,

the system will notify you
Table 3.16. Profile Management: Update personal information
55
3.2.12. Place an order: Add products to your cart
USE CASE-12
Use-case Name Add products to your cart
Author HuyenPT
Description User adds a product to the cart
Triggers Click “Add to your cart”
Post Conditions Add product to cart with quantity equal to 1
1 Click “Shopping” tab
2 Redirect to “Shopping” page
3 Click “Add to your cart” button

of the product you want
4 The product has been successfully added to
the cart
# Action Use case
N/A

code
40 Bad request
56
BR-8 Products are added to cart must be available and enabled
Table 3.17. Place an order: Add products to your cart
3.2.13. Place an order: Delete the product in your cart

USE CASE-13
Use-case Name Delete the product in your cart
Author DuongNT
Description User deletes a product from cart
Triggers Click “Remove from your cart”
User has products in the cart
Post Conditions Remove a product from the cart
1 Click “Cart” icon on the header
2 Cart appears in the right side of the website
3 Click “Remove from your cart”

button in the product that
user wants to remove
4 Remove the product from cart successfully
# Action Use case
N/A

code
57
BR-24 Products are deleted to cart must be available
Table 3.18. Place an order: Delete the product in your cart
3.2.14. Place an order: Change quantity

USE CASE-14
Use-case Name Change quantity
Author DuongNT
Description User can change the quantity of products in the cart
Triggers Click “+”, “-” or enter the number in the quantity box
Post Conditions The quantity of products in the cart has been changed
1 Click “Cart” icon on the

header
2 Cart appear in the right side of the website
3 Click “+” or “-” or enter the

number you want
4 The number of products has been changed to
successfully
58
# Action Use case
N/A

code
BR-25 Products are changed quantity to cart must be available
Table 3.19. Place an order: Change quantity
3.2.15. Place an order: Apply voucher

USE CASE-15
Use-case Name Apply voucher
Author DuongNT
Description User can apply voucher
Triggers Enter the code
Click “Apply” button
Post Conditions User successful applies voucher code
59
2 Cart appears in the right side of the

website
3 Enter voucher code and click

“apply” button
4 Successful user applies voucher code
# Action Use case
N/A

code
403
N/A
Table 3.20. Place an order: Apply voucher
3.2.16. Place an order: Checkout

USE CASE-16
Use-case Name Checkout
Author DuongNT
Actor Customer
Description User checks out
Triggers Click “Checkout” button
60
Post Conditions User checkout successful
2 Cart appear in the right side of the website
3 Click “Chose shopping method”

button
4 Redirect to “Checkout” page
5 Enter all needed information

then click “checkout” button
6 Checkout successful
7 Redirect to “Order Management” page
# Action Use case
N/A

code
BR-9 Customers have to fill in the necessary information and then

make the payment
Table 3.21. Place an order: Checkout
61
3.2.17. Cancel order
USE CASE-17
Use-case Name Cancel order
Author DuongNT
Actor Customer
Description User has logged into the system
User can cancel an order
Triggers Click “Cancel” button
Chose the reason and confirm again
User has orders with status “pending”
Post Conditions User cancel an order successfully
1 Click avatar icon
3 Click “Order Management”

tab
5 Click the “Cancel order”

button in the order you
want to cancel that have
“pending” status
6 Popup “reason cancel the order” box appear
7 Enter the reason then click

“Confirm”
8 Cancel the order successful
62
# Action Use case
N/A

code
401 Unauthorize User has not logged in yet

d
BR-10 The order cannot be canceled if it is 2 hours after placing the

order and have “pending” status
Table 3.22. Cancel order
3.2.18. View all orders

USE CASE-18
Use-case Name View all orders
Author DuongNT
Actor Customer
Description User has logged into the system
User can view all orders
Triggers Click “My Personal Information” tab on header
Click “Order Management” tab
Post Conditions User sees all the orders
63
tab on “My Personal
Information” tab on header
2 Redirect to “My Order” page

tab
# Action Use case
N/A

code
BR-11 Customers can see the orders they have ordered
Table 3.23. View all orders
3.2.19. View order details

USE CASE-19
Use-case Name View all orders
Author DuongNT
Actor Customer
Description User can view order detail
Triggers Click “Order Management” tab
Click “Order Detail” button
64
Post Conditions User view order detail
1 Click “Order Detail” button on

“Order Management” tab
2 Redirect to “Order Detail” page
# Action Use case
N/A

code
Table 3.24. View order details
3.2.20. User Management: View all user

USE CASE-20
Use-case Name User Management: View all user
Author HuyenPT
Actor Administrator
Description Administrator can view all users
Triggers Click “User Management” tab on header
65
Click on the row corresponding to each customer
Post Conditions Administrator can view all customers
1 Click “User Management”

tab on the header
2 Redirect to “User Management” page and list all

information of users
3 Click to choose role on

filter bar

information of users according to chosen role
5 Click on the row

corresponding to each user
6 Redirect to “User Detail” page and list all

information of user detail
# Action Use case
N/A

code

d
BR-13 User’s information must be strictly confidential
Table 3.25. User Management: View all users
66
3.2.21. User Management: Enable/disable user account
USE CASE-21
Use-case Name User Management: Enable/disable user account
Author HuyenPT
Actor Administrator
Description Administrator can enable/disable all users
Triggers Click on the row corresponding to each user
Click “Enable/Disable” button
Post Conditions User account is enabled/disabled

tab on the header

3 Click to choose role on

filter bar

information of users according to chosen role
5 Choose account to
enable/disable
6 Click “Enable/Disable”
button
7 Enabled/Disabled user detail account saved in
the database
8 Redirect to “User Detail” page
67
# Action Use case
N/A

code

d
BR-14 Check customer information:
-If the information is not in the correct format or has an error,

Customer’s information must be strictly confidential
Table 3.26. User Management: Enable/Disable user account
3.2.22. Order Management: View order detail

USE CASE-22
Use-case Name Order Management: View order detail
Author HuyenPT
Actor Administrator
Description Administrator views order detail
Triggers Click “Order” tab on header
Click on the row corresponding to each order
Post Conditions Administrator can view order detail
68
1 Click “Order” tab on the
header
2 Redirect to “Order” page and list all information

of orders
3 Click on the row

corresponding to each
order
4 Redirect to “Order Detail” page and list all

information of order detail
# Action Use case
N/A

code
401
403
BR-15 Check manager information:
- If the information is not in the correct format or has an error,

Table 3.27. Order Management: View order detail
3.2.23. Branch Management: View all branch

USE CASE-23
Use-case Name Branch Management: View all branch
Author HuyenPT
Date 8/2/2023 Priority Medium
Actor Administrator
Description Administrator view all branch
69
Triggers Click “Branch” tab on header
Click on the row corresponding to each branch
Post Conditions Administrator view all branch
1 Click “Branch” tab on the

header
2 Redirect to “Branch” page and list all

information of branches
3 Click on the row

branch
4 Redirect to “Branch Detail” page and list all

information of branch detail
# Action Use case
N/A

code

d
N/A
Table 3.28. Branch Management: View all branch
3.2.24. Branch Management: Add branch

USE CASE-24
70
Use-case Name Branch Management: Add branch
Author HuyenPT
Actor Administrator
Description Administrator adds branch
Triggers Click “Branch” icon
Click “Add” button
Post Conditions Administrator adds branch

header

3 Click “Add” button
4 Redirect to “Add Branch” page and list all blank

information field of branch
5 Fill in all information and

then click the “Save”
button
6 New branch saved in the database
Redirect to “Branch” page
# Action Use case
N/A

code

d
71
BR-16 When a new branch is created it needs to be confirmed by the

system's management
Table 3.29. Branch Management: Add branch
3.2.25. Branch Management: Update Branch

USE CASE-25
Use-case Name Branch Management: Update Branch
Author HuyenPT
Actor Administrator
Description Administrator edit branch
Triggers Click “Branch” tab on header
Click “Edit” button
Post Conditions Information of the branch change and update

header

information of branch

then click button “Save”
4 Update branch’s information to database
5 Return new branch’s information
# Action Use case
72
N/A

code

d
N/A
Table 3.30. Branch Management: Update Branch
3.2.26. Branch Management: Enable/Disable branch

USE CASE-26
Use-case Name Branch Management: Enable/Disable branch
Author HuyenPT
Actor Administrator
Description Administrator enables/disables branch
Triggers Click “Branch” icon
Click “Enable” button
Post Conditions Administrator enables/disables branch

header

73
button
4 Enabled/Disabled branch saved in the database
5 Redirect to “Branch” page
# Action Use case
N/A

code
BR-16 When a new branch is edited needs to be confirmed by the

system's management
Table 3.31. Branch Management: Enable/Disable branch
3.2.27. Product Management: View product

USE CASE-27
Use-case Name Product Management: View product
Author HuyenPT
Actor Administrator
Description Administrator views product
Triggers Click “Product” tab on header
Click on the row corresponding to each product
74
Post Conditions Administrator views product
1 Click “Product” tab on

header
2 Redirect to “Products page
3 Click on the row

product
4 Redirect to “Product Detail” page and show all

information of product
# Action Use case
N/A

code
N/A
Table 3.32. Product Management: View product
3.2.28. Product Management: Add product

USE CASE-28
Use-case Name Product Management: Add product
Author HuyenPT
Actor Administrator
Description Administrator adds product
Triggers Click “See More” button on “Product List” page
75
Post Conditions Administrator adds new product
1 Click “See More” button on

“Product List” page
2 Redirect to “Product” page and list all

4 Redirect to “Add Product” page and list all blank

information field of product

then click the “Save” button
6 New product saved in the database
Redirect to “Product” page
# Action Use case
N/A

code
BR-17 The chain manager has to fill in the information of the newly
added product
Table 3.33. Product Management: Add product
76
3.2.29. Product Management: Edit product
USE CASE-29
Use-case Name Product Management: Edit product
Author HuyenPT
Actor Administrator
Description Administrator edits product
Post Conditions Administrator edits product
1 Click “See More” button

on “Product List” page

3 Click “Edit” button
4 Redirect to “Add Product” page and list all

information field of product to edit
5 Edit information and then

click the “Save” button
6 Edited product saved in the database
Redirect to “Product” page
# Action Use case
N/A

code
77
BR-18 Check product’s information:

Table 3.34. Product Management: Edit product
3.2.30. Product Management: Enable/Disable product

USE CASE-30
Use-case Name Product Management: Enable/Disable product
Author HuyenPT
Actor Administrator
Description Administrator enables/disables product
Click “Enable/Disable” button
Post Conditions Administrator enables/disables product
1 Click “See More” button

on “Product List” page

button
78
4 Enabled/Disabled product saved in the
database
5 Redirect to “Product” page
# Action Use case
N/A

code

Table 3.35. Product Management: Enable/Disable product
3.2.31. Category Management: View all category

USE CASE-31
Use-case Name Category Management: View all category
Author HuyenPT
Actor Administrator
Description Administrator views category
Triggers Click “Category” tab on header
Click on the row corresponding to each category
79
Post Conditions Administrator views all categories
1 Click “Category” tab on the

header
2 Redirect to “Category” page and list all

information of categories
3 Click on the row

category
4 Redirect to “Category Detail” page and list all

information of category detail
# Action Use case
N/A

code
N/A
Table 3.36. Category Management: View all category
3.2.32. Category Management: Add category

USE CASE-32
Use-case Name Category Management: Add category
Author HuyenPT
Actor Administrator
Description Administrator adds category
80
Triggers Click “Category” icon
Post Conditions New category was added

header

4 Redirect to “Add Category” page and list all

blank information field of category

button
6 New category saved in the database
Redirect to “Category” page
# Action Use case
N/A

code

d
N/A
Table 3.37. Category Management: Add category
81
3.2.33. Category Management: Edit category
USE CASE-33
Use-case Name Category Management: Edit category
Author HuyenPT
Actor Administrator
Description Administrator edits category
Post Conditions Category was edited

header

4 Redirect to “Edit Category” page and list all

information field of category to edit

6 Edited category information saved in the

database
# Action Use case
N/A
82
code

d
N/A
Table 3.38. Category Management: Edit category
3.2.34. Category Management: Enable/Disable category

USE CASE-34
Use-case Name Category Management: Enable/Disable category
Author HuyenPT
Actor Administrator
Description Administrator enables/disables category
Post Conditions Category was enabled/disabled

header

button
83
6 Enabled/Disabled category saved in the
database
# Action Use case
N/A

code

d
N/A
Table 3.39. Category Management: Enable/Disable category
3.2.35. Post Management: View post

USE CASE-35
Use-case Name Post Management: View post
Author HuyenPT
Actor Administrator
Description Administrator views posts
Triggers Click “News” tab on header
Click on the row corresponding to each post
Post Conditions Administrator views all posts
84

header
2 Redirect to “News” page and list all information

of posts
3 Click on the row

corresponding to each post

information of post detail
# Action Use case
N/A

code
N/A
Table 3.40. Post Management: View post
3.2.36. Post Management: Edit post

USE CASE-36
Use-case Name Post Management: Edit post
Author HuyenPT
Actor Administrator
Description Administrator edits posts
Triggers Click “News” icon
85
Post Conditions Post is changed and updated
1 Click “News Detail” icon on

the header

information of posts

then click button “Save”
4 Update post’s information to database
5 Return new post’s information
# Action Use case
N/A

code
BR-19 Check the full information of the posts
Table 3.41. Post Management: Edit post
3.2.37. Post Management: Upload post

USE CASE-37
Use-case Name Post Management: Upload post
Author HuyenPT
Actor Administrator
86
Description Administrator uploads posts
Click “Upload” button
Post Conditions Post is uploaded to the website

header
2 Redirect to “News” page and list all information

of posts
3 Choose post to upload and

click “Upload” button
4 Upload post to the website
5 Redirect to latest post page
# Action Use case
N/A

code

d
Table 3.42. Post Management: Upload post
3.2.38. Post Management: Delete post

USE CASE-38
87
Use-case Name Post Management: Delete post
Author HuyenPT
Actor Administrator
Description Administrator deletes posts
Click “Delete” button
Post Conditions Post is deleted
1 Click “News Detail” icon on

the header

information of posts
3 Click “Delete” button
4 Update deleted post to database
5 Redirect to "News” page
# Action Use case
N/A

code

d
88
Table 3.43. Post Management: delete post
3.2.41. User Management: Add branch manager

USE CASE-41
Use-case Name User Management: Add branch manager
Author HuyenPT
Actor Administrator
Description Administrator adds branch manager
Triggers Click “Branch Manager” icon
Post Conditions Administrator adds branch manager

tab on the header

3 Click “Create User” button
4 Redirect to “Add Branch Manager” page and list

all blank information field of branch manager

button
6 New branch manager saved in the database
Redirect to “Branch Manager” page
89
# Action Use case
N/A

code

d
BR-20 Only Manager and Administrator have the right to manage

system branches
Table 3.44. Branch Manager Management: Add branch manager
3.2.42. Request Management: View request

USE CASE-42
Use-case Name Request Management: View request
Author HuyenPT
Actor Administrator
Description Administrator views request
Triggers Click “Request” tab on menu header
Click on the row corresponding to each request
Post Conditions Administrator can view request
1 Click “Request” tab on the

menu header
90
2 Redirect to “Request” page and list all
information of requests
3 Click on the row

request
4 Redirect to “Request Detail” page and list all

information of request detail
# Action Use case
N/A

code

system branches
Table 3.45. Request Management: View request
3.2.43. Request Management: Accept/decline request

USE CASE-43
Use-case Name Request Management: Accept/decline request
Author HuyenPT
Actor Administrator
Description Administrator accepts/declines request
Triggers Click “Request” icon
91
Click “Accept/decline” button
Post Conditions Administrator can accept/decline request
1 Click “Request” icon on the

storage page

3 Click “Accept/Decline”
button
4 Accepted/Declined request saved in the
database
5 Redirect to “Request” page
# Action Use case
N/A

code

system branches
Table 3.46. Request Management: Accept/decline request
3.2.44. View orders of their branch

USE CASE-44
92
Use-case Name View orders of their branch
Author HuyenPT
Actor Branch Manager
Description Branch manager view orders of his branch
Triggers Click “Order” tab on menu header
Click on the row corresponding to each order
Post Conditions Show all orders of his branch

header

of orders
3 Click on the row

order

# Action Use case
N/A

code

d
N/A
93
Table 3.47. View orders of their branch
3.2.45. Receive orders from customers that ordered to their branch

USE CASE-45
Use-case Name Receive orders from customers that ordered to their branch
Author HuyenPT
Description Branch manager receives orders from customers that ordered to their branch
Triggers Click “Order” tab
Click “Receive Orders” tab
Post Conditions Show all receive orders from customers that ordered to their branch
1 Click “Receive Orders” tab

on the Order page
2 Redirect to “Receive Orders” page and list all

information of receive orders
# Action Use case
N/A

code

d
94
BR-21 Check the customer's order information before further
processing
Table 3.48. Receive orders from customers that ordered to their branch
3.2.46. Approve an order

USE CASE-46
Use-case Name Approve an order
Author HuyenPT
Description Branch manager approves an order when branch has full ingredients for the
order to make
Triggers Click on the row corresponding to each order
Click “Approve” button
Post Conditions Order is approved

header

of orders
3 Click on the row

order

5 Click “Approve” button
6 Approved order saved in the database
95
# Action Use case
N/A

code

d

processing
Table 3.49. Approve an order
3.2.47. Cancel an order

USE CASE-47
Use-case Name Cancel an order
Author HuyenPT
Description Branch manager cancels an order when branch doesn’t have full ingredients
for the order to make
Click “Cancel” button
Post Conditions Order is cancelled
96
header

of orders
3 Click on the row

order

5 Click “Cancel” button
6 Cancel order saved in the database
# Action Use case
N/A

code

d

processing
Table 3.50. Cancel an order
3.2.48. View information of customers ordering (phone number, name, address)

USE CASE-48
Use-case Name View information of customers ordering (phone number, name, address)
97
Author HuyenPT
Description Branch manager view information of customers ordering (phone number,

name, address) at his branch
Click “Customer Information” button
Post Conditions Show all information about customers ordering (phone number, name,
address) at the branch

header

of orders
3 Click on the row

order

5 Click “Customer
Information” button
6 Redirect to “Customer Information” page and list

all information of customer
# Action Use case
N/A

code
98
d

processing
Table 3.51. View information of customers ordering (phone number, name, address)
3.2.49. Branch-self Management: View information of their branch

USE CASE-49
Use-case Name Branch-self Management: View information of their branch
Author HuyenPT
Description Branch manager view information of his branch
Triggers Click menu icon on header
Click “Branch” tab
Post Conditions Show all information of the branch

header

information of branch
# Action Use case
N/A
99
code

d
N/A
Table 3.52. Branch-self Management: View information of their branch
3.2.50 Branch product management: Enable/Disable product in the menu of their

branch
USE CASE-50
Use-case Name Branch product management: Enable/Disable product in the menu of their
branch
Author HuyenPT
Description Branch manager enables/disables product in the menu of their branch
Triggers Click “Menu” tab on the header
Click “Enable” button
Preconditions User logged in to the website
Post Conditions Product was enabled/disabled in the menu
1 Click “Menu” tab on the header
2 Redirect to “Menu” page
3 Click “Enable/Disable” button
100
4 Product was updated to be
enabled/disabled in database
5 Return new menu
# Action Use case
N/A

code
401
403

Table 3.53. Branch product management: Enable/Disable product in the menu of their branch
3.2.51. Branch Request Management: Create request

USE CASE-51
Use-case Name Branch Request Management: Create request
Author HuyenPT
Description Branch manager creates request
Click “Create Request” button
101
Post Conditions Request was created

header

information of request
3 Click “Create Request”

button
4 Redirect to “Create Request” page and list all
blank information field of request

button
6 New request saved in the database
Redirect to “Request” page
# Action Use case
N/A

code
N/A
Table 3.54. Branch Request Management: Create request
3.2.52. Branch Request Management: Edit request

USE CASE-52
102
Use-case Name Branch Request Management: Edit request
Author HuyenPT
Description Branch manager edits request
Triggers Click on the row corresponding to each request
Post Conditions Request was edited

header page

information of created requests
3 Click on the row

request

5 Redirect to “Edit Request” page and list all

information field of request to edit

7 Edited request information saved in the

database
8 Redirect to “Request Detail” page
# Action Use case
103
N/A

code
N/A
Table 3.55. Branch Request Management: Edit request
3.2.53. Branch Request Management: Send request

USE CASE-53
Use-case Name Branch Request Management: Send request
Author HuyenPT
Description Branch manager sends request
Click “Send” button
Post Conditions Request was sent

header page

104
3 Click on the row
request

3 Click “Send” button
6 Request was sent to Chain Manager
Redirect to “Request Detail” page
# Action Use case
N/A

code
N/A
Table 3.56. Branch Request Management: Send request
3.2.54. Branch Request Management: Cancel request

USE CASE-54
Use-case Name Branch Request Management: Cancel request
Author HuyenPT
Description Branch manager cancels request
105
Click “Cancel” button
Post Conditions Request was cancelled

header page

3 Click on the row

request

5 Click “Cancel” button
6 Cancelled request information saved in the

database
# Action Use case
N/A

code
N/A
Table 3.57. Branch Request Management: Cancel request
106
3.2.55. Branch Request Management: View request detail
USE CASE-55
Use-case Name Branch Request Management: View request detail
Author HuyenPT
Description Branch manager views request detail
Click on the row corresponding to each request
Post Conditions Branch manager can view request detail

header page

3 Click on the row

request

# Action Use case
N/A

code
107
N/A
Table 3.58. Branch Request Management: View request detail
3.2.56. Branch Request Management: Completed request

USE CASE-56
Use-case Name Branch Request Management: Completed request
Author HuyenPT
Description Branch manager complete request
Click "Complete" button
Post Conditions Request is completed

header page

3 Click on the row

request

5 Click "Complete" button
6 Completed request saved in database
108
# Action Use case
N/A

code
N/A
Table 3.59. Branch Request Management: Completed request
3.2.57. Completed an order

USE CASE-57
Use-case Name Completed an order
Author HuyenPT
Description Branch manager completes order when order is delivered success
Click “Complete” button
Post Conditions Order is completed

header
109
of orders
3 Click on the row

order

5 Click “Complete” button
6 Completed order saved in the database
# Action Use case
N/A

code

d

processing
Table 3.60. Completed an order
3.4. Non-Functional Requirements

3.4.1 External Interfaces
3.4.1.1. User Interfaces
• UI-01: The website will work smoothly on these: Chrome, Firefox, Safari, and Edge.
• UI-02: The website is suitable for all different users and is friendly.
• UI-03: All error messages should be clear and can provide troubleshooting guidance to the
user.
• UI-04: The application supports English only.
110
3.4.1.2. External Interfaces
• EI-01: System will support most web browsers with responsive design.
• EI-02: All data must be integrated via API.
• EI-03: Response API uses JSON format.
3.4.2. Quality Attributes

3.4.2.1. Usability
• US-01: Users will quickly grow used to and productive at core operations.
• US-02: Error and warning messages are simple.
• US-03: Prominent board and card features. The board and card features should be
prominent and easy to use.
3.4.2.2. Reliability
• RE-01: Before being sent to the server, every information submitted by the user is verified.
• RE-02: The system complies with business rules.
3.4.2.3 Performance
• PE-01: Data will be stored on a good-performance server.
• PE-02: Optimize query statements.
• PE-03: The response time of the functions in the system is less than 4 seconds.
3.4.2.4. Security
• SE-01: Depending on the role of the user, the corresponding screen will be displayed.
• SE-02: The database will be safely kept on the server.
3.5. Requirement Appendix

3.5.1. Business Rules
ID Rule Definition
BR-1 The email used for register must match the email format
BR-2 Each registered account will correspond to only 1 of their mail
BR-3 User can view the nearest facilities in his current location and can choose one of them
BR-4 Check account:
-Check username format
-Check password format
BR-5 Users need to verify the owner of the mail that they have registered
BR-6 User have to confirm by email
BR-8 Products are added to cart must be available and enabled

BR-9 Customers have to fill in the necessary information and then make the payment
BR-10 The order cannot be canceled if it is 2 hours after placing the order and have
“pending” status
111
BR-12 Customers will make checkout according to the system's method
BR-13 Customer’s information must be strictly confidential
BR-14 Check customer’s information:
-If the information is not in the correct format or has an error, the system will notify
you
BR-15 Check manager’s information:
- If the information is not in the correct format or has an error, the system will notify
you
BR-16 When a new branch is created it needs to be confirmed by the system's management
BR-16 When a new branch is edited needs to be confirmed by the system's management
BR-17 The branch manager has to fill in the information of the newly added product
-If the information is not in the correct format or has an error, the system will notify
you
BR-20 Only Manager and Administrator have the right to manage system branches
BR-21 Check the customer's order information before further processing
BR-22 The user needs to enter the correct old password
BR-23 Check user information:
- If the information is not in the correct format or has an error, the system will notify
you
BR-24 Products are deleted to cart must be available
BR-25 Products are changed quantity to cart must be available
3.5.2. Common Requirements

3.5.3. Application Messages List
# Message Message Context Content
code Type
1 MSG01 In line There is not any search result No search results.
2 MSG02 In red, under Input-required fields are empty The * field is required.
the text box
112
3 MSG03 Toast Updating asset(s) information Update asset(s)
message successfully successfully.
4 MSG04 Toast Adding new asset successfully Add asset successfully.
message
5 MSG05 Toast Confirming email of asset A confirmation email has
message hand-over is sent successfully been sent to
{email_address}.
6 MSG06 Toast Resetting asset information Return asset(s) successfully.
message successfully
7 MSG07 Toast Deleting asset information Delete asset(s) successfully.
message successfully
8 MSG08 In red, under Input value length > max length Exceed max length of
the text box {max_length}.
9 MSG09 In line Username or password is not Incorrect username or
correct when clicking sign-in password. Please check
again.
113

Group4 CoffeeChain Report

Uploaded by

Copyright:

Available Formats

Group4 CoffeeChain Report

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Group4 CoffeeChain Report

Uploaded by

Copyright:

Available Formats

MINISTRY OF EDUCATION AND TRAINING

Capstone Project Document

Supervisor Tran Dinh Tri

- Hanoi, April 2023 -

ERD Entity Relationship Diagram

GUI Graphical User Interface

SDD Software Design Description

SPMP Software Project Management Plan

SRS Software Requirement Specification

UAT User Acceptance Test

API Application Program Interface

1.1.2 Project Team

Tran Dinh Tri Lecturer tritd@fe.edu.vn 0913091952

Nguyen Tuan Duong Leader duongnthe150423@fpt.edu.vn 0934455456

Le Nguyen Anh Tuan Member tuanlnahe150485@fpt.edu.vn 0399420013

Pham Duc Anh Member anhpdhe150529@fpt.edu.vn 0975516981

Phuong Thanh Huyen Member huyenpthe150576@fpt.edu.vn 0975122951

Phan Duc Manh Member manhpdhe151290@fpt.edu.vn 0338622864

Table 1.1. Project Team

1.2. Product Background

Figure 1.1. Description

1.3.1.3. Pros & cons

Figure 1.2. Description

1.3.2.3. Pros & cons

1.4. Business Opportunity

1.6. Project Scope & Limitations

1.6.2. Out of scope

1.6.3. Limitations & Exclusions

Figure 2.1. Scope & Estimation

2.1.2. Project Objectives

Testing Stage Test Coverage No. of Defects % of Defect Notes

1 Reviewing 100% 250 71.43%

2 Unit Test 100% 52 14.86%

3 Integration Test 100% 33 9.43%

4 System Test 100% 15 4.28%

5 Acceptance Test 100% 0 0%

Table 2.1. Quality

1 All Iteration objectives have been completed

2 Project will be finished before April 16 2023

Table 2.2. Project management

# Members Weekdays Weekends

1 Nguyễn Tuấn Dương 6 hours 6 hours

2 Lê Nguyễn Anh Tuấn 6 hours 6 hours

3 Phạm Đức Anh 6 hours 6 hours

4 Phương Thanh Huyền 6 hours 6 hours

5 Phan Đức Mạnh 6 hours 6 hours

Table 2.3. Allocated Effort

2.1.3. Project Risks

Table 2.4. Project Risks

Figure 2.2. Iterative and Incremental model

The reasons that we choose Iterative and Incremental model are:

2.2.2. Quality Management

2.2.3. Training Plan

Java Spring Boot Nguyen Tuan Duong During project Mandatory

Git, Github All members During project Mandatory

NextJs Phan Duc Manh During project Mandatory

2.3. Project Deliverables

1. Report 1 - Project Introduction 02/03/2023 Instructor

2. Report 2 - Project Management We 1/31/23 Instructor