Smart Canteen Test phase, srs, design phase and source code final deliverable
Project Domain / Category
Web based Application
Abstract / Introduction
Now a days, people don’t have quite a few time to waste inside the canteen looking forward to the waiter to take the order. Many patron visits the canteen in their lunch damage and recess in order that they have restrained time to consume and go back to their respective workplaces and colleges and so on. So, this Web based totally Application will help us to store time and order food whenever they need without calling the team of workers again and again.
Functional Requirements:
The system contains of four primary modules and their sub modules as follows:
1. Admin Module:
2. Manager Interface:
3. Customer Interface:
four. Head Chef Interface:
Admin Module:
As Admin is permitted to perform CRUD operations on Staff Members, Menu Items and Inventory Items. So, the admin module may have following:
Admin Login
• First you’ll want to create a consumer who can login to the admin web page.
• Enter your favored username and press enter.
• You will then be triggered on your favored e-mail address:
• The very last step is to go into your password. You can be asked to enter your password two times, the second one time as a affirmation of the first.
• The system offers ability to the admin to feature, edit and delete team of workers participants. Using this selection an admin can add cooks, waiters, and managers.
• Admin will assign each role for other group of workers, with the list of permissions wanted. If they want extra permissions supply them.
View Order/info
Bill Print
Add/ Remove Food Items
Add Offers
Update Inventory
View Sales for each day and month
Sales of person object for the day
Total Earnings
• Order located via Customer:
o The device will give customers the ability to place their orders the usage of our product.
O It will show a list of to be had and unavailable dishes within the menu where unavailable dishes could be grayed out.
O Customer may be capable of pick out a couple of dishes and their quantity for a particular order.
Manager Interface
• Manager may have a display wherein he will get notification on every occasion an order is finished. System will notify the supervisor about the order quantity and table variety.
• Manager also has a screen in which all orders are indexed, and standing button to mark the order as paid.
• Moreover, he also has an interface display screen to see and the repute of tables in the restaurant as unfastened/available.
Head Chef Interface
• In head chef interface, machine will show all the cutting-edge orders in element i.E. All of the dishes of a particular order.
• In each order, there is a button for you to be used to mark that dish cooked. Moreover, whilst client wants to take away a dish from his order, machine will show head chef a notification to approve the removal of the dish.
Customer Interface
• The purchaser interface will incorporate three interfaces /sections. All three interfaces/sections will have a steady format.
Place Order
o In this, machine indicates a listing of playing cards (UI Elements) of dishes. Each dish can have an photo, its fee in step with serving.
Timer and Edit/Cancel Order
o After confirming the order, the user will be proven a timer display screen. In this display screen purchaser will be shown “Edit Order” and “Cancel Order” buttons and a timer which shows the final touch time of the order. There may also be a button to request for bill.
Bill Payment & Feedback
In feedback interface, at the top right nook, a button for “Request Bill” could be proven. Customer pays invoice through any approach which includes Cash on delivery, Debit Card or Credit Card. Beneath this, button we will display a shape a good way to have distinct more than one-desire inquiries to take remarks and a publish feedback button.
Tools:
• Python Web framework Django
• Django officially helps the following databases, PostgreSQL, MariaDB, MySQL, Oracle, SQLite.
• Code editor (Pycharm, Sublime3)
Supervisor:
Name: Abdul Ghani
