PRE2019 3 Group18
Group Members
Name | ID | Major | |
---|---|---|---|
Planning
Meetings held on Mondays and Thursdays. Tasks specified in the table have to be completed before the given meeting.
KdB = Kasper, N = Nick, D = Davide, KM = Kamil, M = Milan
Week | Monday (morning) | Thursday (afternoon) |
1 | -- | -- |
---|---|---|
2 | ALL: Form a group, decide on the subject |
|
3 |
|
|
4 | ||
5 | ||
6 | ||
7 | ||
8 | ||
9 |
Subject
Problem statement
WHO, short for World Health Organization, published an article on 30 October 2018 named ‘Diabetes’ (REF1). The article stated some key facts about diabetes. For example, the number of people with diabetes changed from 108 million to 422 million in 34 years. This is a rather concerning number, especially with the fact that diabetes can be treated (note: not cured!) and its effects can be delayed or even avoided with the help of a medication, a healthy lifestyle; a healthy diet with good physical activity and with the help of proper, professional screening of the patient. Present-day these challenges can be tackled properly, but the USE-aspect still has a lot of improvements to undergo. Later in this section we will look more in depth into the USE-aspect of problems with current technology.
Diabetes is a well-known disease, but there is still a lot of ignorance about the disease. Diabetes is a disease which occurs when the amount of glucose in your blood is too high. Having too much glucose in your blood for a long period of time can cause health problems. Diabetes is a general name for the diseases, it defines severel types of diabetes. Although there is no cure for diabetes (yet), a person can manage their diabetes to stay healthy and will be safe from its fatal consequences.
A lot of people undergo constraints because of the disease and with the help of technology products will make lives easier for diabetes patients. Diabetes patients first of all need to take medicine, depending on their type of diabetes (REF2). Also, they have to follow a personal diet matching with their diabetes type (REF2). This is a very important step for the treatment of diabetes and it requires a lot of effort from the patient. The diet has to be very specific, healthy and available to the patient. Problems with a good diet for a patient could be that a person is allergic to certain food, the diet does not provide a complete diet with all necessary vitamins or the food itself is too expensive for the person or even not available to the patient in his current location. These are all some technical issues that can arise when focusing on a good diet. But also the USE-aspect of technology to help patients is a big part. The app has to be user friendly and clear for people to use it concisely and correctly. Wrong data or mere laziness due to the app being hard to understand is disadvantageous and could potentially be fatal to patients. That is why this is an important problem which needs to be solved.
REF1 : https://www.who.int/news-room/fact-sheets/detail/diabetes
REF2: https://www.medicinenet.com/diabetes_treatment/article.htm#what_is_the_treatment_for_diabetes
Objectives
- Researching the state-of-the-art on diabetes
- Researching the needs of a diabetic patient
- Creating an app to assist these people with their diet
Users
- People who have diabetes and could use assistance with their diet
The application we aim to develop has a clear group of users; diabetic patients. Approximately 1,2 million Dutch people have diabetes. There are two types of diabetic patients, called type 1 and type 2. About 90% of all diabetic patients are type 2 diabetics. For now, our focus is on the patients of type 1 diabetes, which is the more severe form. These people need a specific diet and have to regulate their blood sugar level by administering insulin. These patients will probably benefit from a wellmade application that can support them with their diet and blood sugar regulation. We will try to find out how these people can be best supported by an application, and what their needs are going to be. An interview with the patient-communication advisor of Diabeter Eindhoven, and diabetic patient type 1 himself, Wietske Wits, is planned for monday 13-02-2020. He will elaborate on the user needs he finds important.
Requirement of the users
Our user requirements mostly depend on the functionalities our patient would need or want as a functionality of the app. The app has to make sure that the patient will follow a good diet (and that the patient will take his medicine). To help the patient to stick to this diet it will give many different examples of good meals to cook, but also to give the patient enough freedom to change some ingredients of those meals. It should also be possible to choose a good meal from those example meals with a certain budget. The app should also need the data of the measurement of the amount of glucose in the blood, based on these data the app can change the diet or call a doctor. It is not possible to measure the blood 24/7, so either a computer must simulate a person based on some measurements or the patient must measure his own blood three or more times a day (the app can help remind this). This is very important, because wrong date or laziness of taking those measurements could potentially be fatal to patients.
State-of-the-art
Diabetes applications
The market of diabetes applications on smartphones has grown immensely over the past years. Users can choose between many options, no matter which operating system is running on their phone. Presented research has focused on Android users, since our prototype will also be developed for that platform. This article consists of a list with the most popular applications described. At the end there is a paragraph summing up the general findings.
- Calorie Counter - MyNetDiary, Food Diary Tracker
- link to Google Play
- Made not specifically for diabetic people, but for anyone who wants to have better control over their diet. Biggest advantage is the very big database of foods, with the possibility of updates from users. Includes a barcode scanner that allows to scan the food package for easy calorie and nutrients entry.
- The proposed (by the creators) way to use the application is as follows:
- Set a weight goal
- Enter a target date ( vacation, wedding, or reunion )
- Get a calculated Calorie Plan
- Log daily meals and exercise
- Follow daily Calorie Budget
- Reach your goal
- The application is extensive and sophisticated. However, it lacks support for functionalities specifically in need by people with diabetes, such as measuring/logging sugar levels. Some of those features are only unlocked if the user buys the full version of the application. A subscription costs $9 USD monthly. Thus rendering this option attractive for our target user only if they are willing to pay.
- mySugr - Diabetes App & Blood Sugar Tracker
- link to Google Play
Approach
Milestones
Week 1
- Form a group
Week 2
- Choose a subject, make it concrete.
- Update the wiki page with all the basic information (problem statement, objectives, users, deliverables, milestones)
- Prepare a meeting with a person from the diabetes centre
- Make a separate plan of the application development process
Week 3
Week 4
Week 5
Week 6
Week 7
Week 8
Finish writing our wiki and give the presentation of our project
Deliverables
The literatures
Logbook
Week 1
Missed because of problems with group forming
Name | Student number | Activities (hours) | Total time spent |
---|---|---|---|
Kasper de Bruijn | 1333046 | ... | 0 |
Nick Jansen | 1260731 | ... | 0 |
Davide Fabbro | 1255401 | ... | 0 |
Kamil Musiał | 1283073 | ... | 0 |
Milan Koumans | 1256041 | ... | 0 |
Week 2
Name | Student number | Activities (hours) | Total time spent |
---|---|---|---|
Kasper de Bruijn | 1333046 | user research(2) | 2 |
Nick Jansen | 1260731 | Working on wiki(1) | 1 |
Davide Fabbro | 1255401 | ... | 0 |
Kamil Musiał | 1283073 | ... | 0 |
Milan Koumans | 1256041 | ... | 0 |
Week 3
Name | Student number | Activities (hours) | Total time spent |
---|---|---|---|
Kasper de Bruijn | 1333046 | ... | 0 |
Nick Jansen | 1260731 | ... | 0 |
Davide Fabbro | 1255401 | ... | 0 |
Kamil Musiał | 1283073 | ... | 0 |
Milan Koumans | 1256041 | ... | 0 |
Week 4
Name | Student number | Activities (hours) | Total time spent |
---|---|---|---|
Kasper de Bruijn | 1333046 | ... | 0 |
Nick Jansen | 1260731 | ... | 0 |
Davide Fabbro | 1255401 | ... | 0 |
Kamil Musiał | 1283073 | ... | 0 |
Milan Koumans | 1256041 | ... | 0 |
Week 5
Name | Student number | Activities (hours) | Total time spent |
---|---|---|---|
Kasper de Bruijn | 1333046 | ... | 0 |
Nick Jansen | 1260731 | ... | 0 |
Davide Fabbro | 1255401 | ... | 0 |
Kamil Musiał | 1283073 | ... | 0 |
Milan Koumans | 1256041 | ... | 0 |
Week 6
Name | Student number | Activities (hours) | Total time spent |
---|---|---|---|
Kasper de Bruijn | 1333046 | ... | 0 |
Nick Jansen | 1260731 | ... | 0 |
Davide Fabbro | 1255401 | ... | 0 |
Kamil Musiał | 1283073 | ... | 0 |
Milan Koumans | 1256041 | ... | 0 |
Week 7
Name | Student number | Activities (hours) | Total time spent |
---|---|---|---|
Kasper de Bruijn | 1333046 | ... | 0 |
Nick Jansen | 1260731 | ... | 0 |
Davide Fabbro | 1255401 | ... | 0 |
Kamil Musiał | 1283073 | ... | 0 |
Milan Koumans | 1256041 | ... | 0 |
Week 8
Name | Student number | Activities (hours) | Total time spent |
---|---|---|---|
Kasper de Bruijn | 1333046 | ... | 0 |
Nick Jansen | 1260731 | ... | 0 |
Davide Fabbro | 1255401 | ... | 0 |
Kamil Musiał | 1283073 | ... | 0 |
Milan Koumans | 1256041 | ... | 0 |
Week 9?
Name | Student number | Activities (hours) | Total time spent |
---|---|---|---|
Kasper de Bruijn | 1333046 | ... | 0 |
Nick Jansen | 1260731 | ... | 0 |
Davide Fabbro | 1255401 | ... | 0 |
Kamil Musiał | 1283073 | ... | 0 |
Milan Koumans | 1256041 | ... | 0 |