Task One: The League $-$ Conceptual Model and Logic Design $(15$ points$)$

Develop an E$/$ER model $($conceptual model$)$ for the following description, with appropriate

entity types, relationships, cardinality, and disclaimers.

A regional youth soccer league would like to use an ORACLE database to manage teams,

coaches, and players data, replacing a paper$-$based system.

For teams, we need team name, the year in which the team was established in our league, and

home location. Captain is one of its players. For players, we need their lastname, firstname,

date of birthday, and which school they attend. For coaches, we record their lastname,

firstname, date of birthday, social security number for tax purpose, and when they started

coaching. Currently, we do not include people other than players and coaches in our database,

such as staff. One person cannot be both player and coach. Current paper$-$based system does

not include any particular information to identify people.

For a particular year, a coach is assigned to a team and over the years coach may switch teams.

Coaches and players do not switch teams in the middle of the year. Coaches' salary and sign$-$up

bonus $($if any$)$ may vary year to year. One of the players of a team is the captain. A player may