Need help building the ERD for this question if you could build one and explain how you did it then I will give you a thumbs up.

SITUATION: You own a confectionary store called Alberta Sweetness. You started with one small store, and due to your success, you are now opening three new locations. You've been managing a bit by "feel" in the original store, but you know you will not be able to keep as close of tabs on the four stores and will need some data to make decisions. You will need to maintain a list of all confectionary products carried in your stores. For each store, you will need to maintain the inventory of all products. For each product, you track a list price and cost price, but for now, you require the prices to be consistent across all stores. You dream of someday opening stores across Canada and know the price will vary across Canada, but for now, you want to focus on the minimum viable product and build the necessary scalability into the database. You do anticipate opening more stores throughout Alberta. You also have an old customer database where you track customers. Their purchases are tracked via invoices, including the quantity, list price, percentage discount, and price paid for each item. At the time of sale, the list price matches the list price for the product, but the product list price can change, whereas the invoice list price remains the same. Unfortunately, this database has been corrupted and you need to start from the beginning. Products are classified into different categories (such as gum, gummy, lollipop, licorice, etc.). These categories are further grouped into product lines (candy and chocolate for now, although you anticipate adding ice cream in the future). Each product may belong to only one category. Additionally, products are associated with specific tags to help identify sales opportunities. For instance, candy hearts may be associated with the tags "anniversary". "romantic" and "Valentine's". ADDITIONAL INFORMATION: While not all products are available at all stores, there is a large overlap in the products. In addition to the invoice percentage discount for each item, there may be an overall discount applied to a complete invoice. For each customer, an address and list of phone numbers are tracked. Previously you only allowed customers to enter a home and mobile number, but you found many customers are giving an alternate mobile number and you have decided the new database should support as many phone numbers as customers choose to give. At least one phone number is required for easy customer lookup. HASKAYNE Bachelor of Commerce 1 For small quick purchases, without a discount, there is a "guest" customer that is associated with the purchase. This customer is associated with the phone number "000-000-0000". Stores are identified by a short name (e.g. Kensington) and a full name (e.g. Calgary - Kensington). It is important to understand what products are sold in which stores. Although somewhat redundant based on the list price and percentage discount, the actual sell price and total invoice amount are both stored in the database for easy querying later. Products are sold either by weight, item, or package. You can't be sure that you won't allow additional methods (such as length or alternate weights) in the future, so you have decided to allow for new methods to be added. Assume there is no sales tax on any of the items. REQUIREMENTS: Create an Entity Relationship Diagram (ERD) for your Albertasweetness situation. Include the cardinality of relationships and make sure to define the primary (PK) keys(s), foreign (FK) key(s), composite keys (FK,FK), and which attributes are involved in each relationship. All bridging tables should make use of a composite key. Many-to-Many relationships may not be used, and your final product should be in 3ss normal form. ADDITIONAL REQUIREMENT AND NOTES: (1) This is a group assignment, that is, each group should complete the assignment on their own. Refer to the course outline for definitions of cheating and plagiarism, as these and other types of misconduct will not be tolerated. (2) Please submit your ERD in PDF format ONLY. Name your file according to your group number. If you are in group 3, lecture 3, please name your PDF file, "group03lecture03.pdf" a. Submit your PDF file to the correct Dropbox in D2L before the assignment 2 due date. Late submissions will receive a grade of zero as per the late policy within the course outline. b. Do not email your assignment to your instructor. Submissions via email will not be accepted. (3) This assignment is due on February 12, 2023, at 11:59PM