CS 2336 – PROJECT 2 – Mario Super Sluggers 2 Solved

Description

Pseudocode 

KEY ITEMS: Key items are marked in red. Failure to include or complete key items will incur additional deductions as noted beside the item.

Submission and Grading:

• All project source code will be submitted in zyLabs.
  • Projects submitted after the due date are subject to the late penalties described in the syllabus.
• Each submitted program will be graded with the rubric provided in eLearning as well as a set of test cases. These test cases will be posted in eLearning after the due date. – zyLabs will provide you with an opportunity to see how well your project works against the test cases. Although you cannot see the actual test cases, a description will be provided for each test case that should help you understand where your program fails.
• Type your name and netID in the comments at the top of all files submitted. (-5 points)

Objective: Use object-oriented programming to implement and utilize a linked list data structure

Problem: Now that the Mushroom Kingdom League has ended and crowned a new champion, it is time to determine the league leaders in several different baseball categories. Being the only person in the Mushroom Kingdom that knows how to write a computer program, you have been asked by Princess Peach herself to write a program that will determine the league leaders.

Pseudocode: Your pseudocode should describe the following items

• Identify the functions you plan to create for each class
  • You do not have to include pseudocode for basic items like constructors, accessors, mutators
• For each function, identify the following
  • Determine the parameters
  • Determine the return type
  • Detail the step-by-step logic that the function will perform

This will project will extend the basic logic and retain most of the requirements of Project Zero. Differences from Project Zero will be written in blue.

Details:

• Classes
  • Use good programming practice for classes – proper variable access, mutators and accessors, proper constructors, etc.
  • Remember that classes exist to be used by other people. Just because you don’t use it in the program doesn’t mean it shouldn’t be coded and available for others to use in theirs.
  • As with previous projects, you are open to design the classes as you see fit with the minimum requirements listed below
  • Both classes must be of your own design and implementation.

Requirements
▪ Linked list class (-10 points if missing)

• Named LinkList.java
• Members
  • Head pointer
  • Recursive print function
  • A sort function of your own design ▪ Node class
• Named Node.java
• Must be a generic class (-10 points if not)
• Payload variable
• Next pointer ▪ Player class (-5 points if missing)
• Named Player.java
• Design class to hold stats
  • Do not hold stats that are calculated from other stats
  • Use functions to calculate when needed
  • This prevents stale data
• Start the program by prompting the user for the input filename
  • This would normally be hardcoded in an application, but zyLabs requires a filename for multiple test files
• Nodes will be added to the end of the linked list
• Stats will be calculated for the following categories:
  • Batting Average (BA)
    • Batting average = hits / at-bats
  • On-base percentage (OB%)
    • On-base percentage = (hits + walks + hit by pitch) / plate appearances
  • Strikeouts (K)
  • Walks (BB)
  • Hit by Pitch (HBP)
  • Hits (H)
• Calculate all stats per person and record the highest value for each category
• There may be ties for the leaders
• If there is a tie, output all names for tied value
• All data must be held and manipulated in a linked list (-10 points if not)
• Any global variables used must be constant
• Use as few variables as possible

Input: All input will be read from a file. Each player’s data will be listed on separate lines in the file and will follow the same format.

• Format:
• Mario HOOKWSHHKOHPWWHO
• The name will be a single word.
• The batting record will be a series of capital letters representing various results during a baseball game
  • H – hit
  • O – out
  • K – strikeout
  • W – walk
  • P – hit by pitch
  • S – sacrifice
• Walks, sacrifices and hit by pitches are not considered an at-bat
• Batting records may contain invalid characters.
  • If an invalid character is encountered, disregard it
  • Invalid characters are not counted as an at-bat
• Each line in the file will end in a newline (except the last line of the file which may or may not have a newline)
• The batting record for each person may not have the same number of results
• The input file may have multiple entries for the same person o Combine that data into one node for the player

Output:

• All output will be written to a file – leaders.txt
• All values are displayed to 3 decimal places
• Display each player’s data in the following order with a tab between each field
  • Player name
  • At-bats
  • Hits
  • Walks
  • Strikeouts
  • Hits by pitch
  • Sacrifices
  • Batting average
  • On-base percentage
  • Write a newline after the on-base percentage (there is no tab before the newline)
• Output the player data by name in alphabetical order (A to Z)
• After the player data table, display an additional newline and the LEAGUE LEADERS header
• Display the top 3 leaders for each category
• Because of ties all places may not be awarded. o For example, if there is a 3 way tie for first, there would not be a second or third place. o When displaying the leader list, separate each name with a comma and a space
• League Leader Order
  • Batting Average
  • On-Base Percentage
  • Hits
  • Walks
  • Strikeouts
  • Hit By Pitch
• League Leader Output Format
  • CATEGORY newline
    • All caps
  • value _tab_first leader list _newline
  • value _tab _second leader list _newline
    • Second leader list is optional
    • No second place if first place has 3 or more ties
  • value_tab_third leader list__newline
    • Third leader list is optional
    • No third place if first or second place has a tie
  • newline