Course Project Spring 2015
Your course project should address an important, interesting open
problem related to computer security, ideally cloud or distributed
systems security. It's up to you to find a good topic, but I'd like to
discuss your ideas with you in order to help refine them.
Your be working in groups of 2–3. The larger the group, the
more I'll expect you to accomplish.
Pre-Proposal Discussion — Due 4/17
Form a group and tentative project and idea, and schedule a meeting with me to discuss and refine it.
Written Proposal — Due 4/24
Write a 2–3 page description of your project and email it to me. It should include:
- Group: Group member names and CNetIDs.
- Title: What would you call the eventual paper or product?
- Problem: A description of the problem you will address and why it is important.
- Context: A survey of related work and past approaches to the problem.
- Approach: How you will address the problem and how your approach differs from past work.
- Evaluation: How you will test how well your approach works (e.g., experimental measurements).
- Scope: What you plan to accomplish and deliver by each of the checkpoints and by the end of the quarter.
Checkpoint I — Due 5/8
Write a concise status report (no more than two pages) and email it to me. It should answer
the following questions:
- Progress: What have you accomplished so far? What do you have left to do?
- Schedule: Are you on track to complete what you proposed?
- Obstacles: Have you encountered any surprises or unexpected problems?
- Workarounds: If you're having problems, how do you intend to solve them or work around them?
- Preliminary results: Can you draw any preliminary conclusions from your results so far? Include data.
Checkpoint II — Due 5/22
Email me a second status report following the format of the first.
Project Presentations — In class 6/9 10:30–12:30
Give a 20 minute conference-style talk on your project.
Final Paper — Due 6/12
Your group's final project report should be written in the style of
a workshop or conference submission, like most of the papers we have
read this quarter. Please include at least the following:
- An abstract that summarizes your work.
- An introduction that motivates the problem you are trying to solve.
- A related work section that differentiates your contributions.
- Section(s) describing your architecture or methodology.
- Results and/or evaluation section(s), with data or figures to support your claims as appropriate.
- A brief future work section explaining what is left to do.
- Appropriate citations and references from the literature.
See also: Advice on writing technical articles.
The length of your report should not exceed 8 typeset pages,
excluding bibliography and well-marked appendices. There is no limit
on the length of appendices, but graders are not required to read
them. The text must be formatted in two columns, using 10 point Times
Roman type on 12 point leading, in a text block of 6.5” by
9”. I strongly encourage you to
use LaTeX and
USENIX template files. Please submit your report via email to me.
Submitting Your Work for Publication
You should consider submitting your results to a technical workshop. I'd be glad to discuss potential venues with you.