Student and Course
The smallest useful E-R diagram: two entities and one many-to-many association carrying its own attribute.
Each example is a complete and correct conceptual model. Read the requirements, look at the diagram, then open a copy in the editor and change it.
10 examples
The smallest useful E-R diagram: two entities and one many-to-many association carrying its own attribute.
Titles versus physical copies: why a loan points at a copy and not at a book, and how a copy gets an external identifier built from its title.
An order line is an entity, not an attribute of a many-to-many: it has its own attributes, its own key and its own price frozen at the moment of the order.
An appointment is an entity where four facts meet — patient, doctor, department and time — and not a ternary association between the first three.
A reservation is an entity, not a many-to-many between guest and room: it has a code of its own, its own dates, and payments that refer to it.
An enrolment is the pair (student, course) - an external identifier - and yet it deserves its own node with its own date and grade.
A reaction is an entity, not a many-to-many between user and post: it has a type and a timestamp, and "one reaction per post per user" is a rule the diagram can only document.
An agency that rents the same car many times: the example that shows what an E-R schema records about time, and what it silently cannot forbid.
A school where a class, a subject and a teacher meet: the example that shows when a many-to-many pair has to be promoted to an entity.
A hierarchy and a staffing table in one schema: the example built on a recursive association and on an entity that exists only to resolve a many-to-many.
ERMap Academy explains every construct you see here, from requirements analysis to the SQL implementation, using the same diagrams you can open in the editor.
Start learning