Skip to content

Use Cases

Gilles Arnout edited this page Feb 20, 2024 · 16 revisions

Use Cases

All the use cases are listed here.

All Use Cases

User Management

  • create teacher/student (admin)
  • remove teacher/student (admin)
  • change information about teacher/student (admin)

Subject

  • create subject (teacher)
  • remove subject (teacher)
  • change subject (teacher)
  • (un)subscribe to subject (student)

Project

  • create project (teacher)
  • remove project (teacher)
  • change project (teacher)
  • change visibility of project (teacher)
  • create group for project (teacher/student)
  • submit project (student)
  • join group (student)

Details Use Cases

User Management Details

Title create teacher/student (admin)
Description A new teacher/student must be created in the system.
Pre-conditions The admin is logged in.
Post-conditions A new teacher/student has been added.
Actors Admin
Normal flow
  1. Admin chooses to create a new teacher/student
  2. Admin fills in info of the new teacher/student
  3. Admin confirms the creation of the new teacher/student
  4. The system creates a new teacher/student
  5. The system creates an automatic message to the new teacher/student with an automatically generated password
Alternative flow Admin does not confirm user creation:
  1. The creation of the teacher/student will be aborted and returned to the previous screen.
Title remove teacher/student (admin)
Description An existing teacher/student must be removed from the system.
Pre-conditions The admin is logged in and the teacher/student exists in the system.
Post-conditions The teacher/student is removed from the system.
Actors Admin
Normal flow
  1. Admin chooses to remove a specific teacher/student
  2. Admin clicks on the remove button
  3. Admin confirms the removal of the teacher/student
  4. The system removes the teacher/student
  5. The system sends a message to the teacher/student that his account has been removed
Alternative flow Admin does not confirm user removal:
  1. The removal of the teacher/student will be aborted and returned to the previous screen.
Title change information about teacher/student (admin)
Description Information about a teacher/student is modified.
Pre-conditions The admin is logged in and the teacher/student exists in the system.
Post-conditions The teacher/student's information is updated.
Actors Admin
Normal flow
  1. Admin chooses to change the information about a specific teacher/student
  2. Admin clicks on the change information button
  3. Admin fills in the new information about the teacher/student
  4. Admin confirms the information change of the teacher/student
  5. The system changes the information about the teacher/student
  6. The system sends a message to the teacher/student that there information has changed
Alternative flow Admin does not confirm information change:
  1. The new information changes will be discarded and returned to the previous screen.

Subject Details

Title create subject (teacher)
Description A new subject must be created in the system.
Pre-conditions The teacher is logged in.
Post-conditions A new subject has been added.
Actors Teacher
Normal flow
  1. Teacher chooses to create a new subject
  2. Teacher fills in the specifications of the new subject
  3. Teacher confirms the creation of the new subject
  4. The system creates the new subject
Alternative flow Teacher does not confirm subject creation:
  1. The creation of the subject will be aborted and returned to the previous screen.
Title remove subject (teacher)
Description An existing subject must be removed from the system.
Pre-conditions The teacher who created the subject is logged in and the subject exists in the system.
Post-conditions The subject is removed from the system.
Actors Teacher
Normal flow
  1. Teacher chooses to remove a specific subject
  2. Teacher clicks on the remove button
  3. Teacher confirms the removal of the subject
  4. The system removes the subject and unsubscribes all the students from the subject
Alternative flow Teacher does not confirm subject removal:
  1. The removal of the subject will be aborted and returned to the previous screen.
Title change information about subject (teacher)
Description Information about a subject is modified.
Pre-conditions The Teacher who created the subject is logged in and the subject exists in the system.
Post-conditions The subject's information is updated.
Actors Teacher
Normal flow
  1. Teacher chooses to change the information about a specific subject
  2. Teacher clicks on the change information button
  3. Teacher fills in the new information about the subject
  4. Teacher confirms the information change of the subject
  5. The system changes the information about the subject
  6. The system sends a message to the subscribed students that the information of the subject has changed
Alternative flow Teacher does not confirm information change:
  1. The new information changes will be discarded and returned to the previous screen.
