Description
Necessary Views
The database needs to be able to store its operational data in such a way that the final app will be able to show
the following views (at minimum). You don’t need to implement the views, but the necessary data should be
modeled.
• A graph will be generated of how many calories a user consumed each day of the week.
• A similar graph will be generated that shows how many calories were burnt each day of the week
through workout.
• Show a pie graph of the percentage of the diet made up of each macronutrient during a given time
period (day, week, month).
• Track the consumption of a given micronutrient/chemical over a specified period of time. If there is a
recommended daily value, show a comparison of their consumption with the recommended amount.
• Allow the user to search through the food database to find common foods, in order to plan their diets.
These same foods will be used to track their eating.
• The user will search through a list of workouts to find the one closest to the one they’re going to do,
in order to track the activity.
• A line graph of user weight over time.
CSCI 466 Assignment 1 2 of 2
What to turn in?
You should turn in, via Blackboard, the following:
• A PDF file containing the diagram you’ve drawn. You can draw this in any graphics program. If you
must, you may draw it by hand and scan it, but it must be legible. Credit will not be given for portions
of the diagram that cannot be read.
• A text file or another PDF that explains all entities and relationships you’ve chosen to use, along with
a description of each of their attributes. List any assumptions that you will have made when deciding
cardinalities that are not specified explicitly by the requirements.
