-
Design a
Relational Data Model
for the following ER model
of a Faculty/Student database:
Comments on the ER-diagram:
- The Faculty entity represent the faculties of the university
- The Student entity represent the students of the university
- The Course entity represent the courses of the university
- The key in each
entity is
underlined with a
solid line.
- The Advivor relationship represents the faculty-student advising relationship
- The teaches relationship represents the teaching duties of faculties
- The takes relationship represents the course enrollment of students
Your relational model answer must satisfy the following requirements:
- Use the smallest possible number
of relations
- Attributes in relations
must not have
NULL values.
Exception:
- If avoiding NULL values will require creating a new relation, the attribute is allowed to have NULLs.
-
Underline the
primary key
of each relation
- For every foreign key in the
relational model:
- Draw an arrow from the foreign key to the relation that the foreign key is "pointing to" (i.e., it's "home relation").
Answer:
-
Design a
Relational Data Model
for the following ER model
of a manufacturer/customer database:
Comments on the ER-diagram:
- The Manufacturer entity represent the manufacturers
- The Part entity represent the parts
- The Order entity represent the orders made
- The Customer entity represent the customers
- The key in each
entity is
underlined with a
solid line.
- The Makes relationship represents the "who-make-which-part" relationship
- The contains relationship represents the parts in the orders
- The orders relationship represents the "which-customer-made-which-order" relationship
Your relational model answer must satisfy the requirements stated/given in Question 1 above.
Answer:
- Design a
Relational Data Model
for the following ER model
of a bank:
Comments on the ER-diagram:
- The Bank entity represent the banks
- The Branch entity represent
the branches of a bank
Important note:
- The attribute BranchNo in
the Branch is the attribute that
is
required to
form a key
for a Branch entity
(I.e.: BranchNo is like the name attribute in Dependent in the Company Database example)
- The attribute BranchNo in
the Branch is the attribute that
is
required to
form a key
for a Branch entity
- The Account entity represent the bank accounts
- The Loan entity represent the bank loans
- The Customer entity represent the bank customers
- The key in each (non-weak) entity is underlined with a solid line.
-
- The Makes relationship represents the "who-make-which-part" relationship
- The contains relationship represents the parts in the orders
- The orders relationship represents the "which-customer-made-which-order" relationship
Your relational model answer must satisfy the requirements stated/given in Question 1 above.
Answer:
- Design a
Relational Data Model
for the following ER model
of a university:
Comments on the ER-diagram:
- The Student entity represent the students in the university
- The Department entity represent the departments in the university
- The Course entity represent the courses
- The Grade entity represent the different grades that you can receive (A, B, C, D, F)
- The key in each
entity is
underlined with a
solid line.
- The Majors relationship represents
the "who-majors-in-what" relationship
Important note:
- The declareDate is the date on that a student declares (one of) his/her major
- A student can have
(at most) 2 majors
(just like Emory)
When designing this relationship in the Relational Model, make sure that your answer complies with the stated requirements in Question 1 above
- The teaches relationship represents the course offerings
- The GradeReport relationship represents the "who-got-what-grade-in-which-course" relationship
Your relational model answer must satisfy the requirements stated/given in Question 1 above.
Answer:
