Stanford University Computer Science Department

Student Name - Poodle/Filler

Poodle/Filler

(Date Created: 2004-01-20, Last Modified: 2004-01-28, Author: Justin Manus)

Student	Functionality Score	Func. Bucket	Style Bucket	# Late Days
Student Name

Grading Criteria

Poodle, Milestone 1

(15 Points)

Load the student's Poodle.java file and do a little code inspection. This is the part of the assignment where they are supposed to just get the Poodle on screen. Note that this criteria is grade-down!

Points	Criteria description
	Poodle's body is in the correct place (i.e. correct constructor call). -0 for new DOval(10, 40, 200, 100); -1 for messing up some arguments -2 for no body object Score = 0 Score = -1 Score = -2
	Dummy points for grading down. Score = 15
	Poodle's front leg is in the correct place (i.e. correct constructor call). -0 for new new DOval(170, 120, 30, 30); -1 for messing up some arguments -2 for no front leg object Score = 0 Score = -1 Score = -2
	Poodle's back leg is in the correct place (i.e. correct constructor call). -0 for new DOval(20, 120, 30, 30); -1 for messing up some arguments -2 for no back leg object Score = 0 Score = -1 Score = -2
	Poodle's head is in the correct place (i.e. correct constructor call), and the head is properly initialized with "hennessy.jpg". -0 for new DImage(150, 5, 80, 80, "hennessy.jpg"); -1 for messing up some arguments (the first four ints) -1 for messing up the image parameter -2 for no head object Score = 0 Score = -1 Score = -2
	Making a new DWindow. Size can be anything as long as the entire scene is visible. -0 for correctly making a DWindow (and storing the variable) -2 for screwing this up in some way Score = 0 Score = -2
	Adding the four poodle objects to the window. -1 for each object they didn't add. Score = 0 Score = -1 Score = -2 Score = -3 Score = -4
	Section Total

Poodle, Milestone 2

(15 Points)

They are supposed to do the wand animation part here.

Points	Criteria description
	Dummy points for grading down Score = 15
	Does a window.waitClick to wait for the user. -0 if this is done -1 if this is not done Score = 0 Score = -1
	Wand is in the correct place (i.e. correct constructor call), and the head is properly initialized with "wand.png". -0 for new DImage(400, 10, "wand.png"); -1 for messing up some arguments (the first four ints) -1 for messing up the image parameter -2 for no wand object Score = 0 Score = -1 Score = -2
	Wand added to the window -0 if wand is added to the window -1 if the wand is not added to the window Score = 0 Score = -1
	Wand animation. 1 point for each step (x=400, 350, 300, 250, 200) -0 if wand.setX is correctly called and DWindow.waitSeconds is correctly called for the appropriate x value -1 if this is screwed up somehow. Score = 0 Score = -5
	Removes the wand from the window when x = 200 -0 does the removal -3 does not do the removal Score = 0 Score = -3
	Changes the head graphic to "bunny.jpg" -0 for calling head.setImage("bunny.jpg"); or removes the head object and replaces it with a new DImage containing "bunny.jpg". -3 for not doing this Score = 0 Score = -3
	Section Total

Filler, Milestone 1

(7 Points)

Load the Filler.java file and make sure their constructor has the filler2.world world specified. Run the program and observe, then run it with filler.world.

Points	Criteria description
	Dummy points for grading down. Score = 7
	Creates a new Binky, specifying a world (can be either filler.world or filler2.world). -0 for correctly creating a new Binky and storing a pointer to it. -2 for screwing this up Score = 0 Score = -2
	Moves Binky to the end of the cliff correctly (i.e. uses the code from class) -0 for moving Binky correctly to the end of the cliff in both worlds -2 for missing the case where Binky is already at the cliff. -4 for screwing this up in some way -5 nothing there Score = 0 Score = -2 Score = -4 Score = -5
	Section Total

Filler, Milestone 2

(13 Points)

Continuing with the second part of Binky's problem.

Points	Criteria description
	Dummy points for gradng down. Score = 13
	Colors all squares in the gap Color.RED -0 correctly does this -4 attempts this and screws up (off by one, etc.) -6 nothing there Score = 0 Score = -4 Score = -6
	Turns binky around at the bottom of the gap. -0 for turning Binky around -3 for not turning Binky around Score = 0 Score = -3
	Moves Binky back to the top of the gap. -0 for moving Binky back to the top. -3 for screwing this up (gettin a BadBinkyMoveException, etc.) -4 nothing there Score = 0 Score = -3 Score = -4
	Section Total

Extra Credit

(8 Points)

I have no idea what kinds of things people might do here, so please ask me before giving out any extra credit!

Points	Criteria description
	Write what they did here, and give them points Score = 0 Score = 8
	Section Total

Style Grading

Score

Style Criteria

Style is now going to be graded using great flexibility on your part.
We're relying on your gut instinct here, so make sure that gut is
trained up well!

Basically, you are to place each program into one of the three style
buckets based on how well you think they solved the program. Remember
that many things count towards this grade - design, readibility,
comments.... it all matters. However, try not to let your pet peeves
weigh in too much to your decision (you know what I mean).

For a general idea of what kind of program should fall in each bucket,
take a look at the Administrivia handout.

Guidelines
------------
Below is a series of guidelines that I have generated for things you
might want to look for. It's by no means inclusive, but should help
you out a bit in making your decision and classifying programs. Also, some of the general guidelines are more general than you'll need for HW1, but just keep them in mind for later.

If you have more questions about style, send the program to me and I'll
give you my read on it - I trust you guys a lot, so I'll back you up on
this stuff if you need to take a hard line.

General
-------
MAJOR ERRORS
--------------
- Poor decomposition of the problem

MINOR ERRORS
--------------
- Undescriptive method names
- Undescriptive variable names
- Bad whitespace use
- Bad brace matching
- Bad indentation
- No commenting inside code itself
- Unsimplified code

JUST MENTION
------------
- No commenting / Grossly inadequate commenting
- Code off the end of the page (just a warning!)

Poodle/Filler SPECIFIC
--------------------

MAJOR ERRORS
------------
- (I can't think of anything they could do here! If you see something that you think is heinous, just email me.)

MINOR ERRORS
------------
- Bad variable naming

JUST MENTION
------------
- Code is missing their name or the name of their SL.

Style conversion to buckets:
----------------------------
This is a rough guide to converting stylistic probelms to the buckets
we have. If you need to wiggle up or down, just do it - I trust you all.

2-3 Minor Errors = 1 Major Error

Bucket Major Errors
------ ------------
V+ < 1
V 1-2
V 2+

Style Comments:

Style Grade: Check Minus (V-), Check (V), Check Plus (V+)

Overall Comments:

Student	Functionality Score	Func. Bucket	Style Bucket	# Late Days	Save
Student Name

If you have any problems or questions, go ahead and mail the yahoos. We love mail.
If you have received an error message on this page, include its text in your correspondence.