a) Draw an Entity-Relationship Diagram (ERD) for the above scenario using the Crow’s Foot notation (exclude all attributes). Resolve many-to-many relationships, if any. Make common business rule...


a) Draw an Entity-Relationship Diagram (ERD) for the above scenario using the Crow’s Foot notation (exclude all attributes). Resolve many-to-many relationships, if any. Make common business rule assumption if necessary.


b) For each of the entities in the ERD drawn in Question 2 a), list all relevant attributes using Database Design Language (DBDL) format. In your listing, show all the primary keys, composite keys and foreign keys (if any) clearly. Underline all the primary keys or composite keys and identify the foreign
key with an *.


Question 2<br>Consider the following scenario of a food and beverage (F&B) delivery partner.<br>HungryMe is a young entrepreneurial company to offer F&B delivery services that operates between food<br>stalls and consumers. The company receives customers' order via mobile app and redirects the orders to<br>their partner food stalls for preparation. When the foods are ready, the company deliverymen will delivery<br>to respective customers within an estimated timeframe.<br>For every order placement, user must provide the shipment address and particulars of the order. Each order<br>transaction can include one or more menu items. The ORDER entity consists of attributes<br>OrderCode(Identifier), OrderDateTime, ShipmentAddress, EstimaTime, CustPhoneNo and TotalCharge,<br>while MENU_ITEM entity consists of attributes ItemCode(identifier), Desc, UnitPrice , Category and<br>Ratings. Every menu item may be ordered in various orders or haven't been ordered in any order yet.<br>Remark and quantity of each item ordered should be traceable.<br>One menu item comes from a specific food stall. Thus, two menu items with identical description would<br>not have the same identifier as they are provided by two distinct food stalls. Each food stall may cater one<br>or many menu items. The FOOD_STALL entity consists of attributes MerchantCode, MerchantName,<br>MerchantLocation and MerchantPhoneNo.<br>Once an order placement is done, the system will automatically assign a deliveryman in-charge to the order.<br>The attributes for DELIVERY_MAN are EmpCode(Identifier), EmpName, EmpPhoneNo and EmpScore.<br>

Extracted text: Question 2 Consider the following scenario of a food and beverage (F&B) delivery partner. HungryMe is a young entrepreneurial company to offer F&B delivery services that operates between food stalls and consumers. The company receives customers' order via mobile app and redirects the orders to their partner food stalls for preparation. When the foods are ready, the company deliverymen will delivery to respective customers within an estimated timeframe. For every order placement, user must provide the shipment address and particulars of the order. Each order transaction can include one or more menu items. The ORDER entity consists of attributes OrderCode(Identifier), OrderDateTime, ShipmentAddress, EstimaTime, CustPhoneNo and TotalCharge, while MENU_ITEM entity consists of attributes ItemCode(identifier), Desc, UnitPrice , Category and Ratings. Every menu item may be ordered in various orders or haven't been ordered in any order yet. Remark and quantity of each item ordered should be traceable. One menu item comes from a specific food stall. Thus, two menu items with identical description would not have the same identifier as they are provided by two distinct food stalls. Each food stall may cater one or many menu items. The FOOD_STALL entity consists of attributes MerchantCode, MerchantName, MerchantLocation and MerchantPhoneNo. Once an order placement is done, the system will automatically assign a deliveryman in-charge to the order. The attributes for DELIVERY_MAN are EmpCode(Identifier), EmpName, EmpPhoneNo and EmpScore.
Jun 03, 2022
SOLUTION.PDF

Get Answer To This Question

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here