Ch 13: Mapping ER Diagrams to Relational Tables

Consider modeling a proctored database system for a university examination department. You are given the following requirements: 1. Students have a unique Registration Number (RegNo) and student details. 2. Departments offer various Exam papers (CourseCode, CourseTitle). 3. Each exam is scheduled in a specific Room on a specific Date/Time. 4. Students register to take examinations in these rooms, and we must record the Grade they obtain. Formulate the core entities, identify their primary attributes, and draw up the relational mapping tables (including composite keys) required to establish a fully mapped physical database model.

-- Conceptual Schema Design:
-- STUDENT (M) <--- ENROLLMENT ---> (N) EXAM

Consider modeling a conceptual database system for a university examination department. The business rules specify: 1. Students have a unique Registration Number (RegNo), Name, and Date of Birth. 2. Departments offer various Exam papers, identified by a unique CourseCode and CourseTitle. 3. Each student can register for multiple exams, and each exam can host multiple students. We must record the Grade obtained by each student in each exam. Identify the core entity types, attributes, and relationship cardinalities, and design the physical SQL tables (including composite keys) required to model this scenario.

-- Conceptual Schema Mapping:
-- STUDENT (M) <--- EXAM_REGISTRATION ---> (N) EXAM