Reference no: EM133426669

Question: Read the given business scenario. Draw the Entity relationship diagram (Logical Model). Identify all entities. List the attributes underneath each entity. Specify whether they are mandatory or optional. Identify the UIDs and Fks. Identify optionality and cardinality of relationships.

Case Study: "Humber College has several teachers at our school. A teacher can be assigned up to three classes per semester. If a teacher is on leave, he doesn't teach that semester. We keep a record of the teacher's first name, last name, address, phone number, and email address."

"Our school has many departments and each department offers many courses -- such as Database Design, Introduction to SQL, Web Designing, Requirement Analysis and Operating Systems. The departments that are classified as "research only" do not offer any courses.

Each course has a code. For example: Database Design would be CPAN111, Web Designing would be CPAN103, etc. During each semester, a course may be taught in several classes -- so there could be 2 classes of Database Design, 2 classes of Web Designing, etc. Each class can be taught by only one teacher. We assign a unique ID for each class like section A of Database design is given a code like 2729, Section B is 2730 etc. and we also keep track of the day it is taught, the time, and the classroom.

"A student may register in several classes (up to six classes) at a given time. But can take each class only one in that given period e.g. a student can take Database design course in only one class. Each class may have up to 35 students. St_id identifies each student uniquely. Students' lastname, firstname, initial for middle name, phone# and email is recorded in the database."