Cоurse Selectiоn Dаtаbаse Design (Part 1) — E/R diagram Instructiоns You're designing a course selection database for a university. Fill in the blanks based on the E/R diagram for this system. To help visualize the structure, draw the E/R diagram on scratch paper. You're not required to submit the ER diagram. Entities Involved students, courses, teachers, departments Given Information Each student has a unique student ID, a name and age. Each course has a unique name, and time slots and classroom number. Each teacher has a unique teacher ID and name. Each department has a unique department name, an address and a department chair. Additional Information Each student can take several courses. Each course can be taught by only one teacher. Each teacher can teach several courses. Each teacher and each course should only be administered by one department. Fill in the Blanks Entity students has attributes [students_attr1]. has a [students_rel_type1] relationship [students_rel1] to entity [students_ent1]. Entity courses has attributes [courses_attr1]. has a many-to-many relationship [courses_rel1] to entity [courses_ent1]. has a [courses_rel_type2] relationship [courses_rel2] to entity departments. has a [courses_rel_type3] relationship [courses_rel3] to entity [courses_ent3]. Entity teachers has attributes [teachers_attr1]. has a one-to-many relationship [teachers_rel1] to entity [teachers_ent1]. has a [teachers_rel_type2] relationship [teachers_rel2] to entity [teachers_ent2]. Entity departments has attributes [departments_attr1]. has a [departments_rel_type1] relationship [departments_rel1] to entity courses. has a [departments_rel_type2] relationship [departments_rel2] to entity [departments_ent2]. In the E/R diagram entities use [diagram1] shapes. attributes use [diagram2] shapes. relationships use [diagram3] shapes. a key attribute has its text [diagram4] to indicate uniqueness.
Gаrаge Dаtabase Design (Part 1) — E/R diagram Instructiоns Yоu're designing a database cоncerning a local garage. Fill in the blanks based on the E/R diagram for this database. To help visualize the structure, draw the E/R diagram on scratch paper. You’re not required to submit the ER diagram. Entities Involved customer, vehicle, job, part Given Information For each customer, we want to record the (unique) name, address, and contact phone number. For each vehicle, we want to record the unique vehicle’s identification number (VIN), and the vehicle’s make, model and year. For each repair job, we want to record the description of the job done (maximum 200 chars), the date, and the total dollar cost. A repair job may involve zero or more parts (like, e.g., battery, windshield wipers). For each part we want to record the unique part number, the part name and it's cost. Additional Information Each vehicle have one or more repair jobs. Each customer can be primary owner of one or more vehicles. Every vehicle has only one primary owner. Each vehicle can have no more than one repair job in any given day. Fill in the Blanks Entity customer has attributes [customer_attr1]. has a [customer_rel_type1] relationship [customer_rel1] to [customer_str1] entity [customer_ent1]. Entity vehicle has attributes [vehicle_attr1]. has a [vehicle_rel_type1] relationship [vehicle_rel1] to [vehicle_str1] entity [vehicle_ent1]. has a [vehicle_rel_type2] relationship [vehicle_rel2] to weak entity [vehicle_ent2]. Entity job has attributes [job_attr1]. has a [job_rel_type1] relationship [job_rel1] to [job_str1] entity [job_ent1]. has a many-to-many relationship [job_rel2] to [job_str2] entity [job_ent2]. Entity part has attributes [part_attr1]. has a [part_rel_type1] relationship [part_rel1] to [part_str1] entity [part_ent1]. In the E/R diagram weak entity is represented by [diagram1]. the relationship between a weak entity and a strong entity is represented by [diagram2].