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)

Principles of Information Systems (MindTap Course List)
13th Edition
ISBN:9781305971776
Author:Ralph Stair, George Reynolds
Publisher:Ralph Stair, George Reynolds
Chapter12: System Acquisition And Development
Section: Chapter Questions
Problem 3PSE: A new sales ordering system needs a relational database that contains a customer table, a product...
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

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
Principles of Information Systems (MindTap Course…
Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781305971776
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Principles of Information Systems (MindTap Course…
Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781285867168
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Fundamentals of Information Systems
Fundamentals of Information Systems
Computer Science
ISBN:
9781305082168
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Oracle 12c: SQL
Oracle 12c: SQL
Computer Science
ISBN:
9781305251038
Author:
Joan Casteel
Publisher:
Cengage Learning