Create a class (Game from above corresponding UML diagram) that handles names of games, the minimum/maximum age of the players, minimum/maximum number of players and the minimum/maximum time to play the game as if you were making a database of your own collection. In addition to the standard accessor and mutator methods from the instance fields, the class will have two different compare methods; a method to read a single game from a file, and a method that will output the data in a user-friendly format.

Create a class (GameCatalogue from the above corresponding UML diagram) that maintains the catalogue of games. It should be able to handle an initial population from a file. In addition, the class should be able to add a new game to the catalogue, find a game in the catalogue, sort the catalogue, remove a game identified by name from the catalogue and a method that will output the data in a user-friendly format.

Finally, create a class (GameCatalogueDriver from the above corresponding UML diagram), it must ensure that all methods (any method not used is minus 5 points) from both the Game and GameCatalogue classes have been appropriately used within the project.

\begin{tabular}{|l|} \hline GameCataloqueRriver \\ \hline +main (String []) :void \\ \hline \end{tabular}