Online Food Ordering Database – Task 2, Thesis of Community Corrections

A table with the name, phone, address, email, hours, and rating of a restaurant, as well as its primary key. The table is related to a task about designing a database system for online food ordering. The document also includes references to two sources about database systems and ER diagrams.

Typology: Thesis

2023/2024

Available from 01/10/2024

helperatsof-1
helperatsof-1 🇺🇸

4.2

(5)

14K documents

1 / 6

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Running head: ONLINE FOOD ORDERING DATABASE – TASK 2 1
Online Food Ordering Database – Task 2
CPT 310 Database Systems & Management
pf3
pf4
pf5

Partial preview of the text

Download Online Food Ordering Database – Task 2 and more Thesis Community Corrections in PDF only on Docsity!

Running head: ONLINE FOOD ORDERING DATABASE – TASK 2 1

Online Food Ordering Database – Task 2

CPT 310 Database Systems & Management

Tables

Name: Restaurant

PK:R_id

FK: N/A

R_id R_name R_phone R_address R_email R_hours R_rating Datatype 1 Hurtz Pizza 423-555-5440 1 Pizza Street [email protected] 10am – 8pm 4.5 Text

In order to fully comprehend Chen notation and the entity relationship model (ERM), we

must first understand what they actually are and how they relate to database management

systems. The ERM is based upon three concepts, entities, relationships, and attributes, and can

be defined as “a data model that describes relationships (1:1, 1:M, and M:N) among entities at

the conceptual level with the help of ER diagrams” (Colonel & Morris, 2019, p. 45).The ERM

and its associated software was pioneered by Peter Chen in 1976 and it quickly became widely

accepted because of its ability to complement concepts from relational database models (Colonel

& Morris, 2019). Soon after the ERM was created by Chen, the associated ER diagrams became

known as Chen ER diagrams.

There are many advantages to using Chen’s ER diagram model, with the most notable

advantage being its simplicity. Chen’s ER diagram model is very simple to understand and it also

allows the database designer to effortlessly represent the relationship between the entities (Yue,

n.d.). Another advantage of the Chen ER diagram model is that it gives a visual representation of

the database prior to any coding being done which allows the data in the database to be reviewed

and easily changed if necessary (Yue, n.d.). Additionally, this also allows database errors to be

identified prior to coding, which can be addressed right then rather than dealing with the errors

once the coding is finished, which can take a large amount of time. The database is essentially

the blueprint of the database code so any errors that are noticed at the beginning will only save

time on the back end. One way that the entity-relationship diagram (ERD) will influence the

relationship between the tables is by defining the terms between the two models that are related

to the entity-relationship in addition to providing a visual representation of how the tables are

related to each other (Yue, n.d.). Additionally, the ERD shapes the relationship between the

tables by outlining the entities, attributes, and relationships between the two tables.

Reference