The main goals for this lab are for you to get more comfortable with loops and 2-D arrays. In this lab we are going to implement tic tac toe! By the end of this lab you will have a program that will allow two people to play tic-tac-toe.
This lab is a paired programming assignment. What exactly does that mean? You will be working in pairs on the CS lab computers. Each pair will be working on one computer. One person will be the driver and the other person will be the navigator. Here is the rule: the driver controlls the lab computer, but the driver can only type what the navigator tells them to type. For this to work well, each pair should be constantly talking among themselves. After each problem, you will switch roles, the navigator will become the driver and the driver will become the navigator.
Partners You must work with your partner last week. If your partner is not here (or you did not switch last week, let your instructor know). This week will be the last time you work with this partner this semester. Next week you will switch partners again.
Before leaving the lab, make sure you fill out the attendance sheet and go through your answers with a TA or instructor.
Lets begin by making sure you are familiar with tic tac toe. If you arent, briefly look at wikipedia.
Play 3 games of tic-tac-toe with your partner.
Question: 1.1 Out of the three games, who won the most?
When designing a program, its a good idea to take a top-down approach. In a top down approach, we use the following steps:
Before we begin implementing tic-tac-toe, lets follow the steps of our top down approach.
What are the features necessary for tic-tac-toe. Some ideas to consider are what do we need to keep track of what, what does each player need to do, when does the game end? So on and so for.
TODO: 2.1.1: Below, write out the list of features that this program needs for 2 users to play tic-tac-toe.
After listing our features, we need to figure out which of our features should be variables and which of the features should be methods.
TODO Question 2.2.1: How do we figure out which features are methods, and which are variables?
TODO Question 2.2.2: Now, in the space below, write out which features we should represent as variables and which feature we should implement as methods.
DO NOT GO ON IN THIS LAB WITHOUT SHOWING AN INSTRUCTOR YOUR ANSWERS SO FAR. OTHERWISE YOU WILL NOT GET FULL POINTS FOR THIS LAB!
MAKE SURE YOU WROTE OUT ALL OF YOUR ANSWERS TO ALL OF THE QUESTIONS ABOVE.
Now that we outlined what our methods and variables should be, we can go ahead and sketch out the major steps of the program. In esence, we are outlining how the features should fit together.
TODO Question 2.3.1: List out the steps for your algorithm. I’ll start by giving the first three steps (you will likely have more than 6 steps):
After you write out the algorithm by hand (or if you get stuck writing out the algorithm), play tic-tac-toe again with your partner, but this time follow every step in your algorithm. This will help you find errors and mistakes in your algorithm.
TODO QUESTION 2.3.2: How did your algorithm above change when you played tic-tac-toe with your partner using the algorithm you came up with.
DO NOT GO ON IN THIS LAB WITHOUT SHOWING AN INSTRUCTOR YOUR ANSWERS SO FAR. OTHERWISE YOU WILL NOT GET FULL POINTS FOR THIS LAB!
MAKE SURE YOU WROTE OUT ALL OF YOUR ANSWERS TO ALL OF THE QUESTIONS ABOVE.
Before we write out our methods in our code, its important think about what type of variables should we use. The most complicated variable we will need to keep track of is the board.
TODO: Question 2.5.1: What type of variable should we use to represent our board?
Now that we have convinced ourselves that we have a sufficient algorithm for implementing tic-tac-toe, its time to start programming! But, we dont want to program everything at once, instead we will implement one method at a time.
Lets begin by writing out the skeleton of the program. A skeleton of a program is a list of method stubs (these are placeholders for our functions).
TODO: Question 2.6.1: What is different about a method stub compared to an implemented method?
TODO: Question 2.6.2: Now go ahead and write out the skeleton of the program called TicTacToe.java. Make sure to have a method stub for each of the methods (verbs) you identified in 2.2.
DO NOT GO ON IN THIS LAB WITHOUT SHOWING AN INSTRUCTOR YOUR ANSWERS SO FAR. OTHERWISE YOU WILL NOT GET FULL POINTS FOR THIS LAB!
MAKE SURE YOU WROTE OUT ALL OF YOUR ANSWERS TO ALL OF THE QUESTIONS ABOVE.
Now that we’ve written out our skeleton, we can implement each method.
TODO: Question 2.7.2: In your java program, now implement each method. When you implement one method, make sure to test it in the main method.
Congrats! you have impelemnted TicTacToe and can play with your partner!
NOW TRY BEATING YOUR INSTRUCTOR!
DO NOT GO ON IN THIS LAB WITHOUT SHOWING AN INSTRUCTOR YOUR ANSWERS SO FAR. OTHERWISE YOU WILL NOT GET FULL POINTS FOR THIS LAB!
MAKE SURE YOU WROTE OUT ALL OF YOUR ANSWERS TO ALL OF THE QUESTIONS ABOVE.
We can add bells and whistles to our `TicTacToe.java.
Here are some options to consider:
So far we only implemented one round of tic-toc-toe, how can we modify our program such that 2 users can play multiple rounds?
Our implementation requires two users. However, sometimes we might not have any friends who want to play with us. Add an option for a user to play against a computer. Now we need to make choices for a computer.
I’d recommend starting by implementing a naive computer that just chooses squares at random.
In todays lab we covered arrays and top-down design.
Before leaving, make sure your TA/instructor have signed you out of the lab. If you finish the lab early, you are free to go.