Scribd
Upload
162 views

Programming Assignment Unit 2

database

Uploaded by

hamedhussam25
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
162 views

Programming Assignment Unit 2

database

Uploaded by

hamedhussam25
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/ 2

Imagine, you are a database administrator working for a small e-commerce company

that sells a variety of products online. The company wants to enhance its database
system to better manage its inventory, orders, and customers.
1. Considering the four entities namely Product, Customer, Order, and Inventory.
Define the relationships between these entities and identify key attributes for
each entity.
2. Translate the above four identified entities and attributes into tables with
appropriate primary and foreign keys.
3. Create an Entity-Relationship (ER) diagram that visually represents the
structure of the e-commerce company's database system. Include all entities,
relationships, attributes, and keys identified in parts (a) and (b). Clearly
indicate cardinality and participation constraints. Ensure the ER diagram is
properly labelled and easy to understand.
4. Explain two differences between conceptual and physical design in this
scenario, highlighting their respective roles in database development and
implementation.

Differences between conceptual and physical design


Conceptual design:
It focuses on the required data and how it should be organized.
It uses entities, attributes and relationships.
Do not consider how the data is stored or implemented.
Example: identify entities such as product, customer, order, inventory with their
attributes.
Material Design:
It focuses on how data is stored in the database.
It uses tables, columns, data types, indexes and constraints.
Performance, storage and access methods are considered.
Example: defining SQL tables, data types for each column, setting up primary and
foreign keys, designing indexes.

Reference:
Data Modeling: Conceptual vs Logical vs Physical Data Model. (n.d.). Online.visual-

Paradigm.com. https://online.visual-paradigm.com/knowledge/visual-

modeling/conceptual-vs-logical-vs-physical-data-model

You might also like