Common ERD Mistakes

Data modelling is not only for data architects and software engineers. Anyone who works with data, including data analysts, business analysts, and business intelligence designers, needs to understand and be able to create at least simple data models. Even simplistic entity relationship diagrams (ERDs) can help support analysis and data discovery, identify crucial relationships and clarify important groups of data. Sometimes, a conceptual model is sufficient, and on other occasions, a starter logical model with a few attributes will work best to support business & data analysis activities. See this <a href="https://medium.com/business-architected/conceptual-data-modelling-start-with-business-use-cases-10b3f2670d47" rel="noopener">article </a>and <a href="https://youtu.be/ebKoANjnJDs" rel="noopener ugc nofollow" target="_blank">video </a>if you want to learn more. As I taught cohort after cohort of students in a business analytics program, I saw them struggle with the same questions, and make the same mistakes over and over when creating their first ERDs. This article is a summary of typical ERD mistakes and how to avoid them. Before we get there, let’s recap the main elements of the diagram. <h2>ERD Building Blocks</h2> Entity: A person, thing, event or concept about which the business keeps data. Examples: customer, product, order, supplier, employee, department, interaction. Attribute: a distinct characteristic of an entity for which data is maintained. Examples: name, address and cell number could be the attributes of a customer entity; product entity attributes could be product name, price, colour and size. Relationship: an association between entities that represents how the entities relate to each other. <a href="https://medium.com/business-architected/common-erd-mistakes-4535576a5b32">Read More</a>