UML Diagram

Below can be found 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. 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 just the date and time 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.
• 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 association between review and student/tutor is directional so authors of reviews can see what they have written but viewers cannot see authors.
• Tutors will receive a rating out of 5 on their teaching qualities but students will only receive a textual comment hence the separation between student and tutor reviews.
• 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 hence why the multiplicity is 0..1.
• Rooms do not need an availabilities 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.