Changes for page Timetable
Last modified by Jeffrey Lim on 2022/04/05 12:53
From version 
44.1 
44.1
edited by Rohan Sobha
on 2022/04/01 15:33
on 2022/04/01 15:33
Change comment:
There is no comment for this version
To version 35.1
35.1
edited by Ricardo Vogel
on 2022/03/22 17:31
on 2022/03/22 17:31
Change comment:
There is no comment for this version
Summary
Details
-
Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.r sobha1 +XWiki.ricardovogel - Content
-
... ... @@ -129,7 +129,7 @@ 129 129 - Tim | Incorporate Schwartz value model in the value stories 130 130 131 131 Personas: 132 -- --Ricardo | Lecture slides state "Persona's need to have goals". Cornelia and Constantijn have these (to some extent), but Marcus does not yet--132 +- Ricardo | Lecture slides state "Persona's need to have goals". Cornelia and Constantijn have these (to some extent), but Marcus does not yet 133 133 --- Ricardo | Create technology disliking persona scenario-- 134 134 --- Ricardo | Create for each scenario a 'before' and 'after technology' piece-- 135 135 ... ... @@ -176,104 +176,8 @@ 176 176 177 177 ==== Report ==== 178 178 Unassigned | Proofread 179 - Doreen | Consistent use of MiRo (Change every mention of Miro to MiRo)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 +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. 184 184 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 for these two pages 204 -Harmen | Read and check if correct 205 - 206 - 207 -==== Human Factors ==== 208 - 209 -==== Robotic Partner ==== 210 -Tim | Read through and add one citation in the todo 211 - 212 -==== Music and Cognition ==== 213 -Jeffrey | Explanation how doglike sounds and movements could be beneficial based in literature and motivate why music is inappropriate for our use case. 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 -Jeffrey | 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 | Clean up sources or notify what needs to be done on the page 225 - 226 -==== Human-agent Teamwork ==== 227 -Rohan | 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 -Jeffrey | Explanation why we do not use music + what we do use + talk about video of alarm here 235 - 236 -== Specification == 237 -=== Objectives === 238 -Tim | Remove Snoezelen and expand Objectives 239 -Tim | Move everything Snoezelen related to future work and make a coherent story 240 - 241 -=== Use cases === 242 -Rohan | Read through and check for (grammatical) mistakes 243 - 244 -=== Functions === 245 -Tim | Add reference to future work page. 246 - 247 -=== Claims === 248 -Harmen | Expand Claims 249 - 250 -== Evaluation == 251 -=== Prototype === 252 -Laura | Add code to Github, 253 -Laura | Talk about code in Prototype chapter 254 - 255 -=== Test === 256 -Rohan | Rewrite to make a bit more specific, ensure that the test is reproduceable, add Wilcoxon test 257 -Doreen | Add Discussion after the results and ensure that results is just numbers 258 - 259 -== Design Patterns == 260 -Ricardo | Reread and change picture 261 -Ricardo | Add caretaker in team design pattern 262 -Ricardo | Picture for IDP 263 - 264 -== Ontology == 265 -Harmen | Add second Ontology 266 - 267 -== Planning == 268 -Unassigned | Rewrite todo-list as a per week description of what happened 269 -(Optional) Unassigned | Put everything into a nice table like: [[Timetable table >> https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group02/view/Timetable/TimeTable%20Table%20Format/]] 270 - 271 -== Conclusion == 272 -=== Future Work === 273 -Jeffrey and Laura | Add limitations and how we would solve it in future work. 274 -Doreen | 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. 275 -Tim | Suggestions for other tests from presentation = test way of attention grabbing 276 -Rohan | Snoezelen in context of evaluation 277 -=== Conclusion === 278 -Tim and (Rohan) | Write a nice end chapter/conclusion on how it went and summarizing results. 279 -