An ERD is an entity relation diagram, it’s a data model. When first reading about it all, I was a bit confused because of the multiple ways to draw them, however, I soon began to understand. I think the first essential element of understand an ERD is to define what an entity is. An entity is an object or a concept. In our case, an entity is an object where information or data can be stored. What an ERD does is define the entities we use to store data along with its qualities and relationships. An ERD helps us visualize databases and their structures. We can employ ERDs when designing a database, debugging a database, patching or creating a database, etc.. An ERD, similar to a swim-lane, has some primary symbols. A rectangle defines an entity. A diamond defines an action. And an oval defines an attribute, attributes can include a name, an ID, an address…entities can have many attributes that help to define and identify them. ERD’s can also be illustrated through tables, the entity name goes on the top, and the attributes are underneath in the table, and arrows connect them to other entities, describing their relationship. I definitely prefer the ERD tables because I feel that they are much easier to follow and comprehend, plus fitting writing is much easier to do in a table than an oval.
Reader Interactions
Comments
Leave a Reply
You must be logged in to post a comment.
I agree with you in how you believe ERD tables are the easiest form to follow. I dislike the diagrams because the symbols can be confusing.
An Entity Relationship Diagram (ERD) is a data model that illustrates the relationships between entities within an IT system. Such entities could include people, objects, places, concepts or events, and along with each entity comes its own respective attributes including, but not limited to, name/ID, address, phone, etc. ERDs allow for a simple means of visualizing specifically how each entity within a system interacts with other entities. We can use ERDs to help us create, improve, or fix databases.