Skip to content

Data Normalization

Nantawan Paramapooti edited this page Dec 24, 2024 · 9 revisions

To be updated As most of the Translated Relations are already in 3NF form, we'll only focus on the Relations that needed 3NF

1-3 NF Processes

*data instances in the following examples are abstract values for demonstration, may not accurately reflects project's actual instances.

ChatRank (chatrank_id, chatrank_name, allowed_actions)

chatrank_id chatrank_name allowed_actions
1 []
2 []
3 []

1NF: All attributes contain atomic values.

  • Each attribute (post_id, user_id, p_content, timestamp) holds only indivisible values.

2NF: No partial dependency on any subset of a primary key.

  • Since post_id is the primary key, all non-key attributes (user_id, p_content, timestamp) are fully dependent on post_id.

3NF: No transitive dependency on non-key attributes.

  • There are no dependencies between non-key attributes; therefore, no transitive dependency exists.

Conclusion

Allowed Actions relations are already in its 3NF form from the UML design, no further changes needed.

Clone this wiki locally