Consider the following simplified description of a university where professors teach seminars in

which students can enroll. Note: screenshots from other websites$/$tools will not be accepted $(0$

mark$)$

Part $1$: Draw a class diagram for this university. Add attributes and methods when necessary. You

do not have to include getters and setters for attributes. Visibility modifiers $($public$,$ private, etc.$)$

are not required.

A professor possesses the following attributes: name, address, phone number,

email address, and salary. A student, on the other hand, also has a name,

address, phone number, and email address, but does not receive a salary.

Instead, a student has an average mark, which is derived from the final marks

obtained in their seminars.

A seminar is identified by a name and a unique number. When a student enrolls

in a seminar, their marks for that seminar are recorded, and one can retrieve

both the current average mark and the final mark, if it has been assigned.

Additionally, a list of all seminars a student is enrolled in can be accessed.

Professors are responsible for teaching seminars, with each seminar being

taught by a minimum of one and a maximum of three professors. Seminars are

categorized into two types: bachelor and master. Students enrolled in bachelor

seminars are not allowed to withdraw, whereas students enrolled in master

seminars have the option to withdraw.

Part $2$: Create a UML Use Case Diagram that shown the main functionalities $(5$ or $6)$ from the

previous scenario in $($Part $1)$ for Professor.