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)
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...
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
-
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)
Expert Solution
This question has been solved!
Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.
Step by step
Solved in 3 steps with 1 images
Knowledge Booster
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.Recommended textbooks for you
Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781305971776
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781285867168
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Fundamentals of Information Systems
Computer Science
ISBN:
9781305082168
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781305971776
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781285867168
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Fundamentals of Information Systems
Computer Science
ISBN:
9781305082168
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning