University of Virginia, Department of Computer Science
CS655: Programming Languages
Spring 2000
Project Preliminary Report
|
|
Out: 2 March 2000
Preliminary Report Due: Thursday, 23 March, 11:59pm |
Preliminary Report
The project preliminary report describes your progress so far. It
should form the basis of your final report.
The preliminary report should include:
- Problem: A clear description of the problem you are addressing. This
should be more refined and persuassive than the version in your
original proposal.
- Related work: A good summary and analysis of the work
relevant to your project. Everything you describe should be related directly to your
project:
- Why is it relevant? (Don't assume the reader can read your mind.)
- If it attempts to solve a similar problem, why is it not a satisfactory solution?
- What ideas in the other project can be applied to your project?
If there is related work you have not yet studied, list
that in the related work section along with your plans for learning
about it.
- Proposed Solution: Describe your idea for solving the problem. This need not yet be complete, but should include some specific ideas.
- Research Plan: Describe clearly exactly what you will do.
- Evaluation Plan: Describe how you will evaluate your work. This should include (possibly speculative) descriptions of specific sample programs you will use in your evaluation.
- Schedule and Division of Labor: Calendar showing specific milestones, when they will be accomplished, and how the team will split up the work.
There are no length constraints on the preliminary report, but
you should aim to be as concise, clear and organized as possible.
Since you are working in groups, the writing and presentation should
be at a high quality. You should be able to reuse most of the
preliminary report (after changing the verb tenses!) in your final
report.
