14-829: Mobile Security

14-829 / 18-638: Mobile Security - Fall 2017

Course Project - Final Project Deliverables

Due: in-class presentations during last two weeks of class, other components due December 12, 2017

Description: Toward the end of the term, each team will prepare a final in-class presentation to highlight their project work to the rest of the class as well as a paper, poster, and demo video comprising the final project report.

  1. Present your project work - Each team will have time in class to give a final presentation to highlight the work done during the semester. You won't have time to talk about everything, so focus on the main highlights. At a minimum, each team must include a brief overview of the (possibly revised) problem, a summary of the completed tasks, any interesting results (design, simulation, experiments, etc.), a summary of contributions made to the state of the art in the problem area, and a few ideas for future work. Time will be strictly limited for the final presentations.
  2. Make a poster - Imagine that you are participating in a poster session where you get to show off the work you've done. Create a standard conference-style poster that highlights the problem, main contributions, and any interesting results. Format and guidelines will be discussed in class closer to the deadline.
  3. Make a demo video - Now imagine you are advertising your work to an audience to try to get them to attend your poster session or read your paper. Make a fun advertisement video to highlight the project goals and contributions. Format and guidelines will again be discussed in class closer to the deadline.
  4. Write up your final report - Each team will also write a final paper that includes all aspects of the project. The final report should be written as a formal technical report (like a conference paper) including: concise abstract, detailed and persuasive introduction that describes the problem as well as the original hypothesis or goals, discussion of related work and motivation to extend the state of the art, relevent models and assumptions for system components or adversaries, a detailed description of the approach taken and technical details of the work, a summary of any results obtained through simulation or experimentation (if appropriate), a summary of any design component (if appropriate), a summary of conclusions and future work, and a discussion of challenges faced and any revisions made to the original project goals. These aspects can be included in any order that makes sense and is clear.

Deliverables and Submission: The final project report has two separate deliverables. For the final presentation, the team will present during class on November 28, November 30, December 5, or December 7; the order of presentations will be set shortly before these dates. Final presentations will be strictly limited in time. One member of each team must submit a .pdf copy of the presentation slides to the corresponding group deliverable in Canvas by December 7. The remaining components of the final report (paper, poster, demo video) must be submitted to the corresonding group deliverable in Canvas by December 12. No extensions will be granted for final report deliverables. If multiple group members submit any component, the latest submission will be taken as final. All team member names should be included on the first page/slide of each deliverable.

Grading: The in-class final presentation deliverable is worth 40 points: eight (8) points for reiterating the high-level problem, ten (10) points for a detailed description of the completed project tasks, twelve (12) points for discussing interesting project outcomes and results at a level appropriate for the time alloted, five (5) points for concisely summarizing the contributions of the project, and five (5) points for briefly discussing future work ideas. The final report deliverable is worth 80 points, with ten (10) points allocated to each of the poster and demo video. The remaining points are allocated to the final paper, with ten (10) points for the overall introduction to and description of the problem, six (6) points for motivation of the work beyond the state of the art, six (6) points for concise statement of the hypothesis or goals, four (4) points for descriptions of models and assumptions, sixteen (16) points for a detailed description of the approach and technical details, eight (8) points for the summary of any designs or results obtained via simulation or experimentation, four (4) points for discussion of conclusions and future work, and six (6) points for discussion of challenges faced during the project. For all final report components, we reserve the right to deduct points for lack of clarity, inappropriate content, improper length, etc.

Warning: Students are expected to follow strict ethical guidelines during the course project. At no point should any malicious code be deployed or disseminated publicly. Please contact the instructor if anything is unclear or if you have any doubts.