This diagram shows a user database for an online multiplayer game. All components of ER diagram are included: Entities (Red Player and Player), Relationship (Friendship), and Attributes (Email Address, Name, Nickname, Password, etc).
Player ER diagram code in Gleek
Player
Player–email address:oval
Player–name:oval
Player–nickname:oval
Player–password:oval
Player–location:oval
Player–date of birth:oval
Player–signup date:oval
name–first name:oval
name–last name:oval
Red Player–friendship–Player
friendship:diamond
About ER diagrams
We often make an entity-relationship (ER) diagram, ERD, or entity-relationship model, in the early stages of designing a database. An ERD is perfect for quickly sketching out the elements needed in the system. The ERD explains how the elements interact. ER diagrams can be shared with colleagues. Their simplicity makes them ideal even for non-technical stakeholders.
Similar ER diagram examples
Hospital management system entity-relationship diagram
Inventory management system ER diagram (Chen notation)
Simple order process entity-relationship diagram