Draw an ER diagram according to the notations discussed in class to accurately represent the design specification below. You can use any tools to draw the ER diagram or simply draw it by hand. In your diagram, indicate all the entity sets, relationship sets, cardinality ratios, participations, attributes, and primary keys. Clearly specify any reasonable assumptions if they are not specified in the design specification. Submit your ER diagram and the assumptions you make in a PDF file. Design Specification: Suppose you want to design a database for a member-only supermarket inventory and check-out system. The database should store the following information: Each member has a unique membership number, customer name which consists of first name and last name, age, gender, and zip code. For each product, store the Universal Product Code (UPC), brand, product name, product description (e.g., 12 16-oz bottles of Coke), price per unit, and quantity in stock. A product's category is also recorded (e.g., Fruit, Vegetable, Meat, Beverage, etc.). All transactions are recorded. Each transaction (from one check-out) contains a unique transaction ID, transaction date, transaction total (in $), and payment method. Customers can make transactions. Some customers don't make any transactions and they can still exist. Assume that each transaction is made by only one customer. One transaction contains one or more products. One product can be contained in one or more transactions, or the product is not purchased at all. We also want to record each product's quantities purchased in each transaction (quantities purchased, not quantities in stock).

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Related questions

Question

Sketch ER Diagram

Transcribed Image Text:Draw an ER diagram according to the notations discussed in class to accurately represent the design specification below. You can use any tools to draw the ER diagram or simply draw it by hand. In your diagram, indicate all the entity sets, relationship sets, cardinality ratios, participations, attributes, and primary keys. Clearly specify any reasonable assumptions if they are not specified in the design specification. Submit your ER diagram and the assumptions you make in a PDF file. Design Specification: Suppose you want to design a database for a member-only supermarket inventory and check-out system. The database should store the following information: Each member has a unique membership number, customer name which consists of first name and last name, age, gender, and zip code. For each product, store the Universal Product Code (UPC), brand, product name, product description (e.g., 12 16-oz bottles of Coke), price per unit, and quantity in stock. A product's category is also recorded (e.g., Fruit, Vegetable, Meat, Beverage, etc.). All transactions are recorded. Each transaction (from one check-out) contains a unique transaction ID, transaction date, transaction total (in $), and payment method. Customers can make transactions. Some customers don't make any transactions and they can still exist. Assume that each transaction is made by only one customer. One transaction contains one or more products. One product can be contained in one or more transactions, or the product is not purchased at all. We also want to record each product's quantities purchased in each transaction (quantities purchased, not quantities in stock).

Expert Solution