Changes between Version 21 and Version 22 of P2


Ignore:
Timestamp:
06/15/26 13:42:23 (9 days ago)
Author:
216009
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • P2

    v21 v22  
    1919**Subject** ( __Id__, __Faculty_Id*__ (Faculty), Name, Semester, Credits )
    2020
    21 **Subject_Professor** ( __Subject_Id*__ (Subject), __Professor_Id*__ (Professor) )
    22 
    23 **Student_Subject** ( __Ss_Id__, __Student_Id*__ (Student), __Subject_Id*__ (Subject), Final_Grade, Status, Enrollment_Date, Absences_Count )
    24 
     21**Student_Subject** ( __Ss_Id__, __Student_Id*__ (Student), __Subject_Id*__ (Subject), __Professor_Id*__ (Professor), Final_Grade, Status, Enrollment_Date, Absences_Count )
    2522----
    2623
     
    4845== Final Result
    4946
     47== Final Result
     48
    5049== Tables
    5150
     
    6059**Subject** ( __Id__, __Faculty_Id*__ (Faculty), Name, Semester, Credits )
    6160
    62 **Subject_Professor** ( __Subject_Id*__ (Subject), __Professor_Id*__ (Professor) )
    63 
    64 **Student_Subject** ( __Ss_Id__, __Student_Id*__ (Student), __Subject_Id*__ (Subject), Final_Grade, Status, Enrollment_Date, Absences_Count )
     61**Student_Subject** ( __Ss_Id__, __Student_Id*__ (Student), __Subject_Id*__ (Subject), __Professor_Id*__ (Professor), Final_Grade, Status, Enrollment_Date, Absences_Count )
    6562
    6663**Advice** (__Student_Id*__ (Student), __Professor_Id*__ (Professor), Start_Date, End_Date)
     
    8784Schema Normalization Review: I provided the AI with my initial 7-table layout (University, Faculty, Professor, Student, Subject, Subject_Professor, and Student_Subject). We reviewed the constraints to ensure proper cascading rules and column data integrity.
    8885
    89 Relationship Modeling: To handle business requirements for office hours and mentorship, I formulated an Advice entity. The AI helped me refine its composite key structure to accurately capture timeline interactions between students and professors.
     86Relationship Modeling & Professor Assignment: To handle business requirements for office hours and mentorship, I formulated an Advice entity. Additionally, based on professor feedback regarding ambiguity in grading when multiple professors teach the same course, we removed the legacy Subject_Professor table. The Professor_Id was successfully migrated directly into the Student_Subject enrollment schema. This ensures that for every specific course enrollment, the system explicitly tracks which professor taught the student and is authorized to enter the final grade, eliminating any multi-instructor ambiguity.
    9087
    9188Affiliation Tracking: I noticed a missing link where a professor might be affiliated with a specific university outside of just their faculty assignment. The AI assisted me in mapping this out cleanly as an Affiliated bridge table to prevent normalization redundancy.