Suppose you want to design and implement a database for a member-only supermarketinventory and check-out system (think Costco).The database should store basic information about the members: membership number(unique), customer name, gender, and phone number.The database should also have information on current store inventory. For each product,store the Universal Product Code (UPC), brand, product name, product description (e.g.12 16-oz bottles of Coke), category (e.g. Fruit, Vegetable, Meat, Beverage, etc.), priceper unit, and quantity in stock. For simplicity, assume that each product belongs to onlyone category.All transactions are recorded. A transaction (from one check-out) contains a (unique)transaction ID, the transaction date, products purchased in the transaction along with theirrespective quantities (quantities purchased, not quantities in stock), transaction total (in$), and the customer who made the transaction.Draw the ER diagram for the given database, identifying the following:(i) all the entity sets and their attributes;(ii) all the relationship sets;(iii) all the required key constraints and participation constraints;(iv) the primary key for each entity set (and weak entity set, if any).In some cases, you may have to make your own constraint assumptions. Clearly state,and justify your assumptions. Does your diagram capture all the given requirements? Ifnot, specify which requirement(s) is (are) not captured.