Thanks for the nice comments, I really enjoyed writing it.
Regarding requirements gathering, what I was trying to get across was that its part of the process we go through with stakeholders.
When building a new model there's lots of back and forth and clarification of what's required now, later and what can be delivered after go live. Ideally all the requirements are locked down early but in reality, this doesn't always happen.
At the first step, with the Conceptual Data Model, we can go back to the stakeholders to double check the requirements and do our best to avoid scope creep. Hopefully ;)
As far as debugging goes the ERD gives us a point of reference for how things 'should' work. If multiple team members are releasing changes to the model we can visually see how it fits together and where the dependencies are.
It's also helpful when doing any kind of database migration.
I really like stringing my posts together in series and use the instructions here to do so:
I'm also a fan of the Table of Contents at the top of my posts:
Thanks for replying Helen, your explanations are really clear!😄
Also, thank you for pointing me to these articles.
You're welcome, looking forward to reading more of your posts :D
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.