CS173: Intro to Computer Science - Debugging Table (10 Points)

The Assignment

Debugging Table

Please submit to your class notebook your Debugging Table. The Debugging Table is a list of errors, which you can write down or screen-shot, along with an explanation of the error and how you fixed it. The format is up to you, but a reasonable entry might look like this:

Example.java:5: error: cannot find symbol
                System.out.println(y);
                                   ^
  symbol:   variable y
  location: class Example

I had initialized a variable x in the following example, but accidentally printed a variable called y.  
Since y didn't exist, the print statement on line 5 of my Example.java file failed.  
I changed this to print x instead, and it worked!

int x = 99;
System.out.println(y);

You should have one such entry for each new error that you encounter.

Submission

In your submission, please include answers to any questions asked on the assignment page in your README file. If you wrote code as part of this assignment, please describe your design, approach, and implementation in your README file as well. Finally, include answers to the following questions:
  • Describe what you did, how you did it, what challenges you encountered, and how you solved them.
  • Please answer any questions found throughout the narrative of this assignment.
  • If collaboration with a buddy was permitted, did you work with a buddy on this assignment? If so, who? If not, do you certify that this submission represents your own original work?
  • Please identify any and all portions of your submission that were not originally written by you (for example, code originally written by your buddy, or anything taken or adapted from a non-classroom resource). It is always OK to use your textbook and instructor notes; however, you are certifying that any portions not designated as coming from an outside person or source are your own original work.
  • Approximately how many hours it took you to finish this assignment (I will not judge you for this at all...I am simply using it to gauge if the assignments are too easy or hard)?
  • Your overall impression of the assignment. Did you love it, hate it, or were you neutral? One word answers are fine, but if you have any suggestions for the future let me know.
  • Any other concerns that you have. For instance, if you have a bug that you were unable to solve but you made progress, write that here. The more you articulate the problem the more partial credit you will receive (it is fine to leave this blank).

Contract Grading

To Receive an A

  • At least five new entries are made into the Debugging Table
  • Each entry contains a description of the error, and a brief explanation about how to fix the error
  • At least 80% of the explanations on how to correct the errors are correct

To Receive a B

  • At least three new entries are made into the Debugging Table
  • Each entry contains a description of the error, and a brief explanation about how to fix the error
  • At least 70% of the explanations on how to correct the errors are correct

To Receive a C

  • At least two new entries are made into the Debugging Table
  • Each entry contains a description of the error, and a brief explanation about how to fix the error
  • A reasonable effort is made to describe how to fix each of the errors encountered, even if the explanation is incorrect

To Receive a D

  • At least one new entry is made into the Debugging Table
  • The entries do not contain both a description of the error and a brief explanation about how to fix the error

Please refer to the Style Guide for code quality examples and guidelines.