CS 411W LAB I - PRODUCT DESCRIPTION DOCUMENT FORMAT
1 Introduction
Societal problem
Unhealthy diets and its effects (include statistics)
99% of Americans are lacking necessary nutrients
Special diets are needed (include statistics)
Diets are out of balance
Percentage change needed in consumer diets to meet USDA recommendations
74% of people in the USA need to improve their diets
60% of Americans find it difficult to learn about nutrition
CS410 product introduction
Solution statement
Overview of real world product (RWP)
2 Nutricipe Product Description
Nutricipe goal
Provide meal planning tool
Organize proper diets
Accommodate individual needs and preferences
Educate customers
Nutricipe summary
2.1 Key Product Features and Capabilities
Product features and capabilities
- satisfy needs of the customers who require special diets
- satisfy needs of the customers who don’t require special diets
- recommend nutritional guidelines
- recommend a variety of foods
- provide food combining guidelines
- offer healthy recipes
- provide shopping list based on
o selected recipes
o food variety report
o selected diet
o time of the year
o store/location
- food tracking to meet long term goals
- Three application interfaces: web, mobile and client stand-alone applications.
2.2 Major Components (Hardware/Software)
Major components
Application interfaces
o Web application
o Mobile application
o Client stand-alone application
Database
o USDA Nutrient database
o Recipe database
o User profile
Algorithms
o Calorie needs algorithm
o Food variety algorithm
o Recipe nutritional content calculator
o Food combining guidelines algorithm
o Swapping algorithm
o Recipe selection algorithm
o Shopping list generator
o Food tracking algorithm
Web server
Third party recipe databanks
Google Ads
Internet
Include MFCD for RWP
2.3 Target Market/Customer Base
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 XXX Product Prototype Description
<Top level description of the CS 411W prototype as it relates to the end product (410) –
goal. Are capabilities reduced or eliminated? Simulated – modeled?>
3.1 Prototype Functional Goals and Objectives
<Specific functional objectives the prototype will demonstrate and why these are
significant Environment- show customer you can do it, easy to use, intuitive, etc. Input,
Output, and Processes. Table of comparison between RWP and Prototype either in here
or next section.>
Table 1. Database comparison between real product and prototype
Database
Real World Project
Prototype
Food item database
Recipe database
USDA nutrient database
USDA recipe database, a
variety of third party recipe
databases
User profile database
Comprehensive user profile
which will include
customer’s age, gender,
activity level, family
history, diseases, health
recommendations, food
preferences and available
ingredients
Food combining guidelines
which will specify what
foods should and should not
be eating together for
proper digestion
USDA nutrient database
A minimal number of
recipes from USDA recipe
database and third party
databases that is needed for
prototype implementation
Reduced user profile which
will not cover customer’s
family history and diseases
Combinations database
Not included
Table 2. Profile comparison between real product and prototype
Profile
Real World Project
Prototype
Age, gender and activity
level
Customer’s age, gender and
activity level will be
included in order to
estimate daily calorie needs
based on the USDA data
Customer will be able to
specify what diseases he
currently has and include
family history in order to
build a menu that will
improve or at least maintain
his current health conditions
Customer will be able to
include different health
recommendations to set up
his personal goals
Customer’s age, gender and
activity level will be
included in order to
estimate daily calorie needs
based on the USDA data
Not included
Family history and
diseases
Health
recommendations
Food preferences
Available ingredients
Customer will be able to
specify his food preferences
Customer will have an
option to include the
ingredients he has on hand
Customer will be able to
include different health
recommendations to set up
his personal goals. A
number of health
recommendations will be
reduced to a minimal
number necessary for
prototype implementation
Customer will be able to
specify his food preferences
Customer will have an
option to include the
ingredients he has on hand
Table 3. Algorithm comparison between real product and prototype
Algorithms
Real World Project
Prototype
Calorie needs algorithm
Estimate customer’s calorie
needs based on the
customer’s age, gender and
activity level
Generate a list of foods that
customer needs to consume
based on the customer’s
family history, diseases,
personal goals and
preferences
Purchased nutrient
Estimate customer’s calorie
needs based on the
customer’s age, gender and
activity level
Generate a list of foods that
customer needs to consume
based on the customer’s
goals and preferences
Food variety algorithm
Recipe nutritional
If nutritional content of
content calculator
calculator
Food combining
guidelines algorithm
Generate a list of foods and
specify what foods should
and should not be eating
together for proper
digestion
To better accommodate
customer’s goals, modify
existing recipes using the
customer’s profile
information. Build meals
based on the user profile
information and preferences
Swapping algorithm
Recipe selection
algorithm
Shopping list generator
Food tracking algorithm
individual recipes is not
available, it will be
calculated based on the list
of ingredients.
When individual recipes are
combined to build a meal,
the nutritional content of a
meal (combination of
recipes) is calculated based
on the nutritional content of
individual recipes
Not included
To build meals that will
accommodate customer’s
goals, individual recipes
will be combined based on
the user profile information
and preferences.
To create the best
combinations of recipes,
individual recipes will be
swapped in and out
Select recipes from the
Select recipes from the
recipe database based on the recipe database based on the
customer’s profile and
customer’s profile and
preferences
preferences
Generate a shopping list
Generate a shopping list
based on selected recipes,
based on selected recipes
food variety list, time of the and food variety list
year and store/location
Keep track of all the recipes Keep track of all the recipes
and foods the customer
that the customer selects.
consumes. Provide the
Provide the Percent Daily
report on how the customer Value for each recipe
is meeting his goals based
on the tracking history
Table 4. User access comparison between real product and prototype
Features
Non authenticated user
Authenticated user
Admin
Real World Project
Access welcome page,
Create an account,
Pay for individual account,
Gain access to Nutricipe as
a health club member
Access all pages,
Request different reports,
View profile information,
Modify profile information,
Renew subscription
Access individual profiles,
Create individual profiles,
Modify individual profiles,
Delete individual profiles,
Make changes to Nutricipe,
Generate different reports
Prototype
Access welcome page,
Create an account
Access all pages,
Request different reports,
View profile information,
Modify profile information,
Flag will be set indicating
that all current users have a
valid subscription
Access individual profiles,
Create individual profiles,
Modify individual profiles,
Delete individual profiles,
Make changes to Nutricipe,
Generate reports about
users goal achievements
Table 5. Additional features comparison between real product and prototype
Features
Real World Project
Prototype
Web application
Mobile application
Client stand-alone
application
Google Ads
Web server
Included
Included
Included
Included
Not included
Not included
Included
Web servers
Liability
Legal disclaimer, HIPAA
privacy
Authentication,
HTTP Authentication,
Not included
ODU CS department web
server
The user will need to accept
the terms and conditions
before proceeding with
creating a profile. Under no
circumstances Nutricipe and
its creators will be liable for
any perceived damage or
personal negligence arising
from the use of Nutricipe
?
Profile security,
Website security
access control mechanism
implementation for
authorization
3.2 Prototype Architecture (Hardware/Software)
<How will the prototype be structured to demonstrate key features of the 410 product.
Prototype MFCD provided and described.>
3.3 Prototype Features and Capabilities
<What does the prototype demonstrate – why is that significant in showing how the
problem is solved – or why you have demonstrated success. How does the prototype
address the 410 project risk mitigation?>
Prototype features: satisfy needs of the customers based on their profiles (age, gender,
activity level, health recommendations, available ingredients, customer preferences),
recommend nutritional guidelines (how many calories a customer should consume),
recommend a variety of foods (what foods a customer should prefer according to his
health recommendations), offer healthy recipes, and keep the recipe history in user
profile.
Prototype characteristics: food item database (includes nutritional information for every
ingredient (USDA database)), recipe database (USDA), user profile database, web
server.
3.4 Prototype Development Challenges
<Challenges expected while completing the objectives of the prototype – ie knowledge
missing, capability missing, supporting technology issues.>
???????
Glossary
References