Question: We would like to build a database that contains information about the departments and courses offered by the departments. The description of a department consists
We would like to build a database that contains information about the departments and courses offered by the departments. The description of a department consists of the department name, the full name of the chairperson, the number of building where a department is located (wo assume that each department is located in only ane building), and the budget. Departments offer courses. Courses are described by course code (0.g. CSIT115), title, amount of credit points, and semester (e.g. Autumn, Spring, or Summer). Departments offer many courses and each course is offered by only one department. Each department is uniquely identified by a department name. It is aiso identified by the chairperson's name. Course code is a unique identification of each course. We would like to add to the database information about students and courses enrolled by students. The description of a student consists of the student's number, name and date of birth. Student number uniquely identifies each student. The description of a course is the same as in the design created so far. There is no need to change it. Students are allowed to enroll in zero or more courses. Each course is enrolled by one or more students, Enrolment is described by enrolment date. There are two groups of students: undergraduate students and postgraduate students, Undergraduate students are additionally described by the title of the software project. Postgraduate students are additionally described by a name of the academic staff member who supervises the preparation of their postgraduate thesis. Draw a conceptual schema for the specification of a database domain listed above, Use a notation of UML simplified ciass diagrams explained to you during the lecture classes in the subject. There is NO NEED to provide a detailed analysis of how a condeptual schema has been created. The final conceptual schema expressed in a notation of UML simplified classes is completely sufficient. It is not allowed to add any attributes that are not mentioned in the specification above. We would like to build a database that contains information about the departments and courses offered by the departments. The description of a department consists of the department name, the full name of the chairperson, the number of building where a department is located (wo assume that each department is located in only ane building), and the budget. Departments offer courses. Courses are described by course code (0.g. CSIT115), title, amount of credit points, and semester (e.g. Autumn, Spring, or Summer). Departments offer many courses and each course is offered by only one department. Each department is uniquely identified by a department name. It is aiso identified by the chairperson's name. Course code is a unique identification of each course. We would like to add to the database information about students and courses enrolled by students. The description of a student consists of the student's number, name and date of birth. Student number uniquely identifies each student. The description of a course is the same as in the design created so far. There is no need to change it. Students are allowed to enroll in zero or more courses. Each course is enrolled by one or more students, Enrolment is described by enrolment date. There are two groups of students: undergraduate students and postgraduate students, Undergraduate students are additionally described by the title of the software project. Postgraduate students are additionally described by a name of the academic staff member who supervises the preparation of their postgraduate thesis. Draw a conceptual schema for the specification of a database domain listed above, Use a notation of UML simplified ciass diagrams explained to you during the lecture classes in the subject. There is NO NEED to provide a detailed analysis of how a condeptual schema has been created. The final conceptual schema expressed in a notation of UML simplified classes is completely sufficient. It is not allowed to add any attributes that are not mentioned in the specification above