Scribd
Upload
11 views2 pages

ER Activity L3

Uploaded by

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

ER Activity L3

Uploaded by

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

The Scenario:

A University contains many Faculties. The Faculties in turn are divided into several Schools. Each
School offers numerous programs and each program contains many courses. Lecturers can
teach many different courses and even the same course numerous times. Courses can also be
taught by many lecturers. A student is enrolled in only one program, but a program can contain
many students. Students can be enrolled in many courses at the same time and the courses
have many students enrolled.

The entities in this scenario are:

University  Faculty  School  Program  Course  Lecturer  Student

Attributes, primary keys (in bold black) and foreign keys (in bold blue) are shown below:

University (Uni_Name, Ful_Address, Uni_type, President)

Faculty (Full_Name, dean, location, university)

School (Sch_Name, HoD, location, faculty)

Program (Prog_Name, total_credits, duration, school)

Course (Course_code, Course_name, credit_hours, co_ordinator, program)

Lecturer (emp_code, Full_Name, Designation, Room, school)

Student (reg_no, Ful_Name, program, email, cell, Ful_Address)

Relationships:
Here we have identified the relationships and we can see that student-course and lecturer-
course exhibit many-to-many relationship and we need to introduce another entity to break
this M:M relationship.
Here come two more entities:

1- Course Registration (reg_no, course_code, date, assigned_by)

Combination of reg_no & course_code serves as primary key for this table. reg_no &
course_code are also foreign keys here as they are primary keys in their respective tables.
2- Course-Allocation (emp_code, course_code, date, assigned_by)

Combination of emp_code & course_code serves as primary key for this table. emp_code &
course_code are also foreign keys here as they are primary keys in their respective tables.

Now you can create ERD based on these 9 entities and their identified
relationships. (A rough sketch in given below).

University Faculty School

Student Course Program

Registratio Course
n Lecturer
Allocation

You might also like