COSC/EATS/PHYS 4001.06 Space and Communication Sciences Workshop
Last updated Sep. 10, 2002
Project contract template
A contract is typically one or two pages in length.
||Universal DoAll Tool
|Supervisor name (email):
||I. M. Super (super@somewhere)
|Student name (email):
||A. Nonymous (anon@elsewhere)
Location: Laboratory where the project will be carried out
Project description: What the project is to achieve, a half to
Resources required: This is worth spelling out because it may be
more helpful to the student in choosing a project than the project description.
Prerequisite courses: list of courses already taken, minimum mark
Corequisite courses: list of courses to be taken concurrently
Other experience: technical know how needed, familiarity with languages
and systems, mathematical background, etc.
Readings: A short list of research papers/books that could/must
be studied or referenced for the project, that can help give some idea
of what your project is about and the background required.
Software: list of programming languages, tools, operating systems,
etc. (e.g. C++, Unix, Tcl/Tk, Slowgo spreadsheet)
Hardware: list of computer and equipment characteristics (e.g. Unix
workstation with X windows, Acme laser scanner)
Deliverables: List of artifacts to be completed by the final
due date; includes programs, documentation, reports, user guides, etc.
Milestones: Milestones to be reached during the project. Useful
for the project contract and progress evaluation. A sequence of dates at
2-4 week intervals, suggesting what should be completed. You may have to
add/modify milestones specific to your project.
Evaluation: Some indication as to how the project will be evaluated.
For example, the project will be marked on the basis of progress towards
stated goals, and the clarity and completeness of programs, documentation
and reports. It is strongly recommended and encouraged that evaluation consists
of a number of components (e.g., four or five) and not just a grade at the end.
Grades can be associated with different deliverables or parts of deliverables.
Components could include documentation, programming style, easy of use
-- interface design, project proposal presentation, project status presentation,
Sept. ?: Contract completed. Students should have decided on a project.
Students who do not have a project by Sept. 30 must petition the course
director in writing to be allowed to continue in the course, explaining
why they were unable to find a project by that time.
Oct. ?: Background reading completed.
Oct. ?: Preliminary project description document due. Background summary
(2 pages). Specification of the work to be performed in terms of Technical
milestones (4 pages). Rationale for the approach and expected intellectual
contribution (2 pages).
Nov. ??: Project proposal presentation. First in-class presentation.
Dec. ??: Progress report due. Summary of achievements so far, difficulties
encountered, possible change in the technical milestones.
Feb. ??: Preliminary draft of the final documents. Anticipating second presentation.
April ?: Project status presentation.
Apr. ??: Project due. All deliverables completed.
about 20% of the grade should be obtained before the end of the fall term
as an indication of progress to both a student and a supervisor.
The following is an example.
Proposal presentation -- 10% First term
Fall term status and report -- 15%
Project status presentation -- 10% Second term
Documentation & reports -- 25%
Programming/technical work -- 30%
Meeting milestones -- 10%