Oodle Final Details

The following options for oodle are acceptable in terms of meeting the requirements. All oodlers are invited to add additional functionality, but the criteria below will satisfy the original oodle specs (be sure to read the original oodle specs!)

oodle -i
interactive oodle as in stage 2, user gets to choose where to go and how to sort
oodle -log dirname
the directory 'dirname' is, recursively logged for subsequent diff with oodle
oodle -diff dirname
differences between current dirname (recursively) and last logged dirname are displayed as described in the oodle stage 3 assignment

It's ok to require that dirname match exactly, and not be a subdirectory logged as part of a previous oodle -log run. However, the more optimizations the better.

Turn in Details

Each group must submit all code, suitably documented. A 'man page', (or user manual) must be provided. Ideally this will be in a format similar to man pages, but need not be so. It must describe all the oodle functionality.

Each group must also turn in a diagram of the classes used in the oodle code and how they relate to each other.

Group Grading

Each group member must submit by email an analysis of their group and how the group worked together. This should include an assessment of each group member, including yourself.

I have changed group grading criteria from those I announced in class. If n-1 group members in a group of n agree that the remaining group member contributed substantially less, then different grades may be awarded. I will not award different grades for different people unless and until all group members have been consulted. In particular, if you think your group will evaluate your contributions poorly you should be sure to address this in the email you submit regarding your performance.

Note: not all group members will contribute equally! Each of us has different strengths. So, it's not enough to say "I did more, I should get a higher grade". I expect that each group member will contribute substantively of her/his time, the resulting contributions will be different because some people have more experience, more ability, more time this week, etc.. If, however, it is the judgment of the group that one person has ignored repeated requests to get together, has failed to follow through, or has in some other way not contributed then this should be noted.

Each group must submit in a README file an estimate of how many hours were spent on oodle.

Each group must turn in all source code, an RCS log, hardcopy of man pages and oodle class diagrams as well as a signed statement indicating how many hours the group worked on oodle. This document should be turned in according to the time frame below. Each group member should have a copy of this document for a software portfolio that you MUST keep.

Time Frame For Submissions

The final oodle submission must be turned in electronically by 8:00 am Thursday, February 6. If a group submits a written request for an extension before 7:00 pm on Wednesday, the extension is granted. Late oodling without an extension results in a deduction of points.

To submit, use:

    submit108 oodle oodle.tgz

One copy of all code, documents, etc. is due at the beginning of class on Thursday, Feb 6. Documents turned in AFTER 12:45 will lose 5 of the 35 points. Documents turned in after 1:00 will lose 10 of the 35 points. Class begins at 12:40. Extensions change all rules on turn in times.

Owen L. Astrachan

Last modified: Wed Feb 5 18:04:09 EST