Decide how we want to create a use case diagram. What did you guys use for that assignment.

I used Draw.io. Its not super great, but not awful. Basically a rich editor to draw lines and stuff which can create a pdf we can put in the repo.

The constructor is missing a javadoc

• 50% of backlog should be complete
• Update Docs to reflect code changes
• Create Docs for how to Build and Play
• Create Unit Tests
• Create Instructions for Functional GUI Tests (This would be a check list of what a QA team would need to do to ensure the GUI elements are working as expected.)

make sure you address what should be happening when you press start without creating a character.

I think the trello needs to be public so they can grade the backlog

Game

• A way to 'hitTheBall' for a player
• A method to determine which player's turn it is (currently 2 methods, both don't work)
• Method to go to the next hole
• Getter for the current hole number
• A way to get each players distance from hole
• A way to get strokes of individual players

Stats

• Store hits per player per hole
• Store stats and players persistently (load them on startup, save them on close)
• Store wins per hole per person (and make a getter for david)

Housekeeping

• Update Javadocs / Create Javadocs
• Make code meet coding standards
• Update Unit Tests / Create Unit Tests

This is how the game will be played:

Launch App
Create Players (You can't start without creating at least one)
Click Play Button
Choose Number of Holes (anything > 1)
Each hole will be a random distance
Each player will take turns (furthest away goes soonest)
Once each player scores there will be a next hole button
Upon finishing all holes a sort of scorecard will be displayed. Bare minimum this must display total number of hits and who won. It would be nice (and not hard) to be able to display a scorecard thing that would show how many hits it took each player on each turn see generic golf scorecard (Of course we wouldn't have a par)
Thats it.

What this would entail from the logic:

Either set the number of holes or dynamically expand the statistics data once a method is called to go to the next hole
Calling the method to go to a hole should create a randomly distanced hole
There should be a method to determine who's turn it is
Taking a turn should either assume it is the person's turn who the method above specifies or take in the index of the person

Additionally for the players:
There must be a way to add players
There must be a way to store player names
There could be a way to store player colors (I'll do this if I feel like it)
There must be a way to get the player names
Player names must be stored on the disk and loaded upon startup.

For the scorecard:
There needs to be a way to get all of the data which would be on the scorecard.
This all needs to be stored and loaded upon startup.

Additionally

EVERYTHING NEEDS TO BE TESTED, JUNIT TESTED MAKING A MAIN METHOD DOESNT COUNT!!

NO 1 LETTER VARIABLES

NO BREAKS/RETURNS IN LOOPS, NO RETURNS BEFORE THE END OF THE FUNCTION (I'm slightly guilty of this too, I'll need to revise my code a bit)

DOCUMENTATION!!

• 100% of backlog should be complete
• Project Description's features should be implemented
• There should be thorough unit test coverage
• All docs should be up to date

• Come up with idea for what we are doing
• Create Backlog
• User Stories
• Use Case Diagram
• Everyone makes 1 commit to this repo

This is when calling currentPlayer() after it. Related to the fact that roll() and hitTheBall() aren't player specific and probably don't modify the correct data structures.