0% found this document useful (0 votes)
146 views13 pages

Entity Relationship Modeling: Objectives

The document discusses entity relationship modeling and its components. ER modeling is a top-down approach to database design that uses entities, attributes, and relationships. Entities can be people, places, objects, events, or concepts. Relationships define associations between entities and have names, degrees, and cardinalities. Attributes provide additional information about entities. Finally, the document provides examples of how ER diagrams and database tables incorporate these components.
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
146 views13 pages

Entity Relationship Modeling: Objectives

The document discusses entity relationship modeling and its components. ER modeling is a top-down approach to database design that uses entities, attributes, and relationships. Entities can be people, places, objects, events, or concepts. Relationships define associations between entities and have names, degrees, and cardinalities. Attributes provide additional information about entities. Finally, the document provides examples of how ER diagrams and database tables incorporate these components.
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 13

Entity Relationship Modeling

Objectives:

To illustrate how relationships between entities are

defined and refined.


To know how relationships are incorporated into the

database design process.


To describe how ERD components affect database

design and implementation.

Entity-Relationship (ER) Modeling.


ER Modeling is a top-down approach to database design. Entity Relationship (ER) Diagram
A detailed, logical representation of the entities,

associations and data elements for an organization or business

Notation uses three main constructs


Data entities Relationships Attributes

Notation
Entity Attribute Relationship EntityName EntityName List of Attributes Verb phrase

Acceptable

Entities
Examples of entities:
Person: LECTURER, STUDENT Place: CLASS ROOM, WAREHOUSE Object: MACHINE, PRODUCT, CAR Event: REGISTRATION, LECTURE Concept: COURSE, LECTURE

Guidelines for naming and defining entity types:


An entity type name is a singular noun

An entity type should be descriptive and specific


An entity name should be concise Event entity types should be named for the result of the event, not the

activity or process of the event.

Attributes
Example of entity types and associated attributes:
STUDENT: Student_ID, Student_Name, Home_Address, Phone_Number, B_Date

Guidelines for naming attributes:


An attribute name is a noun. An attribute name should be unique To make an attribute name unique and clear, each attribute name

should follow a standard format


Similar attributes of different entity types should use similar but

distinguishing names.

Relationship
Associations between instances of one or more entity types that is of interest Given a name that describes its function. relationship name is an active or a passive verb.

Relationship name: Lecture Lecturer Subject

An Lecturer gives lecture on one or more Subjects A Subject can be taught by one or more lecturer.

Relationship
The degree of a relationship = the number of entity

sets that participate in the relationship


Mostly binary relationships Sometimes more

Mapping cardinality of a relationship 1 1 1 many many 1 Many-many

One-One and One-Many

Many-one and many-many

Notations

Notations

Example

Tables
Student PK N_ID

F_Name
L_Name Enrollment Stud_ID CK Course_Name CC# Enroll_Date Lecture PK CC# Subject Time Date FK FK FK FK Address B_Date PK

Subject
Subject_Dscription Subject_Unit Subject_Code

Lecturer L_Address L_FirstName L_LastName L_Email

Lecturer_ID

FK

PK

Lecturer_ID

You might also like