| ... |
... |
@@ -31,18 +31,18 @@ |
| 31 |
31 |
==== Reminders for activities ==== |
| 32 |
32 |
|
| 33 |
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. |
|
34 |
+Add a reminder that a relative will pay a visit on Sunday with the format as "<relative name> will visit you on Sunday at 3 pm for some tea". Set the reminder to remind you 10 min before that. |
| 35 |
35 |
))) |
| 36 |
36 |
* ((( |
| 37 |
|
-Add a reminder USING A VOICE COMMAND that today at 2 pm will have a general health checkup. |
|
37 |
+Check the remainder for this week and verify the new remainder added for the event. |
| 38 |
38 |
))) |
| 39 |
|
-* ((( |
| 40 |
|
-Check the reminders you have added for today and tomorrow. |
| 41 |
|
-))) |
| 42 |
42 |
|
| 43 |
43 |
==== Personal profile ==== |
| 44 |
44 |
|
| 45 |
45 |
* ((( |
|
43 |
+Browse through relative profiles and read the info. |
|
44 |
+))) |
|
45 |
+* ((( |
| 46 |
46 |
Add relatives as a contact in the "profile" section. |
| 47 |
47 |
))) |
| 48 |
48 |
|
| ... |
... |
@@ -54,7 +54,7 @@ |
| 54 |
54 |
|
| 55 |
55 |
==== Medicine reminders ==== |
| 56 |
56 |
|
| 57 |
|
-(for professional caregivers) |
|
57 |
+(for professional caregivers - not part of the evaluation) |
| 58 |
58 |
|
| 59 |
59 |
* ((( |
| 60 |
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. |
| ... |
... |
@@ -68,9 +68,9 @@ |
| 68 |
68 |
|
| 69 |
69 |
== 2.4 Measures == |
| 70 |
70 |
|
| 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. |
|
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 the software. |
| 72 |
72 |
|
| 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. |
|
73 |
+In addition to the quantitative measures, a structured interview with open-ended questions was conducted with randomly selected participants. 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 |
74 |
|
| 75 |
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 |
76 |
|
| ... |
... |
@@ -93,16 +93,83 @@ |
| 93 |
93 |
|
| 94 |
94 |
= 3. Results = |
| 95 |
95 |
|
| 96 |
|
-|=(% 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) |
| 97 |
|
-|(% style="width:199px" %)Turning the robot on and off|(% style="width:147px" %) |(% style="width:146px" %) |(% style="width:185px" %) |(% style="width:175px" %) |
| 98 |
|
-|(% style="width:199px" %)Add a reminder using "+" button|(% style="width:147px" %) |(% style="width:146px" %) |(% style="width:185px" %) |(% style="width:175px" %) |
| 99 |
|
-|(% style="width:199px" %)Add a reminder using voice|(% style="width:147px" %) |(% style="width:146px" %) |(% style="width:185px" %) |(% style="width:175px" %) |
| 100 |
|
-|(% style="width:199px" %)Check the reminder|(% style="width:147px" %) |(% style="width:146px" %) |(% style="width:185px" %) |(% style="width:175px" %) |
| 101 |
|
-|(% style="width:199px" %)Create a personal profile|(% style="width:147px" %) |(% style="width:146px" %) |(% style="width:185px" %) |(% style="width:175px" %) |
|
96 |
+=== (% style="color:inherit; font-family:inherit" %)Results of the survey:(%%) === |
| 102 |
102 |
|
| 103 |
|
-if possible, note down some Parts Where Users Struggled in each task. |
|
98 |
+[[Figure: //Percentage of user satisfaction and SUS score//>>image:attach:chart.png]] |
| 104 |
104 |
|
|
100 |
+(% class="wikigeneratedid" %) |
|
101 |
+As mentioned earlier, the user evaluation incorporated two quantitative measures. The first measure evaluated the various attributes of the system, including accessibility, trustworthiness, perceivability, understandability, and empowerment. The second measure employed was the System Usability Scale (SUS). |
|
102 |
+ |
|
103 |
+(% class="wikigeneratedid" %) |
|
104 |
+The attributes-related evaluation was analyzed based on the following way: if a respondent had a minimum total score of 60% (15 out of 25) or more, he or she was considered to be satisfied with the application. 11 out of 14 (78.57%) of the users achieved a score of 15 or higher. The average score is 18. According to the standard operating protocol (Quintana et al., 2020), the feasibility test was to be considered successfully completed if at least 75% were satisfied with the use of the application. Therefore, based on this criterion, the feasibility test was considered successfully completed. |
|
105 |
+ |
|
106 |
+The System Usability Scale (SUS) was interpreted in terms of percentile ranking. The average SUS score for the stand-alone application is 54.17 (grade D), and that of the robot is 71.86 (grade B). Based on research, a SUS score above 68 would be considered above average and anything below 68 is below average. As a result, the usability of the robot was from this point of view considered successfully completed. |
|
107 |
+ |
|
108 |
+ |
|
109 |
+|(% style="width:215px" %)**Attributes**|(% style="width:211px" %)**Mean (control group)**|(% style="width:229px" %)**Mean (Experimental group)**|(% style="width:197px" %)**P-value** |
|
110 |
+|(% style="width:215px" %)Accessibility|(% style="width:211px" %)2,33|(% style="width:229px" %)3,25 |(% style="width:197px" %)0,0644 |
|
111 |
+|(% style="width:215px" %)Trustability|(% style="width:211px" %)3,83|(% style="width:229px" %)4,125|(% style="width:197px" %)0,3165 |
|
112 |
+|(% style="width:215px" %)Perceivability|(% style="width:211px" %)3,33|(% style="width:229px" %)3,5|(% style="width:197px" %)0,4112 |
|
113 |
+|(% style="width:215px" %)Understandability|(% style="width:211px" %)3,33|(% style="width:229px" %)4,25|(% style="width:197px" %)0,1151 |
|
114 |
+|(% style="width:215px" %)Empowerment|(% style="width:211px" %)3,33|(% style="width:229px" %)4|(% style="width:197px" %)0,0895 |
|
115 |
+|(% style="width:215px" %)Usability|(% style="width:211px" %)54,16666667|(% style="width:229px" %)71,875|(% style="width:197px" %)0,0903 |
|
116 |
+ |
|
117 |
+(% class="wikigeneratedid" %) |
|
118 |
+//Table: User evaluation score// |
|
119 |
+ |
|
120 |
+=== Observation: (Total percentage sums up to 100) === |
|
121 |
+ |
|
122 |
+|=(% style="width: 199px;" %)Tasks|=(% style="width: 147px;" %)Succeeded by Themselves|=(% style="width: 146px;" %)Succeeded with Some Guidance|=(% style="width: 185px;" %)Succeeded with Detailed Explicit Instructions|=(% style="width: 175px;" %)Average Time to Complete Task (s) |
|
123 |
+|(% style="width:199px" %)Add a reminder|(% style="width:147px" %)14.29%|(% style="width:146px" %)28.57%|(% style="width:185px" %)57.14%|(% style="width:175px" %)97 |
|
124 |
+|(% style="width:199px" %)Check weekly remainders on the Calendar page|(% style="width:147px" %)100%|(% style="width:146px" %)NA|(% style="width:185px" %)NA|(% style="width:175px" %)36 |
|
125 |
+|(% style="width:199px" %)Create a personal profile|(% style="width:147px" %)7.14%|(% style="width:146px" %)50%|(% style="width:185px" %)42.86%|(% style="width:175px" %)69 |
|
126 |
+|(% style="width:199px" %)Verify current profiles|(% style="width:147px" %)85.71%|(% style="width:146px" %)14.29%|(% style="width:185px" %)NA|(% style="width:175px" %)32 |
|
127 |
+|(% style="width:199px" %)Play memory game|(% style="width:147px" %)0%|(% style="width:146px" %)42.86%|(% style="width:185px" %)57.14%|(% style="width:175px" %)208 |
|
128 |
+ |
|
129 |
+//Table: Results of user performance of tasks // |
|
130 |
+ |
|
131 |
+ |
|
132 |
+|(% style="width:330px" %)**Tasks**|(% style="width:523px" %)**Parts where people struggled** |
|
133 |
+|(% style="width:330px" %)Add a reminder|(% style="width:523px" %)((( |
|
134 |
+* Don't know where to start |
|
135 |
+* No immediate audio feedback indicating success |
|
136 |
+))) |
|
137 |
+|(% style="width:330px" %)Create a personal profile|(% style="width:523px" %)((( |
|
138 |
+* It's hard to type with taped fingers |
|
139 |
+))) |
|
140 |
+|(% style="width:330px" %)Play memory game|(% style="width:523px" %)((( |
|
141 |
+* Have no idea how to play the game, sometimes even after listening to the explicit instructions |
|
142 |
+* There are too many words in the text |
|
143 |
+* The beta version has no right or wrong prompts, different from the instructions, making people confused |
|
144 |
+))) |
|
145 |
+ |
|
146 |
+//Table: Difficulties that users struggled with when solving tasks// |
|
147 |
+ |
| 105 |
105 |
= 4. Discussion = |
| 106 |
106 |
|
|
150 |
+(% class="wikigeneratedid" %) |
|
151 |
+In light of our research question, we found no notable disparities between the stand-alone application and the robot. The results may be influenced by the experimental setup. While we aimed to emulate a real-world scenario for participants to perform the tasks, their pre-existing digital device proficiency could have played a role. The participants may have had prior experience with using similar applications or robots, which could have affected their performance and perception of the two groups. Nevertheless, given that people with dementia likely have limited knowledge of utilizing mobile devices, we maintain a positive outlook on the potential efficacy of the visual-audio aid provided by the robot to enhance the experience of PwDs utilizing the application. |
| 107 |
107 |
|
|
153 |
+==== Limitations: ==== |
|
154 |
+ |
|
155 |
+* We could not adapt the robot to the PwD due to time constraints. This means that we did not take into account the severity of the PwD's visual, acoustic and kinesthetic limitations while setting up Pepper. |
|
156 |
+* We could not test the full capabilities of the robot due to privacy constraints. Since we fabricated the information about relatives to protect the privacy of participants, we were not able to perform the scenarios in a realistic manner. |
|
157 |
+* Since the version of the Google Chrome browser on the Pepper tablet was outdated, we were not able to load our Flutter application onto it and simulate actual scenarios. |
|
158 |
+* Participants were from a wide variety of different backgrounds and mother tongues, it was therefore not possible to adjust Pepper to the specific culture of the participant. |
|
159 |
+ |
|
160 |
+==== Future Improvements: ==== |
|
161 |
+ |
|
162 |
+* We can make our system more realistic/adapted to PwD by incorporating human-like responses, gestures and movements to Pepper. |
|
163 |
+* We can make our system fully gesture/voice controlled to enable the PwD to (% style="color:#000000; font-family:Arial; font-size:11pt; font-style:normal; font-variant:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)use the system without assistance from a caregiver, increasing their autonomy. |
|
164 |
+* (% style="color:#000000; font-family:Arial; font-size:11pt; font-style:normal; font-variant:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)We can incorporate privacy protocols like voice authentication and gaze detection to ensure that all personal information about the PwD, relatives and caregivers are kept safe and confidential. |
|
165 |
+ |
| 108 |
108 |
= 5. Conclusions = |
|
167 |
+ |
|
168 |
+After performing the experiment and running various statistical tests on the results obtained, we have made the following conclusions that hopefully answer some of our research questions: |
|
169 |
+ |
|
170 |
+1. We believe that an information support application **DOES IMPROVE** a PwD's well-being, since it can (% style="color:#000000; font-family:Arial; font-size:11pt; font-style:normal; font-variant:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)provide them with access to important information and support, improving their overall quality of life. |
|
171 |
+1. We believe that a robot assistant **DOES IMPROVE** the experience of a PwD using it. The robot(% style="color:#000000; font-family:Arial; font-size:11pt; font-style:normal; font-variant:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %) can provide companionship and assistance, making them feel independent and less isolated. |
|
172 |
+ |
|
173 |
+(% style="color:#000000; font-family:Arial; font-size:11pt; font-style:normal; font-variant:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)While our experiment had its limitations, we believe that it provides a foundation for future research in developing personalized memory robots for people with dementia. We also believe that our research is applicable to mobile agents which increases the accessibility of the solution. |
|
174 |
+ |
|
175 |
+ |
