Entity Relationship Diagram (ERD) Tutorial and EXAMPLE

calm down it looks like you're about to pop out of the screen when the video begins

Should you link book with check out? Since youre pulling the book id as a fk? Doesnt it need a direct link?

This is a great explanation!! thank you!

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

Man that great explanation, thanks a lot for your content

What the hell is sensco?

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?

My system basically allows lecturers to upload notes and allows students to view, as well submit quizzes. Lecturers can then view the submission and upload assessment for students to view. My entities are quite unclear to me. I've got Student and Admin as my entities only, would there be any other?

great bro

Well done and easy to understand.

Good work

could you please make some videos about writing user stories in agile with some examples

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!

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.

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.