Skip to content

Use Cases

Georges Mourant edited this page Oct 13, 2019 · 35 revisions

Important Use Cases

1. Sign-in/Log-in

Tutors should be able to create an account with a username, a private password and an email to receive student notifications. To update their account information, session availabilities and reviews, tutors should be able to log-in to the application with the credentials created during sign up.

Tutors can only sign up by email invitation once the company manager has approved their teaching credentials.

A workflow diagram describing the sign-up use case can be found here.

2. Apply to teach new subjects (and availability indications)

The tutor must submit an application to the company manager indicating which subject(s) they would like to teach. The tutor is not limited to one application; however they must fill one application per subject matter. I.e. if the tutor wants to teach Math and Spanish in the high school level, they must complete two separate applications.

The tutor must also provide their availability for any time period (weekly, monthly or yearly) in order to be paired with a student once the tutor’s application is verified. A tutor can only modify their availabilities once a month or when applying to teach a new subject.

The workflow diagram for this use case can be found here.

3. Set the hourly rate and know the commission rate

After the tutor gets appointed by the manager for a particular subject matter or multiple subject matters of various academic levels, the tutors must decide how much they want to charge per hour for teaching each subject matter and they submit that information in a form in the website.

These hourly rates are then added with the commission rate set by the company and finally made available to be viewed in the website by the users (students, manager, other tutors etc.) as the tutor’s hourly rate. The tutor is made aware of the commission rate through the form. The amount of money generated from the hourly rates without the commission rate is the tutor’s salary.

This allows students to understand how much they have to pay for a session to study the subject matter by that tutor.

The workflow diagram for this use case can be found here .

4. Tutoring Requests (and request notifications)

In order to be informed when a student makes a tutoring request, the tutor should receive a notification of the request including, but not limited to, an email notification. They should have the ability to view the request using their login on the website including the date, time, student’s name, subject matter, and the student’s school.

Once a student has requested a tutoring session, the tutor should be able to view the requester’s reviews from other tutors and the student’s session history.

Once a tutoring session has been requested, the tutor should have the ability to accept or decline the tutoring session.

The workflow diagram for this use case can be found here

5. Reviews

After each session, tutors have a possibility to review their students. It is a score from 1 to 5 with or without a text review. Tutors are also allowed to review the system's performance.

In order to improve the quality of teaching, tutors should be able to review their students- reviews can be anonymous if wanted. In order to improve the system's performance, tutors should be able to review the system- reviews can also be anonymous.

In both cases, writing the review is optional.

The workflow diagram for this use case can be found here