Changes for page Timetable

Last modified by Jeffrey Lim on 2022/04/05 12:53

From 56.1 to 55.1 From 58.1 to 57.1

From version

57.1

edited by Laura Ottevanger
on 2022/04/05 11:51

Change comment: There is no comment for this version

To version

56.1

edited by Tim Huisman
on 2022/04/04 20:40

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.LauraOttevanger
++XWiki.Tim_Huisman2

Content

@@ -1,309 +1,279 @@
--= Week 1 =
++Week 1:
++In the meeting (8-2) tasks were divided. Deadline is before the meeting next week.
++Ricardo: Work on the report: Personas and problem scenario
++Rohan: Work on the report: Operational demands: environments and stakeholders
++Doreen: See if Bluetooth connection with Miro would be possible (and if we can check distance)
++Jeffrey: Look at the basic behavior of the Miro robot (and maybe try it a bit)
++Harmen: Look into the sounds help
++Tim: Check if the Miro robot can listen to a name/respond to a name
++Laura: Check and possibly code a path tracking possibility in Miro
--|Member|Task|Reflection|\\
--|Tim Huisman|Check if the MiRo robot can listen to a name/respond to a name|The accounts weren't there yet so Harmen, Jeffrey, Tim, and Laura did some research on the necessary packages and code.|\\
--|Harmen Kroon| Look into the sounds help|The accounts weren't there yet so Harmen, Jeffrey, Tim, and Laura did some research on the necessary packages and code.|\\
--|Jeffrey Lim|Look at the basic behavior of the MiRo robot (and maybe try it a bit)|The accounts weren't there yet so Harmen, Jeffrey, Tim, and Laura did some research on the necessary packages and code.|\\
--|Doreen Mulder|See if Bluetooth connection with MiRo would be possible (and if we can check distance)|Doreen made connections between her phone and an Arduino and was able to let the Arduino detect when the distance was too great.|\\
--|Laura Ottevanger|Check and possibly code a path tracking possibility in MiRo|The accounts weren't there yet so Harmen, Jeffrey, Tim, and Laura did some research on the necessary packages and code.|\\
--|Rohan Sobha|Work on the report: Operational demands: environments and stakeholders|Rohan made the Environments and Stakeholders.|\\
--|Ricardo Vogel| Work on the report: Personas and problem scenario|Ricardo made personas.|\\
--|All|In the meeting (8-2) tasks were divided. The deadline is before the meeting next week.| |
++Reflection on Week 1:
++Ricardo made personas. Rohan made the Environments and Stakeholders.
++Doreen made connections between her phone and an Arduino and was able to let the Arduino detect when the distance was too great.
++The accounts weren't there yet so Harmen, Jeffrey, Tim and Laura did some research on the necessary packages and code.
--= Week 2 =
++Week 2:
++Ricardo: Personas & persona scenarios
++Rohan: Robotic Partner / Music recognition
++Harmen: Problem scenarios
++Doreen: State diagram / Leash
++Tim: Commandos/voice recognition, help with personas & scenarios
++Jeffrey: Look into basic behaviour, what does the dog do when touched/petted etc.
++Laura: Look into pathmaking
--|Member|Task|Reflection|\\
--|Tim Huisman|Commandos/voice recognition, help with personas & scenarios|Tim did research on voice recognition and which Python packages are necessary to implement that.
--|\\
--|Harmen Kroon| Harmen: Problem scenarios|Harmen made the problem scenario.|\\
--|Jeffrey Lim| Look into basic behavior, what does the dog do when touched/petted, etc.|Jeffrey tested out with the blockly environment and the Python conversion.|\\
--|Doreen Mulder|State diagram / Leash|Doreen made a flowchart about the behavior of the robot.|\\
--|Laura Ottevanger|Look into pathmaking |Laura made the first storyboard.|\\
--|Rohan Sobha|Robotic Partner / Music recognition|Rohan made the part on Robotic Partner and Music recognition|\\
--|Ricardo Vogel|Personas & persona scenarios|Ricardo extended the personas and made persona scenario.|
--|All|In the meeting (15-2) tasks were divided. The deadline is before the meeting next week. |Wednesday morning we went to the robot lab and were able to upload a basic program to the robot. |
++Reflection on Week 2:
++Ricardo extended the personas and made persona scenario.
++Rohan made the part on Robotic Partner and Music recognition
++Harmen made the problem scenario.
++Doreen made a flowchart about the behavior of the robot.
++Laura made the first storyboard.
++Jeffrey tested out with the blockly environment and the Python conversion.
++Tim did research on voice recognition and which Python packages are necessary to implement that
++Wednesday morning we went to the robot lab and were able to upload a basic program to the robot.
--= Week 3 =
++Week 3:
++Ricardo: Design Patterns
++Rohan: Claims
++Harmen: Ontology
++Doreen: Extending problem scenario, installing MDK.
++Tim: Objectives, Humanoid Robot, name recognition (Is it possible without the mdk)
++Jeffrey: Use cases, figure out object/wall detection
++Laura: Storyboards, test program
--|Member|Task|Reflection|\\
--|Tim Huisman|Work on Objectives, and Humanoid Robot, and check if name recognition is possible without the mdk|Made the Objectives and worked on humanoid Robot. Tim also found some Python libraries for name recognition. Tim also made user value stories for stakeholders |\\
--|Harmen Kroon|Make Ontology|Figured out the program to create an ontology but did not create the ontology yet|\\
--|Jeffrey Lim|Work on use cases, figure out object/wall detection|Did not work on use cases yet but did take a look at the color detection of the MiRo|\\
--|Doreen Mulder|Extending the problem scenario section, and attempt at installing the MDK.|Installed the MDK and made an explanation on how to install it. Doreen did not extend the problem scenario yet.|\\
--|Laura Ottevanger|Make the rest of the storyboards and make the test program|Made the storyboards and some test programs to test on the robot. |\\
--|Rohan Sobha|Make Claims|Made the claims|\\
--|Ricardo Vogel|Make Design Patterns|Made the Design Patterns with a drawing of the system.|\\
--|All|In the meeting (22-2) tasks were divided. |We used Wednesday morning as our lab hours to work on the physical prototype with the MiRo. The MiRo had quite some difficulties in connecting with PCs|
++Reflection on week 3:
++Ricardo made the Design Patterns with a drawing of the system.
++Rohan made the claims
++Harmen: Figured out the program to create an ontology but did not create the ontology yet.
++Doreen installed the MDK and made an explanation on how to install it. Doreen did not extend the problem scenario yet.
++Tim made the Objectives and worked on humanoid Robot. Tim also found some Python libraries for name recognition. Tim also made user value stories at stake holders.
++Jeffrey took a look into use cases but did not make them yet.
++Laura made the storyboards and some test programs to test the robots.
--= Week 4 =
++Week 4:
--|Member|Task|Reflection|\\
--|Tim Huisman|Extend functions and specify design patterns|Worked on design patterns and the human factors design patterns. Extended/rewrote functions and found parts to discuss for during the lab.|\\
--|Harmen Kroon|Make the Ontology and write the human factors ontology page|Made ontology. Started on human factors ontology, made some code for demo|\\
--|Jeffrey Lim|Use Cases and work on mid-term presentation |Made use cases and presented presentation|\\
--|Doreen Mulder|Extend the problem scenario and work on the wristband for the prototype. Also, make a "hondenriem" prototype (out of cardboard)|Extended problem scenario, and started working on a physical prototype|\\
--|Laura Ottevanger|Work on Evaluation and work on mid-term presentation |Made and presented the presentation, made a start on evaluation and made some code for the demo.|\\
--|Rohan Sobha|Work on Evaluation and work on mid-term presentation |Made a start on evaluation, made the presentation, and presented the presentation.|\\
--|Ricardo Vogel|Specify design patterns and work on the human factors design patterns page|Worked on design patterns and the human factors design patterns|\\
--|All|In the meeting (1-3) tasks were divided. |In addition to the common Wednesday morning in the Insyght lab, Rohan, Jeffrey, and Laura spend Wednesday afternoon working on the presentation. In the lab we made some small videos for the mid-term presentation:
++Ricardo: Specify design patterns + human factors design patterns.
++Rohan: Evaluation + Presentation 1
++Harmen: Ontology + human factors ontology
++Doreen: Extend problem scenario + work on wristband for prototype + Prototype + make a "hondenriem" prototype out of cardboard
++Tim: Extend functions + specify design patterns
++Jeffrey: Use Cases + presentation 1
++Laura: Evaluation + Presentation 1
--* Snoezelen = for which we will use the demo version of MiRo,
--* The Wristband = Doreen creates it with an Arduino
--* Walking = We will Wizard of Oz it with a remote control
--* When a PwD walks in the wrong direction = Harmen will create some code for it
--* Ask for attention = Harmen and Laura look into mimicking a barking dog
--* Positive response = Laura will create some code where MiRo is barking, wagging its tail, etc. |
++We are going to create small videos:
++Snoezelen = demoversion of Miro
++Wristband = Doreen creates is with Arduino
++Walking = Wizard of Oz with remote control
--= Week 5 =
++When person with dementia walks in the wrong direction: follow the person, make a sound/bark, turn head as if confused, turn back in correct direction, walk some steps, check if the dog is followed = Harmen
++Ask for attention:  (bark as real dog) = Doreen
++Positive response: wagging, turn ears, yap = Laura
-- Mid-term presentation
++Reflection on week 4:
++Ricardo: Worked on design patterns and the human factors design patterns
++Tim: Worked on design patterns and the human factors design patterns. Extended/rewrote functions and found parts to discuss about it.
++Rohan: Made a start on evaluation, made the presentation and presented the presentation.
++Harmen: Made ontology. Started on human factors ontology, made some code for demo
++Doreen: Extended problem scenario, started working on a physical prototype
++Jeffrey: Made use cases, presented presentation
++Laura: Made and presented the presentation, made a start on evaluation, made some code for demo.
--|Member|Task|Reflection|\\
--|Tim Huisman|Design pattern diagrams, reread all XWiki pages to check for consistency and todos. Also, refactor some pages|Reread all XWiki pages to check for consistency and made a full to-do list for the rest of the project. Also gave feedback on the evaluation form|\\
--|Harmen Kroon|Make an extra ontology schema, make human factors ontology, and do some research on existing robot dogs|Due to Harmen being sick, he worked a little bit on some research for existing robot dogs but couldn't finish ontology.|\\
--|Jeffrey Lim|Make some MiRo code for an alarm when a PwD falls and for snoezelen with different levels of movement.|Made and tested the four pieces of code Wednesday. |\\
--|Doreen Mulder|Elaborate on evaluation and collaborate with Rohan on experimental setup|Elaborated evaluation and worked on experimental setup|\\
--|Laura Ottevanger|Also do some research on existing robot dogs and make 4 pieces of code for the prototypes: snoezelen low movement, medium movement, a lot of movement, and the alarm mode|Started with some research on existing robot dogs and made the four prototypes mentioned|\\
--|Rohan Sobha| Elaborate on evaluation and collaborate with Doreen on experimental setup|Elaborated evaluation and worked on experimental setup|\\
--|Ricardo Vogel|Going to work on ethics and test if we can connect MiRo to a server and/or with packets|Worked on ethics|\\
--|All|In the meeting (9-3) tasks were divided. This was in the Insyght lab as during the lecture hours there were presentations|We decided to combine the pieces of code for alarm from Jeffrey and Laura to create an alarm mode. The snoezelen we decided to scrap as we noticed that it would be difficult to test snoezelen with the MiRo, the MiRo is too easy to break|
++Week 5:
++Ricardo: Going to work on ethics + test if we can connect miro to a server and/or with packets
++Tim: Design pattern diagrams + reread all XWiki pages to check for consistency and todo's + refactor some pages
++Doreen: Elaborate on evaluation + collaborate with Rohan on experimental setup
++Rohan: Elaborate on evaluation + collaborate with Doreen on experimental setup
++Harmen: Extra ontology schema + human factors ontology + research on existing robot dogs
++Laura: Also do some research on existing robot dogs + make 4 prototypes/code: snoezelen 1,2,3 + alarm mode
++Jeffrey: Make some MiRo code for an alarm when a PwD falls and for snoezelen with different levels of movement.
--= Week 6 and 7 =
++Reflection on Week 5:
++Ricardo: Worked on ethics.
++Tim: reread all XWiki pages to check for consistency and made a full to-do list for the rest of the project. Also gave feedback on the evaluation form.
++Doreen: Elaborated evaluation + worked on experimental setup
++Rohan: Elaborated evaluation + worked on experimental setup + created and worked on the questionnaire
++Harmen: Due to Harmen being sick, he worked a little bit on some research for existing robot dogs but couldn't finish ontology
++Laura: Started on some research on existing robot dogs + made 4 prototypes/code: snoezelen 1,2,3 + alarm mode
++Jeffrey: Made and tested the four pieces of code Wednesday.
--|Member|Task|Reflection|\\
--|Tim Huisman|\\
++We decided to combine the pieces of code for alarm from Jeffrey and Laura to create an alarm mode. The snoezelen we decided to scrap as we noticed that it would be difficult to test snoezelen with the Miro, the miro is too easy to break
--* Update flowchart to remove snoezelen to be coherent with the current idea of MiRo
--* Add a textual description of walking with MiRo to incorporate what MiRo should do if PwD stops to talk during the walk
--*  Create value stories for indirect stakeholders
--* Incorporate Schwartz's value model in the value stories
--* Describe every single signal, sound, a movement that the PwD will receive/MiRo will make, the reasoning behind it, and its desired effect
--* Link to Technology - Music Management for the explanation of why we do not use music.
++== Todos ==
++Format: Assignee | Todo
++=== Specification ===
++Objectives:
++- Jeffrey | Expand product vision with Snoezelen and check incorporation in objectives
--|\\
++Use cases:
++--- Laura | Review use cases--
--* Updated flowchart
--* Added the textual description
--* -
--* -
--* Describing the sounds has been completed in the final week.
--* Link to technology has been completed in the final week.
++Functions:
++- Tim | Update flowchart to remove snoezelen to be coherent with current idea of MiRo
++- Tim | --Add textual description of walking with MiRo to incorporate what MiRo should do if PwD stops to talk during walk--
++Claims:
++- --Rohan | Review current claims and perhaps add upon sections with small amounts of text/description--
++- --Rohan | Add sources on why autonomy is important (basically just link to Self Determination Theory)--
++- --Rohan | Check if we can validate claims with evaluation--
--|\\
--|Harmen Kroon|\\
++Future work:
++--- Laura | Add future work page indicating our future work, and also that we would have liked to incorporate snoezelen--
--* Add research on interactions between elderly people and/or PwD's and robots + any other relevant research on the effect of pets/robots on PwD's.
--* Add ontology image to XWiki
++=== Foundation ===
++====Operational demands ====
++Environments:
++- Jeffrey | Expand and clarify technologies
--|\\
++Stakeholders:
++- Tim | Create value stories for indirect stakeholders
++- Tim | Incorporate Schwartz value model in the value stories
--* Added research on existing robots/dogs
--* Ontology image has been added
++Personas:
++--- Ricardo | Lecture slides state "Persona's need to have goals". Cornelia and Constantijn have these (to some extent), but Marcus does not yet--
++--- Ricardo | Create technology disliking persona scenario--
++--- Ricardo | Create for each scenario a 'before' and 'after technology' piece--
--|\\
--|Jeffrey Lim|\\
++Problem scenario:
++--- Doreen | Add sources for self-determination theory claims--
++--- 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--
--* Expand product vision with Snoezelen and check incorporation in objectives
--* Explain why music is not suitable for our goal/case
++====Human Factors====
++Robotic partner:
++--- Laura | Elaborate on limitations of MiRo w.r.t. snoezelen--
++--- 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.--
++- 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.
--|\\
++Design patterns:
++- Ricardo | Make team design pattern into something that is not drawn
++- Ricardo | Make team design pattern including the caretaker
++- Ricardo | Create diagrams for IDP's
--* -
--* -
++Ontology:
++--- Harmen | Add ontology image to XWiki--
--|\\
--|Doreen Mulder|\\
++Music and Cognition:
++- Tim | Describe each single signal, sound, movement that the PwD will receive/MiRo will make, the reasoning behind it and its desired effect
++- Tim | Link to Technology - Music Management for the explanation why we do not use music.
--* Add sources for self-determination theory claims
--* Look into "Design scenarios" (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
--* Write inclusive design page
--* Change every mention of Miro to MiRo
--* Write in Evaluation the Test about the little interview she had with Erik and how the product was perceived by a hard-of-hearing person.
++Measuring instruments:
++We do not yet know what should be here.
--|\\
++Group's core theoretical foundation:
++- Unassigned |  Add all sources here at the end of the project?
--* Added the sources for SDT claims
--* Worked on the Design Scenarios.
--* Inclusive design page has been created.
--* Made MiRo consistent
--* Write an evaluation on a hard-of-hearing person
++Inclusive design:
++--- Doreen | Write this page--
--|\\
--|Laura Ottevanger|\\
++Human-Agent teamwork:
++We do not yet know what should be here.
--* Review use cases
--* Add a future work page indicating our future work, and also that we would have liked to incorporate snoezelen
--* Elaborate on limitations of MiRo
--* Add research on interactions between elderly people and/or PwD's and robots + any other relevant research on the effect of pets/robots on PwD's.
++==== Technology ====
++Humanoid robot:
++--Done--
--|\\
++Music management:
++- Jeffrey | Explain why music is not suitable for our goal/case
--* Reviewed use cases and made small changes
--* Asked for the future work page and mentioned snoezelen in future work
--* Elaborated on the limitations
--* Did research on existing robots
++==== Report ====
++Unassigned | Proofread
++--Doreen | Consistent use of MiRo (Change every mention of Miro to MiRo)--
++Unassigned | Talk about the name WAF (Walking Assisting Friend)
++Unassigned | The group's core foundation
++--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.
++--
--|\\
--|Rohan Sobha|
--* Review current claims and perhaps add upon sections with small amounts of text/description
--* Add sources on why autonomy is important (basically just link to Self Determination Theory)
--* Check if we can validate claims with evaluation
--|\\
++=Todo list 2.0=
++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.
--* Reviewed current claims
--* Added the sources on why autonomy is important
--* Validated claims with evaluation
++== Introduction ==
++Laura | Introduction - Rewrite: problem, solution, what is where.
++Laura | Move MiRo difficulties to Technology
--|\\
--|Ricardo Vogel|\\
++== Foundation ==
++==== Operational Demands ====
--* Lecture slides state "Persona's need to have goals". Cornelia and Constantijn have these (to some extent), but Marcus does not yet
--* Create a technology disliking persona scenario
--* Create for each scenario a 'before' and 'after technology' piece
--* Make team design pattern into something that is not drawn
--* Make team design pattern including the caretaker
--* Create diagrams for IDP's
++=== Environments and Personas ===
++--Ricardo | Write 2 sentences as intro on basic Operational Demands page.--
++--Ricardo | Read and check if correct--
--|\\
++=== Stakeholders and Problem Scenario ===
++--Harmen | Write 2 sentences as intro for these two pages--
++--Harmen | Read and check if correct--
--* Added goals for Marcus
--* Created a new persona
--* Created for each scenario a 'before' and 'after technology' piece
--* Completed new design pattern drawing in the final week
--* Completed including the caretaker in the final week
--* -
--|\\
--|All|In the meeting (15-3) tasks were divided to work on for week 6 and week 7|In week 6 we did the first test run of the evaluation and in week 7 we performed the entire evaluation. In addition to their tasks, Doreen, Tim, Ricardo, and Harmen created the presentation.|\\
++==== Human Factors ====
--= Week 8 =
++==== Robotic Partner  ====
++--Tim | Read through and add one citation in the todo--
--End presentation
++==== Music and Cognition ====
++Jeffrey | Explanation how doglike sounds and movements could be beneficial based in literature and motivate why music is inappropriate for our use case.
++= Design Pattern and Ontology =
++--Harmen and Ricardo | Cite some references--
--|Member|Task|Reflection|\\
--|Tim Huisman|
++==== Measuring Instruments ====
++Rohan and Doreen? | cite papers about what we use for evaluation
--* Robotic Partner: Read through robotic partner and add one citation in the todo
--* Objectives: Remove Snoezelen from Objectives and expand Objectives
--* Future work: Move everything Snoezelen related to future work and make a coherent story
--* Future work: Write about the suggestions for other tests from the presentation in Future work e.g. test way of attention-grabbing
--*  Conclusion: Write a nice end chapter/conclusion on how it went and summarize the results.
++==== Group's core theoretical foundation ====
++Jeffrey | Talk about people with dementia getting lost, if walking helps by PwD, how good walking is for people, budget care homes
--|\\
++==== Inclusive Design ====
++--Doreen  | Clean up sources or notify what needs to be done on the page--
--* Changed robotic partner and added the citation
--* Removed Snoezelen and expanded Objectives
--* Move everything Snoezelen related to future work and make a coherent story
--* Wrote about other tests in future work
--* Wrote the conclusion and summary
++==== Human-agent Teamwork ====
++Rohan | Talk about humans and robots working together based in literature
--|\\
--|Harmen Kroon|\\
++=== Technology ===
++==== Humanoid Robot ====
++Laura | Specify specific limitations and technical options for MiRo
--* Stakeholders and Problem Scenario: Write 2 sentences as an intro for stakeholders and problem scenario
--* Stakeholders and Problem Scenario: Read through the stakeholders and problem scenario
--* Human factors - Design pattern and ontology: Cite some references in Ontology
--* Claims: Expand Claims
--* Ontology: Add a second Ontology
++==== Music Management ====
++Jeffrey | Explanation why we do not use music + what we do use + talk about video of alarm here
--|\\
++== Specification ==
++=== Objectives ===
++--Tim | Remove Snoezelen and expand Objectives--
++Tim | Move everything Snoezelen related to future work and make a coherent story
--* Intro has been written
--* Has been read through
--* Cited some references in Ontology
--* Expanded claims
--* Added extra ontology
++=== Use cases ===
++Rohan | Read through and check for (grammatical) mistakes
--|\\
--|Jeffrey Lim|\\
++=== Functions ===
++Tim | Check if we want to move storyboard to future work
--* Music and Cognition: Explanation of how doglike sounds and movements could be beneficial based on literature and motivate why music is inappropriate for our use case.
--* Group's core theoretical foundation: Talk about people with dementia getting lost, if walking helps by PwD, how good walking is for people, budget care homes
--* Music management: Explanation of why we do not use music + what we do use + talk about the video of alarm here
--* Future Work: Add limitations and how we would solve them in future work.
++=== Claims ===
++--Harmen | Expand Claims--
--|\\
++== Evaluation ==
++=== Prototype ===
++Laura | Add code to Github,
++Laura | Talk about code in Prototype chapter
--* Added why doglike sounds are beneficial for walking and added a small chapter on music and cognition
--* Wrote text in the theoretical foundation
--* -
--* -
++=== Test ===
++Rohan  | Rewrite to make a bit more specific, ensure that the test is reproduceable, add Wilcoxon test
++--Doreen | Add Discussion after the results and ensure that results is just numbers--
--|\\
--|Doreen Mulder|\\
++== Design Patterns ==
++Ricardo | Reread and change picture
++Ricardo | Add caretaker in team design pattern
++Ricardo | Picture for IDP
--* Measuring Instruments: cite papers about what we use for evaluation
--* Inclusive design: Clean up sources or notify what needs to be done on the page
--* Discussion: Add Discussion after the results and ensure that the results are just numbers
--* Future work: Talk about having only 8 participants, not a correct room (not a care home hallway but a single room), using PwD as test subjects = more realistic test.
++== Ontology ==
++--Harmen | Add second Ontology--
--|\\
++== Planning ==
++Unassigned | Rewrite todo-list as a per week description of what happened
++(Optional) Unassigned | Put everything into a nice table like: [[Timetable table >> https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group02/view/Timetable/TimeTable%20Table%20Format/]]
--* Cited papers in teamwork with Rohan
--* Added sources and created the page
--* Added Discussion and changed results
--* Has been put in Test as it might suit better for now
++== Conclusion ==
++=== Future Work ===
++Jeffrey and Laura | Add limitations and how we would solve it in future work.
++--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.-- I put this in "Test" for now, since it fits better there. If needed I can repeat it in a few sentences on this page as well.
++--Tim | Suggestions for other tests from presentation = test way of attention grabbing--
++Rohan | Snoezelen in context of evaluation
++=== Conclusion ===
++--Tim and (Rohan) | Write a nice end chapter/conclusion on how it went and summarizing results. --
--|\\
--|Laura Ottevanger|\\
--
--* Introduction - Rewrite: problem, solution, what is where.
--* Technology: Move MiRo difficulties to Technology
--* Technology: Specify specific limitations and technical options for MiRo
--* Add code to Gitlab
--* Prototype: Talk about the code in the Prototype chapter
--* Future Work: Add limitations and how we would solve them in future work.
--* Perform Wilcoxon test on test data
--
--|\\
--
--* Created a small introduction
--* Rewrote difficulties a bit to add it to Technology
--* Specified specific limitations and technical options for MiRo for the next group as well
--* Add code as snippets to Gitlab
--* Talked about the code in the Prototype chapter
--* Added limitations and how we would solve them in future work.
--* Wilcoxon test has been performed
--
--|\\
--|Rohan Sobha|\\
--
--* Measuring Instruments: cite papers about what we use for evaluation
--* Human-agent teamwork: Talk about humans and robots working together based on literature
--* Use cases: Read through and check for (grammatical) mistakes
--* Test: Rewrite to make it a bit more specific, ensure that the test is reproducible, add the Wilcoxon test
--* Future work: Add Snoezelen in the context of the evaluation
--* Conclusion: Write a nice end chapter/conclusion on how it went and summarize the results.
--
--|\\
--
--* Cited papers in teamwork with Doreen
--* Added the Human-agent teamwork page and elaborated on working together
--* Use cases have been read through
--* Test page has been rewritten to adhere to the requirements
--* Added Snoezelen in future work
--* Wrote a nice end chapter/conclusion.
--
--|\\
--|Ricardo Vogel|\\
--
--* Environments and Personas: Write 2 sentences as an intro on the basic Operational Demands page.
--* Environments and Personas: Read through and check if correct.
--* Human factors - Design pattern and ontology: Cite some references
--* Design patterns: Reread and change the picture
--* Design patterns: Add caretaker in team design pattern
--
--|\\
--
--* The introduction for Environments and Personas has been made
--* Have been read through
--* References in the design patterns have been made
--* New picture has been created
--* Caretaker has been added
--
--|\\
--|All|The final presentation occurred. Doreen, Tim, Ricardo, and Harmen did the presentation. We divided tasks at 31-3 and 1-4 |We evaluated the tasks on 5-4.|\\