UML Diagram

Please find below the class diagram used to generate code for the repository.
Comments:

• The purpose of the user class is to minimize repetition of information if a person requires both a student account and a tutor account. This class is linked to the role class (player-role occurrence) where the user can either tutor or student, or both. They will have a different username and password depending on the account but the same contact information.
• A tutor will have availabilities which is represented by the availability class which consists of the date (day_month_year) and time (min_hour) that the tutor is available. The tutor will therefore have a list of availabilities. The student does not need to input their availabilities.
• The purpose of the courseOffering class is to indicate which specific term and year the course is being taught in. The general information of the course such as course code and description are contained in the Course class which will be true for all offerings. The course class will only display courses that are supported by the system and will only be available if the university class is also supported by the system.
• Both the student and tutor can access the reviews written about themselves however, they will not know the author of the review. This is why the "author" association between review and role is directional so authors of reviews can see what they have written but viewers cannot see authors.
• Reviews can be either textual, which will need to be approved by the company manager, or they can be just a rating out of 5.
• To create a session, a student will select the date, time and tutor for a specific class. There will not be a room assignment until a tutor accepts the request, hence why the multiplicity is 0..1.
• Rooms do not need an availability class since the only way they are occupied is if they have a session booked. Unlike tutors who have outside commitments, the availability of the room can be found by looking at all the sessions it is booked for.