Homework Help is Here – Start Your Trial Now!
Engineering
Computer Science
Draw an Entity Relationship Diagram for the proposed system based on the requirements showing the Entities, Attributes and Cardinality between entities.   Entities and Attributes Flavor Attributes: FlavorID, Name, Description Inventory Attributes: InventoryID, FlavorID, Quantity, ReorderThreshold Sale Attributes: SaleID, CustomerID, FlavorID, Date, Quantity, TotalAmount Customer Attributes: CustomerID, Name, Email, Phone Feedback Attributes: FeedbackID, CustomerID, Comment, Date, Rating Supplier Attributes: SupplierID, Name, ContactInfo Order Attributes: OrderID, SupplierID, FlavorID, OrderDate, Quantity, DeliveryDate Forecast Attributes: ForecastID, FlavorID, PredictedDemand, Date Relationships and Cardinality Flavor - Inventory One Flavor can have multiple inventory records. (1:N) Flavor - Sale One Flavor can be part of multiple sales. (1:N) Customer - Sale One Customer can have multiple sales. (1:N) Customer - Feedback One Customer can provide multiple feedbacks. (1:N) Flavor - Order One Flavor can be included in multiple orders. (1:N) Supplier - Order One Supplier can be associated with multiple orders. (1:N) Flavor - Forecast Each Flavor has multiple demand forecasts. (1:N)

Draw an Entity Relationship Diagram for the proposed system based on the requirements showing the Entities, Attributes and Cardinality between entities.   Entities and Attributes Flavor Attributes: FlavorID, Name, Description Inventory Attributes: InventoryID, FlavorID, Quantity, ReorderThreshold Sale Attributes: SaleID, CustomerID, FlavorID, Date, Quantity, TotalAmount Customer Attributes: CustomerID, Name, Email, Phone Feedback Attributes: FeedbackID, CustomerID, Comment, Date, Rating Supplier Attributes: SupplierID, Name, ContactInfo Order Attributes: OrderID, SupplierID, FlavorID, OrderDate, Quantity, DeliveryDate Forecast Attributes: ForecastID, FlavorID, PredictedDemand, Date Relationships and Cardinality Flavor - Inventory One Flavor can have multiple inventory records. (1:N) Flavor - Sale One Flavor can be part of multiple sales. (1:N) Customer - Sale One Customer can have multiple sales. (1:N) Customer - Feedback One Customer can provide multiple feedbacks. (1:N) Flavor - Order One Flavor can be included in multiple orders. (1:N) Supplier - Order One Supplier can be associated with multiple orders. (1:N) Flavor - Forecast Each Flavor has multiple demand forecasts. (1:N)

Database System Concepts
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
icon
Related questions
Question

Draw an Entity Relationship Diagram for the proposed system based on the
requirements showing the Entities, Attributes and Cardinality between entities.

 

Entities and Attributes

  1. Flavor

    • Attributes: FlavorID, Name, Description

  2. Inventory

    • Attributes: InventoryID, FlavorID, Quantity, ReorderThreshold

  3. Sale

    • Attributes: SaleID, CustomerID, FlavorID, Date, Quantity, TotalAmount

  4. Customer

    • Attributes: CustomerID, Name, Email, Phone

  5. Feedback

    • Attributes: FeedbackID, CustomerID, Comment, Date, Rating

  6. Supplier

    • Attributes: SupplierID, Name, ContactInfo

  7. Order

    • Attributes: OrderID, SupplierID, FlavorID, OrderDate, Quantity, DeliveryDate

  8. Forecast

    • Attributes: ForecastID, FlavorID, PredictedDemand, Date

Relationships and Cardinality

  1. Flavor - Inventory

    • One Flavor can have multiple inventory records. (1:N)

  2. Flavor - Sale

    • One Flavor can be part of multiple sales. (1:N)

  3. Customer - Sale

    • One Customer can have multiple sales. (1:N)

  4. Customer - Feedback

    • One Customer can provide multiple feedbacks. (1:N)

  5. Flavor - Order

    • One Flavor can be included in multiple orders. (1:N)

  6. Supplier - Order

    • One Supplier can be associated with multiple orders. (1:N)

  7. Flavor - Forecast

    • Each Flavor has multiple demand forecasts. (1:N)
Expert Solution
steps

Step by step

Solved in 3 steps with 1 images

SEE SOLUTIONCheck out a sample Q&A here
Blurred answer
Knowledge Booster
Enhanced ER Model
Learn more about
Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.
Similar questions
  • SEE MORE QUESTIONS
Recommended textbooks for you
Database System Concepts
Database System Concepts
Computer Science
ISBN:
9780078022159
Author:
Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:
McGraw-Hill Education
Starting Out with Python (4th Edition)
Starting Out with Python (4th Edition)
Computer Science
ISBN:
9780134444321
Author:
Tony Gaddis
Publisher:
PEARSON
Digital Fundamentals (11th Edition)
Digital Fundamentals (11th Edition)
Computer Science
ISBN:
9780132737968
Author:
Thomas L. Floyd
Publisher:
PEARSON
C How to Program (8th Edition)
C How to Program (8th Edition)
Computer Science
ISBN:
9780133976892
Author:
Paul J. Deitel, Harvey Deitel
Publisher:
PEARSON
Database Systems: Design, Implementation, & Manag…
Database Systems: Design, Implementation, & Manag…
Computer Science
ISBN:
9781337627900
Author:
Carlos Coronel, Steven Morris
Publisher:
Cengage Learning
Programmable Logic Controllers
Programmable Logic Controllers
Computer Science
ISBN:
9780073373843
Author:
Frank D. Petruzella
Publisher:
McGraw-Hill Education
SEE MORE TEXTBOOKS