Notes

KATHMANDU UNIVERSITY


SCHOOL OF ENGINEERING

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING



MINI PROJECT

REPORT ON
























KU RESTAURANT



A second year mini project report submitted in complete fulfillment of the requirements for COMP 232 by:

Prajwol Lamichhane (26)
Abhay Raut (43)

CE 2nd year 2nd semester


Date of Submission : 22nd July 2018
KU RESTAURANT


Description:

Objective:

1. To understand the concept and utilization of database management system.
2. To develop a database regarding the ordering, billing and staff managements of the restaurant.

3. To create a simple website to perform and demonstrate the basic operations on the created database including insert, delete, update and search.

System Design:

1. Programming Language: PHP, HTML
2. Database Management System: MySQL
3. Tools used: phpMyAdmin,

Scenario:

This project primarily focuses on the management of the overall restaurant database. The system is very much convenient for the customers as they can digitally place their order through a well designed user interface. As soon as the customer places an order it is then directed to the concerned staff from which the order is confirmed and the serving is done. The billing system is also automatic as per the foods ordered by the customer. The final amount is printed and provided to the customer.

Schemes:

There is a Login interface for the restaurant manager from which he is directed to a special interface in which he can add, delete or update records from the database. The customers can only view and order the food.





















ENTITIES AND THEIR ATTRIBUTES


Table 1:
1. artists: artist_id (Primary Key)
first_name
middle_name
last_name

This table consists the name of the people who add items to the menus list. The one who adds the item has an id as primary key along with his or her full name.


2. contactus: contact_id
first_name
last_name
email
message
date_created

The table contactus stores the customers detail along with their feedback on the database. The table consists of first name, last name, email, message, date_created information which directly goes into the admins messages.

3. customers: customer_id (Foreign Key)
email
pass
This table consists the information of a customer. The table stores the email and password of the customers.

4. employees: employee_id
first_name
last_name
email
pass
title
date_created
This table consists the information of the employees. The employees are added in this table along with their name, email, pass, title and date joined.

5. food: food_id (Foreign Key)
5. food_name
6. food_type
7. food_description
8. food_price
9. The table food consists the list of food items, name types and their price and descriptions.

6. menu: menu_id
food_id (Foreign Key)
10. menu_name
11. price
12. size
13. description
14. image_name
The menu uses foreign key. The food_id is used as foreign key from food table. The menu table shows the food name, price, size, description and also its image.

15.
7. orders: order_id (Foreign Key)
16. customer_id (Foreign Key)
17. total
18. order_date
The orders table consists the customer_id as foreign key from which the name of customer is displayed imported from the customers table along with the table and order date.

19. 8. order_content: oc_id
20. order_id (Foreign Key)
21. print_id (Foreign Key)
22. quantity
23. price
24. ship_date
This table contains the ordered contents the ordered items, quantity, price and ship date.



FUNCTIONAL DEPENDENCIES
¬¬¬
Table employees: {employee_id,first_name,last_name,email,title}
{employee_id}{first_name}
{employee_id}{last_name}
{employee_id}{title}





Candidate Keys of Entity
1. employees: employee_id

Primary Key¬¬
The underlined attributes in each entity are the primary keys of the corresponding entities because it uniquely identifies each entity.
1. employees (employee_id, first_name, last_name, email, title)
Employee_id is selected as the primary key because it can have a distinct value unlike other attributes in the table employee i.e first_name, last_name

2. branch (employee_id, branch)
Several branches can be in the same location so in order to identify each row uniquely we have used employee id as the primary key here.

3. salary (employee_id, salary)
Salary data can be repeated for the staffs so in order to point each row uniquely employee_id have been selected as the primary key here.

Normalisation: