Question

. Consider the scenario where the School has to automate its systems and wants to store details of its
staff details like their sno, name, salary, DOB, DOJ, experience, age, gender, phNo are stored. Sno
is the primary key, experience is a derived attribute. The student details like regNo, Name, sem,
age, city, dob, age, phNo are stored. regNo is the primary Key, phNo is a single valued attribute.
Students have to mandatorily register for Courses (ccode, cname, credits) that are taught by staff.
Students and staffs are associated with one or the other departments which have only one attribute
dname which also serves as a primary key. Draw the ER diagram with appropriate notations,
relationships with cardinalities and participation constraints. (Note: Make no new assumptions
regarding the design and strictly adhere to the given details only)

Answer 1

The ER diagram is as followed.

Some notations dislayed in the ER diagram are:

rectangular box - entity

oval box - attributes

dashed oval - derived attributes

underlined attributed - primary key

diamond box - relationships

For any doubts feel free to ask.