Timetable
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
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:
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
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:
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
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:
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
We are going to create small videos:
Snoezelen = demoversion of Miro
Wristband = Doreen creates is with Arduino
Walking = Wizard of Oz with remote control
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
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.
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.
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.
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
Todos
Format: Assignee | Todo
Specification
Objectives:
- Jeffrey | Expand product vision with Snoezelen and check incorporation in objectives
Use cases:- Laura | Review use cases
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
Future work:- Laura | Add future work page indicating our future work, and also that we would have liked to incorporate snoezelen
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
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
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
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
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.
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?
Inclusive design:- Doreen | Write this page
Human-Agent teamwork:
We do not yet know what should be here.
Technology
Humanoid robot:Done
Music management:
- Jeffrey | Explain why music is not suitable for our goal/case
Report
Unassigned | Proofread
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 foundationDoreen | Write in Evaluation -> Test about the little interview I had with Erik and how the product was perceived by a hard of hearing person.