Problem Statement A local high school wants to keep track of statistics for the basketball team....

Transcribed Image Text:

Problem Statement A local high school wants to keep track of statistics for the basketball team. The coach wants to get insight into average scores, low/high scores, etc. The coach would like to be able to run reports on demand using a menu-driven application. The application must keep track of both the team scores and the opponent scores of every game played. You must create entry screens for the scores. The season is 10 games long. The scores can be saved in a matrix, or an arrayList, or optionally for bonus points a separate file that can be loaded in (csv, text, etc). The information must be updated with any changes from the user. You have freedom to design and implement the UI and functionality, so no sample output is provided. You can use a text base or a GUI based screen. Functioning GUI based programs will receive extra credit. Requirements A menu to access the screens and reports. Enter/Edit screen for the scores. Each game will have points for each quarter, for each team (8 scores per game). There are 10 games in a season. Analytics reports that include the following information: Average points per quarter, half, and game by each team (Should be the averages for all games - EX: the average for every 1st quarter if the user enters that they want 1st quarter averages. For half game averages - it should either be the average of all 1st and 2nd quarters, or 3rd and 4th quarters - depending on the user's selection.) The lowest point total scored during any quarter during the whole season. The highest point total scored during any quarter during the whole season The program should use what you have learned in this class and use objects with proper OOP methods. Grading Details 15% Correct usage of OOP and modular programming concepts 15% Correct data handling 15% Supporting code and logic (control structures, logic, etc.) 10% Good UI/UX design 10% User friendliness (good prompts and outputs) 10% Program runs, produces expected results 10% Descriptive variable names 10% Comments (minimum required comments and human readable clarification for any unclear or unintuitive code) 5% Proper code indentation/formatting Problem Statement A local high school wants to keep track of statistics for the basketball team. The coach wants to get insight into average scores, low/high scores, etc. The coach would like to be able to run reports on demand using a menu-driven application. The application must keep track of both the team scores and the opponent scores of every game played. You must create entry screens for the scores. The season is 10 games long. The scores can be saved in a matrix, or an arrayList, or optionally for bonus points a separate file that can be loaded in (csv, text, etc). The information must be updated with any changes from the user. You have freedom to design and implement the UI and functionality, so no sample output is provided. You can use a text base or a GUI based screen. Functioning GUI based programs will receive extra credit. Requirements A menu to access the screens and reports. Enter/Edit screen for the scores. Each game will have points for each quarter, for each team (8 scores per game). There are 10 games in a season. Analytics reports that include the following information: Average points per quarter, half, and game by each team (Should be the averages for all games - EX: the average for every 1st quarter if the user enters that they want 1st quarter averages. For half game averages - it should either be the average of all 1st and 2nd quarters, or 3rd and 4th quarters - depending on the user's selection.) The lowest point total scored during any quarter during the whole season. The highest point total scored during any quarter during the whole season The program should use what you have learned in this class and use objects with proper OOP methods. Grading Details 15% Correct usage of OOP and modular programming concepts 15% Correct data handling 15% Supporting code and logic (control structures, logic, etc.) 10% Good UI/UX design 10% User friendliness (good prompts and outputs) 10% Program runs, produces expected results 10% Descriptive variable names 10% Comments (minimum required comments and human readable clarification for any unclear or unintuitive code) 5% Proper code indentation/formatting