ERD

1 of
Published on Video
Go to video
Download PDF version
Download PDF version
Embed video
Share video
Ask about this video

Page 1 (0s)

ERD. Entity Relationship Diagram. Diagram Description automatically generated.

Page 2 (8s)

Introduction. White on blue abstract wintry background.

Page 3 (16s)

Introduction. Entity-Relationship diagrams or ER diagrams are one of the database design tools that will be useful for you to understand. ER diagrams are pictures that represent how the data in a database are supposed to be connected or related to one another..

Page 4 (31s)

How Entity-Relationship Diagrams Work. Top view of cubes connected with black lines.

Page 5 (39s)

Representation. Normally, they look like a collection of ovals, rectangles and diamonds collected by lines. Clearly, Diagrams are not fine art. These diagrams can be very helpful for writing tricky queries in database..

Page 6 (53s)

Entities. One big red drawing pin in front of many smaller black drawing pins.

Page 7 (1m 2s)

Entities. The boxes in the Diagram are called Entities. 01 They represent categories of data your database will keep track of. 02 Each box is one category. 03 Eventually, each entity will probably become a table when the database is made. 04.

Page 8 (1m 16s)

Entity Example. Autoradiogram on white paper.

Page 9 (1m 24s)

Rules of Entity. Always in Rectangular form. Always be in capital letter. Always Singular..

Page 10 (1m 33s)

STUDENT. COLLEGE.

Page 11 (1m 39s)

Types of Entity.

Page 12 (1m 46s)

Types of Entity. Strong Entity Weak Entity Associative Entity.

Page 13 (1m 53s)

Strong Entity. Close-up of chain link.

Page 14 (2m 1s)

Strong Entity. These shapes are independent from other entities, and are often called parent entities, since they will often have weak entities that depend on them. They will also have a primary key, distinguishing each occurrence of the entity..

Page 15 (2m 15s)

Strong Entity. STUDENT.

Page 16 (2m 21s)

Weak Entity.

Page 17 (2m 27s)

Weak Entity. Weak entities depend on some other entity type. They don't have primary keys, and have no meaning in the diagram without their parent entity.

Page 18 (2m 39s)

Weak Entity. APARTEMENT. WEAK ENTITY.

Page 19 (2m 45s)

Weak Entity. BUILDING. APARTEMENT. BuildingID. NumberOfFloors.

Page 20 (2m 55s)

Weak Entity. BUILDING. APARTEMENT. BuildingID. NumberOfFloors.

Page 21 (3m 4s)

Weak Entity. BUILDING. APARTEMENT. BuildingID. NumberOfFloors.

Page 22 (3m 13s)

Weak Entity. BUILDING. APARTEMENT. BuildingID. NumberOfFloors.

Page 23 (3m 21s)

Weak Entity. BUILDING. APARTEMENT. BuildingID. NumberOfFloors.

Page 24 (3m 29s)

Weak Entity. BUILDING. APARTEMENT. BuildingID. NumberOfFloors.

Page 25 (3m 37s)

Associative entity. Hand with red strings.

Page 26 (3m 45s)

Associative Entity. Associative entities relate the instances of several entity types. They also contain attributes specific to the relationship between those entity instances..

Page 27 (3m 55s)

Associative Entity. ASSOCIATE ENTITY.

Page 28 (4m 2s)

Attributes. Pile of rocks.

Page 29 (4m 9s)

Attributes. The ovals in the Diagram are called Attributes. These represent aspects of each category or entity that will be recorded. Attributes will likely become the columns in the table that will be built around that entity. Each attribute in the Diagram has to be connected to at least one entity. Further, according to the rules of set theory, each attribute must be unique for that entity..

Page 30 (4m 29s)

STUDENT. COLLEGE. StudentID. StudentName. CollegeStartDate.

Page 31 (4m 38s)

Types of Attribute. Colourful rulers and protractors.

Page 32 (4m 46s)

Types of Attribute. Simple Attributes Derived Attribute Composite Attribute Multivalued Attribute.

Page 33 (4m 54s)

Simple Attributes.

Page 34 (5m 0s)

Simple Attributes. Attributes are characteristics of an entity, a many-to-many relationship, or a one-to-one relationship.

Page 35 (5m 10s)

Simple Attributes. StudentID.

Page 36 (5m 16s)

Derived Attribute. A honeycomb glass surface.

Page 37 (5m 23s)

Derived Attribute. Derived attributes are attributes whose value can be calculated from related attribute values..

Page 38 (5m 32s)

Derived Attribute. Age. DateOfBirth.

Page 39 (5m 39s)

MULTIVALUED ATTRIBUTE. A honeycomb glass surface.

Page 40 (5m 46s)

Multivalued Attribute. Multivalued attributes are those that are can take on more than one value..

Page 41 (5m 55s)

Multivalued Attribute. Phone Number.

Page 42 (6m 2s)

Composite Attribute. A honeycomb glass surface.

Page 43 (6m 9s)

Composite Attribute. Important measurement that can be completely reconstructed using other entities..

Page 44 (6m 18s)

Composite Attribute. CLASSROOM. ( ClassRoomID ). NumberDesks.

Page 45 (6m 26s)

Composite Attribute. CLASSROOM. ( ClassRoomID ). NumberDesk.

Page 46 (6m 34s)

Composite Attribute. Building RoomNumber. CLASSROOM.

Page 47 (6m 41s)

Multivalued Attribute VS Composite Attribute. A honeycomb glass surface.

Page 48 (6m 49s)

Multivalued Attribute VS Composite Attribute. Phone Number.

Page 49 (6m 58s)

Multivalued Attribute VS Composite Attribute. Phone Number.

Page 50 (7m 9s)

Relationship. A honeycomb glass surface.