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 of the game.

Here we assumed that each game in the schedyle is identified by a unique Game #, 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 each player in a game.

This attribut can be designed to keep the information needed for statistics, and may be quite complex. One possible design for the perfoemance 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 of three multivalued components: Hitting, Pitching and Defense.

a.) Hitting has a value for each AtBat of of a player, and records the HitType (suitable coded; for example, 1 for single, 2 for double, 3 for triple, 4 for homerun 0 for walk, -1 for strikeout,

b.)Pitching has a value for each inning during which the played pitched.

c.)Defense has a value for each inning a played played a fielding position

Design an Entity-Relationship (ER) schema for this application, and draw an ER diagram for the schema. Specific key attributes of each entity type and structural constraints on each relationship type. Note an unspecified requirements, and make appropriate assumptions to make the specification complete.