Scribd
Upload
2 views6 pages

DB Week 2 Assigment

The document outlines the development of a database system for managing inventory, orders, and customers in a company. It describes the conceptual, logical, and physical data models, detailing entities such as Customer, Product, Order, and Inventory, along with their relationships and SQL table structures. Additionally, it highlights the differences between conceptual and physical design, emphasizing the importance of both in understanding business needs and ensuring efficient data management.

Uploaded by

othnielnduka2020
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
2 views6 pages

DB Week 2 Assigment

The document outlines the development of a database system for managing inventory, orders, and customers in a company. It describes the conceptual, logical, and physical data models, detailing entities such as Customer, Product, Order, and Inventory, along with their relationships and SQL table structures. Additionally, it highlights the differences between conceptual and physical design, emphasizing the importance of both in understanding business needs and ensuring efficient data management.

Uploaded by

othnielnduka2020
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/ 6

Math Week 2

Department Of Computer Science - University of The People

MATH 1201 – College Algebra

Instructor Wellwerts

February 14, 2025


Introduction

In this paper I would be working with a company that wants to enhance their database

system to better manage its inventory, orders and customers.

Answers

Describing the Concept of a Conceptual Data Model

A conceptual data model is a high-level representation of an organization’s data and

its relationship. It defines entities, relationships, and constraints without specifying data

storage mechanisms (Elmasri & Navathe, 2020).

1. The Four Entity (Product, Customer, Order & Inventory)

As a Logical Data Model

A logical data model takes entities a step further and work out the details of how their

attributes and relationships. It defines the structure, but does not concern itself with the

technical aspects of how the database will be constructed (Constantine Nalimov, gleek_).

Customer (Customer_ID (PK), Name, Email, Phone, Address)

Product (Product_ID (PK), Product_Name, Description, Price, Stock_Quantity)

Order (Order_ID (PK), Customer_ID (FK), Order_Date, Total_Amount)

Inventory (Inventory_ID (PK), Product_ID (FK), Quantity_Available, Warehouse_Location)

Relationships

a. The customer places an order (one-to-many: one customer can place multiple orders).

b. An order contains products (many-to-many: an order can have multiple products, and

a product can be multiple orders).

c. An inventory tracks products (one-to-one: each product has a single inventory record).
As a Physical Data Model

A physical data model specifies how the database is implemented in a specific

database management system (DBMS). It includes data types, indexing, and storage

considerations (Coronel & Morris, 2018).

2. The Four Entities into Tables

Customer Table

CREATE TABLE Customer (

Customer_ID INT PRIMARY KEY,

Name VARCHAR(100),

Email VARCHAR(100) UNIQUE,

Phone VARCHAR(15),

Address TEXT

);

Product Table

CREATE TABLE Product (

Product_ID INT PRIMARY KEY,

Product_Name VARCHAR(255),

Description TEXT,

Price DECIMAL(10,2),

Stock_Quantity INT
);

Order Table

CREATE TABLE Orders (

Order_ID INT PRIMARY KEY,

Customer_ID INT,

Order_Date DATE,

Total_Amount DECIMAL(10,2),

FOREIGN KEY (Customer_ID) REFERENCES Customer(Customer_ID)

);

Inventory Table

CREATE TABLE Inventory (

Inventory_ID INT PRIMARY KEY,

Product_ID INT UNIQUE,

Quantity_Available INT,

Warehouse_Location VARCHAR(255),

FOREIGN KEY (Product_ID) REFERENCES Product(Product_ID)

);

3. Entity-Relationship (ER) Diagram

4. Differences Between Conceptual and Physical Design

Conceptual Design Physical Design


Focuses on what the database should
Focuses on how the database is
represent (high-level entities and
implemented (tables, indexes, and storage).
relationships).

Independent of a specific database Tied to a specific DBMS such as MySQL,

management system PostgreSQL, or Oracle.

Example: Identifying Customer, Order, Example: Defining Customer_ID as INT

Product, and Inventory as entities PRIMARY KEY in an SQL table.

Conceptual design helps in understanding business needs, while physical designs ensures

efficient data storage and retrieval (Elmasri & Navathe, 2020).


References

What is a Conceptual Data Model? With Examples! (September 22, 2021), Constantine

Nalimov. Gleek_.

https://www.gleek.io/blog/conceptual-data-model.html

Connolly, T., & Begg, C. (2015). Database systems: A practical approach to design,

implementation, and management (6th ed.). Pearson.

Coronel, C., & Morris, S. (2018). Database systems: Design, implementation, &

management (13th ed.). Cengage Learning.

Elmasri, R., & Navathe, S. (2020). Fundamentals of database systems (7th ed.). Pearson.

Hoffer, J., Venkataraman, R., & Topi, H. (2019). Modern database management (13th

ed.). Pearson.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy