Wiki source code of Tim - Self Reflection
Last modified by Tim Reddering on 2023/04/11 20:45
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | At the start of my Self Reflection I want to mention that I joined the team late in week 3. I want to thank the team that they took me and helped me get up to speed fast. | ||
2 | |||
3 | |||
4 | ==== Week 1: Introduction to Socio-Cognitive Engineering ==== | ||
5 | |||
6 | In this week I learned about the project by going through the lectures slides, the papers and discovered the Brightspace page. | ||
7 | |||
8 | The lecture started with an introduction to the course with an introduction to the team and an explanation on how the course was set up. After that Human Centered Design was explained together with the standards. Than, the ReJam and PAL project were presented. The ReJam project was a project for people with Dementia in Pieter van Foorest where music was used to stimulate group activities. | ||
9 | |||
10 | The Lab Session slides together with the XWiki learned me what I should think about for the Quick Start menu and which Robots are available. | ||
11 | |||
12 | |||
13 | ==== Week 2: Dementia, Memory and Music as an Intervention ==== | ||
14 | |||
15 | From the lecture slides I learned that age is an important factor for changes in cognitive abilities. Also, your lifestyle can have a huge effect. This can be explained by the term 'cognitive reserve'. This essentially means that with good life choices (much exercise for mind and body, healthy food etc.), the brain is more resistant to illness. When a person does get ill, for example with dementia, music can help with regulating mood and emotions. | ||
16 | |||
17 | The second lecture talks about the Socio-Cognitive Engineering Method. The inclusive design also gets explained by what it should address. After that, the stakeholder gets explained which can be direct but also indirect. Lastly, scenarios were discussed. Why they are important and how they should be constructed. | ||
18 | |||
19 | |||
20 | ==== Week 3: PAL ==== | ||
21 | |||
22 | This week I joined the team and they brought me up to speed. I was introduced to the subject and how it would improve lives of people with dementia. | ||
23 | |||
24 | In this week's lecture, I learned about how the PAL project used the SCE design cycle to build a diabetes management robot for children with Type 1 diabetes. The lecture emphasized the significance of stakeholder analysis and building value stories to inform our design, which we applied in finalizing our personas, stakeholders, environment, design, and problem scenario for the project presentation in Week 4. | ||
25 | |||
26 | |||
27 | ==== Week 4: First Presentation ==== | ||
28 | |||
29 | This week we had the first presentation which are teammates gave. We worked together on the slides and did a test-presentation after which I gave feedback. In this first presentation we talked about our problem scenario, personas, stakeholders and presented our solution. I think the presentation went well and our story was clear. | ||
30 | |||
31 | |||
32 | ==== Week 5: Design Specifications ==== | ||
33 | |||
34 | In the lecture I learned about emotional expression with eye colour but also body language with the robot. After that I learned about the evaluation and different methods of evaluation. We learned about ethical issues and that we needed to have consent of the participant. Lastly, we talked about ontologies. | ||
35 | |||
36 | In our group we discussed what kind of evaluation we wanted to do. We agreed we wanted to do interactive storytelling vs non-interactive storytelling. The evaluation would be a summative assessment with a questionnaire. And, of course, we are going to ask consent. | ||
37 | |||
38 | |||
39 | ==== Week 6: Implementation and Initial Testings ==== | ||
40 | |||
41 | This week we worked on the robot First, we tried to understand the software used for controlling the robot. Second, we tried to use the robot and looked how the robot react to different inputs. Once we understood the software and the robot, we got to work. We programmed two stories for the robot: one about thanksgiving and one about a picnic. We tested the stories and found that some things did not really work. For example, the audio input did not always work. We decided that if talking to the robot did not work, we should be able to make the choice on our tablet/computer. This way we cycled through the design and came to a good working design. | ||
42 | |||
43 | |||
44 | ==== Week 7: Evaluation ==== | ||
45 | |||
46 | This week we did the evaluation. We did our own evaluation together with two other groups so we could help each other. Our evaluation went according plan. | ||
47 | |||
48 | After the evaluation we analyzed the results. We did a statical analysis on the results to look which questions are significant. | ||
49 | |||
50 | |||
51 | ==== Week 8: Final Presentation ==== | ||
52 | |||
53 | At the start of this week, on Monday, we had our final presentation. We worked on the slides and discussed what was important to include and also what could be left out. A test-presentation in our own group was done to make sure everything we told was clear. | ||
54 | |||
55 | In our presentation we first had a quick recap of our problem scenario, than an explanation of our design and theories to support it. After that, I showed a video of our experiment and presented our evaluation and results. We received feedback on our statistical analysis and choice of questionnaire. | ||
56 | |||
57 | |||
58 | ==== Week 9: The Finishing Touch ==== | ||
59 | |||
60 | This week was the deadline for our XWiki on Tuesday. Of course, most work was done, but we went through everything and improved parts that were unclear. Finally, we handed in the XWiki and the project came to an end. I want to thank my team for all the hard work and I am very happy with the final result! Also, I want to thank Mark and the whole Socio-Engineering team for teaching us this course. | ||
61 | |||
62 |