Modeling Relationships in a Supermarket: ER Model with Cardinalities

  • Context: MHB 
  • Thread starter Thread starter mathmari
  • Start date Start date
  • Tags Tags
    Model
Click For Summary
SUMMARY

The discussion focuses on modeling relationships in a supermarket using an Entity-Relationship (ER) model with cardinalities. Key entities identified include Employee (Angestellter), Department (Abteilung), Item (Artikel), and Supplier (Lieferant). Each employee belongs to one department, while each item can be offered in multiple departments and is supplied by a single supplier. The discussion emphasizes the importance of defining key attributes such as employee numbers, names, addresses, and pricing details for effective ER modeling.

PREREQUISITES
  • Understanding of Entity-Relationship (ER) modeling
  • Familiarity with cardinalities in database design
  • Knowledge of key attributes in data modeling
  • Basic concepts of supermarket operations and inventory management
NEXT STEPS
  • Learn how to create an ER diagram using tools like Lucidchart or draw.io
  • Study cardinality types and their implications in database design
  • Explore normalization techniques to optimize the ER model
  • Investigate the use of UML diagrams for complex data relationships
USEFUL FOR

This discussion is beneficial for database designers, data modelers, and anyone involved in developing inventory management systems for supermarkets.

mathmari
Gold Member
MHB
Messages
4,984
Reaction score
7
Hey! 😊

In a supermarket, there are the following relationships: For each employee (Angestellter), there are employee numbers (AngNr), last name (Name), first name (Vorname), address (Adresse) and department (Abteilung) known. Each employee works in exactly one department. Of each department knows their name (Name), their employees (Angestellte), the responsible manager (Manager) and the items (Artikel) offered.
An item can be offered in several departments. Description (Bezeichnung), supplier (Lieferant), sales price (Verkaufspreis) and an article number (Artikelnummer) assigned by the supplier as well as by the supermarket. From each supplier the name (Name), address (Adresse) and items (Artikel) delivered to the supermarket with delivery prices are known. An article is supplied by exactly one supplier, but can be supplied at different prices.

Represent these relationships in an ER model with cardinalities and define suitable ones key attributes.Does this mean that we have to make a graph with how these attributes are related ? :unsure:

Do we have the attributes employee, department, article, supplier ? :unsure:
 
Last edited by a moderator:
Physics news on Phys.org
So far I have done the following :
1643740958824.png


Is that correct so far? :unsure:
 
Last edited by a moderator:

Similar threads

MHB Understanding Primary and Foreign Keys in Database Relations
  • · Replies 7 ·
Replies
7
Views
1K
How Should Manage Be Represented in an ER Diagram for a Video Rental Company?
  • · Replies 1 ·
Replies
1
Views
8K
Please Review Database Tables for Advanced Database Class
  • · Replies 2 ·
Replies
2
Views
4K
Please Revise My Statement of Purpose
  • · Replies 5 ·
Replies
5
Views
11K
  • Sticky
Physics Forums Global Guidelines
  • · Replies 2 ·
Replies
2
Views
503K