home—info—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.
-
extra-credit homework:
Converting Explorer pockets to backpacks;
due Apr.20
-
extra-credit homework:
the cost of gas (static, and methods calling methods;
due Apr.27)
-
hw10: connecting rooms
(due Apr.27 (Fri) 17:00); no late turn-ins after midnight)
If you want your program to use Rooms and Treasures from
the wiki,
you'll need to download and add Entry.java to your project.
See the comments at the start of that file for further instructions.
-
hw09: interactive explorers
(due Apr.18 (Wed) 17:00))
Solution:
files
jar
(Apr.25 15:00
Fixed so that select won't loop forever on empty lists)
For your amusement: a GuiIO.java,
which is exactly like a TextIO, but different.
However, it requires lab15's
superclass
-
hw08: Rooms to explore
(due Apr. 09 (Mon) 17:00))
code source files (including test cases),
code .jar file
(how to get .jar files into BlueJ)
-
hw07: a list of questions
soln
-
hw06: Explorerss
soln to short-answers,
code source files (including test cases),
code .jar file
(how to get .jar files into BlueJ)
-
extra-credit homework:
eBayFees revisited.
-
extra-credit homework:
ClockDisplay as 12-hour clock internally
-
hw05: ClockDisplay:
objects containing objects; top-down design.
hw05soln's
ClockDisplay.java and
ClockDisplayTest.java tests.
-
hw04: Treasures: calling
constructors.
hw04-soln
- Extra credit: body mass index
(functions calling functions, if-else-if).
-
hw03: Dogs: objects with state.
hw03-soln
-
Practice problems: Comparing dates:
part 1 (.doc),
part 2 (.doc), and
soln (.doc).
-
hw02: VolleyballJudge: local variables; booleans.
solution
-
hw01: TempConverter: calling functions (from functions)
solution,
grading guide,
-
hw00: introductions; finger exercises
Instructions for submitting
- Always turn in both a hard copy, and submit on WebCT.
Leaving off either step will delay your grading,
and may result in 10% penalty.
-
Your file should include your name and the assignment-number
at the top (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.)
home—info—exams—lectures—labs—hws
Recipe—Laws—lies—syntax—java.lang docs—java.util docs
rad�ford.edu