6.824 - Spring 2016

6.824 Project

Proposals due: May 18 23:59
Code and write-up due: May 6 23:59
Presentations: May 12


You can do either of two kinds of final project in 6.824. One possibility is to do a "default" final project along the lines described here. The other possibility is to choose your own idea for a final project; this web page describes the latter plan.

If you want to choose your own idea, you must get our approval for your idea in advance. You must form a group of 2 or 3 6.824 students to collaborate on the project. You'll turn in your code and a short write-up describing the design and implementation of your project, and make a short in-class presentation about your work. We will post your write-up and code on the web site after the end of the semester, unless you explicitly talk to us about why you want to keep yours confidential.

Your project should be something interesting and challenging that's closely related to 6.824 core topics, such as fault tolerance. Below you'll find some half-baked ideas that we think could turn into interesting projects, but we haven't given them too much thought.


There are four concrete steps to the final project, as follows:

  1. Form a group and decide on the project you would like to work on. Feel free to use Piazza to find group members and discuss ideas. Course staff will be happy to discuss project ideas via e-mail or in person.
  2. Flesh out the exact problem you will be addressing and how you will go about solving it. By the proposal deadline, you must submit a proposal (less than a page) describing: your group members list, the problem you want to address, how you plan to address it, and what are you proposing to specifically design and implement. Submit your proposal to https://6824.scripts.mit.edu:444/submit/handin.py/. We'll tell you whether we approve, or not, and give you feedback.
  3. Execute your project: design and build something neat!
  4. Write a document describing the design and implementation of your project, and turn it in along with your project's code by the final deadline. The document should be about 3 pages of text that helps us understand what problem you solved, and what your code does. The code and writeups will be posted online after the end of the semester.
  5. Prepare a short in-class presentation about the work that you have done for your final project. We will provide a projector that you can use to demonstrate your project. Depending on the number of project groups, we may have to limit the total number of presentations, so some groups might not end up presenting.

Half-baked project ideas

Here's a list of ideas to get you started thinking -- but you should feel free to propose your own ideas.