Changes between Version 12 and Version 13 of Conceptual Design – ER Diagram and Data Requirements

Timestamp:

08/26/25 14:48:27 (2 months ago)

Author:

221531

Comment:

--

Conceptual Design – ER Diagram and Data Requirements

@@ -1 +1 @@
 
 == ER Diagram
-[[Image(ticket:2:ER_Diagram.jpg​)]]
+[[Image(ticket:3:FFFINAL.jpg​)]]
 
 == Data Requirements
@@ -173 +173 @@
     **''is_part_of''** – relation between Ingredient and Item Ingredient, where an ingredient can belong to multiple items.\\
 \\
+* Item ↔ Item Category ↔ Category\\
+    **Junction: ** Item Category solves M:N relation of Item and Category, by storing the composite key (category_id, item_id)\\
+
+    **''belongs''** – relation between Item and Item Category where an item can belong to multiple categories.\\
+
+    **''has''** – relation between Category and Item Category, where a category can have multiple items.\\
+\\
+* Restaurant ↔ Restaurant Category ↔ Category\\
+    **Junction: ** Restaurant Category solves M:N relation of Restaurant and Category, by storing the composite key (category_id, restaurant_id)\\
+
+    **''belongs''** – relation between Restaurant and Restaurant Category where a restaurant can belong to multiple categories.\\
+
+    **''has''** – relation between Category and Restaurant Category, where a category can have multiple restaurants.\\
+\\
 * Order ↔ Delivery Man ↔ Restaurant \\
     **Junction**: A ternary relationship exists because an Order links the Restaurant where it was placed and a Delivery Man who delivers it.\\