Suppose you are the database analyst designing a database for a swim team league

Suppose you are the database analyst designing a database for a swim team league called Water Fun League (WFL):First, WFL wants to keep track of the swim teams in the league and their swimmers. Each swim team has an official name and a captain. A team is made up of many swimmers. WFL tracks each swimmer’s name, address, phone number, and date of birth. A swimmer can be a member of only one team.Second, WFL wants the database to keep track of the swim meets it holds. WFL has a numbering system for each swim meet. A swim meet also has an official name (such as “Father’s Day Swim Meet”), and the time and location are announced as soon as available. All teams in the league can compete at each meet.A meet consists of a variety of events (e.g., Men’s 50m freestyle, Women’s 100m butterfly, so on and so forth). The league keeps the League Record for each event as well as the corresponding national amateurs’ record as a reference. A swimmer can compete in multiple events at a swim meet.Design an ER diagram for the WFL database. Save it as YourInitialWFL and upload it here. Make any assumption/ business rules you may need. STATE THEM CLEARLY (required). (Use your initials to begin the name of each attribute, table, entity and the file)The ER diagram must include the necessary entity classes and all attributes specified in the description.Identifiers for all entity classes must be shown clearly.Relationships must be named, with cardinalities clearly shown.