Design an EER diagram for a database used to manage a racket sport association (for example, US Tennis Association). The following is a list of simplified requirements.

Each member of the sport association has an id, a name, sex, age, an address, a phone number.

A member can be a player, an umpire (i.e., referee), a coach, or an officer (i.e. a member can belong to one or more of the above categories).

An umpire has a type (i.e., national, international, etc.). A coach has a certificate (i.e., level I, II, etc.). An officer has an office (i.e., a room number such as 101 or 212 in the main building).

Each club has a name, an address, an owner, and a phone number.

Except for some officers, every member belongs to one or more clubs (Hint: Make relationships between the subclasses of member and club).

A player can be a professional or an amateur (but not both). A professional player has a rank (such as 1, 2, etc. within the association), and a coach (Note: Every professional should have one coach). An amateur player has a division (i.e., junior, college, senior, and master).

The association sanctions tournaments each of which has a name, a date, and a location, and is organized by a club (Note: Every tournament should have one organizing club).

Each tournament consists of a set of matches (Note: Every match should belong to a tournament). Each match has a division (such as open, senior, master, college, and junior), an event (such as mens single, mixed double, etc), a round (such as first, second, semi-final, and final), a set of scores, and an umpire. Also, assume that a match" is a weak entity (and hence show the partial key and the identifying relationship).

Each match is refereed by an umpire (Note: Each match should have one empire), played by a number of players (that is, a single match is played by two players, and a double match is played by four players, two on each side), and won by one or two players depending on whether the match is single or double (Note: Each match should definitely have some players and definitely some winners).

Make sure to specify the unique attributes (keys) and relationship constraints (using cardinality ratios or (min, max) notation). The above requirements may still be incomplete for this specific application domain, and you may specify additional requirements or assumptions that are consistent with the listed requirements.