This unit, you will convert an ER diagram for a similar situation into a Relational Data Model. The ER Diagram is shown at the end of the directions and represents a slightly different scenario from last week. In particular, the differences are as follows:

1. Schools and Departments are not considered to be entities on their own, but just attributes in other tables.
2. Course offerings are an associative relationship between Faculty and Course entities. A Faculty member teaches a course that is being offered. An offering has a unique OfferingID that is never repeated. The offering relationship keeps track of the Semester in which the Offering took place, the name of the section and the classroom where it was taught. As before, when a semester ends, students grades are reported to a file of Official Records. Every student with grades as references to the Official Records where all her/his grades are saved.
3. Student associations may now be advised by none, one or more than one Faculty member.

You must convert the given ER Diagram into a Relational Data Model following the guidelines of the textbook and the course shell. Be sure to create rows of boxes for every required table, each box should contain a field within the table. Primary keys should be properly underlined and foreign key relations should be clearly indicated with arrows.

Deliverables

Create and submit a Relational Data Model Design with a diagram showing all tables, primary keys, and foreign key relationships that describe the given ER Diagram.

Advises HI Advises FACULTY Faculty ID First Name Initials Last Name Position Office Phone No STUDENT StudentiD First Name Initials Last Name Classification School Major Belongs STUDENT ASSOCIATION AssociationID Association Name Teaches Has COURSE CourselD Name Department Credit Hours OFFERING Semester Section Classroom Reports Offers OFFICIAL RECORD Grade