Need an ER Diagram created based on the below criteria modeled in SQL.

Use the following business rules to create a single Entity-Relationship Model using the SQL Data Modeler software. Show all appropriate relationships and cardinalities in the diagram. You do not need to resolve any many-to-many relationships for this question, and you need not include primary keys unless specified. A local youth league needs a database system to help track the children (players) who sign up to play soccer. Data needs to be kept for each team and the children who are playing on the team. Information for the parents must also be stored for each child. Information for each coach assigned to each team must also be available, including the date that a background check was completed for the coach. In addition, game schedules for the teams must be stored. Use the following rules when developing your ER-diagram: A team may have zero or more players assigned to it, and a player may be assigned to a single team A team must have one or more coaches assigned to it, and a coach must be assigned to only one team. A parent must have 1 or more player in the league and a player must have one or more parent. d.) Each team may compete in many matches, and each match is between two teams e. Each match will be assigned to a single field, but each field will have many matches assigned to it. f.) Additional data requirements: For each player, track the player's first and last names, address, phone number and age. For each parent, track the parent's first and last names, address, and phone number. For each coach, track the coach's first and last names, address, phone number, and date of background check. For each match, track the date of the match, the time of the match and the field number (a foreign key to the Field). For each field, track the field name, field number and field city. Each team has a name and an attribute to store the maximum number of players allowed on the team. You should have entities, attributes and relationships in your model. Include the verb phrases for each relationship but you do not need to include data types or domains for the attributes. You do not need to include primary keys if they are not defined in the business rules. You do not need to distinguish between Identifying and Non-Identifying relationships for this model