SPORTS AND HEALTH (FOOD TRACKER)

CHAPTER 1

1.0 Project Background

1.1 Statement of the Problem
1.2 Project Scope
1.3 Stakeholders
1.4 Methodology (Waterfall Model)
1.5 Project Timeline
1.6 Discussion of Integration
1.7 Benefits
1.7.1 Admin
1.7.2 User(s)
1.7.3 Client
1.7.4 Developer/Team
2.0 Foreign and Local Studies
2.1 Foreign Studies (5)
2.2 Local Studies (5)
2.3 Matrix Table of Comparative Analysis
3.0 Architectural Diagrams
3.1 WBS
3.2 Business Process Architecture
3.3 Application Architecture
3.4 EIS Integration
4.0 Conclusion and Recommendation
1.0 Project Background

The food tracker was created to maintain the balance of the body and to
make the user aware to the food they eaten in their daily lives. Food
Tracker was created to attract the user to maintain the foods and to know
how many food calories was take. Food tracker exactly know how much we
eaten and monitoring the food calories in all seriousness can be quiet
effective. Dietary self-monitoring is consistently related to both short and
long term weight loss.

The purpose of the food tracker was to qualify the time we spent and the
daily frequently in self-monitoring necessary for weight loss success, in this
app the data has been collected the login per days, times we spent logging
and know if you successfully gain your weight loss. But after that we took
only less than 30 minutes per day to track our food and after 6 months the
minute we need to take is less than 16 minutes if you think that your weight
is improving.

Food tracking a prevalent approach in self-monitoring, helps people

gain awareness of their food practices and improve their diet. From
healthcare provider’s perspective, the data collected through food tracking
has clinical values for assessing patient’s nutrient intake and providing
treatment. For example, by examining patient’s food intake, providers can
identify triggers allergy, gastrointestinal problems

Understand how patient’s eating habit after their health. Traditional

techniques to collect food intake include questionnaires, interviews, and
paper-based diaries. Today, many people turn to digital food tracking tools
and a Personal Digital Assistant or PDA, mobile phone, computer for
convenience, while some still prefer tracking food on paper. As food is
central to people’s daily life, food data cover a broader context beyond
what people eat. Food data could include when they eat, where they eat,
who they eat with, how they feel about the food, and what they do before or
after eating. However, among the numerous food tracking applications that
are available in the internet is (fat secret, lost it, fit bit, and etc.) most of
them focus on collecting nutrition facts (calories, protein, carbohydrates,
sugar, fat, fiber) of every meal, providing limited flexibility for people to
choose what to track about their food.

1.1 Statement of the Problem

1.2 Project Scope

The project addresses an opportunity to provide a tool which

supports both patient and provider in the personalization of the
health care experience with the goal being optimization of overall
health and wellness. This system provides a dashboard enabling
access to a patient portal, appointment tracker. Rx tracker,
telehealth device, fitness tracker, and a dietary tracker. In addition,
notifications or alerts will be utilized to ensure patient health and
wellness. There are many health-related applications currently
available which provide the functionally of the individual elements of
this system. However, this application offers a complete set of
features designed to provide an efficient and effective means to
achieve optimal health and wellness in the most user-friendly format
possible.

1.3 Stakeholders
The traditional British approach to Christmas is well known, but
now January has come and the festive treats have run out. And for
many of us trying to get back to healthy habits, food-tracking apps
are playing a role.
 Apps like MyFitnessPal, Noom Coach and MyNetDiary aren’t
designed just for losing weight, even if thiat’s how a lot of people
use them.
They’re as much about learning what’s in our meals, snacks, and
drinks, and understanding how what we eat relates to the exercise
we get (or don’t get) every day.

1.4 Methodology (Waterfall Model)

1.5 Project Timeline
1.6 Discussion of Integration
1.7 Benefits
1.7.1 Admin
1.7.2 User(s)
1.7.3 Client
1.7.4 Developer/Team

2.0 Foreign and Local Studies

2.1 Foreign Studies (5)
2.2 Local Studies (5)
2.3 Matrix Table of Comparative Analysis
3.0 Architectural Diagrams
3.1 WBS
3.2 Business Process Architecture
3.3 Application Architecture
3.4 EIS Integration
4.0 Conclusion and Recommendation