It is possible that more than one relationship can exist between entities. Example: different relationships exist between person and class (attend, teach, write). Well, this article is all about constructing ER Diagram components that represent entities, relationships and attributes.
This article covers the following objectives:
- Construct ER diagram components that represent entities, attributes and database relationships according to diagramming conventions
Purpose of the ER Diagram
- People speak different languages throughout the world, but some signs are understood globally.
- Guess the meaning of these signs.
- How well did you do?
- Did you guess the meaning of most signs?
Shared Convention – ER Diagram
- It is efficient to communicate information in a way that can be easily understood by many people.
- ER diagramming is like that — you may say or write things differently because of the way you speak, your accent, and so on, but everyone draws ER diagrams according to the same conventions.
Another example is International Sign Language – it is another way for people to communicate without even talking out loud!
HR System: EMPLOYEEs, JOBs, and DEPARTMENTs
- “We need to store data about each of our company’s employees. We need to track each employee’s first name, last name, hire date and salary. For each employee on commission, we also need to track his/her potential commission.”
- “Each employee is allocated a unique employee number.”
- “Our company is divided into departments. Each employee reports to a department – for example, accounting, sales, or development.”
- “We need to know the department responsible for each employee. Each department has a unique number.”
- “All employees hold a job, and we keep track of the job title, max and min salary for each job. Every job has a unique job id.”
ER Drawing Conventions
- Entities are represented by softboxes.
- Entity names go in the softboxes.
- Entity names are always singular and written with all capital letters.
- Attributes are listed under the entity names.
- Mandatory attributes are marked with an asterisk: “*”
- Optional attributes are marked with a circle: “o”
- Unique identifiers are marked with a hash sign: “#”
- Relationships are lines that connect entities.
- These lines are either solid or dashed.
- These lines terminate in either a “single toe” or a “crow’s foot” at the end of each entity.
- You will learn the specific details about relationship lines in the next lesson.
Any attribute that is part of the UID is always mandatory.
It is convention to draw it with only the “#” symbol before the name. The “*” is not required because it is implied by the Unique Identifier constraint
Key terms used in this tutorial included:
- ER diagram
- Crow’s Foot
- Single Toe
In this article, you should have learned how to:
- Construct ER diagram components that represent entities and attributes according to diagramming conventions