Title (un)subscribe to subject (student)
Description Students can (un)subscribe to a subject.
Pre-conditions Student is logged in.
Post-conditions Student (un)subscribed to a subject.
Actors Student
Normal flow
  1. Student chooses to (un)subscribe to a specific subject
  2. Student clicks on the (un)subscribe button
  3. Student confirms the (un)subscription to the subject
  4. The system (un)subscribes the student to the subject
Alternative flow Student does not confirm (un)subscription:
  1. The (un)subscription will be canceled and returned to the previous screen.

Project Details

Title create project (teacher)
Description A new project must be created in the system.
Pre-conditions The teacher is logged in.
Post-conditions A new project has been added.
Actors Teacher
Normal flow
  1. Teacher chooses to create a new project
  2. Teacher fills in the specifications of the new project
  3. Teacher confirms the creation of the new project
  4. The system creates the new project
  5. The system sends a message to the subscribed students that a new project has been added
Alternative flow Teacher does not confirm project creation:
  1. The creation of the project will be aborted and returned to the previous screen.
Title remove project (teacher)
Description An existing project must be removed from the system.
Pre-conditions The teacher who created the subject where the project is from is logged in and the project exists in the system.
Post-conditions The project is removed from the system.
Actors Teacher
Normal flow
  1. Teacher chooses to remove a specific project
  2. Teacher clicks on the remove button
  3. Teacher confirms the removal of the project
  4. The system removes the project
Alternative flow Teacher does not confirm project removal:
  1. The removal of the project will be aborted and returned to the previous screen.
Title change information about project (teacher)
Description Information about the project is modified.
Pre-conditions The teacher who created the subject where the project is from is logged in and the project exists in the system.
Post-conditions The project's information is updated.
Actors Teacher
Normal flow
  1. Teacher chooses to change the information about a specific project
  2. Teacher clicks on the change information button
  3. Teacher fills in the new information about the project
  4. Teacher confirms the information change of the project
  5. The system changes the information about the project
  6. The system sends a message to the subscribed students that the information of the project has changed
Alternative flow Teacher does not confirm information change:
  1. The new information changes will be discarded and returned to the previous screen.
Title change visibility of project (teacher)
Description The visibility of a project is modified.
Pre-conditions The teacher who created the subject where the project is from is logged in and the project exists in the system.
Post-conditions The project's visibility is updated.
Actors Teacher
Normal flow
  1. Teacher chooses to change the visibility of a specific project
  2. Teacher clicks on the change visibility button
  3. Teacher confirms the visibility change of the project
  4. The system changes the visibility of the project
Alternative flow Teacher does not confirm visibility change:
  1. The new visibility changes will be discarded and returned to the previous screen.
Title create group for project (teacher/student)
Description A group is created for a project that students can join.
Pre-conditions The teacher/student is logged in and the project is a group project.
Post-conditions A group is created for the project.
Actors Teacher and Student
Normal flow
  1. Teacher/Student chooses a specific project
  2. Teacher/Student click on the create a group button
  3. Teacher/Student confirm the creation of the group
  4. The system creates a group for the specific project
Alternative flow Teacher/Student does not confirm group creation:
  1. The group creation will be aborted and returned to the previous screen.
Title submit project (student)
Description A student submitted his solution for the project.
Pre-conditions The student is logged in and the project exists in the system.
Post-conditions The solution of the student is submitted.
Actors Student
Normal flow
  1. Student chooses a specific project
  2. Student clicks on the submit button
  3. Student confirms the submission for the project
  4. The system stores the submission
  5. The system sends a message to the student that the submission is succesfull
Alternative flow Student does not confirm submission:
  1. The submission will be aborted and returned to the previous screen.
Submission does not meet requirements:
  1. The system denies the submission and sends a message to the student.
  2. Return to the previous screen.
Title join group (student)
Description A student joins a group for a project.
Pre-conditions The student is logged in, the group exists in the system and the project exists in the system.
Post-conditions The student joins the group.
Actors Student
Normal flow
  1. Student chooses a specific project
  2. Student chooses a specific group
  3. Student clicks the join button
  4. The student confirms joining the group
  5. The system puts the student in the group
  6. The system sends a message to all group members that a new student has joined
Alternative flow Student does not confirm joining the group:
  1. Joining the group will be aborted and returned to the previous screen.
The group is full:
  1. The system denies joining the group and sends a message to the student.
  2. Return to the previous screen.
Clone this wiki locally