We would like to store information in a database about laboratories, subjects, and employees at auniversity.A subject is described by a subject code, title, description and credits. The subject code uniquely identifies a subject.A subject may require many laboratories. A laboratory belongs to one subject. A laboratory consists of year, session, day of the week, building number, room number, start time, and end time. The attributes year, session, day of the week, building number, room number, and start time together uniquely identify a laboratory.Those who have studied the related subject are eligible candidates for potential tutor positions. A candidate is described by the first name, last name, phone number and email address. A phone number can uniquely identify a candidate. Email is unique too. The database should record the year, session and final grade that the candidates study the subjects.Lecturers teach subjects. A subject may be taught by one or more lecturers. A lecturer teaches zero or more subjects. The database system records the year and session when lecturers teach subjects. A lecturer is described by employee number, first name, last name, phone number, email and salary level. The employee number uniquely identifies a lecturer. The phone number is unique. The email is unique as well.We need tutors or lecturers to supervise laboratories. Tutors and lecturers are employees. When a candidate is hired as a tutor to supervise a laboratory, the database records the employee number and pay rate for the tutor role. The hire date is also recorded in the database. Lecturers can supervise laboratories as well. A laboratory is supervised by one or two employees. An employee can supervise more than one laboratory.Draw a conceptual schema for the specification of a database domain listed above. Use a notation of UML simplified class diagrams explained to you during the lecture classes in the subject.