Expertiza_Wiki - User contributions [en]

CSC 216 F09/Debugging Scavenger Hunt

2009-11-18T05:00:49Z

Sjlouder:

==Debugging Scavenger Hunt==
By: Steven Loudermilk and Shane Oaks

===Introduction===

This exercise will help students get used to debugging and the debugging techniques/processes of many IDEs. It also gives students a realistic task that they will most likely come across during their programming career. However, it is best utilized once students are familiar with the basics of a debugging environment, not as an introduction.

===Materials===

For this exercise, you will need: 
-The source code of a rigged program 
-Java IDE

===How To Play===

Students are given the source code to a program. The code will contain comments that explain the intended function of the variables, methods, etc., however will have many different kinds of errors. From this, they are given the task of finding the errors, and correcting them. The first team that can produce the intended output wins!

===Source Code===

The source code should have errors that deal with many different types of debugging problems, for example:

-A loop where the second-to-last run produces a division by zero. In order to make this more difficult to detect, have the loop contain a trig function (sin(x), cos(x), etc) 
-A function that calls a variable in another class that is declared as private 
-A GUI where one of the elements isn't lined up correctly 
-An arrayOutOfBounds() exception 
-etc.

CSC 216 F09/Debugging Scavenger Hunt

2009-11-18T04:57:24Z

Sjlouder:

==Debugging Scavenger Hunt==
By: Steven Loudermilk and Shane

===Introduction===

This exercise will help students get used to debugging and the debugging techniques/processes of many IDEs. It also gives students a realistic task that they will most likely come across during their programming career. However, it is best utilized once students are familiar with the basics of a debugging environment, not as an introduction.

===Materials===

For this exercise, you will need: 
-The source code of a rigged program 
-Java IDE

===How To Play===

Students are given the source code to a program. The code will contain comments that explain the intended function of the variables, methods, etc., however will have many different kinds of errors. From this, they are given the task of finding the errors, and correcting them. The first team that can produce the intended output wins!

===Source Code===

The source code should have errors that deal with many different types of debugging problems, for example:

-A loop where the second-to-last run produces a division by zero. In order to make this more difficult to detect, have the loop contain a trig function (sin(x), cos(x), etc) 
-A function that calls a variable in another class that is declared as private 
-A GUI where one of the elements isn't lined up correctly 
-An arrayOutOfBounds() exception 
-etc.

CSC 216 F09/ VisualExceptionHandlingExercise

2009-11-18T04:54:40Z

Sjlouder:

==Exercises==

===Data Structures===

[[CSC 216 F09/Data Structure Jeopardy|Data Structure Jeopardy]]

===Debugging===

[[CSC 216 F09/Debugging Scavenger Hunt|Debugging Scavenger Hunt]]

===Exceptions===
[[Visual Exception Handling Excercise]]

===GUIs===

[[CSC 216 F09/javicimo|Javicimo]]

[[CSC 216 F09/ActionListener|ActionListener Charades]]

[[CSC 216 F09/Who want to be Millionaire|Who want to be Millionaire]]

===Inheritance===

[[CSC 216 F09/Inheritance-Polymorphism|Inheritance-Polymorphism]]

===Interfaces===

[[CSC 216 F09/Interfaces1|Interfaces-Comparing Similarities Among Different Types of Objects]]

===Other===

[[CSC 216 F09/Who Wants to be a CSC Major|Who Wants to be a CSC Major]]

[[CSC 216 F09/Java Pursuit|Java Pursuit]]

===Polymorphism===

[[CSC 216 F09/polymorphism showdown|Polymorphism Showdown]]

===Recursion===

[[CSC 216 F09/Recursion Exercise|Recursion Exercise]]

CSC 216 F09/Recursion Exercise

2009-11-18T04:37:22Z

Sjlouder:

==Background==
This is a simple exercise for finding recursive equations and writing them as Java code.

===Props===
1. Whiteboard

2. Access to a Java editor

===Procedure===

1) Give each row a sequence of numbers.

Ex:

a) 2, 6, 10, 14,...

b) 0, 1, 0, 1...

c) 2, 6, 12, 20...

d) 1, 4, 9, 16...

2) Then have each row work together to find the recursive definition for the sequences.

Ex:

a) 4n-2

b) 1+(-1)^n

c) n(n + 1)

d) n^2

3) Lastly, each group should write Java code to implement the recursive equation and submit via Google Docs.

Ex:

a)

public int recursion( int n ){
int a = 0;
if(n == 1) a = 2;
else a = recursion( n - 1 ) + 4;
return a;
}

By: David Duran & Dereck Allred

CSC 216 F09/ VisualExceptionHandlingExercise

2009-11-18T04:34:18Z

Sjlouder:

[[Visual Exception Handling Excercise]]

[[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/polymorphism_showdown Polymorphism Showdown]]

==Exercises==

===Inheritance===

===GUIs===

[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/javicimo Javicimo]

===[[CSC 216 F09/Data Structure Jeopardy|Data Structure Jeopardy]]===

===[[CSC 216 F09/Who Wants to be a CSC Major|Who Wants to be a CSC Major]]===

===[[CSC 216 F09/Interfaces1|Interfaces-Comparing Similarities Among Different Types of Objects]]===

===[[CSC 216 F09/ActionListener|ActionListener Charades]]===

===[[CSC 216 F09/Who want to be Millionaire|Who want to be Millionaire]]===

===[[CSC 216 F09/Inheritance-Polymorphism|Inheritance-Polymorphism]]===

===[[CSC 216 F09/Java Pursuit|Java Pursuit]]===

===[[CSC 216 F09/Debugging Scavenger Hunt|Debugging Scavenger Hunt]]===

[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/ Recursion Exercise]

CSC 216 F09/Debugging Scavenger Hunt

2009-11-18T04:29:51Z

Sjlouder:

===Introduction===

This exercise will help students get used to debugging and the debugging techniques/processes of many IDEs. It also gives students a realistic task that they will most likely come across during their programming career. However, it is best utilized once students are familiar with the basics of a debugging environment, not as an introduction.

===Materials===

For this exercise, you will need: 
-The source code of a rigged program 
-java IDE

===How To Play===

Students are given the source code to a program. The code will contain comments that explain the intended function of the variables, methods, etc., however will have many different kinds of errors. From this, they are given the task of finding the errors, and correcting them. The first team that can produce the intended output wins!

===Source Code===

The source code should have errors that deal with many different types of debugging problems, for example:

-A loop where the second-to-last run produces a division by zero. In order to make this more difficult to detect, have the loop contain a trig function (sin(x), cos(x), etc) 
-A function that calls a variable in another class that is declared as private 
-A GUI where one of the elements isn't lined up correctly 
-An arrayOutOfBounds() exception 
-etc.