Changes for page TimeTable Table Format
Last modified by Laura Ottevanger on 2022/04/05 10:59
From version
2.2


edited by Laura Ottevanger
on 2022/04/05 10:56
on 2022/04/05 10:56
Change comment:
There is no comment for this version
To version
1.4


edited by Laura Ottevanger
on 2022/04/05 10:43
on 2022/04/05 10:43
Change comment:
There is no comment for this version
Summary
Details
- Page properties
-
- Content
-
... ... @@ -1,51 +2,50 @@ 1 -= Week 1 = 2 2 2 += Week 1= 3 3 4 -|Member|Task|Reflection|\\ 5 -|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.|\\ 6 -|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.|\\ 7 -|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.|\\ 8 -|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.|\\ 9 -|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.|\\ 10 -|Rohan Sobha|Work on the report: Operational demands: environments and stakeholders|Rohan made the Environments and Stakeholders.|\\ 11 -|Ricardo Vogel| Work on the report: Personas and problem scenario|Ricardo made personas.|\\ 4 + 5 +|Member|Task|Reflection| 6 +|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.| 7 +|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.| 8 +|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.| 9 +|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.| 10 +|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.| 11 +|Rohan Sobha|Work on the report: Operational demands: environments and stakeholders|Rohan made the Environments and Stakeholders.| 12 +|Ricardo Vogel| Work on the report: Personas and problem scenario|Ricardo made personas.| 12 12 |All|In the meeting (8-2) tasks were divided. The deadline is before the meeting next week.| | 13 13 14 -= 15 +=Week 2= 15 15 16 -|Member|Task|Reflection| \\17 +|Member|Task|Reflection| 17 17 |Tim Huisman|Commandos/voice recognition, help with personas & scenarios|Tim did research on voice recognition and which Python packages are necessary to implement that. 18 -| \\19 -|Harmen Kroon| Harmen: Problem scenarios|Harmen made the problem scenario.| \\20 -|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.| \\21 -|Doreen Mulder|State diagram / Leash|Doreen made a flowchart about the behavior of the robot.| \\22 -|Laura Ottevanger|Look into pathmaking |Laura made the first storyboard.| \\23 -|Rohan Sobha|Robotic Partner / Music recognition|Rohan made the part on Robotic Partner and Music recognition| \\19 +| 20 +|Harmen Kroon| Harmen: Problem scenarios|Harmen made the problem scenario.| 21 +|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.| 22 +|Doreen Mulder|State diagram / Leash|Doreen made a flowchart about the behavior of the robot.| 23 +|Laura Ottevanger|Look into pathmaking |Laura made the first storyboard.| 24 +|Rohan Sobha|Robotic Partner / Music recognition|Rohan made the part on Robotic Partner and Music recognition| 24 24 |Ricardo Vogel|Personas & persona scenarios|Ricardo extended the personas and made persona scenario.| 25 25 |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. | 26 26 27 -= Week 3 = 28 - 29 -|Member|Task|Reflection|\\ 30 -|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 |\\ 31 -|Harmen Kroon|Make Ontology|Figured out the program to create an ontology but did not create the ontology yet|\\ 32 -|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|\\ 33 -|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.|\\ 34 -|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. |\\ 35 -|Rohan Sobha|Make Claims|Made the claims|\\ 36 -|Ricardo Vogel|Make Design Patterns|Made the Design Patterns with a drawing of the system.|\\ 28 +=Week 3= 29 +|Member|Task|Reflection| 30 +|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 | 31 +|Harmen Kroon|Make Ontology|Figured out the program to create an ontology but did not create the ontology yet| 32 +|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| 33 +|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.| 34 +|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. | 35 +|Rohan Sobha|Make Claims|Made the claims| 36 +|Ricardo Vogel|Make Design Patterns|Made the Design Patterns with a drawing of the system.| 37 37 |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| 38 38 39 -= Week 4 = 40 - 41 -|Member|Task|Reflection|\\ 42 -|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.|\\ 43 -|Harmen Kroon|Make the Ontology and write the human factors ontology page|Made ontology. Started on human factors ontology, made some code for demo|\\ 44 -|Jeffrey Lim|Use Cases and work on mid-term presentation |Made use cases and presented presentation|\\ 45 -|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|\\ 46 -|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.|\\ 47 -|Rohan Sobha|Work on Evaluation and work on mid-term presentation |Made a start on evaluation, made the presentation, and presented the presentation.|\\ 48 -|Ricardo Vogel|Specify design patterns and work on the human factors design patterns page|Worked on design patterns and the human factors design patterns|\\ 39 +=Week 4= 40 +|Member|Task|Reflection| 41 +|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.| 42 +|Harmen Kroon|Make the Ontology and write the human factors ontology page|Made ontology. Started on human factors ontology, made some code for demo| 43 +|Jeffrey Lim|Use Cases and work on mid-term presentation |Made use cases and presented presentation| 44 +|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| 45 +|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.| 46 +|Rohan Sobha|Work on Evaluation and work on mid-term presentation |Made a start on evaluation, made the presentation, and presented the presentation.| 47 +|Ricardo Vogel|Specify design patterns and work on the human factors design patterns page|Worked on design patterns and the human factors design patterns| 49 49 |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: 50 50 51 51 * Snoezelen = for which we will use the demo version of MiRo, ... ... @@ -55,25 +55,20 @@ 55 55 * Ask for attention = Harmen and Laura look into mimicking a barking dog 56 56 * Positive response = Laura will create some code where MiRo is barking, wagging its tail, etc. | 57 57 58 -= Week 5 = 59 - 60 - Mid-term presentation 61 - 62 -|Member|Task|Reflection|\\ 63 -|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|\\ 64 -|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.|\\ 65 -|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. |\\ 66 -|Doreen Mulder|Elaborate on evaluation and collaborate with Rohan on experimental setup|Elaborated evaluation and worked on experimental setup|\\ 67 -|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|\\ 68 -|Rohan Sobha| Elaborate on evaluation and collaborate with Doreen on experimental setup|Elaborated evaluation and worked on experimental setup|\\ 69 -|Ricardo Vogel|Going to work on ethics and test if we can connect MiRo to a server and/or with packets|Worked on ethics|\\ 57 +=Week 5= Mid-term presentation 58 +|Member|Task|Reflection| 59 +|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| 60 +|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.| 61 +|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. | 62 +|Doreen Mulder|Elaborate on evaluation and collaborate with Rohan on experimental setup|Elaborated evaluation and worked on experimental setup| 63 +|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| 64 +|Rohan Sobha| Elaborate on evaluation and collaborate with Doreen on experimental setup|Elaborated evaluation and worked on experimental setup| 65 +|Ricardo Vogel|Going to work on ethics and test if we can connect MiRo to a server and/or with packets|Worked on ethics| 70 70 |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| 71 71 72 -= Week 6 and 7 = 73 - 74 -|Member|Task|Reflection|\\ 75 -|Tim Huisman|\\ 76 - 68 +=Week 6 and 7= 69 +|Member|Task|Reflection| 70 +|Tim Huisman| 77 77 * Update flowchart to remove snoezelen to be coherent with the current idea of MiRo 78 78 * Add a textual description of walking with MiRo to incorporate what MiRo should do if PwD stops to talk during the walk 79 79 * Create value stories for indirect stakeholders ... ... @@ -80,88 +80,58 @@ 80 80 * Incorporate Schwartz's value model in the value stories 81 81 * Describe every single signal, sound, a movement that the PwD will receive/MiRo will make, the reasoning behind it, and its desired effect 82 82 * Link to Technology - Music Management for the explanation of why we do not use music. 83 - 84 -|\\ 85 - 86 -* Updated flowchart 77 +|* Updated flowchart 87 87 * Added the textual description 88 88 * - 89 89 * - 90 90 * Describing the sounds has been completed in the final week. 91 91 * Link to technology has been completed in the final week. 92 - 93 -|\\ 94 -|Harmen Kroon|\\ 95 - 83 +| 84 +|Harmen Kroon| 96 96 * 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. 97 97 * Add ontology image to XWiki 98 - 99 -|\\ 100 - 87 +| 101 101 * Added research on existing robots/dogs 102 102 * Ontology image has been added 103 - 104 -|\\ 105 -|Jeffrey Lim|\\ 106 - 90 +| 91 +|Jeffrey Lim| 107 107 * Expand product vision with Snoezelen and check incorporation in objectives 108 108 * Explain why music is not suitable for our goal/case 109 - 110 -|\\ 111 - 94 +| 112 112 * - 113 -* - 114 - 115 -|\\ 116 -|Doreen Mulder|\\ 117 - 96 +* - | 97 +|Doreen Mulder| 118 118 * Add sources for self-determination theory claims 119 119 * 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 120 120 * Write inclusive design page 121 121 * Change every mention of Miro to MiRo 122 122 * 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. 123 - 124 -|\\ 125 - 103 +| 126 126 * Added the sources for SDT claims 127 127 * Worked on the Design Scenarios. 128 128 * Inclusive design page has been created. 129 129 * Made MiRo consistent 130 130 * Write an evaluation on a hard-of-hearing person 131 - 132 -|\\ 133 -|Laura Ottevanger|\\ 134 - 109 +| 110 +|Laura Ottevanger| 135 135 * Review use cases 136 136 * Add a future work page indicating our future work, and also that we would have liked to incorporate snoezelen 137 137 * Elaborate on limitations of MiRo 138 138 * 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. 139 - 140 -|\\ 141 - 142 -* Reviewed use cases and made small changes 143 -* Asked for the future work page and mentioned snoezelen in future work 144 -* Elaborated on the limitations 145 -* Did research on existing robots 146 - 147 147 | 148 - 149 - |RohanSobha|\\150 - 116 +* Reviewed use cases and made small changes 117 +* Asked for the future work page and mentioned snoezelen in future work| 118 +|Rohan Sobha| 151 151 * Review current claims and perhaps add upon sections with small amounts of text/description 152 152 * Add sources on why autonomy is important (basically just link to Self Determination Theory) 153 153 * Check if we can validate claims with evaluation 154 154 * Elaborate on limitations of MiRo 155 155 * Added research on existing robots/dogs 156 - 157 -|\\ 158 - 124 +| 159 159 * Reviewed current claims 160 160 * Added the sources on why autonomy is important 161 161 * Validated claims with evaluation| 162 - 163 -|Ricardo Vogel|\\ 164 - 128 +|Ricardo Vogel| 165 165 * Lecture slides state "Persona's need to have goals". Cornelia and Constantijn have these (to some extent), but Marcus does not yet 166 166 * Create a technology disliking persona scenario 167 167 * Create for each scenario a 'before' and 'after technology' piece ... ... @@ -168,9 +168,7 @@ 168 168 * Make team design pattern into something that is not drawn 169 169 * Make team design pattern including the caretaker 170 170 * Create diagrams for IDP's 171 - 172 -|\\ 173 - 135 +| 174 174 * Added goals for Marcus 175 175 * Created a new persona 176 176 * Created for each scenario a 'before' and 'after technology' piece ... ... @@ -177,91 +177,68 @@ 177 177 * Completed new design pattern drawing in the final week 178 178 * Completed including the caretaker in the final week 179 179 * - 142 +| 143 +|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.| 180 180 181 -|\\ 182 -|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.|\\ 183 - 184 -= Week 8 = 185 - 186 - End presentation 187 - 188 -|Member|Task|Reflection|\\ 189 -|Tim Huisman|\\ 190 - 191 -* Robotic Partner: Read through robotic partner and add one citation in the todo 192 -* Objectives: Remove Snoezelen from Objectives and expand Objectives 193 -* Future work: Move everything Snoezelen related to future work and make a coherent story 194 -* Future work: Write about the suggestions for other tests from the presentation in Future work e.g. test way of attention-grabbing 195 -* Conclusion: Write a nice end chapter/conclusion on how it went and summarize the results. 196 - 197 -|\\ 198 - 145 +=Week 8= End presentation 146 +|Member|Task|Reflection| 147 +|Tim Huisman| 148 +* Read through robotic partner and add one citation in the todo 149 +* Remove Snoezelen from Objectives and expand Objectives 150 +* Move everything Snoezelen related to future work and make a coherent story 151 +* Write about the suggestions for other tests from the presentation in Future work e.g. test way of attention-grabbing 152 +* Write a nice end chapter/conclusion on how it went and summarize the results. 153 +| 199 199 * Changed robotic partner and added the citation 200 200 * Removed Snoezelen and expanded Objectives 201 201 * Move everything Snoezelen related to future work and make a coherent story 202 202 * Wrote about other tests in future work 203 203 * Wrote the conclusion and summary 204 - 205 -|\\ 206 -|Harmen Kroon|\\ 207 - 208 -* Stakeholders and Problem Scenario: Write 2 sentences as an intro for stakeholders and problem scenario 209 -* Stakeholders and Problem Scenario: Read through the stakeholders and problem scenario 210 -* Human factors - Design pattern and ontology: Cite some references in Ontology 211 -* Claims: Expand Claims 212 -* Ontology: Add a second Ontology 213 - 214 -|\\ 215 - 159 +| 160 +|Harmen Kroon| 161 +* Write 2 sentences as an intro for stakeholders and problem scenario 162 +* Read through stakeholders and problem scenario 163 +* Cite some references in Ontology 164 +* Expand Claims 165 +* Add second Ontology 166 +| 216 216 * Intro has been written 217 217 * Has been read through 218 218 * Cited some references in Ontology 219 219 * Expanded claims 220 220 * Added extra ontology 221 - 222 -|\\ 223 -|Jeffrey Lim|\\ 224 - 172 +| 173 +|Jeffrey Lim| 225 225 * 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. 226 226 * 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 227 227 * Music management: Explanation of why we do not use music + what we do use + talk about the video of alarm here 228 -* Future Work: Add limitations and how we would solve them in future work. 229 - 230 -|\\ 231 - 177 +* Add limitations and how we would solve them in future work. 178 +| 232 232 * Added why doglike sounds are beneficial for walking and added a small chapter on music and cognition 233 233 * Wrote text in the theoretical foundation 234 234 * - 235 235 * - 236 - 237 -|\\ 238 -|Doreen Mulder|\\ 239 - 183 +| 184 +|Doreen Mulder| 240 240 * Measuring Instruments: cite papers about what we use for evaluation 241 241 * Inclusive design: Clean up sources or notify what needs to be done on the page 242 -* Discussion: Add Discussion after the results and ensure that the results are just numbers 243 -* 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. 244 - 245 -|\\ 246 - 187 +* Add Discussion after the results and ensure that the results are just numbers 188 +* In 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. 189 +| 247 247 * Cited papers in teamwork with Rohan 248 248 * Added sources and created the page 249 249 * Added Discussion and changed results 250 250 * Has been put in Test as it might suit better for now 251 - 252 -|\\ 253 -|Laura Ottevanger|\\ 254 - 194 +| 195 +|Laura Ottevanger| 255 255 * Introduction - Rewrite: problem, solution, what is where. 256 -* Technology:Move MiRo difficulties to Technology257 -* Technology:Specify specific limitations and technical options for MiRo197 +* Move MiRo difficulties to Technology 198 +* Specify specific limitations and technical options for MiRo 258 258 * Add code to Gitlab 259 -* Prototype: Talk about the code in the Prototype chapter 260 -* Future Work: Add limitations and how we would solve them in future work. 261 -* Perform Wilcoxon test on test data 262 - 263 -|\\ 264 - 200 +* Talk about the code in the Prototype chapter 201 +* Add limitations and how we would solve them in future work. 202 +* Perform Wilcoxon test on testdata 203 +| 265 265 * Created a small introduction 266 266 * Rewrote difficulties a bit to add it to Technology 267 267 * Specified specific limitations and technical options for MiRo for the next group as well ... ... @@ -269,19 +269,15 @@ 269 269 * Talked about the code in the Prototype chapter 270 270 * Added limitations and how we would solve them in future work. 271 271 * Wilcoxon test has been performed 272 - 273 -|\\ 274 -|Rohan Sobha|\\ 275 - 211 +| 212 +|Rohan Sobha| 276 276 * Measuring Instruments: cite papers about what we use for evaluation 277 277 * Human-agent teamwork: Talk about humans and robots working together based on literature 278 278 * Use cases: Read through and check for (grammatical) mistakes 279 279 * Test: Rewrite to make it a bit more specific, ensure that the test is reproducible, add the Wilcoxon test 280 -* Future work: Add Snoezelen in the context of the evaluation 281 -* Conclusion: Write a nice end chapter/conclusion on how it went and summarize the results. 282 - 283 -|\\ 284 - 217 +* Future work: Add Snoezelen in context of evaluation 218 +* Conclusion: Write a nice end chapter/conclusion on how it went and summarizing results. 219 +| 285 285 * Cited papers in teamwork with Doreen 286 286 * Added the Human-agent teamwork page and elaborated on working together 287 287 * Use cases have been read through ... ... @@ -288,23 +288,10 @@ 288 288 * Test page has been rewritten to adhere to the requirements 289 289 * Added Snoezelen in future work 290 290 * Wrote a nice end chapter/conclusion. 226 +| 227 +|Ricardo Vogel| 291 291 292 -|\\ 293 -|Ricardo Vogel|\\ 229 +| 294 294 295 -* Environments and Personas: Write 2 sentences as an intro on the basic Operational Demands page. 296 -* Environments and Personas: Read through and check if correct. 297 -* Human factors - Design pattern and ontology: Cite some references 298 -* Design patterns: Reread and change picture 299 -* Design patterns: Add caretaker in team design pattern 300 - 301 -|\\ 302 - 303 -* The introduction for Environments and Personas has been made 304 -* Have been read through 305 -* References in the design patterns have been made 306 -* New picture has been created 307 -* Caretaker has been added 308 - 309 -|\\ 231 +| 310 310 |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.|