Lab 5

At the bottom is a .cpp file containing some non-functional Tic-Tac-Toe code.  In the process of refactoring it, the functionality was broken.  It's your job to go through and fix all the problems with it.  Also attached at the bottom is the beginnings of a bug report.  As you make fixes, add the bugs to the bug report, so that others can review the changes you made, and you can justify the decisions you came to.

The format for the bug report is as follows:

1. LineNumber:  Original Line

                        Replacement Line

                        Sentence describing error and fix, related numbers

You must specify the line number in the original document of which line(s) you changed, the line(s) you replaced it with, and provide a description of why you changed it.  Whether or not it's an obvious change, be descriptive with why you changed it.  If you are applying this fix due to something you changed elsewhere, provide the numbers of those fixes so the reader can cross-reference your changes.

An example is given in the text document, and ask if you need further clarification.

• Stage 1: Identify at least 5 errors in the program.

• Stage 2: Get the Tic-Tac-Toe program completely working.  

  • I had to fix about 10 errors to get it into working order, (11, but it depends on how you count), but the number isn't as important as the program being entirely functional, and your description of what you fixed and why.  Note that there is more than one way to go about this.

• Stage 3: Get the program entirely functional, and identify a further 5 minor bugs.  

  • These are things which do not impact correctness of the program, but should be modified for good coding style.  This means eliminating unnecessary parts of the code or making the code more efficient.  Note that changing a function parameter type and then the function call counts as a single bug.  Provide as many as you can, and if you reach 5 unique bugs you'll get the points.  As a note, I have 11 minor bugs listed, but it depends on how you decided to fix the program.  Once again, descriptions are key, tell me why you made the modifications.

Once again, it is highly recommended that you work with a partner, as the errors can be tricky, but be sure you understand why things are wrong, and why the change fixes them.  You will be asked to submit your files at the 50 minute mark, so be sure you're keeping both files up to date as you go, so you can submit at that time.  Everyone will need to leave the lab by 55 after, so be sure you turn in on time.  If you can't turn in by the end of lab, you can turn in by noon on Friday at a 1 point penalty, and I'll expect a good job.

Submit both the fixed .cpp file, and the text file with names at the top in the right format to Blackboard.  If you don't submit the text file in the specified format, you will receive no credit for this lab.