1. a) Draw an E/R Diagram to model the “recipes” database system, identifying all entity sets, their

attributes, key attributes, and relationships.

A recipe can have one or more “tags” that can be used to identify “meal types” such

as breakfast, brunch, lunch, tea, supper, dinner, or snack. Users can “tag” their recipes anyway

they want. A recipe lists all of its ingredients, each identified by a three-letter code, also having a longer description. For example, “salted butter” might be cataloged in the system as “sbt” with a longer description “Salted Butter.” A recipe must define, for each of its ingredients, the quantity used in the recipe and their unit (cup, teaspoon, tablespoon, grams, pinch, etc.). Finally, a recipe defines a list of steps, each step uniquely identified (within a recipe) by a sequential number accompanied by a short description of the step.