Scribd
Upload
15 views

Data 2

Word

Uploaded by

theagriprof
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
15 views

Data 2

Word

Uploaded by

theagriprof
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/ 4

1.

Entity Definitions and Relationships

Entities and Key Attributes

1. **Product**

- **Key Attributes**:

- `ProductID` (Primary Key)

- `ProductName`

- `Description`

- `Price`

- `Category`

- `StockQuantity`

2. **Customer**

- **Key Attributes**:

- `CustomerID` (Primary Key)

- `FirstName`

- `LastName`

- `Email`

- `PhoneNumber`

- `Address`

3. **Order**

- **Key Attributes**:

- `OrderID` (Primary Key)


- `OrderDate`

- `CustomerID` (Foreign Key)

- `TotalAmount`

- `OrderStatus`

4. **Inventory**

- **Key Attributes**:

- `InventoryID` (Primary Key)

- `ProductID` (Foreign Key)

- `QuantityInStock`

- `ReorderLevel`

#### Relationships

- **Product** to **Inventory**: One-to-One (A product can have one inventory record)

- **Customer** to **Order**: One-to-Many (A customer can place multiple orders)

- **Order** to **Product**: Many-to-Many (An order can contain multiple products, and a product can
be part of multiple orders)

### 2. Tables with Keys

Here are the tables based on the entities and their relationships, including primary and foreign keys:

#### Product Table

| ProductID (PK) | ProductName | Description | Price | Category | StockQuantity |

|----------------|-------------|-------------|-------|----------|---------------|
#### Customer Table

| CustomerID (PK) | FirstName | LastName | Email | PhoneNumber | Address |

|-----------------|-----------|----------|------------------|-------------|------------------|

#### Order Table

| OrderID (PK) | OrderDate | CustomerID (FK) | TotalAmount | OrderStatus |

|---------------|-----------|------------------|-------------|-------------|

#### Inventory Table

| InventoryID (PK) | ProductID (FK) | QuantityInStock | ReorderLevel |

|------------------|-----------------|------------------|--------------|

#### Junction Table for Order and Product (to handle the many-to-many relationship)

| OrderID (FK) | ProductID (FK) | QuantityOrdered |

|---------------|-----------------|------------------|

### 3. Entity-Relationship (ER) Diagram

You can create the ER diagram using an online tool like [dbdiagram.io](https://dbdiagram.io). Below is a
textual description of how to represent the entities and relationships in the ER diagram:

- **Entities**: Represent each entity as a rectangle.

- **Attributes**: List key attributes inside each rectangle.

- **Primary Keys**: Indicate primary keys (PK) clearly.

- **Foreign Keys**: Indicate foreign keys (FK) in the relationships.


- **Relationships**: Use diamonds to show relationships.

- **Cardinality**: Use notation like 1:N or M:N to show the relationships and participation constraints.

### 4. Differences Between Conceptual and Physical Design

1. **Level of Detail**:

- **Conceptual Design**: This is a high-level overview of the database structure. It focuses on the
entities, relationships, and constraints without getting into technical specifics. It defines what the data
model should look like from a business perspective.

- **Physical Design**: This involves the actual implementation details of the database. It includes data
types, indexing strategies, storage requirements, and how data will be physically stored on hardware.

2. **Purpose**:

- **Conceptual Design**: The main purpose is to provide a clear framework for understanding the
database structure, ensuring stakeholders agree on the system's requirements and scope.

- **Physical Design**: The purpose is to translate the conceptual model into a working database
schema that optimizes performance and storage, addressing the technical aspects of how the database
will function in a specific environment.

### Conclusion

This structured approach helps in understanding the database design for the e-commerce company. For
the ER diagram, you can use any of the suggested tools to visually represent the entities and their
relationships effectively.

You might also like