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

Información del envío

Número del envío: 45

ID del envío: 577

Submission UUID: 6366e08b-f863-41eb-95ee-012128f2a18c

Submission URI: /es/projects/waterverse/waterverse_pilots_feedback_long_submit

Creado: Mié, 24/04/2024 - 14:23

Completado: Mié, 24/04/2024 - 14:35

Modificado: Mié, 24/04/2024 - 14:35

Remote IP address: 80.74.51.59

Enviado por: Anónimo

Idioma: English

Is draft: No

Página actual: Completo

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: Rihab Feki

Profile of participant

Pilot site/country Germany

I participate in this pilot exercise with the role: Technology developer (partner)

Affiliated Organisation FIWARE

Type of affiliated organisation: Regulatory Body at national level, Regulatory Body at EU level

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

No deviation between the actual and reasonably expected results. 4

Low frequency of encountering inaccurate results/behaviour. 3

functional_suitability_average 3

Reliability

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

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

The component/tool has sufficient attractiveness of the user interface. 2

A sufficiently high proportion of the user interface elements could be customised to my satisfaction. 1

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

usability_average 2

Page 2

Performance efficiency

Satisfactory response time of the functionality. 3

Throughput of the operations close to the specified requirements. 4

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

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

performance_efficiency_average 4

Maintainability

Sufficiently easy to analyse a failure occurrence. 3

Sufficiently easy to find the cause of a failure. 1

Sufficient ability of recording individual activities during operation of the involved services/functions. 2

Sufficient ability to monitoring the execution status. 3

Sufficient readiness of services to accept parameterisation. 4

Sufficient availability of the appropriate mechanisms to be ready for changes at any time. 3

Sufficient ability to decompose the service/functionality into smaller pieces, without affecting the operation of the others. 4

Sufficient ability to keeping the effect of the modification of the involved tool/functionality local. 2

Sufficient availability of information on the tool/component functionality, in order to perform the testing. 3

Acceptable time needed for testing after a failure resolution. 2

Sufficient ability to take pieces of the tool/component and use it in another context. 3

maintainability_average 3

Portability (please, rate based on best guess given the information available)

Good adaptability of the tool/component to several hardware and software operation environments and network facilities. 3

Good adaptability of the tool/component to other infrastructures of water organisations. 4

Low level of effort required for the tool/component to be adapted to a specific operational environment. 3

Sufficient documentation for the installation process. 2

Sufficnent ease and flexibility of installation process. 3

Sufficient ease of performing subsequent installations. 2

Sufficient ease of maintaining the tool/component when replacements of other parts of the system happen. 3

Sufficient ease of maintaining the continuation of the data flows at replacement requests. 3

portability_average 3

Page 3

Compatibility

Sufficient ability to operate within a shared integration environment, together with other tools/components. 3

Low degree of customisation required when the tool/component needs to co-exist in a specific integration environment. 3

Sufficient use of standard application programming interfaces. 4

Sufficient openness and ease of use of the interfaces. 4

compatibility_average 4

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

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

Solapas secundarias