Member Avatar for Precious_7

hello everyone im taking database course this year and it's my first time to take it so i need help how to draw a ERD for following busniess case AND IF there many to many relation how i can establish a new relation !

Entity (Artist )
Attribute : death , DOB, the nationality.
Entity (museum )
Attribute: location , specialty .
Entity: (paintings)
Attribute: size of canvas, year of painted, tittle , style

Relation between Artist and paintings : Paint
Relation between paintings and museum : Display 

 An art researcher has asked you to design a database to record details of artists and the museum in which their paintings are displayed. 
For each painting, the researcher wants to know the size of the canvas, year painted, title, and style.  
The nationality, date of birth and death of each artist must be recorded.  
For each museum, record details of its location and specialty, if it has one.
Edited by Precious_7
  • 2 Contributors
  • 1 Reply
  • 387 Views
  • 3 Hours Discussion Span
  • Latest Post Latest Post by rproffitt

Dani AI

Generated

asked how to turn the posted art‑museum scenario into an ERD and how to handle many‑to‑many relations; is right that class conventions determine exact notation, but a general, robust approach works for most assignments.

First, follow a simple workflow: identify the main entity types (the ones already listed in the thread), pick a primary key for each (surrogate IDs like ArtistID, PaintingID, MuseumID are safe), list attributes on the appropriate entity, then determine relationship types and cardinalities. Mark optional attributes (allow NULL where data may not exist) and mandatory ones (NOT NULL) in the diagram so constraints are clear.

For a possible many‑to‑many case (for example, when a single painting can be shown at several museums over time and a museum shows many paintings), resolve it with an associative (junction) entity. The associative entity converts the M:N into two 1:N links and is the correct place to store relationship attributes such as loan dates or exhibition start/end. Implementation patterns and options for keys (composite FK primary key vs. surrogate key) are discussed in standard ER resources. (Open Textbook — ER model chapter, RelationalDBDesign — relationship types, Associative entity overview).

Practical drawing tips: show cardinality (crow’s‑foot or min/max), indicate optionality explicitly, put any relationship-specific attributes on the associative box, and enforce referential integrity with foreign keys when moving to a relational schema. Keep the classroom notation and grading rubric in mind, but use the associative/junction pattern whenever a true many‑to‑many relationship appears.

Member Avatar for rproffitt

That's your work to do but here's why I can't do it for you (besides the problem you won't be doing your homework.)

During your class they taught how they want the ERD done. How I would do this could be incorrect. Go back over your course material to find out how this is done for this class.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.