Model the data that supports this application using an ER diagram for the elements below. Use the notation from class (e.g. 0..1, 1..1, 0..*, 1..* annotations on edges; double boxes on weak entity sets, the defining relationship set, etc.). Create an electronic version of each diagram using draw.io, Powerpoint, Word, Visio, OpenOffice Draw, OmniGrae, Google Drive Document or any other software that you are familiar with, and export it to PDF format. Do not turn in handwritten diagrams as they are hard to read!

Consider an application for a golf club, which tracks courses, rounds of golf, and players.

The golf club has a set of courses. Each course is identified by name, and has a rating and slope (think of these as integers).

Each course consists of a set of consecutively numbered holes (starting at 1). Each hole is identified by its number, and has information about yardage (distance from the tee to the hole, think of this as an integer), par (the number of strokes that a proficient golfer requires to complete the hole) and notes.

Players are identified by their club id. Players additionally have a name, address and handicap (an integer measuring the golfer's skill that is used to enable players of varying abilities to compete against one another).

A round of golf is played on a course by a set of up to 4 players. Each round is identified by the datetime that it is played on a course. Two rounds cannot be played on the same course at the same datetime, and a round must have at least one player.

A player has a score for each round of golf that they play, as well as an indication of whether or not they used a cart (as opposed to walking). For simplicity you can think of the score as an array of integers, one for each hole played.

A. (24 points) Draw an ER diagram for this scenario. Note:

- Both entity and relationship sets can have attributes

- Primary keys should be determined from the descriptions, and should be shown in the ER diagram by underlining the attribute(s)

- Cardinality constraints should be indicated according to the descriptions

- Feel free to give the entity and relationship sets any names that are reasonable.

B. (6 points) Suppose that you wish to design this database for a set of golf clubs rather than for a single golf club. Each golf club is identified by its name (assume these are unique), and has an address, phone, and website. Assume that a player belongs to a single golf club, but that course names are not unique across all golf courses (i.e. there could be a Spring Mill course at XYZ Golf Club as well as at ABC Golf Club).

1. Show how your ER diagram would change (you can elide the portions that do not change).

2. Briefly discuss how you address the issue that course names are not unique across all golf courses.