Changes for page Manali - Self Reflection

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -16,6 +16,29 @@
16	16
17	17	**Week 2**
18	18
19		-Since our project pertained to a human centric approach of a robot for patients with dementia, it was quite fitting to have a guest lecture which made us aware of the medical aspects of dementia: as engineers, this is a side which we might not know.
	19	+Since our project pertained to a human centric approach of a robot for patients with dementia, it was quite fitting to have a guest lecture which made us aware of the medical aspects of dementia: as engineers, this is a side which we might not know. We learned about the changes in the brain while ageing, and the possible decline in memory and cognitive function. We learn about the different types of dementia, and the ways of diagnosing it. We gain an understanding of the current interventions and treatments: these could possibly be included in the robot as well for higher effectivity. Music too plays a major role by activating parts of the brain which affect emotion, attention and physiological aspects.
20	20
21		-
	21	+Even without the perspective of this course, it was quite enlightening to see how lifestyle changes can improve the quality of life in the long run: something which most of us ignore.
	22	+
	23	+All in all, it was a very informative session from the perspective of understanding the target audience and their needs better, and the biological outlook. This will particularly help in designing the solution better, instead of shooting shots in the dark of what we, as engineers, think will help.
	24	+
	25	+In the project, we finalized the personas, stakeholders and the problem and design scenario. We designed the problem scenario to be in the evening, where the patient suffers from Sundown Syndrome, and hence faces mood swings when the sun goes down, and loses motivation to eat due to this. The design scenario is centered around getting the patient to complete meals while enjoying them, also facilitating conversations between family members: this is done while the robot narrates stories, providing prompts for interaction.
	26	+
	27	+This incorporates the "SCE Method" which considers the involvement of stakeholders, and a multidisciplinary (biological, engineering, musical) and iterative design process to perfectly refine the core functions and design rationale.
	28	+
	29	+
	30	+**Week 3**
	31	+
	32	+In this week, we dive deeper into PAL, the robot which assists children with diabetes, and see how this was approached. It gave an insight into how we must define our use cases, environments, stakeholders, values and personas. They use the zone of proximal development to facilitate collaborative learning in children. It is very clearly shown how the demands, human factors and technology are all in sync with each other, as should be in any project. The project is viewed as a partnership between humans and robots, where they both work together to achieve objectives and goals.
	33	+
	34	+We finalized our personas, stakeholders, environment, design and problem scenario for the project in this week, for the presentation in Week 4. We also looked for supporting literature and research which we used in our design scenarios. We decided to use the Pepper robot too.
	35	+
	36	+
	37	+**Week 4**
	38	+
	39	+I gave the first presentation for my team, and described the premise of the project we were working on: the personas, stakeholders, environment and problem scenario. It was intriguing to see what the other groups had been working on, and I did notice that ours was the only group which targeted patients at home, with family, and not in a care home. This gave us a whole new scenario we could work with, and more freedom to involve family members. The downside of this, as we realized, was that it will be costlier to deploy the robot for a single patient, compared to that in a care home.
	40	+
	41	+We were taught the design of use cases, along with the team design pattern, which I feel is the heart of the project. It gives a detailed overview of the whole project and provides a visualization of how the team envisions the project to work. We give a reasoning behind why each feature was chosen, what features were debated and not chosen, and the reasoning behind it.
	42	+
	43	+
	44	+**Week 5**