The local city youth league needs a database system to help track children that sign up to play soccer. Data needs to be kept on each team and the children that will be playing on each team as well as their parents. Also, data needs to be kept on the coaches for each team.

Create an ERD with draw.io Links to an external site.based on the details below. SUBMIT a PNG EXPORT

Remember to denote primary and foreign keys (PK, FK) as well as both cardinality (one/many) and participation (mandatory/optional) for relationships.

Note that there is a SINGLE many-to-many relationship in this model--and you must create a 'join' or 'bridge' table to hold the foreign keys.

Also remember to use proper/valid field names (no spaces or special characters, except _)--and follow the convention of using all lowercase.

Entities required: Team, Player, Coach, and Parent.

Attributes required for each entity:

Team: Team_ID number, name, and colors.

Player: Player_ID number, first name, last name, and age.

Coach: Coach_ID number, first name, last name, and home phone number.

Parent: Parent_ID number, last name, first name, Home phone number, and Home Address (Street, City, State, and ZIP Code--to simplify for this exercise, just put all of these into a a single 'address' field).

Further requirements:

Team is related to Player.

Team is related to Coach.

Player is related to Parent.

Specifically:

A Team may have many Players.

A Player has only one Team.

A Team may or may not have a Player.

A Player must have a Team.

A Team may have many Coaches.

A Coach has only one Team.

A Team may or may not have a Coach.

A Coach must have a Team.

A Player may have many Parents.

A Parent may have many Players.

A Player must have a Parent.

A Parent must have a Player.