Hackathon Project 2: Deliverables and Requirements
Two parts: first report (due Wed April 25th) and final deliverable (due Wednesday May 9-10th-12th).
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, April 25th at 11:59pm
20% of project 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 May 9th at 1:55pm (Presentations), Saturday May 12th Thursday May 10th 11:59pm (Report)
Project grade contribution: 20% presentation, 60% report
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 report deadline; late submissions will be penalized. The report should include a link to the working system or prototype.
Your demo, should be of a clear, working system based on your initial hackathon presentation but with an actual working system. The larger your team, the more advaned/deep and/or broad we expect your contribution to be.
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 for the report:
- 20% Motivation, background (paper)
- 20% Coherence of design, features (paper)
- 40% Technical implementation (prototype/system)
- 20% Considerations, limitations, future work.