home—info—archive—exams—lectures—labs—hws
Recipe—Laws—lies—syntax—java.lang docs—java.util docs
Homeworks
If you're wondering about some of the markup on your returned papers,
check out
the general grading guide (w/
greek letters),
and also
common
proofreader marks.
-
hw12—Finishing loops: loops calling loops, due Apr.25 (Fri).
part (a) solution
and PlayLists.java.
-
Extra-credit, due Apr.25 (Fri).
Any of the following labs/assignments used in previous semesters1:
-
hw11—loops: exam re-do; short-answer, short-programs, and
full soln.
-
hw10—Playlists: for-each; input, and
soln for (a),
PlayList.java,
.jar,
-
hw09,
and solution: Song.java,
.jar
-
hw08—Unpredictable EmCees: mult. choice; non/static methods
(Part (a) will be accepted on both Friday and Monday.)
As preparation for next Friday's exam2,
hw08 has a larger part (a) than usual, and smaller parts (b),(c) than usual.
hw08a,b,c solution
-
There will be a couple more extra-credit homeworks.
-
(No homework for spring break, woo-hoo!
Though be ready to start hw08 when you get back, since
it will be larger than the last couple of homeworks.)
-
hw07—Objects containing objects: Students with Dates
hw07a,b,c solution
with a drawing
-
hw06a,b,c
hw06a solution
-
hw05b,c
(because of exam, hw05a is extra-credit which you can turn in Monday)
hw05 solution
-
hw04—quotient and remainder
hw04a,b,c solution
-
hw03—booleans, if: volleyball
hw03 solution (b,c solutions are
linked at the bottom of that solution set)
-
hw02—functions, and Strings: shortened greetings
hw02 solution
-
hw01 a,b,c: a first program
hw01 solution
(Don't look until you've turned it in, of course!)
Instructions for submitting
- Part (a) (short-answers) are due hard-copy only;
parts (b) (test cases & signatures) and (c) (working code)
are due both as hard-copy and electronically via Blackboard.
Always due at start of class on the due-date.
-
Your file should include
your name, the assignment-number,
and your 120 section (e.g. “10:00”)
at the top of your file, in comments.
Also, if your function does not work completely,
say so clearly at the top (in comments).
You get more points for knowing what your program doesn't do,
than not knowing.
(Submitting code which doesn't compile, without acknowledging such,
may result in a summary 0.
In the workplace, it is unacceptable.)
-
If the gradebook in WebCT lists a homework but your score is empty,
then it means I think you didn't turn it in.
(Note that if I haven't released a column to the gradebook section
of WebCT, then I haven't yet finished grading for that assignment.)
It is your responsibility to report any missing scores in the gradebook.
-
Moreover: Any empty gradebook entry
which is not reported within three weeks of appearing in the gradebook
is liable to not be graded, and you will get a 0.
(Otherwise I have too many students suddenly needing regrades
in the last week, of assignments I'd graded months earlier.)
- Spelling and punctuation counts (in your comments).
The first such error is okay, but -1/2 for every error after that.
(Sentence fragments, though, can be acceptable if the context is clear.)
1Note
that the current semester is only 14 weeks long, not 15 weeks as in the past ↩
home—info—archive—exams—lectures—labs—hws
Recipe—Laws—lies—syntax—java.lang docs—java.util docs
rad�ford.edu