Use cases

Client-defined use cases

These use cases serve as a foundation for the development and implementation of features within the application.

General use cases

User wants to create an account or log in

1. User opens the application
2. User gets redirected to the application (if not yet logged in)
3. User clicks on "Log In"
4. User logs in using CAS
5. User gets redirected to the application dashboard

For the use cases that follow, we assume the user has already succesfully been logged in

Student use cases

Professor use cases

Professor wants to create a course

2. Professor lands on the dashboard
3. Professor clicks on the "create a course" button
4. Professor fills out necessary course fields
5. Professor submits the form

Professor wants a summary of submissions for a project

1. Professor lands on the dashboard
2. Professor selects (or searches) a course
3. Professor selects a project under the selected course
4. Professor sees an overview of submissions for the selected project

Professor wants to manage assistants

1. Professor lands on the dashboard
2. Professor selects (or searches) a course
3. Professor sees a list of assistants for the selected course 4. Professor clicks on the "add" button, a pop-up appears with a search input for adding assistants 4. Professor clicks on the "remove" button to remove assistants from the list

Assistant use cases

Admin use cases