vestr-at-work
commented
1 month ago Use case
Starting situation (Initial assumption)
The clerk has registered a subject and assigned relevant teachers to it. The teacher has opened an editable view of the subject's metadata in Study Information System (SIS).
Normal
- The teacher changes the metadata and clicks on the save button.
- SIS checks if mandatory fields are filled in.
- SIS shows the preview of the changed metadata and asks if teacher really wants to proceed with changes.
- The teacher confirms.
- SIS updates subject's metadata history and saves the data to the database.
What can go wrong
- Not all mandatory metadata saved by the teacher are satisfied. In that case SIS tells the user which metadata are not filled in and teacher must fill them in.
System state on completion
- SIS has the new metadata saved in database and the history showing the changes to the subject is updated as well.
- New metadata can be viewed by users.
User requirement as a user story
As a teacher, I need to be able to update metadata of the subject, such as literature, conditions for passing the subject, description, as I need to ensure the accuracy of information presented to attending students.