INFORMATION SYSTEM MANAGEMENT

ASSIGNMENT 2

ENTITY RELATIONSHIP DIAGRAM

Submitted by
VIGNESHWAR R
23AD46
INTRODUCTION:

An Entity-Relationship Diagram (ERD) is a visual representation of a data model that depicts the
relationships between various entities in a database. It's like a map of your data, helping you
understand the connections and organize information effectively. It is a widely used technique in
database design and software engineering to demonstrate a database's logical structure. The ERD
aids in understanding how different entities interact and how data is stored and retrieved in a
database system.

COMPONENTS OF ERD:

Key components of ERD are,

 Entities: These are the main data objects you want to store information about, like
customers, products, orders, or employees. They're represented as boxes or rectangles in
the diagram.
 Attributes: These are the specific details or features of each entity, such as the name of a
customer, their address, the price of a product, or the ID of an employee. These details are
displayed inside the box representing the entity on the diagram.
 Relationships: Entities are like different pieces of information in a database, such as
customers, products, employees, or projects. Relationships show how these pieces are
connected. For instance, a customer can place an order for a product, or an employee can
work on a project. In diagrams, relationships are drawn as lines between these pieces, with
labels explaining how they are linked.
 Cardinality: This tells you how many entities can be involved in a relationship on each
side.

TYPES OF CARDINALITY:

Cardinality in an ERD is all about quantifying the relationships between

entities, specifically, it tells you how many instances of one entity can be related to instances of
another entity. It's like specifying the traffic flow on the data highways in your diagram.
One-to-One (1:1):

Only one instance of one entity and one instance of another can be related.

One-to-Many (1:N):

One instance of an entity can be related to multiple instances of another entity,

while the "many" side can only be related to one "one" side instance. A customer can place many
orders, but an order belongs to only one customer.

Many-to-Many(N:M):

This is the bustling intersection, where many instances of one entity can be
related to many instances of another entity. Orders can contain multiple products, and products can
be included in multiple orders.

Here the ERD is created for the different Cardinalites based on the Warehouse Management
System.

Entities

 Warehouse: (Primary Key: Warehouse ID):

o Attributes: Name, Location, Capacity, Storage Units.
 Product: (Primary Key: Product ID):
o Attributes: Name, Description, Category, Manufacturer, Unit Price.

 Supplier: (Primary Key: Supplier ID)

o Attributes: Name, Contact Information, Payment Terms

 Customer: (Primary Key: Customer ID)

o Attributes: Name, Contact Information, Delivery Address

 Order: (Primary Key: Order ID)

o Attributes: Order Date, Customer (Foreign Key), Delivery Date, Status

  Stock: (Primary Key: Stock ID)

o Attributes: Product (Foreign Key), Warehouse (Foreign Key), Quantity, Minimum

Stock Level
 Shipment: (Primary Key: Shipment ID)

o Attributes: Order (Foreign Key), Supplier (Foreign Key), Shipment Date,

Estimated Arrival Date, Status
 Employee: (Primary Key: Employee ID)

o Attributes: Name, Role, Department, Warehouse (Foreign Key)

One to One (1:1):

One to Many (1:N):

Many to One (N:1):

Many to Many (M:N):

Reference:

 Google Bard AI
 https://www.techtarget.com/searchdatamanagement/definition/entity-relationship-
diagram-
ERD#:~:text=An%20entity%20relationship%20diagram%20(ERD,information%20technol
ogy%20(IT)%20system.