You are on page 1of 3

CS304-07S1 - Database Systems

Project Part I

Group N
ER diagram
Table Specifications
(resulting from the reduction of the ER diagram to relational schema)

students (stud_reg_no, f_name, l_name, field, dob, address)


postgraduate (stud_reg_no, degree)
undergraduate (stud_reg_no, degree)

modules (module_no, module_name)


ays (ays_id, year, semester)
['ays' is used as an acronym for 'academic year and semester']

learn (stud_reg_no, module_no, ays_id, fb_given)


[Student could repeat the same module at various years]

teach (lect_reg_no, module_no, ays_id)


[Lecturer could teach the same same module every year]

coordinate (lect_reg_no, module_no, ays_id)


[Coordinator can repeat coordinating the same module every year]

lecturers (lect_reg_no, f_name, l_name, dob, address)


lect_degrees (lect_reg_no, degree)
[This is for a multivalued attribute]

works_for (lect_reg_no, dept_code)


[A lecturer can be attached to multiple departments, sometimes]

departments (dept_code, department, faculty)


[Multiple faculties might have same department names]

fb_for (fb_id, lect_reg_no, module_no)


fb_give (fb_id, access_ip, stud_reg_no)
[stud_reg_no would be an optional field, thus could hold null when anonymous]

feedback (fb_id, access_date, access_time, ... ... ... )


[Many other feedback form values will come under this table, such fields provided in the normal
printed feedback form provided by the University at present]

You might also like