Compsci 108, Fall 2005, Project Handin
Each group should turn in hard copy of all code and all
supporting documentation, but not javadoc. This should all be
available from the group website as well (including javadoc). Turn
this in when you meet with me.
- Group 1, Wed 7:00 pm
- Group 2, Thu 10:00 pm
- Group 3, Tue 10:30 pm
- Group 4, Wed 10:00 pm
- Group 5, Wed 8:00 pm
- Group 6, Mon 10:30 pm
- Group 7, Wed 9:00 pm
- Group 8, Thu 5:00 pm
To print your code 2-up you can upload your project to your acpub/oit
space, then cd into the directory where your code is and run this
This will print all .java files in any directory below the one in which
you invoke the command. The single file of output will be sent to an
Here's the script if you want to run it yourself or modify it.
set psfile = "printout.ps"
set login = `whoami`
set printcommand = "a2ps -E -C -2 -o $psfile --left-footer=$login --file-align=fill"
find . -name "*.java" | xargs -t $printcommand
What to Hand In
Please turn in all documentation either bunched together by a giant
binder-clip, in a three-ring binder, or in some way that keeps the pages
together. Please include the group number and names of all group
members on a title page.
The final group project will have 5% of the grade based on individual
assessments of the group and each group member. Each member of the group
should create a text file (word is ok) in which the following questions
are addressed/answered by assigning both reasons and a number. The
numbers are on a 1-5 scale, with 5 meaning extraordinary, 4
meaning very good, 3 meaning acceptable, 2 meaing
needs improvement, understandable, 1 meaning inadequate,
very poor. Please provide a justification for each of your
numerical evaluations. Note that an evaluation of 5 is
extraordinary. I welcome such evaluations, but I expect such
evaluations to be backed by achievement commensurate with the
evaluation. Remember, however, that you had only a short time to
complete the project, so a 5 is certainly possible without having a
masterpiece as your project's final outcome.
Please email your assessment/evaluation to ola AT duke.edu as an
attachment or in the body of the email with the subject 108 final
The completeness of this evaluation contributes 5% to your individual
final project grade and, if everyone completes it satisfactorily, adds a
bonus of 5% to your final grade. Any group member whose self-evaluation
is completely out-of-synch with the evaluation provided by all other
group members should ask "why?" and be prepared for me (ola) to ask the
- Overall group performance, address each of the following with
a separate number/evaluation.
- Final product (what was actually produced).
- Final vision (what you think you could produce with more time, with
the same level of effort done so far).
- Final teamwork (how well you worked as a group).
- Your own contributions to the group: please make clear what you
contributed in terms of group ethos, vision, code, support,
etc. Make sure you evaluate your contribution on the 1-5 scale
and provide solid evidence for your assessment.
- Each member of the team's contribution on the 1-5 scale with an
Owen L. Astrachan
Last modified: Mon Dec 12 10:55:33 EST 2005