3. Pilot Feedback - Long [WATERVERSE Project Pilots]: Submission #35

Submission information

Submission Number: 35

Submission ID: 541

Submission UUID: 8bfc2309-6439-4ecb-bc13-87846ccbd905

Submission URI: /el/projects/waterverse/waterverse_pilots_feedback_long_submit

Δημιουργήθηκε: Τετ, 04/24/2024 - 14:17

Completed: Τετ, 04/24/2024 - 14:20

Τροποποιημένο: Τετ, 04/24/2024 - 14:20

Remote IP address: 80.74.51.59

Submitted by: Ανώνυμος

Γλώσσα: English

Is draft: Όχι

Τρέχουσα σελίδα: Complete

Webform: 3. Pilot Feedback - Long [WATERVERSE Project Pilots]

Information and Consent

[WaterVerse Project Pilots] Pilot feedback - Long WaterVerse Logo

Target responders: All WATERVERSE Pilot Participants

Please, read the Participant Information Sheet and provide your explicit consent below before moving to the pilot participation and feedback provision.

The pre-assessment questionnaire requires approximately 10 minutes to be completed.

Statement of Informed Consent

Name and Date

Full name: Matteo Basile

Profile of participant

Pilot site/country Germany

I participate in this pilot exercise with the role: IT personnel at the water organisation

Affiliated Organisation ENG

Type of affiliated organisation: Research Centre

Email [optional]: {Empty}

Telephone [optional]: {Empty}

Page 1

Functional suitability

The functionality of the tool with regards to the user requirements is complete. 3

The implementation of data and information transfers through the interface functions is correct. 4

Low frequency of failures to exchange data between the component and other involved components/tools. 4

No deviation between the actual and reasonably expected results. 3

Low frequency of encountering inaccurate results/behaviour. 4

functional_suitability_average 4

Reliability

The component/tool was operational and available when required for use. 3

When a failure occurred, no much time was required before gradual start-up of the component/tool. 3

Sufficient capability of the involved functionality in restoring itself after an abnormal event or at request. 3

reliability_average 3

Usability

I am able to recognise whether the component/tool is appropriate for fulfilling my requirements. 4

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. 2

The component/tool offered sufficient support in avoiding errors when using its functionality. 3

usability_average 3

Page 2

Performance efficiency

Satisfactory response time of the functionality. 3

Throughput of the operations close to the specified requirements. 3

Proper utilisation of memory resources (did you, for example, encounter “low memory” problems?). 2

Ability for the system to remain operational when pushed to its limits in terms of number of users, frequency of requests, etc. 2

performance_efficiency_average 3

Page 3

Compatibility

Sufficient use of standard application programming interfaces. 3

Sufficient openness and ease of use of the interfaces. 3

compatibility_average 3

Security

The software ensures that only authorised individuals have access to sensitive data. 4

The software prevents unauthorised access or modification of data, ensuring data accuracy and consistency. 4

The software provides evidence of actions or events, making it difficult for involved parties to deny their involvement. 2

The software traces actions and activities to specific entities, ensuring clear accountability. 3

The software verifies and ensures the true identity of subjects or resources within the system. 3

security_average 3

Δευτερεύουσες καρτέλες