Distinguish Strong vs Weak Entity Sets and Draw ER Diagrams for Weak Entities

In the Entity–Relationship (ER) model, an entity set is classified as strong or weak based on how it gets identified.

Key idea: identification dependency

• A strong entity set has a primary key that uniquely identifies each entity instance by itself.
• A weak entity set does not have a complete primary key on its own; instead, it has a partial key and relies on an identifying relationship with an owner (strong entity).

This dependency is reflected in ER notation: weak entities are drawn with a double rectangle, their partial keys are distinguished, and the identifying relationship is shown with double lines.

Learning targets

1. Tell when an entity set is strong vs weak.
2. Identify the owner strong entity set and the weak entity set.
3. Draw the ER diagram properly for a weak entity (double rectangle, identifying relationship with double lines, and partial key marking).

Strong Entity Set (what makes it “strong”)

A strong entity set has:

• A primary key that uniquely identifies each entity instance.
• No need for another entity to establish identity.

Typical interpretation:

• Each instance exists and can be uniquely referenced without requiring a related instance.
• In design problems, you can often ask: “Can I uniquely locate a row/instance of this entity using only its own attributes?” If yes, it’s strong.

Common exam cues

• Single rectangle (not double).
• Key underlined (normal key notation).
• Relationship edges are single (not double) because identity is not dependent.

Weak Entity Set (what makes it “weak”)

A weak entity set exists as a dependent concept:

• It has only a partial key.
• It is identified only when paired with the owning (strong) entity through an identifying relationship.

Typical interpretation:

• A weak entity instance cannot be uniquely distinguished without knowing which strong entity it belongs to.
• Example intuition: “An individual bed needs the hospital ward to identify which bed it is.”

Common ER cues

• Double rectangle for the weak entity.
• Partial key is marked (often with dashed/underlined conventions depending on the textbook).
• Identifying relationship shown with double diamond/double line to indicate the identifying nature.

Constructing the ER Diagram for a Weak Entity Set

You generally need to show three things:

1. The owner strong entity set (single rectangle) with its key.
2. The weak entity set (double rectangle) with its partial key.
3. The identifying relationship (double diamond/ double connection) connecting them.

Below is an illustrative example you can reuse.

Example ER: Project and Department-Project Assignments (Weak Entity)

Scenario

• A Department (strong) has a DepartmentID as its primary key.
• A DepartmentProjectAssignment (weak) represents a project assignment within a department.
  • It has a AssignmentNo that is only meaningful within a department (partial key).
  • It is uniquely identified by (DepartmentID, AssignmentNo) via an identifying relationship.

ER interpretation

• Department = strong entity set.
• DepartmentProjectAssignment = weak entity set.
• Identifying relationship connects them and is shown with double lines.

Note: Mermaid ER syntax may not perfectly capture “double rectangle/double diamond” styling. The standard concept still holds: weak entity + identifying relationship with double-line semantics.

How the “key” becomes unique for a weak entity

Let:

• Owner strong entity have key $K$.
• Weak entity have partial key $k_p$.

Then the weak entity’s effective key is commonly modeled as:

This expresses that the pair uniquely identifies each weak entity instance.