-
Notifications
You must be signed in to change notification settings - Fork 1
Use Cases
The creation of a new user
Creating a new user
Student
Creating a new user
- The new user is a student
- The user has an email address
- The student fills in the form and sends it to the server.
The user is in the database of users to be reviewed.
The user now has to create an engagement.
(An admin creates a new admin, that is possibly not a student.)
To be checked: do we have to create a use case “create student”, “create coach”, …?
The user creates an accoubt with “Connect to GitHub”
Before you can use your newly created account an admin first has to approve it
Create user
Admin
Accepting a user
- The user had been created.
- The user has not yet been activated.
- The admin gets a notification that a new user has been created.
- The admin accepts the user.
The user has been activated and is in the group of people to be reviewed.
The user is denied and deleted.
A user requests to have his account deleted
User modification
Admin
Deleting a user
- The user account has been created.
- The system deletes the account.
- The system deletes the linked engagements.
The user is removed from the system and no information is left about it.
Not applicable.
After each edition, all users are cleared from the database
User modification
Admin
Deleting all users
- The session has ended
- The system deletes all accounts.
- The system deletes the linked engagements.
All users are removed from the system and no information is left about it.
Not applicable.
The creation of a new project
create project
admin
Create project.
Project is not created yet.
Fill in form for new project:
- required skills for the project
- who is the partner
- number of students needed
Project is created.
A coach suggests a student for a project
suggest yes/no/maybe for user for project
coach
user has tag yes/no/maybe from specific coach for specific project
- The user had been created.
- The user has been activated.
- The coach has been assigned a project
- The coach chooses suggestion (yes/no/maybe)
- update user
user is updated
An admin deems that a certain is the right person for a certain project
Create project
Admin
Assigning a user to a project.
- The user had been created.
- The project has been created.
- The admin can assign a student to the project
The user has been added to the project.
The user is swiped to the project, but is already assigned to another project.
- The admin gets a notification that there is a conflict.
- The admin needs to resolve the conflict, by deleting student from project.
During project initialization an admin needs to assign coaches to a project
Create project
Admin
Assigning a coach to a project.
- The user had been created.
- The project has been created.
- The admin can assign a coach to the project
The user has been added to the project.
During certain steps mails need to be sent out
Notification
Admins
Let student know yes/maybe/no OR if account is removed.
- The user has been created.
- The admins have decided on yes/maybe/no OR the student asked to remove its data.
- The student has not yet received an email about the same subject.
- The button to decide on a student is hit OR the student has hit the button to remove its profile.
- The template for yes/maybe/no is taken and parameters are filled in OR the template that a user has been deleted is filled in.
- The email is sent to the student.
The student has received an email from the admins.
The creation of a new template
Send e-mail
Admin
Create a template for an automated email.
None
- The admin creates an email template with placeholders for certain words, names, ...
- The admin saves the template.
A new email template is created and can be used to send emails to certain users for certain actions.
The user is swiped to the project, but is already assigned to another project.
- The admin gets a notification that there is a conflict.
- The admin needs to resolve the conflict, by deleting student from project.
A template should be editable
Create project
Admin
Assigning a user to a project.
- The user had been created.
- The project has been created.
- The user can be matched with the project.
- The admin can be swiped into the project.
The user has been added to the project.
The user is swiped to the project, but is already assigned to another project.
- The admin gets a notification that there is a conflict.
- The admin needs to resolve the conflict, by deleting student from project.