Next: Version Control
Up: Overview
Previous: NewsgroupFiles, Web
Each team must submit a number of documents
- implementation plan
- testing plan
- scheduling plan
- user guide
- maintenance report and effort accounting
along with well-documented, stylistically-acceptable code.
One team member acts as ``presenter and
individual responsible for the final review''
of each document.
The responsible person should ``sign off'' on the
document; that is, his/her name should be clearly indicated on the
cover page of the document and his/her signature
should be on the cover page.
No team member may act more than once in this capacity
until all team members have signed off on a document at least once.
The ``signer off'' will receive an individual
grade based upon the quality of the document's form.
In particular, such things as
poor English, shoddy formatting, haphazard organization,
unclear exposition, poor or incomplete presentation, and lack
of neatness will be counted against
the him/her.
The grade for the content of the document, as opposed to its form,
will be assigned to the team as a whole.
Time constraints will probably prevent each team from making a presentation
on each of their planning documents, but any signer off must be prepared
to make a presentation of approximately 15 minutes on the main points
of the document's content, and the Instructor reserves the right to
call upon any signer off to make such a presentation without prior notice.
If teams are large, there may not be enough documents for everyone
to sign off a document. Team members who are left out
may acquire
a grade of equal weight by submitting a diary
of their activity in the team (see Section 2.8).
These submitted diaries will be judged on their form and comprehensiveness
in the same way as the quality judgment applied to planning documents
and reports.
Next: Version Control
Up: Overview
Previous: NewsgroupFiles, Web
Mon Sep 9 09:16:07 EDT 1996