Update Non functional requirements verification authored by elisabet hein's avatar elisabet hein
--- ---
title: Non-functional requirements verification title: Non-functional requirements verification
--- ---
# **Perormance**
1. **_An emergency alert should be processed and visible in the ticket management page in less than 20 seconds after submitting it._**
**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 rolw - e.g. if all fields in the alert are filled or if some are left empty.
2. **_A picture should be uploaded to Google Drive in less than 1 minute after submitting an emergency alert._**
**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.
# **Usability**
1. **_Four out of five people should be able to report an injury within minutes without having any introduction to the reporting form. (UC-1 and UC-3))_**
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:**
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.
**Result:**
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.
**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