PRE2019 3 Group18: Difference between revisions

From Control Systems Technology Group
Jump to navigation Jump to search
Line 102: Line 102:


#; Calorie Counter - MyNetDiary, Food Diary Tracker
#; Calorie Counter - MyNetDiary, Food Diary Tracker
[[File:MyNetDiaryexamplescreen.png|frameless|alt=alternative text|right|upright=0.78|Example screen from MyNetDiary]]
: [https://play.google.com/store/apps/details?id=com.fourtechnologies.mynetdiary.ad link to Google Play]
: [https://play.google.com/store/apps/details?id=com.fourtechnologies.mynetdiary.ad 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.
: 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.

Revision as of 16:14, 16 February 2020

Group Members

Name ID Major Email
Kasper de Bruijn
1333046
Applied Physics
k.j.d.bruijn@student.tue.nl
Nick Jansen
1260731
Computer Science and Engineering
n.j.jansen@student.tue.nl
Davide Fabbro
1255401
Electrical Engineering
d.h.fabbro@student.tue.nl
Kamil Musiał
1283073
Computer Science and Engineering
k.musial@student.tue.nl
Milan Koumans
1256041
Electrical Engineering
m.koumans@student.tue.nl

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
  • KdB: Making questionaire diabetics (to discuss/improve during the meeting), plan visit to diabetes centre
  • N: find and gather info about similar projects on the wiki, gather ideas about app functionality
  • KM: Create wiki template, research state-of-the-art diabetes technologies
  • D: Research diabetes and needs of diabetics (IO for App)
  • M: gather ideas about app functionality
3
  • KdB: Write down the users part of the wiki, prepare for the meeting with diabetes center
  • N: List on the wiki all gathered requirements, functionalities, ideas what the app does; Help with app development plan
  • KM: Create app development plan, start setting up the project and its repository
  • D: write down the milestones and deliverables section on the wiki
  • M: write down the problem statement on the wiki
4
5
6
7
8
9

Subject

Problem statement

- Helping diabetes patients with having a good diet

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

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.


  1. Calorie Counter - MyNetDiary, Food Diary Tracker
alternative text
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.

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

Minutes

Minutes

References