CSC 160
Homework 6

Assigned Mar 20, due Apr 1

Pair Programming

As before, you are encouraged to do this assignment in a two-student team, following the principles of Pair Programming. If you've worked with the same partner for the last several assignments, see if you can find somebody different to work with: you'll both learn more that way.

There are 20 problems, but 9 of them are "practice" or "worked" exercises for which you don't need to turn anything in; just do them to make sure you're comfortable with the topics before trying to do the "turn-in" problems. You have 9 days, so that's roughly two problems per day, half of which are to be turned in. Start early!

Problems


What to turn in and how

All of these are programming problems, except that 11.3.6 asks you to use the function you wrote in 11.3.5 to answer some other questions. I recommend putting all of the programming problems in one big Definitions pane, because some of them depend on others.

Send me an e-mail, attaching the file containing your saved Definitions pane. (Make sure to save it, then test it, then e-mail it to me, or I may end up grading an out-of-date version.) Make sure to put your name(s) in the Subject line!

If there's a particular function that you can't get working, turn in as many steps of the recipe as you've managed to do, commented out (so they don't mess up the other functions).

Also turn in a log of how many errors of different kinds you encountered in the assignment, with brief comments describing each one ("mismatched parentheses" is self-explanatory, but more complex errors might need more description). Note that "errors" means not only error messages from DrScheme, but also wrong answers. You may do this using the PSP forms, or simply by keeping track in a text file or on paper and turning it in.

Grading standards

In order to get you feedback quickly, I won't actually grade all of these problems; I haven't decided yet which ones I'll grade, but it'll include some easy ones and some hard ones.

Error log:       25 points
(I'm not grading on how many or how few errors you encountered, only on whether you recorded them correctly.)

The table below has columns for each step in the design recipe, and a row for each function that I decide to grade. You won't turn in a separate skeleton, inventory, and body, but rather write a skeleton and then add inventory and body to turn it into a complete definition. However, if you don't get the definition working, you'll still get partial credit for a correct contract, skeleton, and/or inventory.

Function Contract Examples Skeleton Inventory Body
whatever /5 /5 /5 /5 /15
Some especially complicated functions will be worth more points.

General skills:

Following directions /10
Writing contracts from word problems /10
Choosing examples /10
Choosing names, indentation, white space... /10
Coding /10
Code re-use and function composition /10

Total:         /???


Last modified:
Stephen Bloch / sbloch@adelphi.edu