Converting ER Diagrams to Relational Model

The ER chapter ended with a finished diagram and a promise: turning it into tables follows fixed rules.

Here are the rules, as a procedure you can run in order. Every step has one decision, and none of them needs judgement once the diagram is right.

Then we run the whole procedure on the employee management system from the ER chapter.

The procedure

Step 1. Every strong entity becomes a table. Its key attribute becomes the primary key.

Step 2. Simple attributes become columns. One column each, same name.

Step 3. Composite attributes become one column per part. `Full_Name