Specification

The National Basketball Association Game System will consist of four main components: team management, player management, an association component, and a season scheduling component.

1.    The association component allows users to manage the teams and game season via text-based menus.

2.    The team management stores a team list, while each team has its own players. The team management component is capable of displaying all teams, displaying all players, adding a new team, managing an existing team, deleting an existing team, and displaying all players at a particular level.

3.    The  player  management  component  is  accessible  from  the  team  management  menu.  The  player management component allows displaying all the players that belong to this team, the registration and removal of players in this team, and the update of players’ information.

Each player’s information includes the name, credit, No., level, and age, while the level is calculated based on the credit.

4.    The season scheduling component allows users to start a new season, while each season contains multiple rounds, and each round contains multiple games. Users can register the team for the round, display the teams in the current round, run the games in the round, and display the game results. After the round is completed, the players’ credits will be updated according to the result and the average credit differences between the two teams. Gaming rules are listed below to make it as clear as possible:

•     Game: Each game is played between 2 teams and generates one winner and one loser. The team that has a LARGER AVERAGE CREDIT will WIN this game . Suppose we have two teams in a game: Team A and Team B. The average credit of A’s players is 1000, and the average credit of B’s players is 500. As 1000>500, A will be the winner of the game.

•     Round: A season may contain multiple rounds. Each round may contain several games, and the number will be decided by how many teams register. Suppose we have 4 teams, namely A, B, C, and

D. Then there will be 2 games in the first round, i.e. team A vs team C, and team B vs team D . After the first round is completed, the winners of each game will be automatically added to the next round.

•     An illustration of this process is listed in Season:

When registering the first team for a season, a game will be created automatically, and the round number of the Season and the term number of the game will start from 1. When the second team registers for the season, the round number of the Season and the term number of the game stays the same, and the second team will be assigned to the same game as the first team.

When registering the third team for a season, a new game will be created automatically, and the round number of the Season will be kept as 1, while the term number of the game will increase to 2, representing the second game. When the fourth team registers for the season, the round number of the Season and the term number of the game stays the same as the third team, as the third team will compete with the fourth team.

After playing games in the current round, two winning teams will be recorded and only the winning teams can register for the next round. In such case, the round number will increase to 2 and the term number will start from 1.

The User Interface and sample I/O will be posted on the Assignment page on Canvas and ED for a detailed description.

An aside

While reading the first part of the specification, you will notice there is a lot going on.

•     How many functions did you identify?

•     How many classes did you identify?

•     What are the fields in each class?

•     How many goals did you identify?

•     How many patterns did you think of that might be applicable?

This assignment will be challenging, and you will probably want to manage your time well.

•     How long do you think it will take you to code the functions?

•     How long do you think it will take you to code each goal?

•     A good rule of thumb is to think of an estimate, and then multiply that number by 3 or 4!

•     To manage your time well, you may need to figure out which parts of the assignment you can start early.

•     Which parts can you start now?

•     Which parts can you start in week 6?

If you complete parts in the same week that you learn the topics (while they are fresh in your mind), they will take less time to complete.

Requirements

•     Your design will consist of exactly the following classes with the listed fields, declared as indicated. You may not add or remove classes or fields; however, you may add constructors, functions and procedures to complete your design (in fact, you will have to!). You should pay careful attention to the tests on ED, as these will help guide you with some (but not all) of these methods.

•     To help visualize the design, a partial class diagram has been provided:

•     Classes – your design will consist of these 10 classes for java and 9 classes for python:

1.    Association: The fields contain Teams and Season.

2.    Season: The fields contain the scheduled game list, the round number, the team list and the record list.

3.    Teams: The fields contain the team list.

4.    Team: The fields contain the Team name and the players .

5.    Players: The fields contain the player list.

6.    Player: The fields contain name, credit, level, age, team and No.

7.    Game: The fields contain the Team list, result list and the term.

8.    Record: The fields contain the WinTeam , LoseTeam, GameNo and round number.

9.    Utils (this is the class to facilitate format, do not change)

10.  In (this is the class for simple I/O, do not change, python does not have this class)

•     Fields – All the fields have been clarified in each class and they should not be modified. The fields also have some additional requirements and structures:

