ASSESSMENT DESCRIPTION:

GameAlerts is an application that provides real time updates about various tournaments happening around the

world. The updates include tournaments being conducted, teams participating in tournaments, and live score

updates. The app covers a wide variety of sports including but not limited to soccer, tennis, table tennis, cricket,

and polo. The app handles data about all relevant entities such as players, teams, Games, tournaments, and

sponsor details. This generates large volumes of multi$-$structured data and app requires flexibility and scalability

to ensure scores are updated to the users in real time.

$1.$ All players$$ basic information such as name, address, age need to be stored.

$2.$ Player$$s affiliations and previous games$$ statistics and records are to be stored in the system.

$3.$ Teams$$ information such as team name, coaches, managers, and players need to be stored.

$4.$ Tournaments information such as venue, date and time, and teams participating in the tournament,

needs to be stored.

$5.$ For every tournament, games to be played, and relevant information needs to be stored. For every sport

the criteria for games to be played are different.

$6.$ Umpire and sponsor information about the tournaments also need to be stored.

Keeping the above scenario in mind, answer the following:

$1.$ Which database model is best suitable for the case study given above? Provide your recommendation

with appropriate justifications.

$2.$ Assume that you have decided key$-$value databases to be the underlying model of your database.

Create keys for players$$ information. Design at only $20$ different keys $($for different attributes$)$ using

recommended guidelines for Key$-$Value databases.

$3.$ Explain what will be limitations of search if the model used is Key$-$Value databases. Justify and provide

solutions to overcome the limitations$.$

$4.$ Using given information, design the documents for all relevant entities mentioned in the case study.

Create a text file with JSON extension and put documents in the file.

$5.$ Looking at these entities, what are the possible relationships between these entities and how that

would be captured in the designed $($MongoDB$)$ documents?