This will be validated by the organization's users who will record the time for filling a form. The form is not an user-based functionality (no logging in is required), so this functionality cannot be logged in the logs itself and verified that way.
This will be validated by the organization's users who will record the time for filling a form. The form is not an user-based functionality (no logging in is required), so this functionality cannot be logged in the logs itself and verified that way.
**Result:**
**Resuls:** Our test users seemed to be already familiar with this functionality (perhaps because they deal with the same questions on the from on every day basis anyway) and they filled the form **on average in 1 minute**. This will depend on how long description is being written to the filed of 'What has happened?'. Some users were very throughout and provided a very detailed description, so their time increased, but none of them faced any difficulties with the task.
We consider this requirement filled, because all users were able to fill the from in a minute or two and the time it takes the user to write a description of their liking is not related to the functionality of this task, e.g. if the user wants to to quickly send the alert or prefers a very detailed description. The goal was rather to verify the understandability of the form, required fields and all validation messages if any happen to be displayed (e.g. some fields are missing).
2.**_Four out of five people should be able to review an alert within 7 minutes after having a 0.5 to 1-hour introduction to the system. (UC-2 and UC-21)_**
2.**_Four out of five people should be able to review an alert within 7 minutes after having a 0.5 to 1-hour introduction to the system. (UC-2 and UC-21)_**
This will be validated by the organization's users who will record their time for opening a new alert and adding all neccessary data to open the alert as a case.
This will be validated by the organization's users who will record their time for opening a new alert and adding all neccessary data to open the alert as a case. The required fields to be filled in order to open a case are: species group, species and region.
**Result: Our test users opened cases in maximum of 3 minutes. Expert users do that on average in 1 minute.**
The results depended on if the user had inserted the alert themself or not. In cases where the user had submitted the alert themself, they already knew what type of animal it was and in what region, so they filled the neccessary fields in under 1 minute. In cases we provided the alert, they had to take some time to read the data, so it took a few minutes more, but always under the required 7 minutes.
**Result:**
Additonally, we noted that the main use case for our users, is to not only open the case but immediately assign it to a volunteer as well, add injuries or some additonal descriptions of the history of the case as well. Meaning they were able to perform additional steps and still finish in a few minutes, so we consider this functionality to be passed.
3.**_Novice users should be able to filter materials in 1 minute and expert users should be able to filter materials in 30 seconds._**
3.**_Novice users should be able to filter materials in 1 minute and expert users should be able to filter materials in 30 seconds._**
This will be validated by the organization's users and they will be given a test case: 'Filter out all materials that have a species group 'Kahepaikne'' and they will record their time.
This will be validated by the organization's users and they will be given a test case: 'Filter out all materials that have a species group 'Kahepaikne'' and they will record their time.
