Secundaire tabs
3. Pilot Feedback - Long [WATERVERSE Project Pilots]: Inzending #55
De pagina Tabel toont de algemene informatie en gegevens van een inzending in een tabel. Video bekijken
Details inzending
Inzendingsnummer: 55
ID inzending: 665
Inzending UUID: 55177325-1d5d-4746-aace-9705d393f5dc
Aangemaakt: wo, 06/26/2024 - 14:47
Voltooid: wo, 06/26/2024 - 14:57
Gewijzigd: wo, 06/26/2024 - 14:57
Extern IP-adres: 84.78.26.86
Ingediend door: Anoniem
Taal: English
Concept: Nee
Huidige pagina: Voltooid
I have read the above statements and I hereby provided my explicit consent. | Ja |
---|---|
[Optional] I agree that my personal data can be used for contacting me in the context of inviting me in future events of interest, related to the WATERVERSE. | Nee |
Full name: | Maria Deocón |
Date of consent: | wo, 06/26/2024 - 00:00 |
Pilot site/country | Spain |
I participate in this pilot exercise with the role: | Operator (user of WATERVERSE WDME) at the water organisation |
Affiliated Organisation | Hidralia |
Type of affiliated organisation: | Water utility |
Email [optional]: | |
Telephone [optional]: | |
The functionality of the tool with regards to the user requirements is complete. | 2 |
The implementation of data and information transfers through the interface functions is correct. | 3 |
Low frequency of failures to exchange data between the component and other involved components/tools. | 3 |
No deviation between the actual and reasonably expected results. | 3 |
Low frequency of encountering inaccurate results/behaviour. | 3 |
functional_suitability_average | 3 |
The component/tool was operational and available when required for use. | 2 |
The component/tool satisfied user needs for using it under normal operation. | 3 |
I felt that the component/tool’s functionality was giving expected results and at expected time. | 3 |
Low frequency of breaks of the component/tool. | 3 |
Low degree of appearance of failures/faults during the testing/evaluation period. | 3 |
When a failure occurred, no much time was required before gradual start-up of the component/tool. | 2 |
Sufficient capability of the involved functionality in restoring itself after an abnormal event or at request. | 3 |
reliability_average | 3 |
I am able to recognise whether the component/tool is appropriate for fulfilling my requirements. | 3 |
Within a reasonable time of training, I felt confident in using the tool with effectiveness, efficiency, freedom from risk and satisfaction in the specified context of use. | 4 |
The component/tool offers features that make it easy to operate and control. | 4 |
I am able to control the tool and its operation is within my expectations. | 3 |
The component/tool has sufficient attractiveness of the user interface. | 3 |
A sufficiently high proportion of the user interface elements could be customised to my satisfaction. | 3 |
The component/tool offered sufficient support in avoiding errors when using its functionality. | 4 |
usability_average | 3 |
Satisfactory response time of the functionality. | 2 |
Throughput of the operations close to the specified requirements. | 2 |
performance_efficiency_average | 2 |
maintainability_average | 0 |
portability_average | 0 |
Sufficient use of standard application programming interfaces. | 3 |
Sufficient openness and ease of use of the interfaces. | 3 |
compatibility_average | 3 |
security_average | 0 |