Changes between Version 2 and Version 3 of Conceptual Design – ER Diagram and Data Requirements


Ignore:
Timestamp:
08/26/25 13:08:05 (7 days ago)
Author:
221531
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Conceptual Design – ER Diagram and Data Requirements

    v2 v3  
    11
    22== ER Diagram
    3 [[Image(ticket:1:Diagram.jpg​)]]
     3[[Image(ticket:2:ER_Diagram.jpg​)]]
    44
    55== Data Requirements
     
    100100* ingredient_id - primary key, numeric, required
    101101* name - text type, required
     102
     103=== Relations===
     104=== 1:1 ===
     105* Restaurant → Menu  \\
     106    **''has''** – a relation which indicates that a restaurant has one menu and a menu belongs to only one restaurant.
     107
     108* Address → Restaurant  \\
     109    **''is_located_at''** – a relation which indicates that a restaurant is located at one location, and a location can have only 1 restaurant.
     110=== 1:M ===
     111* User → Address  \\
     112    **''has''** – a relation which indicates that a user can have multiple addresses, and an address can belong to one user.
     113
     114* Customer → Order  \\
     115    **''has''** – a relation which indicates that a user can have multiple addresses, and an address can belong to one user.
     116=== M:N ===