PRE2022 3 Group12

Logbook

The logbook with member task and time spend per week can be found on the Logbook page

Problem Statement:

Society is currently faced with an ageing population. By around 2040, it is expected that one-quarter of the population will be aged 65 years or older. Compared to today, the size of this group of people will have increased by about 1.2 million people by 2040, all while the number of people working (in the age group 20 to 64 years old) will stay roughly the same. This means a large shortage of healthcare workers will arise, causing some elderly to not receive all care they might be expecting. One important aspect of this care that might easily be overlooked are ways to combat their loneliness. This is often prevalent among the elderly, especially those aged 75 years or older. One possible way to battle loneliness is to provide activities. However, with the reduced availability of care, it will become harder for healthcare workers to provide these activities. In these circumstances, robots can be used to support the workers.

Users:

Our design provides people with an opportunity to play physical card games without the need for other players. This is beneficial for anyone who is for some reason unable or uninclined to play with others. While it is great to have many potential people that are able to use the product, it also results in a large and ill-defined target group. In order to combat this general target group as well as form a starting point for the design and make it feasible considering the size of this project, a subset of the target group is taken. This new target group focuses on elderly people.

The target group of elderly people is chosen as they are generally assumed to have more difficulties with technology. It’s therefore expected that if the elderly people are able to properly use and understand the product, the younger generations will be able to do so as well.

We hope to increase the Quality of Life (QoL) of the elderly by creating this product. For example when they are unable to visit others, or unable to have visitors, they can still play with the robot and enjoy a game of cards.

User Requirements:

Due to their age, most elderly have increased problems with their sight, hearing, or motor skills. Therefore, it is important that the design has options built in to deal with this. For example, an easy-to-read font and text size, clear and loud audio implementations, and a lightweight and easy-to-move design.

Through our literary research, it was also noted that elderly people often experience more difficulties when learning something new. Because of this, it is assumed that using concepts that the elderly are already familiar with, or at least similar to those, is better as they will understand and learn them faster. Therefore, we should choose a game that is easy to understand and known by elderly people. As well as implement a simple interface and design.

Other aspects that could be added in order to improve the user experience, but are not necessary. Are the implementation of motivational messages during the game and multiple difficulty settings as a balance between ability and difficulty is important.

To engage the users’ more while playing with the robot, it is important that the robot has a competitive nature. Instead of having a robot that is relationship driven.

Deliverables:

The aim of this project is to design and build a card-game playing robot to provide social support in the form of entertainment for the increasingly ageing society. Therefore, it is the goal to deliver a prototype version of a card-game playing robot that satisfies some basic requirements that are necessary for the robot to be functional. The most important requirements are listed below.

1. The robot must have a strategy to play one specific card-game with equal performance as the average non-professional human player.
2. The robot must be able to successfully recognize and distinguish all the cards that make up a standard 52-card deck with an accuracy of at least 95%.
3. The robot must be embodied and it must be able to move the cards physically or have an integrated virtual environment by means of a multi-touch table.

In view of these requirements, the following components that make up the prototype will be delivered.

1. An algorithm that uses available information to select the next action or move.
2. An object recognition algorithm trained for a standard 52-card deck.
3. A physical implementation of the robot that is able to move cards or display them virtually.

The physical prototype will then be created by combining these components into one system. All progress of the project will be documented on this wiki, which will serve as the group report at the end of this project. Furthermore, a final presentation will be given at the end of the project combined with a demonstration of the prototype.

Approach:

Graphical representation of the steps of the design process.

During the project, the prototype will be developed by means of a design process. This process consists of multiple phases. Firstly, the problem will be defined as well as the design goal to solve the problem. Secondly, the functional and technical requirements of the prototype will be specified taking into account time, money and resources. From these requirements, it is possible to create concepts for the design. Next, details will be added to the design and the design will be realized. Lastly, tests will be performed to see if the prototype satisfies the requirements. This process can be summarized in the following steps:

1. Define problem
2. Specify requirements
3. Preliminary design
4. Detailed design
5. Prototyping
6. Testing

Given that the final presentations will be planned in week 8 of the course, this process will have a time period of seven weeks. Therefore, every step is expected to be completed within one week, with the exception of the detailed design since this is the most important and difficult step which will therefore require more time. So the time will be managed as follows, step 1 will be completed in week 1, step 2 in week 2, step 3 in week 3, step 4 in weeks 4 and 5, step 5 in week 6 and step 6 in week 7. In this way, all deliverables are finished in week 8.

Another important aspect of the design process is communication. Therefore, a weekly meeting is scheduled to discuss the progress and task division as well as a weekly work session. The meetings and work sessions will be scheduled on Wednesday from 10:30-11:30 and Monday 11:30-12:30 respectively.

Milestones:

The project milestones are both related to the steps of the design process and deliverables in that they break down the project into smaller sections for the tasks that need to be completed. They can be defined as follows:

1. Have a problem definition that clearly states the broader issue and the targeted user as well as the design goal
2. Have created a list of at least 5 requirements for both functional and technical requirements according to the MoSCoW method
3. Have created a complete mock-up (either digitally or physically) that clearly shows how all the requirements are satisfied
4. Have created an algorithm that implements a strategy to select actions for one specific card game
5. Have created an object recognition algorithm to identify a standard 52-card deck
6. Have a bill of materials
7. Have created a system to pick up playing cards
12. Have created a blueprint of the robot's physical embodiment
13. Successfully build, combine and integrate all components
14. The system satisfies the requirements as shown by means of a test

Each milestone will be assigned in a logical way to one step of the design process as shown by the following table.

Week	Step	Milestones
1	Define problem	1
2	Specify requirements	2
3	Preliminary design	3
4	Detailed design	6
5	Detailed design	3, 5, 7, 8
6	Prototyping	9
7	Testing	10

Task Division:

The design process consists of multiple phases and each phase conforms to different types of tasks. For example, the first phase includes a literature study, users study, problem statement and planning. Therefore, the tasks will be divided weekly among the group members during the team meetings. The task division for each week is shown in the tables below.

Week 1	Tasks
Abel Brasse	User study, study 5 scientific papers
Linda Geraets	User study, study 5 scientific papers
Luke van Dongen	Card recognition software, study 5 scientific papers
Sander van der Leek	Robot design sketch/model, study 5 scientific papers
Tom van Eemeren	Approach, milestones, deliverables, study 5 scientific papers
Tom van Liempd	Problem statement, study 5 scientific papers

Literature Study:

The articles read for the literature study accompanied with their summary can be found in the Literature page.

Members

• Abel Brasse (1509128) - a.m.brasse@student.tue.nl
• Linda Geraets (1565834) - l.j.m.geraets@student.tue.nl
• Sander van der Leek (1564226) - s.j.m.v.d.leek@student.tue.nl
• Tom van Liempd (1544098) - t.g.c.v.liempd@student.tue.nl
• Luke van Dongen (1535242) - l.h.m.v.dongen@student.tue.nl
• Tom van Eemeren (1755595) - t.v.eemeren@student.tue.nl

Links

User interview