14-814/18-637: Wireless Network Security - Spring 2017
Course Project
- Teams of students will work on a collaborative project for the duration of the semester. Students are responsible for
forming their own teams based on common interests and/or complementary skills. Teams have the option to either come up with
their own suitable project topic, work on a project sponsored by an industry partner, or work on an existing research project
with a CMU faculty member. In either case, student teams are encouraged to work closely with the instructor and TAs to
identify a project topic. Each team will provide the following deliverables through the semester.
- Project pitch: As with any research project, the team will start by doing a background search and literature survey to study
the state of the art in their chosen project area. The team will be responsible for preparing and giving a brief presentation describing
their project area, the related work, and a high-level project pitch of the topic of study and potential goals. Pitch presentations will be
recorded by individual teams, and videos will be made available to everyone enrolled in the course for offline viewing.
Project pitch videos (or links) must be submitted by February 9 along with a copy of presentation slides for grading.
- Project proposal: Once the initial background and project idea is established, teams will work to properly
scope their project and identify a set of goals, contributions, and tasks to target through the semester. Each team will give a brief
in-class presentation of their project goals and expected outcomes in a proposal presentation on February 23. In
addition, teams will submit a detailed written project proposal, due on the same day.
- Progress report: About two-thirds of the way through the course, teams will prepare and give a brief presentation
to update their progress toward their expected outcomes, discuss any roadblocks or challenges faced, present any changes to the
project goals and expected outcomes, and give a brief demonstration if appropriate. Progress presentations will be recorded by individual
teams, and videos will be made available to everyone enrolled in the course for offline viewing. Videos (or links) must be submitted by
March 23 along with a copy of presentation slides for grading.
- Final presentation: During the final week of class, each team will present their final project outcomes, including a
brief demonstration if appropriate. Final presentations will be strictly limited in time, taking place in class on May 2
and May 4. As with other presentations, each team must submit a copy of their presentation slides for grading.
- Final report: At the end of the term, each team will submit a written final report detailing their project goals and
outcomes. This report will have three components: a conference-style paper, a conference-style poster, and a demo video (all in
formats to be specified in class). All final report components will be due on May 9.
Specific details of the team deliverables will be discussed in class prior to each deadline, and slide and report templates will
be made available on Blackboard.
- Submission Instructions: All submissions should be made via Blackboard. For group submissions, at least one member of
each team should submit on behalf of the group; if multiple group members submit a group deliverable, the latest submission will
be taken as final. All team member names should be included on the first page/slide of each deliverable.
- 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.
