This is an AI translated post.
Kanban Board Project 2 Logical Data Modeling
- Writing language: Korean
- •
-
Base country: All countries
- •
- Information Technology
0000-00-00 00:00:00
Select Language
Summarized by durumis AI
- Based on the conceptual data modeling ERD, we proceed with logical data modeling, and set up relationships with both tables by considering mapping tables.
- After converting the ERD into a tabular form and performing normalization, the first normal form is satisfied, and the Tag in the Ticket table was created as a separate table to satisfy the second normal form.
- During the process of checking whether the third normal form is satisfied, we considered whether to separate the author_id and responsibility_id of the Ticket table. However, since it is not an N:M relationship but an FK, we moved on.
Practice of learning and performing logical data modeling
Conceptual Data Modeling ERD
Conceptual Data Modeling ERD
First, we go through the conceptual data modeling process, and then proceed with logical data modeling using this ERD.
Logical Data Modeling ERD
Logical Data Modeling ERD
One thing that was a bit difficult was that I had to consider the relationship between the two tables based on the mapping table.
After converting the conceptual data modeling ERD into a table format, we proceed with normalization.
Normalization
The normalization steps must be performed sequentially. Looking at the ERD above, it satisfies the 1st normal form.
To satisfy the 2nd normal form, a Tag table is created from the Tag in the Ticket table, and the PK of the Tag is used as FK.
The normalized form
Now we need to see if it satisfies the 3rd normal form, but it's difficult because I haven't learned the concept yet.
I'm wondering if I should separate the author_id and responsibility_id of the Ticket table into other tables, but it's not an N:M relationship, and it's an FK, so I decided to move on.
