Consider a database application about the ingredients and nutrition of different food items available inCanada. In terms of design, following are some major requirements:• Application owner/administrator will add products to the database. For each product, name,barcode, manufacturer, ingredients, stores on which it is sold, nutritional details are some basicattributes.o A nutritional detail contains the item and its amount.o Ingredient information contains the item and its source. • Application owner/administrator may want to interact with manufacturers time to time to collectdata on their products. Name, address, phone number, email are some basic attributes that must bestored.• Application owner/administrator may want to interact with stores time to time to collect data onthe products they sell. Name, address, phone number, email, store locations are some basicattributes that must be stored.• Consumers can also request to add a product by providing its partial or full information.• No data is kept about consumers except email. Email will be kept only if the consumer requestsfor it.• Consumers are provided with the interface to perform all sorts of search on the products currentlystored in the database.• Products are categorized as common dietary preferences such as vegan, vegetarian, halaal, kosheretc.Design an ER/EER schema diagram for this application. Discuss any assumptions you make, and then justify your EER design choices.
Consider a
Canada. In terms of design, following are some major requirements:
• Application owner/administrator will add products to the database. For each product, name,
barcode, manufacturer, ingredients, stores on which it is sold, nutritional details are some basic
attributes.
o A nutritional detail contains the item and its amount.
o Ingredient information contains the item and its source.
• Application owner/administrator may want to interact with manufacturers time to time to collect
data on their products. Name, address, phone number, email are some basic attributes that must be
stored.
• Application owner/administrator may want to interact with stores time to time to collect data on
the products they sell. Name, address, phone number, email, store locations are some basic
attributes that must be stored.
• Consumers can also request to add a product by providing its partial or full information.
• No data is kept about consumers except email. Email will be kept only if the consumer requests
for it.
• Consumers are provided with the interface to perform all sorts of search on the products currently
stored in the database.
• Products are categorized as common dietary preferences such as vegan, vegetarian, halaal, kosher
etc.
Design an ER/EER schema diagram for this application. Discuss any assumptions you make, and then justify your EER design choices.
Step by step
Solved in 2 steps
