Skip to Content

Changes for page Timetable

Last modified by Jeffrey Lim on 2022/04/05 12:53
From version Icon 30.1 Icon
edited by Rohan Sobha
on 2022/03/21 17:09
Change comment: There is no comment for this version
To version Icon 39.1 Icon
edited by Laura Ottevanger
on 2022/03/31 09:59
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.rsobha
1 +XWiki.LauraOttevanger
Content
... ... @@ -106,7 +106,7 @@
106 106  - Jeffrey | Expand product vision with Snoezelen and check incorporation in objectives
107 107  
108 108  Use cases:
109 -- Laura | Review use cases
109 +--- Laura | Review use cases--
110 110  
111 111  Functions:
112 112  - Tim | Update flowchart to remove snoezelen to be coherent with current idea of MiRo
... ... @@ -117,7 +117,7 @@
117 117  - --Rohan | Check if we can validate claims with evaluation--
118 118  
119 119  Future work:
120 -- Laura | Add future work page indicating our future work, and also that we would have liked to incorporate snoezelen
120 +--- Laura | Add future work page indicating our future work, and also that we would have liked to incorporate snoezelen--
121 121  
122 122  === Foundation ===
123 123  ====Operational demands ====
... ... @@ -134,19 +134,19 @@
134 134  --- Ricardo | Create for each scenario a 'before' and 'after technology' piece--
135 135  
136 136  Problem scenario:
137 -- Doreen | Add sources for self-determination theory claims
138 -- Doreen | Look into "Design scenario's" (lecture 3 probably): a story that conveys a new vision, including activity: narratives of typical or critical services, information: details on info provision, interaction: details of user interaction & feedback
137 +--- Doreen | Add sources for self-determination theory claims--
138 +--- Doreen | Look into "Design scenario's" (lecture 3 probably): a story that conveys a new vision, including activity: narratives of typical or critical services, information: details on info provision, interaction: details of user interaction & feedback--
139 139  
140 140  ====Human Factors====
141 141  Robotic partner:
142 -- Laura | Elaborate on limitations of MiRo w.r.t. snoezelen
142 +--- Laura | Elaborate on limitations of MiRo w.r.t. snoezelen--
143 143  --- Unassigned | Describe what MiRo could mean as a robotic partner for elderly people / PwD. Perhaps this is not that relevant anymore to write here since snoezelen will be moved to future work.--
144 144  - Laura + Harmen| Add research on interactions between elderly people and/or PwD's and robots + any other relevant research on effect of pets/robots on PwD's.
145 145  
146 146  Design patterns:
147 -- Tim | Make team design pattern into something that is not drawn
148 -- Tim | Make team design pattern including the caretaker
149 -- Tim | Create diagrams for IDP's
147 +- Ricardo | Make team design pattern into something that is not drawn
148 +- Ricardo | Make team design pattern including the caretaker
149 +- Ricardo | Create diagrams for IDP's
150 150  
151 151  Ontology:
152 152  - Harmen | Add ontology image to XWiki
... ... @@ -162,7 +162,7 @@
162 162  - Unassigned | Add all sources here at the end of the project?
163 163  
164 164  Inclusive design:
165 -- Doreen | Write this page
165 +--- Doreen | Write this page--
166 166  
167 167  Human-Agent teamwork:
168 168  We do not yet know what should be here.
... ... @@ -179,4 +179,99 @@
179 179  Unassigned | Consistent use of MiRo (Change every mention of Miro to MiRo)
180 180  Unassigned | Talk about the name WAF (Walking Assisting Friend)
181 181  Unassigned | The group's core foundation
182 +--Doreen | Write in Evaluation -> Test about the little interview I had with Erik and how the product was perceived by a hard of hearing person.
183 +--
182 182  
185 +
186 +
187 +
188 +=Todo list 2.0=
189 +If you are assigned to a page, please also read the existing text and check for grammatical mistakes. If you are assigned a page, please put an introduction to that page for example: "In this chapter, we will introduce you to our Personas. Personas are <explanation of personas>. Personas are relevant because <enter text here>.". Please explain, what it is and why we use it if relevant.
190 +
191 +== Introduction ==
192 +Laura | Introduction - Rewrite: problem, solution, what is where.
193 +Laura | Move MiRo difficulties to Technology
194 +
195 +== Foundation ==
196 +==== Operational Demands ====
197 +
198 +=== Environments and Personas ===
199 +Ricardo | Write 2 sentences as intro on basic Operational Demands page.
200 +Ricardo | Read and check if correct
201 +
202 +=== Stakeholders and Problem Scenario ===
203 +Harmen | Write 2 sentences as intro on basic Operational Demands page.
204 +Harmen | Read and check if correct
205 +
206 +
207 +==== Human Factors ====
208 +
209 +==== Robotic Partner ====
210 +Unassigned | Read through and add one citation in the todo
211 +
212 +==== Music and Cognition ====
213 +Tim and Jeffrey (whoever gets to it first) | Explanation how doglike sounds could be beneficial based in literature.
214 += Design Pattern and Ontology =
215 +Harmen and Ricardo | Cite some references
216 +
217 +==== Measuring Instruments ====
218 +Rohan and Doreen? | cite papers about what we use for evaluation
219 +
220 +==== Group's core theoretical foundation ====
221 +Unassigned and Unassigned | Talk about people with dementia getting lost, if walking helps by PwD, how good walking is for people, budget care homes
222 +
223 +==== Inclusive Design ====
224 +Doreen (Unassigned) | Clean up sources or notify what needs to be done on the page
225 +
226 +==== Human-agent Teamwork ====
227 +Laura and Unassigned | Talk about humans and robots working together based in literature
228 +
229 +=== Technology ===
230 +==== Humanoid Robot ====
231 +Laura | Specify specific limitations and technical options for MiRo
232 +
233 +==== Music Management ====
234 +Tim and Jeffrey (whoever gets to it first) | Explanation why we do not use music + what we do use + talk about video of alarm here
235 +
236 +== Specification ==
237 +=== Objectives ===
238 +Unassigned | Remove Snoezelen and expand Objectives
239 +
240 +=== Use cases ===
241 +Unassigned | Read through and check for (grammatical) mistakes
242 +
243 +=== Functions ===
244 +Unassigned | Add reference to future work page.
245 +
246 +=== Claims ===
247 +Harmen | Expand Claims
248 +
249 +== Evaluation ==
250 +=== Prototype ===
251 +Laura | Add code to Github,
252 +Laura | Talk about code in Prototype chapter
253 +
254 +=== Test ===
255 +Unassigned | Rewrite to make a bit more specific, ensure that the test is reproduceable, add Wilcoxon test
256 +Unassigned | Add Discussion after the results and ensure that results is just numbers
257 +
258 +== Design Patterns ==
259 +Ricardo | Reread and change picture
260 +Ricardo | Add caretaker in team design pattern
261 +Ricardo | Picture for IDP
262 +
263 +== Ontology ==
264 +Harmen | Add second Ontology
265 +
266 +== Planning ==
267 +Unassigned | Rewrite todo-list as a per week description of what happened
268 +(Optional) Unassigned | Put everything into a nice table like: [Timetable table >> https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group02/view/Timetable/TimeTable%20Table%20Format/]
269 +
270 +== Conclusion ==
271 +=== Future Work ===
272 +Unassigned and Laura | Add limitations and how we would solve it in future work.
273 +Unassigned | Talk about having only 8 participants, not a correct room (not a carehome hallway but single room), using PwD as test subjects = more realistic test.
274 +Unassigned | Suggestions for other tests from presentation = test way of attention grabbing
275 +=== Conclusion ===
276 +Unassigned | Write a nice end chapter/conclusion on how it went and summarizing results.
277 +