Relational Database

Relational Database
Name
Course
Instructor
Date

Based on the assumptions that the semester is a key candidate depicturing the period of study then it follows that this value varies and helps in building the relational database
{Semester, BuildingCode, Room#, TimePeriod, Weekdays} this holds so long as the students cannot be assigned to different courses in the same lecture Room at the same time in the semester
{Univ-Section#} holds so long as it is distinctive for all the semesters.
{InstructorName, Semester} is assumed that there will be no clash in the classes being taught for each semester, and with each instructor teaching only one course.
{Univ_Section#, if the attribute is not unique, then there is a need to understand the section numbering being followed by the university. On the other hand if the course sections have unique numbers for a particular semester it follows that the candidate key is{Univ_Section# student}
Typically, the members of an entity, all participate in a relationship, and the relational model helps to illustrate the references in the relationship constraints. The assumption that an entity participates in only one relationship holds also when there is a constraint and total participation. However, there are also times when there is partial participation since not all entities are in the relationship participation. In a schema of relationship the attributes, key as well as relationship. Using the constraint allows one to define and enforce the data base, since the constraint defines rules on values in the data base while also helping to e...