Problem description from the first assignment: Football manager multiplayer simulation game; The game shall have features for team management, transfer market management, financial management, tactical management, training management, player statistics. The players $($team managers$)$ of the game should be able to form teams to manage by either transferring footballers from other teams or developing young talents within their own organizations. Conversely, team club presidents can place their own footballers? for sale via a marketplace. Each footballer on the marketplace should have a marketplace value, which depends on a base price determined by the president of the team club, and various statistics of the footballer, which denotes the base price for which that footballer can be bought. Depending on the match statistics of the player, the marketplace value of a footballer can increase or decrease. A team$$s total value is the sum of the individual marketplace values of its all footballers. Footballers should also have individual skills which are improved by training. Two game players$$ teams should be able to have a match among themselves, and the result of such a match is determined by several factors including team total values, individual footballer$$s skills, the tactic given by the team manager to his$/$her team before the match, and some degree of randomness and chance. The teams have budgets which they use to buy footballers from other teams via the marketplace. Teams earn money via match ticket sales, jersey sales, and also paid by the football federation based on individual match scores. With this assignment you are expected to specify the use cases you identified for the first assignment in the structured specification template we have seen during the lectures $($Week$04$ lecture notes, replicated below$).$ Please do not omit the possible alternative flows in addition to the normal flows you identified. Please concentrate over the functionalities given as part of the first assignment, and discard any possible non$-$functional requirements that might be of interest in such a system. $1.$ Draw the analysis level class diagram corresponding to the above problem description. Make sure to label all associations with appropriate multiplicities. Remember that, analysis level class diagrams are not necessarily complete, but have only the methods$/$attributes discovered during requirements engineering activities. Concentrate on goals, and requirements, rather than on lower level concepts such as variables, procedures and control flow. Your object classes should reflect domain concepts and characteristics rather than implementation level classes. Clearly state the assumptions you made, if any.