Final Project submission

2020 final reports

Your final project consists of three parts: the project code, a written report, and a demo in class.

Code submission

Please submit your code either as a link to a repository (e.g., on GitHub) or as a ZIP file with clear instructions on how to build and run it.

Final report

Please use the OSDI 2018 submission template for typsetting your report. The report is a piece of scientific writing, similar to a paper like those we read during the course. It should therefore follow the structure of a good paper:

  1. Abstract: a short, high-level summary of the problem you're addressing, why it is important, what your solution does, and how well it works.
  2. Introduction: motivate the problem and the solution, and give an overview of the key insights/ideas in your work. Make sure to highlight any limitations that the reader should be aware of.
  3. Background/related work: explain what literature and ideas you're building upon, and explain any concepts readers need to understand.
  4. Design: describe the design of your system, including how an end-user or application developer uses your system, as well as any key ideas, abstractions, or algorithms involved.
  5. Implementation: give a brief overview of how you implemented your work, how many lines of code you had to write, and what implementation and engineering challenges you had to overcome. (This section can be quite short.)
  6. Evaluation: describe what experiments you conducted to validate that you have indeed solved the problem you set out to address; clearly explain your experimental setup and case studies, and give performance numbers if they are important.
A good report will likely require three to six pages of text.

Important: if your project is a group effort, please include an indication of the individual contributions in the report. It is fine for this to state "the Github commit log is representative of the group member's contributions" or "all group members contributed equally", but if there are any contributions that aren't explicit in the code or writeup, please enumerate and explain them.

Please send your final report by email to Malte by the deadline.

Demo and Presentation

2020 final reports

During the final course meeting on December 9, 2021, you will demo your project to the class. Each project will have six minutes for the presentation and demo (this is a hard limit and will be enforced!). As time is tight, please rehearse your demo well and keep the presentation brief. The presentation should explain the top-level insights from your project: what problem you set out to solve, how you approached it, and how well the solution worked. The demo should illustrate how an end user or developer might use your system, and highlight any key ideas and concepts you invented.

After the presentation, we will have 1 minute for questions; please let the next presenter set up during this discussion.