Online Food Ordering System: A Project Proposal, Assignments of Database Management Systems (DBMS)

Download Online Food Ordering System: A Project Proposal and more Assignments Database Management Systems (DBMS) in PDF only on Docsity!

ONLINE FOOD

ORDERING SYSTEM

Omkar Aditya (18SCSE1140080)

Prakhar Mathur (18SCSE1140017)

ACKNOWLEDGEMENT

• (^) The satisfaction that accompanies that the successful completion of any task would be incomplete without the mention of people whose ceaseless cooperation made it possible, whose constant guidance and encouragement crown all efforts with success.
• (^) We are grateful to our project mentor Dr. Anvesha katti for the guidance, inspiration and constructive suggestions that helps me in the preparation of this project.
• (^) I am also grateful to my friend Prakhar Mathur for helping me with the project finalization process.
• (^) Last but not the least I wish to avail myself of this opportunity, express a sense of gratitude and love to my friends and my beloved parents for their manual support, strength and help.
• (^) Thanking you all,
• (^) Omkar aditya (18SCSE1140080)
• (^) Prakhar mathur (18SCSE1140017)

Introduction It is known globally that, in today’s market, it is extremely difficult to start a new small-scale business and live-through the competition from the well-established and settled owners. In fast paced time of today, when everyone is squeezed for time, the majority of people are finicky when it comes to placing a food order. The customers of today are not only attracted because placing an order online is very convenient but also because they have visibility into the items offered, price and extremely simplified navigation for the order. Online ordering system that I am proposing here, greatly simplifies the ordering process for both the customer and the restaurant. System presents an interactive and up-to-date menu with all available options in an easy to use manner. Customer can choose one or more items to place an order which will land in the Cart. Customer can view all the order details in the cart before checking out. At the end, customer gets order confirmation details. Once the order is placed it is entered in the database and retrieved in pretty much real time. This allows Restaurant Employees to quickly go through the orders as they are received and process all orders efficiently and effectively with minimal delays and confusion.

Motivation

The motivation for designing this application came because I am interested in

fast food and I personally do not like waiting for long in the store or to have to

call store to place an order especially during the peak lunch or dinner hours.

Moreover, I value recent learning about Programming languages as well as

seeing how powerful and dynamic they are when it comes to web designing and

applications. The language used to build this database is Oracle database

because I found them to be extremely useful while working on the technologies.

User: Reason :

• (^) We are taking the entity named as User because from here data will move to other entities and we will manage the database.
• (^) This entity will manage the data of users Attributes:
• (^) If we talk about the attributes, there can be many but we have mention only few those will be more help full to make the project workable and simple

Order:

Reason:

• (^) The reason for choosing this entity is that ,order is one of the main entity in the hostel and we

will keep the database of users and logically related things with the users.

Attributes:

• (^) OrderID, Price , Quantity , etc

These are selected so that hostel administration can easily manage the whole information

about student and through different perspectives students can be accessed by hostel

management.

Payment: Obviously when users will give order they will submit payment. Reason:

• (^) When users will order there will be payment charges on each basis. Attributes:
• (^) Keep the payment status of users.

ER DIAGRAM:

User:

Datatype And Size:

• (^) Each attribute have the suitable data-type and size according to the requirement.

Primary Key:

• (^) UserID because so that by assigning the num it will be easy to track the data.

Constraints:

• (^) Primary key should be unique and cannot be null.

Order: Datatype And Size:

• (^) Each attribute have the suitable data-type and size according to the requirement. Primary Key:
• (^) OrderID is the primary key. Constraints:
• (^) Primary key should be unique and cannot be null.
• (^) When primary key move to the other relation and join the tables the values should be same.

Payment:

Datatype And Size:

• (^) Each attribute have the suitable data-type and size according to the requirement.

Primary Key:

• (^) PaymentID is the primary key.

Constraints:

• (^) PaymentID is the primary key and it can’t be null.

DDL & DML..statement create table User ( User_Id varchar (20) not null, email varchar (30) not null, name varchar (45) not null, password varchar (45) not null, address varchar (45) not null, primary key ( User_Id) );

Tables