Download CS411W Lab I Outline 1. Introduction

CS411W Lab I Outline
1.
Introduction
a. Societal problem (statistics)
i. Unhealthy diets and its effects (include statistics)
ii. 99% of Americans are lacking necessary nutrients
iii. Special diets are needed (include statistics)
iv. Diets are out of balance
v. Percentage change needed in consumer diets to meet USDA
recommendations
vi. 74% of people in the USA need to improve their diets
vii. 60% of Americans find it difficult to learn about nutrition
viii. Lack of knowledge (people do not know what foods can
benefit/harm their health condition (medical needs))
b. Why this is a problem?
i. Ingredient availability
ii. Insufficient time to find meals
iii. Different ways to prepare food
iv. Health conditions
c. Product Introduction
i. Solution statement
ii. Overview of real world product (RWP)
iii. Solution
1. Various home clients
2. Nutritional calculator
3. Profiles (goals, needs, individual information)
4. Recipes
5. Combinations
2.
Nutricipe Product Description
Nutricipe goal
Provide meal planning tool
Organize proper diets
Accommodate individual needs and preferences
Educate customers
Nutricipe summary
a. Key Product Features
i. Profile-based meal planning
1. Health conditions
2. Standard users
ii. Nutritional goals
iii. Food combining guidelines
iv. Food variety recommendations
v. Clients (Web, mobile, client stand-alone application)
vi. Shopping lists based on
1. customized meal
2. time of the year
3. store/location
vii. Food tracking to meet long term goals
viii. Statistical analysis (reports)
b. Major S/W & H/W Components
i. Include MFCD for RWP
ii. Application interfaces
1. Web application
2. Mobile application
3. Client stand-alone application
iii. Database
1. USDA Nutrient database (SR22)
2. Recipe database
3. User profile
4. Cache of available ingredients on hand
iv. Algorithms
1. Calorie needs algorithm
2. Food variety algorithm
3. Nutritional content calculator
4. Food combining guidelines algorithm
5. Recipe selection algorithm
6. Shopping list generator
7. Food tracking algorithm
v. Web server
vi. Third party recipe databanks
vii. Google Ads
viii. Internet
c. Target Market
i. Fitness centers or medical clinics
ii. Individuals (mass market)
Who is it for?
Individuals who are interested in improving their diets and
learning about healthy nutrition
What is it for?
To assist customers in organizing proper diets and
consumption of needed daily nutrients based on their
individual needs and preferences
Primary customers:
Fitness centers
Why?
There are almost 30,000 U.S. health clubs
There are over 45 million health clubs members
Total revenue is almost $20 billion
23% are new members who more likely need nutritional
guidelines
Health clubs members are interested in maintaining healthy
diets and meal plans that will contribute to their overall
health improvements
Health clubs will offer Nutricipe as a part of their
membership
Secondary customers:
Health conscious individuals
Able to purchase membership directly
3.
Nutricipe Product Prototype Description
a. Introduction
i. Scope Reduction (just state that its going to happen for our
prototype)
ii. Scale Reduction (the same)
iii. Goals of prototype (risk mitigation, domain expert for customers
(customer’s ease of use), proof of concept)
b. Prototype functional goals and objectives
i. Create individual profiles
1. Profile comparison table
ii. Database built
1. Reduced scale
2. Same scope
3. Nutrients (SR22)
4. Recipes
5. Profiles
6. Database comparison Table
iii. Web application
iv. Food recommendations
v. Meal builder
vi. Meal history
vii. Design algorithms
1. Calorie needs algorithm
2. Food variety algorithm
3. Nutritional content calculator
4. Recipe selection algorithm
5. Shopping list generator
6. Food tracking algorithm
7. Algorithm comparison table
c. Prototype architecture
i. Prototype MFCD
ii. Prototype MFCD overview
d. Prototype features and capabilities
i. Description of different users capabilities
1. Admin user
2. Administrative privileges diagram
3. Nutricipe user
4. User access comparison table
ii. Nutricipe user use case diagram
1. Use case overall description
a. User profile
b. Nutritional goals
c. Nutritional facts
2. Use case diagram for daily calorie report
3. Use case diagram for food variety report
4. Use case diagram for recipe search report
5. Use case diagram for combining individual components
into a meal
a. Description of how meal is built
b. Meal component diagram
iii. Assumptions table
iv. Additional features comparison table
v. Risk mitigation
a. Free DB hosting (school servers)
b. Lawsuit risk mitigated
c. Risk table for prototype
e. Prototype Development Challenges
1. Critical paths
a. GUI team
b. Algorithm team
c. DB team
2. Complex query-building
Glossary- under development
References- under development