Domognostics+ - Testing and Verification Questionnaire
Information and consent
Before responding to the questionnaire, please, make sure you follow the set of test cases/scenarios given below, which will guide you to cover the functionality of the Domognostics+ platform:
• Login to the platform.
• Change your password through your account .
• Logout from the platform and confirm.
• Navigate through dashboard information and use the presentation of the latest values, as well as the thresholds.
• Create a new building and point its location in a map.
• Add floors to a building, by uploading the floor plan image.
• Mark multiple zones in a floor-plan.
• Add three sensors in two different areas/zones.
• View the resulted building topology.
• Create a new sensor and add at least 3 attributes measured by the sensor (defining the measured property, measurement unit and all other parameters required per type of sensor).
• Go back to the topology of the building and add the new sensor to another zone.
• View the graphical representation of the timeseries of a sensor and zoom in specific areas of the visualisation.
• Add min and max thresholds to generate alerts for a specific sensor/attribute.
• Generate a new report for exporting, for a specific zone and for a specific time-range.
• Check your alerts and clear one of them.
• Change your profile for receiving alerts, choosing email and/or sms.
• Configure the algorithms one by one and set them to run periodically.
• Go to analytics, run the available analysis and check the heatmaps and virtual sensor estimations on the floor plan of one or more floors.
Also note: the scale adopted in the questionnaire is: 1 = Poor, 2 = Good, 3 = Very Good, 4 = Excellent. No answer means that the specific statement/question is not applicable to your tests. In some cases the wording poor…excellent may not fit exactly; in those cases, please, consider it as level of agreement to the statement, level of satisfaction, etc., with 1 remaining the lowest and 4 remaining the highest score.
Consent: *
Yes | No | |
---|---|---|
I provide my explicit consent for my participation in the testing excersise of the Domognostics+ Platform and for the subsequent processing of the data and information I provide, in accordance with the project's research protocol: |
Testing and verification feedback
1. Functional suitability (Degree to which the system/product/module provides functions that meet the stated and implied needs when used under the pre-specified conditions) *
Poor | Good | Very good | Excellent | |
---|---|---|---|---|
The provided functionality is complete and covers all the specified user objectives | ||||
The provided functionality is appropriate and facilitate the accomplishment of the specified user objectives |
Please, elaborate where you deem necessary.
2. Reliability (Degree to which a system, product or component performs specified functions under specified conditions for a specified period of time) *
Poor | Good | Very good | Excellent | |
---|---|---|---|---|
The system and its functionalities were available and operational when I was going through the test cases. | ||||
The functionality is mature and is executed reliably |
Please, elaborate where you deem necessary.
3. Usability (Degree to which a product or system can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use) *
Poor | Good | Very good | Excellent | |
---|---|---|---|---|
My impression when going through the test cases is positive and I could recognise the functions and their appropriateness. | ||||
It was rather easy for me to understand what I should do in order to accomplish the task at hand. | ||||
It was easy for me to operate the system | ||||
I was able to understand and I felt good with the visualisation of the functionality and the results of my actions in the system. | ||||
The system helped me to avoid errors while running the funcitonality. |
Please, elaborate where you deem necessary.
4. Performance efficiency (Performance relative to the amount of resources used under stated conditions) *
Poor | Good | Very good | Excellent | |
---|---|---|---|---|
The system response was very good in terms of time. |
Please, elaborate where you deem necessary.
5. Maintainability (Degree of effectiveness and efficiency with which a product or system can be modified by the intended maintainers) *
Poor | Good | Very good | Excellent | |
---|---|---|---|---|
As a technical person, I can understand the components of the system and how I can modify them to respond to new requirements for improvements or bug fixes. | ||||
The system has been built in a modular way and I can modify parts of it without compromising the functionality of other parts. |
Please, elaborate where you deem necessary.
6. Compatibility (Degree to which a product, system or component can exchange information with other products, systems or components, and/or perform its required functions, while sharing the same hardware or software environment) *
Poor | Good | Very good | Excellent | |
---|---|---|---|---|
The system is able to work with the smart building apps smoothly, without any integration issues. | ||||
The API and the integration guidelines are very clear and I can undertake the integration of additional algorithms in collaboration with the scientific team. | ||||
The algorithms (smart building apps) can use the API and present meaningful results. |
Please, elaborate where you deem necessary.