Scribd
Upload
3 views4 pages

Group 4 SBD Assignment 2

The document outlines the steps for creating relational diagrams from ER and EER modeling, detailing entities such as AIRPORT, AIRPLANE_TYPE, PERSON, and DEPARTMENT, along with their attributes. It describes the mapping of relationships, including binary 1:1, 1:N, and M:N relationships, as well as the handling of multivalued attributes. The document concludes by noting the absence of weak entities and N-ary relationships.

Uploaded by

kochengo303
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
3 views4 pages

Group 4 SBD Assignment 2

The document outlines the steps for creating relational diagrams from ER and EER modeling, detailing entities such as AIRPORT, AIRPLANE_TYPE, PERSON, and DEPARTMENT, along with their attributes. It describes the mapping of relationships, including binary 1:1, 1:N, and M:N relationships, as well as the handling of multivalued attributes. The document concludes by noting the absence of weak entities and N-ary relationships.

Uploaded by

kochengo303
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/ 4

Group 4:

Zaky Rofif Alfalah (5026241002)


Najla Hanasyifa (5026241049)

1. Relational diagram from ER Modelling


Step 1:
AIRPORT
Airport_code City State Name

AIRPLANE_TYPE
Type_name Max_seats Company

AIRPLANE
Airplane_id Total_no_of_seats

FLIGHT
Number Airline Weekdays

Step 2:

Step 3:
There is no binary 1:1 relation type in the ER diagram.
Step 4:

Step 5:

Step 6: There is no multivalued attributes.


Step 7: There is no N-ary relationship types in the ER diagram.
2. EER Modelling to Referential Diagram
Step 1: Mapping of Regular Strong Entity Types
Entity:
1. PERSON
Attributes: Ssn, Bdate, Sex, Name, Address
2. DEPARTMENT
Attributes: Dname, Dphone, Office
3. COLLEGE
Attributes: Cname, Dean, Coffice
4. COURSE
Attributes: C#, Cname, Cdesc
5. SECTION
Attributes: Sec#, Year, Qtr

Step 2: Mapping of Weak Entity Types


There is no weak entity types

Step 3: Mapping of Binary 1:1 Relationships


1. Department with Faculty
Department: Dname, Dphone, Office, Chair_ssn
Faculty: Ssn, Rank, Foffice, Fphone, Salary
PK: Ssn from Faculty
FK: Chair_ssn referencing Ssn from Faculty

Step 4: Mapping of Binary 1:N Relationships


1. BELONGS (Department with Faculty)
FK: Dname in FACULTY referencing DEPARTMENT(Dname)
2. ADVISOR (Faculty with Student)
FK: Advisor_ssn in STUDENT referencing FACULTY(Ssn)
3. MAJOR (Department with Student)
FK: Major_Dname in STUDENT referencing DEPARTMENT(Dname)
4. MINOR (Department with Student)
FK: Minor_Dname in STUDENT referencing DEPARTMENT(Dname)
5. DEPARTMENT with COURSE
FK: Dc in COURSE referencing DEPARTMENT (Dname)
6. COURSE with SECTION
FK: C# in SECTION referencing COURSE (C#)
7. COLLEGE with DEPARTMENT
FK: CD in DEPARTMENT referencing COLLEGE(Cname)

Step 5: Mapping of Binary M:N Relationships


1. REGISTERED (Student with Section)
FK: Ssn in REGISTERED referencing STUDENT(Ssn)
FK: Sect#, Qtr, Year in REGISTERED referencing SECTION(Sect#, Qtr, Year)
Additional attribute: Grade
2. TEACH (Faculty with Section)
FK: Ssn in TEACH referencing FACULTY(Ssn)
FK: Sect#, Qtr, Year in TEACH referencing SECTION(Sect#, Qtr, Year)
3. TRANSCRIPT (Student with Course)
FK: Ssn in TRANSCRIPT referencing STUDENT(Ssn)
FK: C# in TRANSCRIPT referencing COURSE(C#)
Additional attributes: Grade, Quarter, Year

Step 6: Mapping of Multivalued Attributes


1. Dphone (in DEPARTMENT)
Create a new relation: DEPARTMENT_PHONE
• FK: Dname in DEPARTMENT_PHONE referencing DEPARTMENT(Dname)
• Attribute: Dphone
• PK: (Dname, Dphone)
2. Office (in FACULTY)
Create a new relation: FACULTY_OFFICE
• FK: Ssn in FACULTY_OFFICE referencing FACULTY(Ssn)
• Attribute: Office
• PK: (Ssn, Office)
3. Phone (in STUDENT)
Create a new relation: STUDENT_PHONE
• FK: Ssn in STUDENT_PHONE referencing STUDENT(Ssn)
• Attribute: Phone
• PK: (Ssn, Phone)

Step 7: There is no N-ary relationship

You might also like