Changes between Version 36 and Version 37 of RelationalDesign

Timestamp:

09/18/26 14:42:13 (13 days ago)

Author:

216009

Comment:

--

RelationalDesign

@@ -83 +83 @@
 
 Schema Mapping & Normalization Review: All conceptual entities from Phase 1 were mapped to relations. Foreign keys were introdu
-== Entire AI usage log:
+== AI Usage Log ==
 
-Schema Mapping & Normalization Review: All entities from Phase 1 were mapped to relations. Foreign keys were introduced to represent 1:N relationships (`University_Id` in Faculty, `Faculty_Id` in Professor, Student, and Subject).
+'''Schema Mapping & Normalization Review:''' All entities from Phase 1 were mapped to relations. Foreign keys were introduced to represent 1:N relationships (University_Id in Faculty, as well as Faculty_Id in Professor, Student, and Subject).
 
-Weak Entity Materialization: The weak entity `Student_Subject` was mapped by forming a composite primary key consisting of its discriminator (`Ss_Id`) along with the primary keys of its owner entities (`Student_Id` and `Subject_Id`). The regular 1:N relationship with `Professor` (`assignTo`) was materialized via a foreign key `Professor_Id` in this table.
+'''Weak Entity Materialization:''' The weak entity Student_Subject was updated to align with the Phase 1 ER model. Its composite primary key is formed exclusively by its discriminator (Ss_Id) along with the primary keys of its owner entities (Student_Id and Subject_Id). The regular 1:N relationship with Professor (assignTo) is materialized via a foreign key (Professor_Id) in this table and is not part of the primary key.
 
-Relationship Materialization:
-- The M:N relationship `Advises` with attributes (`start_date`, `end_date`) was mapped to the `Advice` table with a composite primary key (`Student_Id`, `Professor_Id`, `Start_Date`).
-- The M:N relationship `affiliated_with` was mapped to the `Affiliated` bridge table with composite primary key (`University_Id`, `Professor_Id`).
-- The M:N relationship `Teach` was mapped to the `Teach` bridge table with composite primary key (`Professor_Id`, `Subject_Id`).
+'''Relationship Materialization:'''
+ '''Advises:''' The M:N relationship with attributes (start_date, end_date) was mapped to the Advice table with a composite primary key (Student_Id, Professor_Id, Start_Date).
+
+ '''affiliated_with:''' The M:N relationship was mapped to the Affiliated bridge table with a composite primary key (University_Id, Professor_Id).
+
+ '''Teach:''' The M:N relationship was mapped to the Teach bridge table with a composite primary key (Professor_Id, Subject_Id).
+
+'''Visual Alignment & Tooling:''' The Phase 2 relational diagram was visually reorganised to strictly mirror the topographical layout of the Phase 1 ER diagram. The diagram was generated using the DBeaver ERD Tool using standard Crow's Foot notation.