7-9 minutes<\/p>\n
Data modeling is a technique to document a software system using entity relationship diagrams (ER Diagram) which is a representation of the data structures in a table for a company\u2019s database. It is a very powerful expression of the company\u2019s business requirements. Data models are used for many purposes, from high-level conceptual models, logical to physical data models and typically represented by the entity-relationship diagram. It serves as a guide used by database analysts and software developers in the design and implementation of a system and the underlining database.<\/p>\n
An Entity Relationship Diagram (ERD) is a pictorial representation of the information that can be captured by a database. Such a \u201cpicture\u201d serves two purposes. It allows database professionals to describe an overall design concisely yet accurately. An ER Diagram can be easily transformed into the relational schema. There are three components in ERD: Entities, Attributes, and Relationships.<\/p>\n
The number of tables you need for your database \u2013 Entities is the basic objects of ERDs. These are the tables of your database, i.e. students, courses, books, campus, employees, payment, projects. A specific example of an entity is called an instance. Each instance becomes a record or a row in a table.<\/p>\n
Information such as property, facts you need to describe each table \u2013 Attributes are facts or descriptions of entities. They are also often nouns and become the columns of the table. For example, for entity students, the attributes can be first name, last name, email, address, and phone numbers.<\/p>\n
Relationships: How tables are linked together \u2013 Relationships are the associations between the entities. Verbs often describe relationships between entities. We will use Crow\u2019s Foot Symbols to represent the relationships. Three types of relationships are discussed in this lab. If you read or hear cardinality ratios, it also refers to types of relationships.<\/p>\n
Cardinality: it defines the possible number of occurrences in one entity which is associated with the number of occurrences in another. For example, ONE team has MANY players. When present in an ERD, the entity Team and Player are inter-connected with a one-to-many relationship.<\/p>\n","protected":false},"excerpt":{"rendered":"