CS9617 Project Proposal Notes
- The project proposal should be short, say a page or two. Rather
than writing paragraphs, most of it should be lists of items.
- Remember the proposal should be handed in on paper by the due date
in the course outline. If you don't have it ready for next class, sliding
it under my door (MC384) is reasonable -- but you should email me to find
out if I got it or not.
- The proposal should have the following format:
- TITLE: the title of your project the briefly summarizes the
intent of the project
- NAME: your name as it appears on your student ID
- EMAIL: your uwo.ca email address
- GOAL: A few sentences indicating what you expect to learn about
while doing your project
- PLAN: This explains how you are going to go about doing your project
- Your project should take roughly 24 hours, spread out across the remainder
of the semester. You should be indicating what you plan on doing with that
time. Some tasks you may plan on doing in a hour or less. Any task that
you expect to take more than 5 hours doing, you should break up into smaller
- You should indicate when during the semester you expect to undertake
these tasks. In particular, which tasks do you expect to have done by
the first progress report, by the second progress report, and by the end
of the semester.
- Note that neither the proposal nor the writeup nor the presentation of
the project are part of the time allocated to doing the project.
- At this point we have read a few papers giving us standard steps on
how to perform simulation projects and a few papers showing us examples
of such projects (although seldom with detail on all the standard steps).
Be sure and take into account the standard steps in your plan, indicating
which you expect to have done and which are not part of your plan.
- Note: your plan is not a contract for what you will hand in at the
end, but just your initial expectations of how things should go. The
progress reports will give you room to revise your plan to reflect what
you find out about how much time things take from actually doing them.
- Overall, aim at not spending more than 24 hours on the project itself.
Keep track of what difficulties you encounter in performing your project and
expect to include them in progress reports and in the final project writeup.
- PROJECT EXTENSIONS: indicate what you plan on doing to further your goal
if the tasks in your plan get done early and you have have four or five
hours not used up
- EVIDENCE: what records such as notebooks, program printouts,
etc. you plan on handing in to demonstrate that you did the work your
- PERMISSIONS: If your project overlaps work you are doing in your
other class or with your supervisor or at work, you need to contact
that person and include their permission to use the work you are doing
for them in this class. You should also explain the nature of the