This is Database Management's project.

Key: Team_ID

FD1: Team_ID ->Team Name, League, Division, Year Founded

1NF: Meets the definition of a relation

2NF: No partial Key dependencies

3NF: No Transitive dependency exists

BCNF: All determinants are candidate keys

Key: Game_ID

FD1: Game_ID ->Season, Date Time, HomeTeamID(FK), AwayTeamID(FK)

1NF: Meets the definition of a relation

2NF: No partial Key dependencies

3NF: No Transitive dependency exists

BCNF: All determinants are candidate keys

Key: Player_ID

FD1: Player_ID ->First Name, Last Name, Address, Contact Number, Weight, Zip Code, Country. Joining Date, Date of Birth

1NF: Meets the definition of a relation

2NF: No partial Key dependencies

3NF:Transitive dependency exists: Player_ID -> Zip Code and Zip Code -> Address, Country

Solution: Split Team relation into two new relations named PlayerData and ZipCodes:

PlayerData (Player_ID(key), First Name, Last Name, Contact Number, Weight, Zip Code, Joining Date, Date of Birth)

Key: Player_ID

FD1: Player_ID -> FirstName, LastName, Contact Number, Weight, Zip Code (fk), Joining Date

1NF: Meets the definition of a relation

2NF: No partial Key dependencies

3NF: No Transitive dependencies

BCNF: All determinants are candidate keys

( ZipCode (key), Address, Country)

Key: ZipCode

FD1: ZipCode -> Address, Country

1NF: Meets the definition of a relation

2NF: No partial Key dependencies

3NF: No Transitive dependencies

BCNF: All determinants are candidate keys

Key: Stat_ID

FD1: Stat_ID ->Player_ID(FK), Game_ID(FK), Team_ID(FK), Singles, Doubles, Triplets, Hits, Runs

1NF: Meets the definition of a relation

2NF: No partial Key dependencies

3NF: No Transitive dependency exists

BCNF: All determinants are candidate keys