-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathtest.txt
79 lines (42 loc) · 4.35 KB
/
test.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
# Smart Restaurant
In current formal dining environments, some form of physical static menu is utilised to convey the available food and beverage choices to customers. Said menus are generally paper based and hence impose restrictions on the textual real estate available and the ability a restaurateur has to update them. Also with the ongoing situation of COVID, such paper based menus act as a hindrance in providing a contactless dining experience.
Three related concepts are encompassed by the general scope of the Smart Restaurant. The first pertains to the replacement of paper-based menus using an electronic format, the second relates to a complementary electronic strategy for the front of house handling of a customer’s order and the third surrounds the process of transferring said electronic orders to the kitchen for preparation. It should be noted that the suggested strategy incorporates the use of various hardware components.***Can these be in client requirements***
## Benefits
Greater flexibility in menus, an increase in restaurant productivity and capacity for extensive business auditing are the primary benefits associated with the Smart Restaurant. Menu updates can be rolled out at any time with no extra labour from printing and distributing new menus, allowing for more dynamic pricing and content changes. With the underlying software system taking responsibility for a customer’s order throughout its lifecycle, not only is accuracy ensured, but all actions are logged in a database for analysis and accountability of staff. This allows the company to audit and account staff, materials and restaurant efficiency, as well as to review exceptional circumstances for future handling.***Similarly can these be client req***
## C requirements Start
### Customer side
* Touch screen device describing a beautiful *food menu* on the table.
* Online Payment options
* Optional feedback form.
### Hotel staff side
* General purpose desktop showing request by the customer.
* The requests by the customers are visible along with table number.
* The Hotel Manager can also view the successful payments paid by the customers.
* Order card will have color determined based on factors like Veg/Non-Veg, VIP customer, customer preferences/allergies, takeaway/in-restaurant etc.
* The manager shall be able to authorize a table using assigned username and password and setting the table where it will be used. This cannot be changed by customer because of lack of requisite authorization.
### Chef side
Timer on order placed is shown to the chef with alert on orders tending to be late.
### Manager side
* Manager/Chef can change availability of dishes. Dynamic menu hiding dishes on customer side.
* Manager able to offer spontaneous discount to table for mishap in service.
* Manager able to add complimentary food.
Real time Reports on
- sales, total revenue generated by day, week, month and custom timeframe.
- best dishes by day, week, month and custom timeframe.
### Non functional requirements
---
* Impressive images.
* Fonts that go well with restaurant theme.
* Generally like to stick to a base of 3 or 4 colours at most.
* Stick to a design language(i.e., material design, ant design, fluid design etc.) that complements.**(This is most probably in D requirements)**
The manager may be viewed as a direct functional beneficiary – who relies on staff to operate the restaurant. Finally, the customer who is paying for services provided by restaurant is the another functional beneficiary of the system.
**(The below para is most probably in D requirements)**
The UI must adopt a fluent grid concept to layout contents on different screen resolutions. In fact, this project favours this approach because it requires smaller overheads to maintain separate sites and possible to achieve maximum reusability.
It scales down or hides certain UI contents to improve presentation on mobile browsers.
Business process may not too be the focus of this report, but possible improvement and automation should be considered as system requirements.
## Future Scope:
1. Payment page coupon code
2. Specific combinations will trigger offer popup.
3. Combo meals
> 1, 2 and 3 require rule engine to check (this is the more flexible approach)
4. Inventory of grocery by chef. Extends recepie and availability of grocery affects availability of dishes that depend on it.