Changes for page b. Test

Last modified by Demi Tao on 2023/04/10 10:13

From version 1.3
edited by XWikiGuest
on 2023/03/24 11:18
Change comment: Added comment
To version 8.3
edited by Demi Tao
on 2023/04/07 17:08
Change comment: Deleted object

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.XWikiGuest
1 +XWiki.DemiTao
Content
... ... @@ -1,32 +1,106 @@
1 1  = 1. Introduction =
2 2  
3 -<include a short summary of the claims to be tested, i.e., the effects of the functions in a specfic use case>
3 +In section [[a. Prototype>>3\. Evaluation.a\. Prototype.WebHome]] two versions of the robot were presented, one with voice functionality and one without.
4 4  
5 +The main claims we are looking to test with this testing procedure are related to the functionality and usability of the robot.
5 5  
7 +The participants will be other students taking this course. The participants will be placed in the shoes of a PwD and be tasked with completing several basic actions with the robot while impaired in several known ways to simulate the difficulties of a PwD.
8 +
9 +After the experiment, the participants will fill out a survey and be asked some more open-ended questions with the purpose of understanding how the interaction with the robot went, and whether they have anything that they find concerning regarding the possible use of the system and its functions in a real-life setting.
10 +
11 +On top of this, a short questionnaire will be sent to several care homes throughout the Netherlands in hopes to get a general idea of whether the caretakers at the facilities think that the system would be a good fit for the proposed use case.
12 +
6 6  = 2. Method =
7 7  
15 +The prototypes are evaluated in a simulated manner and conducted in-person experiments. Participants will be given a [[persona>>doc:Main.sdf.Persona Scenarios.WebHome]] to play act.
8 8  
9 9  == 2.1 Participants ==
10 10  
19 +All students in CS4235 Socio-Cognitive Engineering (2022-2023) in TU Delft are invited to test the robot. In the end, 14 students are presented.
11 11  
12 12  == 2.2 Experimental design ==
13 13  
23 +Prior to the experiment, participants were asked to simulate the experience of a person with dementia. Participants who wore glasses were asked to remove them, while those who did not were provided with short-sighted or far-sighted glasses to replicate the blurred vision and degraded perception that is common in PwDs. Additionally, their index and middle fingers were taped together to simulate the difficulty in controlling movements that many PwDs experience.
14 14  
25 +For this experiment, we used a between-subject design. The control group interacted solely with the stand-alone application, which represented the robot without voice functionality, and received guidance through a single task paper. In contrast, the experimental group engaged with the fully-functional robot, which provided audio instructions, guidance, and encouragement.
26 +
15 15  == 2.3 Tasks ==
16 16  
29 +In the user test, the following tasks were asked of the participants:
17 17  
31 +==== Reminders for activities ====
32 +
33 +* (((
34 +Add a reminder that a relative will pay a visit tomorrow with the format as "sb. will come at 10 am on Friday". Set the reminder to remind you 10 min before that.
35 +)))
36 +* (((
37 +Add a reminder USING A VOICE COMMAND that today at 2 pm will have a general health checkup.
38 +)))
39 +* (((
40 +Check the reminders you have added for today and tomorrow.
41 +)))
42 +
43 +==== Personal profile ====
44 +
45 +* (((
46 +Add relatives as a contact in the "profile" section.
47 +)))
48 +
49 +==== Memory games ====
50 +
51 +* (((
52 +Go to the Games section and play the game.
53 +)))
54 +
55 +==== Medicine reminders ====
56 +
57 +(for professional caregivers)
58 +
59 +* (((
60 +In the section “My Health”, add a medicine reminder to take the medicine **Donepezil**, 1 time per day at 9 PM before going to bed.
61 +)))
62 +* (((
63 +Check medicines that have been added.
64 +)))
65 +* (((
66 +Delete medicines that have been added.
67 +)))
68 +
18 18  == 2.4 Measures ==
19 19  
71 +Two quantitative measures were employed in the user evaluation. The first measure aimed to test attributes including accessibility, trustworthiness, and comprehensibility. The second measure used was the System Usability Scale (SUS), which is a widely-used scale for evaluating the usability of software.
20 20  
73 +In addition to the quantitative measures, a structured interview with open-ended questions was conducted. The aim of this interview was to gain a deeper understanding of participants' experiences with the robot, including any concerns they may have regarding the potential use of the system and its functions in a real-life setting.
74 +
75 +By using both quantitative and qualitative measures, the user evaluation can provide a more comprehensive understanding of participants' experiences and perceptions of the system. This approach allows for a more nuanced analysis of the data and can provide valuable insights into the strengths and weaknesses of the system, as well as areas for improvement.
76 +
21 21  == 2.5 Procedure ==
22 22  
79 +The procedure was conducted as follows:
23 23  
81 +1. Welcome participants and give an introduction.
82 +1. Get them to sign a consent form.
83 +1. Prepare them to pretend to be a person with dementia.
84 +1. Have interaction with the robot and complete the tasks.
85 +1. Complete a questionnaire.
86 +1. Have a short interview with randomly selected participants.
87 +
24 24  == 2.6 Material ==
25 25  
90 +1. Consent form. To protect the privacy of participants and ensure the evaluation process goes smoothly, we will ask participants to sign a consent form, indicating they are willing to take part in the evaluation and the data gathered from the experiment will be analyzed by researchers.
91 +1. Pepper robot.
26 26  
27 27  = 3. Results =
28 28  
95 +|=(% style="width: 199px;" %)Tasks|=(% style="width: 147px;" %)Succeded by Themselves|=(% style="width: 146px;" %)Succeded with Some Guidance|=(% style="width: 185px;" %)Succeded with Detailed Explicit Instructions|=(% style="width: 175px;" %)Average Time to Complete Task (s)
96 +|(% style="width:199px" %)Turning the robot on and off|(% style="width:147px" %) |(% style="width:146px" %) |(% style="width:185px" %) |(% style="width:175px" %)
97 +|(% style="width:199px" %)Add a reminder using "+" button|(% style="width:147px" %) |(% style="width:146px" %) |(% style="width:185px" %) |(% style="width:175px" %)
98 +|(% style="width:199px" %)Add a reminder using voice|(% style="width:147px" %) |(% style="width:146px" %) |(% style="width:185px" %) |(% style="width:175px" %)
99 +|(% style="width:199px" %)Check the reminder|(% style="width:147px" %) |(% style="width:146px" %) |(% style="width:185px" %) |(% style="width:175px" %)
100 +|(% style="width:199px" %)Create a personal profile|(% style="width:147px" %) |(% style="width:146px" %) |(% style="width:185px" %) |(% style="width:175px" %)
29 29  
102 +if possible, note down some Parts Where Users Struggled in each task.
103 +
30 30  = 4. Discussion =
31 31  
32 32  
XWiki.XWikiComments[0]
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.DemiTao
Comment
... ... @@ -1,3 +1,0 @@
1 -The survey can be designed based on UTAUT questionnaire (performance expectancy, effort expectancy, social influence, facilitating conditions) to test usability and user experience.
2 -
3 -Venkatesh, V., Morris, M. G., Davis, G. B., & Davis, F. D. (2003). User Acceptance of Information Technology: Toward a Unified View. //MIS Quarterly//, //27//(3), 425–478. https:~/~/doi.org/10.2307/30036540
Date
... ... @@ -1,1 +1,0 @@
1 -2023-03-23 09:22:38.687
XWiki.XWikiComments[2]
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.MarkNeerincx
Comment
... ... @@ -1,0 +1,5 @@
1 +Refer explicitly to the claims in the specification section ("claims we are looking to test with this testing procedure are related to the functionality and usability" is far too general).
2 +
3 +It is a good start, but try to be more specific (based on this information, other researchers should be able to replicate the test. E.g., how many participants do you plan to include?
4 +
5 +Good that you think about how the participant can play-act as a PwD. Do not put it in footnotes, but make a concise paragraph of it (it is an important part of your test method).
Date
... ... @@ -1,0 +1,1 @@
1 +2023-03-26 16:49:48.530
XWiki.XWikiComments[5]
Author
... ... @@ -1,0 +1,1 @@
1 +Anonymous
Comment
... ... @@ -1,0 +1,8 @@
1 +interview with the person who interact with the tablet only:
2 +
3 +* The system takes time to learn how to use
4 +* prefer audio instructions
5 +* expect audio feedback after completing each task
6 +* prefer visualization over text
7 +
8 +Suggestion: it's better to weaken the existence of the system and make it easier to learn
Date
... ... @@ -1,0 +1,1 @@
1 +2023-04-01 10:17:27.32
XWiki.XWikiComments[6]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.DemiTao
Comment
... ... @@ -1,0 +1,16 @@
1 +**Interpretation for user evaluation **
2 +
3 +If a respondent had a minimum total score of 60% (15 out of 25 for the matrix question) or more, he or she was considered to be satisfied with the application.
4 +
5 +**Scoring SUS**
6 +
7 +* For odd items: subtract one from the user response.
8 +* For even-numbered items: subtract the user responses from 5
9 +* This scales all values from 0 to 4 (with four being the most positive response).
10 +* Add up the converted responses for each user and multiply that total by 2.5. This converts the range of possible values from 0 to 100 instead of from 0 to 40.
11 +
12 +**Interpreting Scores for SUS [[*>>https://measuringu.com/sus/]]**
13 +
14 +Interpreting scoring can be complex. The participant’s scores for each question are converted to a new number, added together and then multiplied by 2.5 to convert the original scores of 0-40 to 0-100.  Though the scores are 0-100, these are not percentages and should be considered only in terms of their percentile ranking.
15 +
16 +Based on research, a SUS score above a 68 would be considered above average and anything below 68 is below average, however, the best way to interpret your results involves “normalizing” the scores to produce a percentile ranking.
Date
... ... @@ -1,0 +1,1 @@
1 +2023-04-07 17:01:06.25