Lists all have the abstract type of List<>, but must be instantiated with a concrete type that implements the List<> behavior (you can choose either – you may also want to think about why you might do things this way).

•     Constructors – the constructors of the class have the following requirements:

1.    The main method of the program will be in the Association class.

2.    All constructors initialize the fields of their classes.

3.    The Association, Teams, Season, and Players constructors take no parameters.

4.    The Team constructor takes one parameter, the name, corresponding to the fields identically named. Other fields require no parameters but the constructor methods.

5.    The Player constructor takes four parameters, the name, the credit, the age, the No., and the level, corresponding to the fields identically named. Other fields require no parameters but the constructor methods.

6.    The Game constructor takes one parameter, the term, corresponding to the fields identically named. If the term is 1, it means this is the first game in this round, and so on.

7.    The Record constructor takes four parameters, the name of the winning team and the losing    team, the Game number, and the round number, corresponding to the fields identically named.

8.    The Player constructor requires the following formula to set the value of the fields:

Type: set by credit

9.    We initialize 4 teams in the system:

10.  Each team has the following players:

•     Utils Class – the Class defines the following formatting:

Take Teams Format as an example:

Java:

teamsHeader( )defines the output format of the header:

+-----------+--------------------+-----------------------+-------------+

| Team Name | Number of Players  | Average Player Credit | Average Age |

+-----------+--------------------+-----------------------+-------------+

teamsTabkeEnd ( )defines the output format of the end of the table .

To print the team’s information following the pre-defined format, you can use the following code:

System.out.format(Utils.teamsFormat,name,NoofPlayers,AvgPlayerCredit, AverageAge) will produce a string of the form.

e.g.

| Suns  |  5  | 2000.0  | 30.60 |

Note: "| %-20s | %-19d | %-21.2f | %- 12.2f |%n" defines the space for the string.           To demonstrate the information of the team, such as the information of suns, the whole code may look like this:

Utils.teamsHeader();

System.out.format(Utils.teamsFormat,name,NoofPlayer,AvgCredit,AvgAge); Utils.teamTableEnd();

As you need to demonstrate the information of all existing teams, you may need to code some loops and use some functions to obtain the statistical data.

Python:

teamsHeader( )defines the output format of the header:

+-----------+--------------------+-----------------------+-------------+

| Team Name | Number of Players  | Average Player Credit | Average Age |

+-----------+--------------------+-----------------------+-------------+

teamsTabkeEnd ( )defines the output format of the end of the table.

To print the team’s information following the pre-defined format, you can use the following code:

print(Utils.teamsFormat(name,NoofPlayer,AvgCredit,AvgAge))

Note:

def teamsFormat(name,numofplayer,avgcredit,avgage):

return "| %-*s | %-*s | %-*s | %-*s |"                                                                   %(20,name,19,numofplayer,21,"{:.2f}".format(avgcredit),12,"{:.2f}".format(avgage))

defines the space for the string.

To demonstrate the information of the team, such as the information of suns, the whole code may

look like this:

Utils.teamsHeader()

print(Utils.teamsFormat(name,NoofPlayer,AvgCredit,AvgAge))

Utils.teamTableEnd()

As you need to demonstrate the information of all existing teams, you may need to use sum pattern and count pattern to obtain the statistical data.

Note: when displaying all the players’ information for all teams, or displaying players at a particular level, you need to display both the player’s information and the corresponding team by using                                          DisplayPlayerFromAllTeamsHeader().

when you are trying to display the player’s information for a specific team, you do not need to display the team information. You can use playerHeader().

*In the format definition of Utils, %s means string, %d means integer and %f means float.

Credit Updating Rules after the Game is Completed

The credit of each player will be updated after the game is completed. Suppose we have 2 teams: A and B. Then it follows the rules:

Difference = AvgCredit(A) − AvgCredit(B)

where AvgCredit means the average credit of the team. Suppose team A is the winning team, then, for the player Lucy in team A, the new credit is:

̅̅e̅̅u̅ =  CreditLucy  +

where ̅̅e̅̅ indicates the new credit of Lucy.

For the player Mike in team B (which is the losing team), the new credit is:

̅̅e̅̅i =  CreditMike −

where ̅e̅