Create an EERD based on the scenario below. If you discover while drawing the diagram that the scenario is incomplete, make up reasonable explanations to complete the story. Supply your explanations along with the diagram.

Note: The EERD you make looks like the one shown in Figure 5.4. Your EERD must show

o Entity: The proper number of entities and their names

o All needed attributes of each entity

o Primary key and Foreign key

o Disjoint/overlapping constraints

o Subtype discriminators

o Partial/total completeness

In drawing the model, use the textbook notation

In drawing the diagram, you can use any (diagraming) software, such as Draw.io, Microsoft Visio, LucidChart, or even Microsoft Word.

Copy and paste the diagram to Microsoft Word or convert them PDF and Submit the Word file or PDF file o Include diagram ONLY, not entire software screen

o Your submission should be readable

(Scenario) Morehead State University keeps information on its student-athletics. Every student-athletic participates in one or more sports. Football, basketball, and baseball are among the many sports. Attributes common to all student-athletics, regardless of sport, include student#, name, major, GPA, weight, height. For studentathletics participating in the sports of football, basketball, and baseball, attributes specific to each sport are:

Football players: touchdowns, speed

Basketball players: points scored, assists, rebounds

Baseball players: batting average, home runs, errors

It is common today for a football player to specialize in either offense or defense. Players can not change their positions from offensive to defensive, or vice versa. Attributes for offensive players include receptions and yards gained. Attributes for defensive players include number of tackles and number of interceptions. Likewise, some baseball players are also pitchers. Attributes about pitchers include ERA, pitching speed, inning pitched, strikeouts, and walks. (Note that there are many different baseball positions: pitcher, catcher, first baseman, second baseman, outfielder, etc. But, you will put only pitcher subtype in your diagram)

Note: subtype discriminators are not listed in the scenario. You Must add them to your diagram.