Sweet Deals is a start-up company that offers deals for gift certificates (e.g., gift certificate to Chipotle, Starbucks, Olive Garden) and merchandise (e.g., area rugs, headphones) via an app. The gift certificates and merchandise are offered at a price lower than retail value, but the prices are only available for a short time and only a specified quantity can be sold.

Sweet Deals would like you to develop a database to house the data generated from app usage and purchases so that it can be analyzed to identify what gift certificates and merchandise perform better than others and seasonal sales patterns by category and geographic region. Consider each of the requirements and business rules documented for you below and create the following:

1.A list of data names and definitions that can be extracted from the case and business rules 2.A preliminary ER model that includes entities, relationships, and attributes1 3.A list of any assumptions you made when designing the ER model that were explicitly specified in the case

*************PLEASE DRAW THE ER MODEL ( IN PAPER / USING VISIO) AND ATTACH IT HERE IN YOUR SOLUTION FOR UPVOTE. CLEARLY EXPLAN RELATIONSHIPS BETWEEN ENTITIES IN THE DIAGRAM ******************

When customers create accounts on the app, their first name, last name, email address, gender, username, and password are collected. Customers can also refer new customers to the site, so the current customer that referred the new customer should be stored. A referral is not required to create an account. Referring others is also not required, but a customer can refer as many others as they would like. Customers can provide multiple shipping addresses to facilitate sending gifts to family and friends. A label for each address should also be stored. For each order, the shipping address selected by the customer should be recorded. Each order can only be shipped to one address. Customers activity on the app should be stored and fall into one of four categories logins, searches, menu clicks, and deal views. For each activity, the timestamp associated with the activity should be stored along with what account was used. Logins are when an account log in is attempted. Both searches and menu clicks represent users navigating through the app, either by typing in a search string or clicking links in the menu. For searches, the text string entered into the search box should be stored, and for menu clicks, the name of the menu button clicked is stored. Deal views are when the description and details of a deal are viewed, and the unique ID number of this deal should be store for this activity type. No additional information is stored for logins.

Customers can purchase as many deals as they would like within each order as long as the deal is still available. Each customer can also purchase each deal as many times as they would like. Each deal has a start date time and duration, as some deals are for just a few hours and some are for 24 hours. Each deal also has a name, sale price, and original retail value. For example, an Olive Garden $40 gift certificate might have a sale price of $20 but the original retail value was$40. Each deal can be a gift certificate, merchandise, or both. For deals containing gift certificates, the address of the store or restaurant at which the certificate can be used should be stored. For deals containing merchandise, the brand of the merchandise and categories (e.g.apparel, electronics) should be stored. Each merchandise must belong to at least one category, and the categories are set by Sweet Deals. Merchandise can also belong to multiple categories. Within the app, customers can also specify which categories of deals they are most interested in, and this is stored along with their account information. Each customer can specify as many categories of interest as they wish.