Scribd
Upload
93 views6 pages

ER Model Example

The document describes the entity relationship (ER) model for a college database. It identifies the main entities as Department, Student, Course, and Instructor. It outlines the key attributes, relationships, and cardinalities between entities. For example, the relationship between Department and Course is one-to-many, as one department can offer many courses but a course belongs to only one department. The ER diagram captures all relevant attributes and relationships.

Uploaded by

Nayan Sinha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
93 views6 pages

ER Model Example

The document describes the entity relationship (ER) model for a college database. It identifies the main entities as Department, Student, Course, and Instructor. It outlines the key attributes, relationships, and cardinalities between entities. For example, the relationship between Department and Course is one-to-many, as one department can offer many courses but a course belongs to only one department. The ER diagram captures all relevant attributes and relationships.

Uploaded by

Nayan Sinha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

ER Model For a college DB:

Assumptions:
• A college contains many departments
• Each department can offer any number of courses
• Many instructors can work in a department
• An instructor can work only in one department
• For each department there is a Head
• An instructor can be head of only one department
• Each instructor can take any number of courses
• A course can be taken by only one instructor
• A student can enroll for any number of courses
• Each course can have any number of students
Steps in ER Modeling:
• Identify the Entities
• Find relationships
• Identify the key attributes for every Entity
• Identify other relevant attributes
• Draw complete E-R diagram with all attributes including
Primary Key
Step 1: Identify the Entities:

• DEPARTMENT
• STUDENT
• COURSE
• INSTRUCTOR

Step 2: Find the relationships:

• One course is enrolled by multiple students and one student enrolls for multiple
courses,
hence the cardinality between course and student is Many to Many.
• The department offers many courses and each course belongs to only one department,
hence the cardinality between department and course is One to Many.
• One department has multiple instructors and one instructor belongs to one and only
one
department , hence the cardinality between department and instructor is one to Many.
• Each department there is a “Head of department” and one instructor is “Head of
department “,hence the cardinality is one to one .
• One course is taught by only one instructor, but the instructor teaches many courses,
hence the cardinality between course and instructor is many to one.

Step 3: Identify the key attributes

• Deptname is the key attribute for the Entity “Department”, as it identifies the
Department uniquely.
• Course# (CourseId) is the key attribute for “Course” Entity.
• Student# (Student Number) is the key attribute for “Student” Entity.
• Instructor Name is the key attribute for “Instructor” Entity.
•

Step 4: Identify other relevant attributes

For the department entity, the relevant attribute is location

• For course entity, course name,duration,prerequisite


• For instructor entity, room#, telephone#
• For student entity, student name, date of birth
ER model for Banking Business:
Assumptions:
• There are multiple banks and each bank has many
branches. Each branch has multiple customers
• Customers have various types of accounts
• Some Customers also had taken different types of
loans from these bank branches
• One customer can have multiple accounts and
Loans
Step 1: Identify the Entities
• BANK
• BRANCH
• LOAN
• ACCOUNT
• CUSTOMER
Step 2: Find the relationships
• One Bank has many branches and each branch belongs to only one bank, hence the
cardinality between Bank and Branch is One to Many.
• One Branch offers many loans and each loan is associated with one branch, hence the
cardinality between Branch and Loan is One to Many.
• One Branch maintains multiple accounts and each account is associated to one and
only one Branch, hence the cardinality between Branch and Account is One to Many
• One Loan can be availed by multiple customers, and each Customer can avail multiple
loans, hence the cardinality between Loan and Customer is Many to Many.
• One Customer can hold multiple accounts, and each Account can be held by multiple
Customers, hence the cardinality between Customer and Account is Many to Many

Step 3: Identify the key attributes


• BankCode (Bank Code) is the key attribute for the Entity “Bank”, as it identifies the bank
uniquely.
• Branch# (Branch Number) is the key attribute for “Branch” Entity.
• Customer# (Customer Number) is the key attribute for “Customer” Entity.
• Loan# (Loan Number) is the key attribute for “Loan” Entity.
• Account No (Account Number) is the key attribute for “Account” Entity.
Step 4: Identify other relevant attributes
• For the “Bank” Entity, the relevant attributes other than “BankCode” would be “Name”
and “Address”.
• For the “Branch” Entity, the relevant attributes other than “Branch#” would be “Name”
and “Address”.
• For the “Loan” Entity, the relevant attribute other than “Loan#” would be “Loan Type”.
• For the “Account” Entity, the relevant attribute other than “Account No” would be
“Account Type”.
• For the “Customer” Entity, the relevant attributes other than “Customer#” would be
“Name”, “Telephone#” and “Address”.

E-R diagram with all attributes including Primary Key:

You might also like