0% found this document useful (0 votes)
6 views1 page

ER Scenario

The document describes a scenario involving an online store that sells electronic devices. It outlines the key entities like customers, products, orders, and payments and their attributes and relationships.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views1 page

ER Scenario

The document describes a scenario involving an online store that sells electronic devices. It outlines the key entities like customers, products, orders, and payments and their attributes and relationships.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Scenario:

Imagine an online store called "Tech Gadgets Galore" that sells various electronic devices.

Customers can browse the website, view product details, add items to their shopping cart,
and place orders.

The system needs to manage customer accounts, including information like name, email
address, and shipping details.

Products have attributes like product ID, name, description, price, stock quantity, and
category.

Orders track customer purchases, with details like order ID, order date, total amount, and
order status (e.g., placed, shipped, delivered). An Order contains many Products. Product
can be included in many Orders

Customers can pay for their orders using different payment methods, so a payment entity
might be needed to capture details like payment type (e.g., credit card, debit card) and
transaction ID.

1. Draw an ERD for the following scenario.


2. Convert the designed ER diagram to tables using relational schema.

You might also like