(ER) Entity - Relationship

3) (30 points) A database is being constructed to keep track of the teams and games of a baseball league. A team has a number of players, not all of whom participate in each game. It is desired to keep track of the players participating in each game for each team, the positions they played in that game, and the result Here, we assumed that each game in the schedule is identified by a unique Gameff, and a game is also identified uniquely by the combination of Date, starting Time, and Field where it is played. The Performance attribute of PARTICIPATE is used to store information on the individual performance of eac This attribute can be designed to keep the information needed for statistics, and may be quite complex One possible design for the Performance attribute may be the following: Performance( {Hitting(AtBat, Inning#, HitType, Runs, RunsBattedIn, StolenBases), Pitching(Inning#, Hits, Runs, EarnedRuns, Strikeouts, walks, Outs, Balks, WildPitches), (Defense(Inning# {FieldingRecord(Position, PutOuts, Assists, Errors)))) ) Here, performance is a composite attribute made up of three multivalued components: Hitting, Pitching, and Defense (a) Hitting has a value for each AtBat of a player, and records the HitType (suitable coded; for example, 1 for single, 2 for double, 3 for triple, 4 for home run, 0 for walk, -1 for strikeout, 2 for fly out,...) and other information concerning the AtBat. 8 6 (b) Pitching has a value for each inning during which the player pitched. (c) Defense has a value for each inning a player played a fielding position. Design an ER schema for this application, and draw an ER diagram for that schema. Specify key attributes of each entity type and structural constraints on each relationship type. Note any unspecified requirements, and make appropriate assumptions to make the specification complete