Browse our guides or talk to our team.
ERD stands for entity relationship diagram, which is a type of diagram that can help you create a clear visualization of your database design.
To learn more about the basics of entity relationship diagrams, check out our blog, What is an ER Diagram? This ER diagram tutorial will cover how to make an ERD anywhere, with specific tips for using Gliffy's ERD tool for Confluence or online. Read on to learn how to make an ER diagram or jump ahead to one of the following sections:
ERDs, also called ER diagrams or ER models, are used to describe data and how pieces of data interact with one another. For this reason, ERDs are extremely important in database design and projects that require a clear structure of all data — think of it as the standardized way to draw a database diagram. By applying this standard, your team can easily understand the structure of a database or the information you collect within your system.
Drawing entity relationship diagrams is easier if you choose to use online diagramming software. Check out Gliffy’s ER diagram tool for Confluence or start a free trial of Gliffy Online.
There are a few basic steps to take to draw an ER diagram anywhere: in Gliffy, with Powerpoint, a whiteboard, or even on the back of a napkin. Here’s the basic order to follow.
Start by identifying the “what”s in your system or architecture. Entities are represented with a rectangle, and you’ll want to give them plenty of room so that you can add to your diagram in the next steps.
Next, consider the attributes that you need to describe each entity. These are drawn and labeled inside ovals. Connect these to the relevant entity and position your attributes to the outside of your diagram, which leaves room for relationships.
Now, think through the relationships or verbs taking place within your system. The easiest way to do this is to look at each entity and try to connect it to another by saying, “What does the ___ do with the ___.” The customer purchases the phone. The cell service maintains the phone. The cell service creates a bill. The customer pays the bill.
The final step for this simple ER diagram is to define the amount of data that will come from each entity. Cardinality is a simple notation that quickly tells your ERD reader whether there are zero, one, many, or some combination of those factors between each entity. Your customer can purchase one or many phones. The cell service maintains many phones. The customer pays one bill.
This is just a high-level ER diagram, but it provides enough detail that you should now have a teammate or partner check your work — if you're working in Confluence, you can even invite them to a real-time collaboration session. One of the best ways to check your work is to simply have them try to read your diagram out loud. If they end up telling a different story than you intended, you need to do some tweaking.
Another good step to take is to clean up or polish your diagram — if you were drawing by hand, you might have some stray eraser marks. Take a moment to finalize your diagram by aligning shapes, adding color, or redrawing lines to more clearly connect your entities, attributes, and relationships. All these steps are easy if you’re using an online diagramming tool like Gliffy!
There are a few benefits to using software to complete the above steps and draw an entity relationship diagram. With Gliffy, you can create ERDs and:
You can give these features a try with a free trial of Gliffy for Confluence, but if your team doesn't use Confluence, you can create your ERD (and other types of application architecture diagrams!) in our online diagramming tool, Gliffy Online.
CREATE YOUR CONFLUENCE ERD TRY GLIFFY ONLINE