Update Non functional requirements verification authored by elisabet hein's avatar elisabet hein
......@@ -5,9 +5,13 @@ title: Non-functional requirements verification
1. **_An emergency alert should be processed and visible in the ticket management page in less than 20 seconds after submitting it._**
Issue: #148
**Result:** Backend logs show that alerts are inserted to database in **less than a second** and after refresing the ticket management page, the alert is visible there as well. Every time it takes only a few seconds. The manual work to refresh the page is also includes in this time, so in reality, this process takes maximum of few seconds. And as the processing time is so little, the amount of fields filled do not play a role - e.g. if all fields in the alert are filled or if some unrequired are left empty.
2. **_A picture should be uploaded to Google Drive in less than 1 minute after submitting an emergency alert._**
Issue: #149
**Result:** Backend logs show that a single picture will be uploaded to Google Drive every time in **less than 10 seconds**. Usually in a few seconds. And is accessible in the Drive itself too in a few seconds (title is the time of the alert submittion + number of the picture (e.g first or second picture of this alert)).
**Problems we found:** Some pictures are too large to be proccessed by our server and result in error code 413, even if the application's properties are set to allow files up to 100MB or are tried to be uploaded in batches. We assume this is because the server does not have much disk space as we have needed to clear up space multiple times now. And our solution to this is to display a message to send those pictures via mail if the files happen to be too large.
......@@ -16,6 +20,8 @@ title: Non-functional requirements verification
1. **_Four out of five people should be able to report an injury within 2 minutes without having any introduction to the reporting form. (UC-1 and UC-3))_**
Issue: #150
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.
**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.
......@@ -23,6 +29,8 @@ title: Non-functional requirements verification
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)_**
Issue: #151
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.**
......@@ -32,6 +40,8 @@ title: Non-functional requirements verification
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._**
Issue: #152
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.
**Results:** None of the test users considered themselves as experts on the materials page but they all were able to fill out the filtering input with correct species group and find the correct material link in under 1 minute. They did not encounter difficulties with this task.
\ No newline at end of file