- 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.