Spring Semester 2006: January 30, 2006 - May 5, 2006
Out on:
April 28, 2006
Due by:
May 5, 2006 by 5:59 pm for full credit (11:59 pm for 10% off, hard deadline)
Collaboration:
Teams
Grading:
Packaging 10%, Style 10%, Performance 20%, Design 20%, Functionality 40%
The twelfth assignment for 600.226: Data Structures once again deals with maps of Baltimore. This is the last installment of your "big project" and also the final assignment in the course. Best of all: It's completely up to you what you spend your time on for this assignment! You must have all the features that were required for Assignments 10 and 11 of course, but what you do beyond those features... Surprise us! :-) And if your assignment didn't work before, now is the time to get all those bugs fixed!
This is a team assignment, and all of you should
know which team you're in (I hope).
Each team hands in one assignment!
Decide early on who is going to be responsible for submitting the
assignment and when.
Make sure to include all the relevant information (who is in the
team?) in your README file!
All members of a team will receive the same score for the product
you submit together.
Please turn in a
gzip
compressed
tarball
of your assignment;
the filename should be
cs226-assign-12-teamcode.tar.gz
with teamcode
replaced by the code assigned to your team for your repository
and your mailing list.
The tarball should contain no derived files whatsoever
(i.e. no .class files, no .html files, etc.),
but allow building all derived files.
And your tarball should definitely not contain copies of
the data files, but instructions of where we have to put them for
your code to find them.
Include a README file that briefly explains what your
programs do and contains any other notes you want us to check out
before grading.
For reference, here is a short explanation of the grading criteria.
Packaging refers to the proper organization of the
stuff you hand in, following the guidelines for Deliverables above.
Style refers to Java programming style, including
things like consistent indentation, appropriate identifiers,
useful comments, suitable javadoc documentation, etc.
Simple, clean, readable code is what you should be aiming for.
Performance refers to how fast your program can
produce the required results compared to other submissions.
Design refers to proper modularization and the
proper choice of algorithms and data structures.
Functionality refers to your programs being
able to do what they should according to the specification
given above; if the specification is ambiguous and you had
to make a certain choice, defend that choice in your
README file.
If your programs cannot be built you will get no points whatsoever.
If your programs cannot be built without warnings using
javac -Xlint
we will take off 10% (except if you document a very good reason).
If your programs fail miserably even once,
i.e. terminate with an exception of any kind,
we will take off 10%.
This project is based on a similar assignment by
Prof. Dr. Jason Eisner:
Thanks a bunch for the inspiration! :-)
You are free to read
Jason's assignment
which contains lots of advice and background information
that I am not providing.
However, remember that you are doing this
version, not Jason's version.
If you use any of Jason's ideas, please give proper credit in your
README file.