Conduct normalization analysis on CLYSTMS by listing the FDs and the highest normal form of each relation. Complete the task by filling in the row "Normalization Analysis."

so far we have this done:

1.

Swimmer(SwimmerId, FName, LName, Phone, Email, JoinTime, CurrentLevelId, Main_CT_Id, Main_CT_Since)

FD's:-

Swimmer --> SwimmerId, FName, LName, Phone, Email, JoinTime, CurrentLevelId,Main_CT_Id

Main_CT_Id --> Main_CT_Since

Highest Noraml Form:- 2 Normal Form

.

2.

Caretaker(CT_Id, FName, LName, Phone, Email)

FD:- CT_Id --> FName, LName, Phone, Email

Highest NF: BCNF

Since This relation satifies all the normal forms upto BCNF. as there is no transitive and no non trivial dependencies in the relation.

3.

OtherCaretaker(OC_Id, SwimmerId, CT_Id, Since)

FD:- CT_Id --> Since

Highest Normal Form:- 1 Normal form

4.

Level(LevelId, Level, Description)

FD:- LevelId, Level --> Description

Highest Normal Form:- BCNF

The relation schema for the next 4 tables:

5	LevelHistory(LH_Id, SwimmerId, LevelId, StartDate, Comment)
Candidate Keys		[1] LH_Id, [2] SwimmerId, LevelId
Foreign Keys		[1] SwimmerId references Swimmer(SwimmerId), [2] LevelId references Level(LevelId).
Nullable Attributes		Comment
Notes		(1) A surrogate key, LH_Id, is created as the primary key. This is optional.
Normalization Analysis		FD: Highest NF:
6	Coach(CoachId, FName, LName, Phone, Email)
Candidate Keys		(1) CoachId
Foreign Keys
Nullable Attributes
Notes
Normalization Analysis		FD: Highest NF:
7	Meet(MeetID, Title, Date, StartTime, EndTIme, VenueId, CoachId)
Candidate Keys		[1] MeetId
Foreign Keys		[1] CoachId references Coach(CoachId), [2] VenueId references Venue(VenueId)
Nullable Attributes
Notes
Normalization Analysis		FD: Highest NF:
8	Venue(VenueId, Name, Address, City, State, ZipCode, Phone)
Candidate Keys		[1] VenueId, [2] Name (likely), [3] {Address, City, State, ZipCode} (likely)
Foreign Keys
Nullable Attributes
Notes
Normalization Analysis		FD: Highest NF:

: