Changes for page Timetable

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

From 31.1 to 30.1 From 47.1 to 46.1

From version

46.1

edited by Tim Huisman
on 2022/04/02 21:52

Change comment: There is no comment for this version

To version

31.1

edited by Rohan Sobha
on 2022/03/21 17:12

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.Tim_Huisman2
++XWiki.rsobha

Content

@@ -106,7 +106,7 @@
  - Jeffrey | Expand product vision with Snoezelen and check incorporation in objectives
  Use cases:
----- Laura | Review use cases--
++- Laura | Review use cases
  Functions:
  - Tim | Update flowchart to remove snoezelen to be coherent with current idea of MiRo
@@ -117,7 +117,7 @@
  - --Rohan | Check if we can validate claims with evaluation--
  Future work:
----- Laura | Add future work page indicating our future work, and also that we would have liked to incorporate snoezelen--
++- Laura | Add future work page indicating our future work, and also that we would have liked to incorporate snoezelen
  === Foundation ===
  ====Operational demands ====
@@ -129,24 +129,24 @@
  - Tim | Incorporate Schwartz value model in the value stories
  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 | 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--
  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--
++- 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
  ====Human Factors====
  Robotic partner:
----- Laura | Elaborate on limitations of MiRo w.r.t. snoezelen--
++- 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
++- Tim | Make team design pattern into something that is not drawn
++- Tim | Make team design pattern including the caretaker
++- Tim | Create diagrams for IDP's
  Ontology:
  - Harmen | Add ontology image to XWiki
@@ -162,7 +162,7 @@
  - Unassigned |  Add all sources here at the end of the project?
  Inclusive design:
----- Doreen | Write this page--
++- Doreen | Write this page
  Human-Agent teamwork:
  We do not yet know what should be here.
@@ -176,104 +176,7 @@
  ==== Report ====
  Unassigned | Proofread
--Doreen | Consistent use of MiRo (Change every mention of Miro to MiRo)
++Unassigned | 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.
----
--
--
--
--=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.
--
--== Introduction ==
--Laura | Introduction - Rewrite: problem, solution, what is where.
--Laura | Move MiRo difficulties to Technology
--
--== Foundation ==
--==== Operational Demands ====
--
--=== 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
--
--
--==== Human Factors ====
--
--==== Robotic Partner  ====
--Tim | Read through and add one citation in the todo
--
--==== 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
--
--==== Measuring Instruments ====
--Rohan and Doreen? | cite papers about what we use for evaluation
--
--==== 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
--
--==== Human-agent Teamwork ====
--Rohan | Talk about humans and robots working together based in literature
--
--=== Technology ===
--==== Humanoid Robot ====
--Laura | Specify specific limitations and technical options for MiRo
--
--==== 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
--
--=== Use cases ===
--Rohan | Read through and check for (grammatical) mistakes
--
--=== Functions ===
--Tim | Check if we want to move storyboard to future work
--
--=== Claims ===
--Harmen | Expand Claims
--
--== Evaluation ==
--=== Prototype ===
--Laura | Add code to Github,
--Laura | Talk about code in Prototype chapter
--
--=== 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
--
--== Design Patterns ==
--Ricardo | Reread and change picture
--Ricardo | Add caretaker in team design pattern
--Ricardo | Picture for IDP
--
--== 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/]]
--
--== 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.
--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.
--