Hackathon Project 1: Deliverables and Requirements

Two parts: first report (due Wed March 7th) and final deliverable (due Wed March 21st Monday March 26).

The first report is meant to provide a short opportunity to reflect on the idea your group landed on in the Hackathon, and on how to take them forward in the next two weeks before the final submission. It is not expected that you have built a technical system during the Hackathon. For the final submission, you are expected to build a working version or technical demo of your system/idea. You may expand or otherwise change the idea you landed on in the Hackathon for the final version.

First Report

Due Wednesday, March 7th at 11:59pm

20% of project 1 grade

Each group should submit a short report on the Hackathon project and immediate plans including:

1) The big idea (50 words)

2) Overview of the system/prototype/plan’s main features (100 words)

3) Technical aspects of Hackathon implementation (100 words)

4) Development plans for final deliverable (in 2 weeks) (200-300 words)

5) Key technical challenges in current work and plan (100 words)

Final System and Report

Due Wednesday, March 21st at 11:59pm

Due Monday, March 26th at 11:59pm

80% of project 1 grade

For your final submission you need to provide a built system or demo, and an updated writeup that adjusts the initial report based on your changes/additions and improvements since.

Submit a report in PDF format via email to the TA Michael Wilber by the deadline; late submissions will be penalized. The report should include a link to the working system or prototype. If you have a demo, app or environment that requires a specific setup, sign up to present during Mor’s office hours on March 22nd. (You can sign up to present even if your prototype/system is publicly available).

The report should have similar sections as the first report above, updated to reflect the latest changes and modification that resulted in the final prototype:

1) The big idea (50 words)

2) Overview of the system/prototype/plan’s main features (100 words)

3) Technical aspects of the final implementation (100 words)

4) Key technical challenges addressed (100 words)

5) Potential future development and directions (200 words).

In your submission make sure to list/include non-Cornell Tech collaborators.

Grading:

• 20% Motivation, background (paper)
• 20% Coherence of design, features (paper)
• 40% Technical implementation (prototype/system)
• 20% Considerations, limitations, future work.