Fall 2009

Cryptology 1: Graduate Projects

[Course Description] [Literature] [Course Materials] [Assignments] [Maple Worksheets] [Examinations] [Graduate Projects] [Maple] [Cryptology Blog]


 

Proposal due date: October 29 (strictly enforced)

Past Projects
 

Each student enrolled for the graduate level version of this course must propose, and complete, an independent cryptology related project for this course.
Please give some serious thought about a possible project, and be creative. It is strongly recommended that you choose something you are interested in doing.
Search the Internet and other resources as books and papers to select your cryptographic topic. You may consult me regarding the topic of your project.

The main check points for the project-process are as follows:

1. Submit in electronic form a proposal of a possible project by the due date.
   In your proposal:

   •  Give a description of the  work you wish to do as your project.

   •  Give some motivation why this is interesting to you, and relevant to cryptography.

   •  Describe possible applications of your proposed work.
      

2. Receive evaluation of the proposal. This may include:

   •  Acceptance of the proposal as is.
   •  Conditional acceptance of the proposal. In this case, the conditions that must be met for a legitimate project will be specified. These conditions must be met in the project, or else the project will receive 0 points. The student's options now are either to accept the modifications by confirming this by e-mail, or else to submit a new proposal that will go through the same process.
   •  Rejection of the proposal.

3. After final acceptance of the proposal, submit an abstract to the conference abstracts page. After submission the proposed project cannot be changed.

4. Start work on the project. You may consult me during your work on the project.

5. Presentation of the results of the project according to the conference schedule.
6. At the end of your presentation submit on a CD the materials of the completed project.
7. The following needs to be submitted

   •  An abstract where you give a brief explanation of your work and results.

   •  A .txt file that contains a detailed explanation of the algorithmic  and mathematical aspects of your project.
   •  Source file(s) of any programs you wrote as part of your project.
   •  A .txt file that contains detailed instructions on compiling and running the program.
   •  Your own critique of your program based on test runs of your program.

Grading:

1. Don't copy programs from anyone  and don't let anyone copy your program. Don't take  projects from the web. You may use web-sites, books or papers as a source for your project, but be sure to cite these sources in your documentation. If you are not sure whether you can use something or not you should ask me in time. Copying someone else's program or allowing someone else to copy your program will result in 0 points for the project, and academic misconduct proceedings.

2. Projects are not accepted beyond the date of the presentation even if they are near completion. The date of the presentations will be announced on the conference web page. Partial credit will be given to incomplete projects turned in at the end of its presentation, but no credit for work handed in late.
3. Turning in a project without documentation will result in losing points. You will lose points if your program does not give correct answers or has serious errors. The number of points assigned to a project depends on the project's difficulty and how much of  the project that you have proposed, you accomplished.

4. Your presence is required at each of the conference presentations. Not being present will result in loosing your participation points.