Entity Relationship Diagram (ERD) Tutorial and EXAMPLE

An Entity Relationship Diagram (ERD or ER Diagram) is commonly used in data modeling to represent the main data entities in an organization or system. In this video, I’ll provide a comprehensive tutorial on entity diagrams for business analysts including different notations such as Chen, UML, and Crow’s Foot. We'll also look at the main components of the diagram including entities, attributes, relationships, and cardinality. The ER Diagram example will also include primary and foreign keys. I’ll also cover the difference between conceptual, logical, and physical entity relationship diagrams followed by an example of this data model.
In general, business analysts use er diagrams to help make understanding the relationship between data items easier for business stakeholders (conceptual and logical), while also illustrating the structure of these relationships (physical ERD) in a way for the technical team to build upon.
Entity Relationship Diagrams are used to:
• Establish and communicate a consistent vocabulary
• Illustrate business rules related to a domain
• Define data requirements for an information system
• Provide details about stakeholders, objects, or concepts
• Plan and set up databases that store relational data
SUBSCRIBE for more high-value business analysis content: / @thebadoc
For IIBA CERTIFICATION TRAINING check out our courses here: the-business-analysis-doctor-...
For Business Analysis TEMPLATES, check out our BA Templates and Elicitation Questions Package here: the-business-analysis-doctor-...
For more business analysis resources, check out our website here: thebadoc.com/
Not Entity Relationship Diagram (ERD) Tutorial - Part 1, but I'm Creating Entity Relationship Diagrams, But this is an Entity Relationship Diagram (ERD) Tutorial, but with Entity-Relationship Diagrams, but with ER Diagram, but I'm showing How to draw ER diagram, but with Entity-Relationship Model, but with DBMS - Entity Relationship Diagram, but an Entity Relationship Diagram (ERD) Tutorial - Part 2, but this Database Lesson, but these are the Concept of Relationships in ER Diagram, but I'm showing How to draw ER diagram, and giving an entity relationship diagram tutorial.
#erdiagram #entityrelationshipdiagram #erd #businessanalysis #datamodeling #datamodel # #businessanalyst #dataanalysis #dataanalyst #babok #babokguide

[@thebadoc]

Be sure to SUBSCRIBE for regular BA training and tips!

[@RJFlash]

This tutorial was more helpful, straightforward, and informative than the first 5 chapters of my textbook that was assigned for Data Management course. Thank you for this incredibly helpful material.

[@user-bk6ck6ju7h]

I need this kind of tutorial in the database, easy to understand and very comprehensive I'm leaving 10/10, thank you

[@masonsingleton3037]

You explained this so well! So many people have tried to train me on this and some of the concepts never made sense until now. Thank you so much.

[@e.denise1450]

This was great! Thanks for sharing the tip about the noun technique. I've always found identifying which entities to include to be a challenge.

[@emanuelarturorivasescobar1085]

Man this is a great explanation, thanks a lot for your content

[@emanuelarturorivasescobar1085]

Man that great explanation, thanks a lot for your content

[@erikvillar9270]

This is a great explanation!! thank you!

[@user-cn3cw9lq6y]

This video is amazing!

[@higiniofuentes2551]

Thank you for this very useful video!

[@BobDust]

Well done and easy to understand.

[@baruchben-david4196]

thank you for this clear explanation.

[@smtxtv]

Good presentation and effective explanation. Thanks ! Asst. due.

[@shanabenjamin8945]

Thank you :) ❤

[@விஜய்குமார்]

great bro

[@cindytutu4632]

Good work

[@chanbella6941]

Best tutorial

[@XPORIA]

Nice overview of the bad old ERD - two things. Firstly, the ERD approach scares people - so many weird words - entity, cardinality, domains, nouns, primary key, foreign key. It's simply a way of describing a system so that a coder can use it to construct a Database. Why are we still doing this? BAs DO develop an understanding of the "System Model" (Types of objects / entities and their associations to other objects in the System) e.g. "Book" -> [author] -> "Contact" - a very simple vision of a system. That's all that is needed! Software can take it from there. Secondly, by dropping the ERD and using a system model approach, it is a much easier and better way to comprehend the System at the correct level of granularity for the process being developed. Of course, as you state, the ERD is really necessary for the coder. But imagine that once you have built your system model you can build your complete system WITHOUT using a software coder. That's what NoCode is all about. Let's move away from software design methods for the last millennium!

[@Itstollol]

Thanks for the great explanation! I have a question - why didn't you add relatinoship between BOOK and CHECKOUT entities?

[@tg8799]

In the last slide, the Book to Renewal relationship - I understand the premise but there is no Book ID in the Renewal table or a Renewal ID in the Book table... is this correct? How can a relationship be established here if there is no connection in relation?