Changes between Version 20 and Version 21 of Normalization

Timestamp:

09/15/26 12:29:18 (12 days ago)

Author:

232012

Comment:

--

Normalization

@@ -243 +243 @@
 
 
-== Normal Form of R Before Decomposition
+== 1NF Decomposition
 
 {{{#!div style="text-align: justify; width: 100%;"
 
-{{{R ∈ 1NF}}}: The universal relation R is in 1NF because all attributes contain atomic values and there are no repeating groups.
+The universal relation R satisfies First Normal Form (1NF) because every attribute contains a single, atomic value for each tuple. None of the attributes contains a set, list, array, or multiple values stored inside a single field.
+
+For example, although a release may be associated with multiple artists, this does not result in several artist values being stored in one attribute. Instead, each association between a release and an artist is represented by a separate tuple through the attributes `release_id` and `artist_id`. The same applies to the relationships between songs and artists, albums and songs, orders and products, wishlists and products, and modifications and products.
+
+Similarly, attributes such as `email`, `username`, `price`, `quantity`, `genre`, `status`, `release_ordinal`, and `song_ordinal` each contain one indivisible value within a tuple.
+
+Therefore, R contains no repeating groups and no non-atomic attributes meaning:
+
+{{{R ∈ 1NF}}}
+
+}}}
+
+== 2NF Decomposition
+
+{{{#!div style="text-align: justify; width: 100%;"
 
 {{{R ∉ 2NF}}}: Since candidate key of R: **K = {order_id, product_id, artist_id, song_id, modification_id, album_id}** is a composite key, we must check for partial functional dependencies in order to determine whether R satisfies 2NF.
@@ -260 +274 @@
 and is not in 2NF.
 
-}}}
-
-== 2NF Decomposition
-
-{{{#!div style="text-align: justify; width: 100%;"
 ==== 1. PRODUCT(product_id, format, price, product_description, stock)