Question

Create an Entity-Relationship Diagram (ERD).

In the ERD include the following:

 entities

 primary keys for all entities

 attributes - use "good" names for attributes, use only single-valued attributes

 relationships - use Crow's foot or UML notation; name relationships that could be ambiguous

 cardinality - minimum (optional/mandatory) and maximum (one or many) on both ends of the relationship - use reasonable assumptions if there is insufficient information in the description

Student/Course registration system for a university

Students have a unique identification number, first name, middle initial, last name, year (Fr/So/Jr/Sr), have declared a major, and are assigned one faculty advisor. We need to know only what is the current major and who is the current advisor, we don't need to keep a historical record of changes.

Advisors are faculty members. Faculty have a unique employee number, first name, last name, year hired, and a highest educational degree. Every faculty member has one or more areas of expertise, naturally, several faculty can be experts in the same area.

Many courses are offered, and each course has a course id, name, description and number of credits. Courses are offered in Sections, the same course can have many sections but each section is only of one course.

Sections have and identification number, a term (spring/fall/summerA, etc), year, and a mode of instruction (face-to-face, hybrid, online) that records the mode for the section as a whole (our current section of System Analysis and Design is a hybrid mode). A section is taught by one faculty member, and each faculty member may teach many sections.

Students can register for any number of sections, and each section may have many students. This combination of sections and students creates a Roster. In the Roster, we record which student is registered for which section and the grade the student received.

Sections are offered in many sessions. A session is the actual delivery of the section material. Every section has multiple sessions but each session only belongs to one section. Each session has and id, and a mode of instruction (one week it could be in-person, another week it could be online, even though the whole section has its own mode).

The available days and times for sessions are kept in a Timeslot entity, with a unique id for each slot, day, start time and end time(e.g., 12,"Mon", "17:00","19:40"). Each session is held at only one timeslot, and each timeslot can have many sessions (e.g., Wed at 9:00 to 9:50 has many sessions across the university). Each session is also held in one location.

Locations have identification numbers, building name, room number and a phone number. Locations are used by many sessions but each session is held only at one location.

Answer 1