General Info

CPSC 503: Project - Assignments

In this course, we will have three assignments:

Before going into these assignments in detail, here are some general remarks. The first two assignments are papers that a student has to hand to his/her supervisor and the instructor. "Hand to" means that the student emails a pdf-file to both, supervisor and instructor (in one email). Note that only pdf-files will be accepted, no Postscript-files and definitely no Word-documents!

Both, papers for conferences (or journals) and research proposals to funding agencies have to adhere to rules regarding the formatting of the paper and for this course we also require that every document you produce for the assignments adheres to a particular style, namely the ACM SIG style for articles in proceedings.

Plagiarism has become quite a problem in academics, as is indicated by the fact that organisations like IEEE have now guidelines how to deal with plagiarism. While the instructor is not aware that there were any problems regarding plagiarism in CPSC 503 in the past, it is nevertheless recommended that the students take a look at Saul Greenberg's page on plagiarism.

Some criteria for grading that will be applied to all papers submitted are

  • Understandability of the English
  • Correctness of the grammar
  • Quality of figures and tables (if there are any)
  • Correctness of the formatting and compliance to the rules for the assignment (the first is mainly for those insisting on letting Microsoft decide how their documents look like, which can be a bad mistake; if you use a Microsoft product, make sure to check every pdf-file produced by it using acroread on our compute servers; some pdfs I received did not comply with the rules when looked at outside of the Microsoft world)

While for all papers these will not be the main criteria, it should be clear that papers that are difficult to understand (due to how they were written) and terrible to look at will not get good grades!

Research proposal:

The purpose of the research proposal is to give its reader an idea what research the project described by the proposal is supposed to perform. This means that there need to be at least two things in such a proposal:

  • A description of the problem that the project wants to address/solve, done in a way that even a non-expert in the field (but you can assume someone with a general Computer Science background) can understand.
  • An initial idea how this solution might look like. This might not be what in the end will be the solution presented in the final report and presentation, but it should become clear that there is at least a starting point towards solving the problem.

Additionally, the proposals should already list some related work in order to provide a basic understanding what the state-of-the-art in solving the problem is and where the proposal differs from this state-of-the-art. Citations of related work should also be there to point to in-depth descriptions of the problem (if such descriptions exist).

The proposal should not be more than 3 pages!

Deadline: September 28, 2012; noon

Final report:

A key point in research is to document the results of the research, so that others can learn from these results and build upon them. Usually, reports on research are done in the form of papers that are submitted to conferences or journals (and are hopefully accepted there). In most areas of Computer Science the main venue to send such a paper are conferences and it is usually very difficult to get a paper into one of the top conferences of an area, because a lot of people submit papers and there are only a limited number of papers that can be presented at a conference. Therefore the review process is very hard and just having one weak accept (and all other reviews suggest a strong accept) might not be enough to get a paper in (and having one or several reject will result in a rejection of the paper).

In this class, we will "accept" all final papers submitted by the students, but their quality will be reflected by the grade you get and you will naturally get a "review" (justifying the grade) from the instructor.

A general structure for a final report is as follows:

  1. Abstract
  2. Introduction/Motivation
  3. Basic definitions/Explanation of the problem
  4. Developed solution to problem
  5. Related work
  6. Evaluation of developed solution
  7. Conclusion
  8. Bibliography
The section titles have to be seen more as an indication what should be in the section and they can be changed to fit better to the particular project. Also, where the related work section goes can differ from project to project (and sometimes this section even has to be merged with the explanation of the problem section).

Not every idea for solving a problem really works. Therefore it can be the case that the result of a student's research is that a particular idea does not work (demonstrated by the evaluation). While this is usually difficult to submit to a conference or journal, it is acceptable for this class, if the report makes clear that the failure is due to the initial idea (and this could only be seen by going all the way to the evaluation) and not due to the student (i.e. there is literature that indicates that the basic idea is not working well and the student did not find it or the evaluation is very sloppy, perhaps one example, so that it is not even clear that the method does not work, and so on). A well-written final report indicating why the initial idea does not work as expected (supported by experiments or sound reasoning) can get as good a grade as a paper reporting on a success.

The final report should not be more than 8 pages!

Deadline: November 30, 2012; noon

Final presentation:

The end of a successful research project is usually the presentation of the results in front of the audience of a conference in which a paper about the research was accepted. The final presentation will try to mimic that. All presentations will be announced to the Department and everyone is welcome to sit in these presentations (even people from outside of the Department). We will schedule each presentation so that at least the supervisor and the instructor can attend it.

The presentation should

  • give an introduction to the problem that the research tried to solve,
  • report briefly on what the state-of-the-art was before the research took place,
  • present the solution idea developed by the student, and
  • present an evaluation of the results produced by the student.
So, the general structure is very similar to the structure of the final report.

Most students will use slides in their presentation and when we schedule the presentations each student should make sure to tell the instructor what equipment he or she needs to have in the presentation!

There are several different ways how to do good presentations and usually it takes a researcher some time to figure out what way is best for him or her (for some researchers this time even seems to converge against infinity). The materials page contains several links with tips for presentations.

The length of each presentation should be not more than 30 minutes and there will be a question period of also up to 30 minutes after the presentation.

Will be scheduled: December 3 to 7, 2012

to the general timetable for the course.

Last Change: 31/7/2012