CS557 (Spring 2018) Project #2


Home Page | Syllabus | Class Schedule


Table of Contents

1 Project outline

The purpose of this project is to challenge students to complete a small-scale research-oriented project. Students will be expected to come up with a suitable and original project idea, complete a substantial amount of work in order to demonstrate their idea, and presents results via recorded presentations. Throughout the project, the instructor will provide support, although students will be expected to operate independently and show creative thinking and problem-solving skills.

The effort and time commitment dedicated to the project must be proportional to the time allocated to the project (approximately 2 months). Students are allowed to choose between two general project categories, described in the following.

Students may work either in pairs, or individually. Projects completed by two students are expected to be significantly more substantial than individual projects.

1.1 Option #1: Investigation

Students choosing this option will be expected to propose a research-oriented problem which has not been fully explored in literature. Completing this type of project will involve a proof-of-concept implementation of the proposed idea (for example a software implementation, one or more network simulations, a small testbed, etc.) and designing an experiment detailed enough to demonstrate a partial or full solution to the target research problem.

In order to determine a suitable project idea, students are advised to consider their expertise and the areas of networking that are closest to their interests (e.g. a student with FPGA programming expertise may want to look into hardware acceleration of network functions). Furthermore, if a student is already involved in research projects, it is acceptable to consider a project idea which fits into the student pre-existing research agenda (as long as the work has not been already completed, and the students will not receive assistance from third parties). Finally, if a student is planning to perform networking-related research as part of her/his course of study, this project may be a good occasion to get the research started.

1.2 Option #2: Repeatability study

Students choosing this option will be expected to conduct a repeatability study of results recently published in networking literature.

A recurring issue in modern computer science is the lack of repeatability of many research studies. This issue is typically caused by unclear experimental setup descriptions, and code and/or datasets not being provided. This situation generates various problems, the most serious being a general skepticism of researchers and general public alike concerning the meaningfulness of certain scientific works. This project option requires students to choose a set of papers and attempt to repeat their results. Students will be expect to obtain the necessary implementations and datasets, potentially supplying them with their own work (e.g. to re-implement minor missing components), and run the experiments discussed in the papers under review. Students will then be expected to comment on the feasibility of repeating the results, and the differences between expected and achieved results. Note that failure is a very possible outcome, in which case students will be expected to comment on the reasons that made repeatability impossible. The number of papers considered will depend on the expected difficulty of repeating the results in each paper. Before starting, students are encouraged to assess the repeatability of the studies of interest, and contact the instructor if unsure.

2 Project organization

The students should initiate their work by (i) forming groups (unless they wish to work individually), and (ii) deciding on one or more preliminary projects idea. They should communicate their project ideas to the instructor in order to discuss them and converge on a concrete project plan. Such discussion may be conducted via in-person meetings, Skype calls, or email exchanges. After an agreement has been reached with the instructor on the project idea, students should produce a project description (at least 2-page in length), and have it approved by the instructor by the project approval deadline.

Once the project idea has been approved, students should work on achieving the project goals during the rest of the semester. Before the end of the semesters, each project team will be expected to produce a short (15- to 20-minute) presentation on their work. Finally, at the end of the semester each team will be required to deliver a final project report.

3 Project timeline

Date Goal
3/23/2018 Approved project plan delivered to instructor (by end of the day)
5/3/2018 Presentation recording due (by end of the day)
5/9/2018 Final project report due (by end of the day)

4 Deliverables

All documents submitted during the project must clearly state (i) the project title and (ii) the names of the participants in the project.

4.1 Initial project description

Students, through discussions with the instructor, must converge on a project idea and a plan to accomplish that idea. Then, they must produce a 2-page (or more) project description specifying:

  • A project title
  • A project summary
  • A list of project goals and how they will be accomplished
  • An expected schedule for accomplishing intermediate and final goals

The project description must be sent to the instructor in PDF format. This plan must be provided to the instructor by the deadline specified in the table above.

Example project description

4.2 Presentation

Before the end of the semester, each project team will be required to produce a short presentation showing their work. Presentations should describe the motivation for the project, background on the project's domain, a summary of the work that was done and a summary of experimental results. The presentation should last approximately 15 to 20 minutes. The presentation should be based on a slide deck in either PowerPoint, LibreOffice or Keynote format.

All students should provide a recording of the presentation by the deadline stated in the table above, together with the slide deck to the instructor ahead of their presentation. The instructor will watch the presentations and send students feedback and questions via email. Each project team will be expect to answer these questions over email before delivering the final project report, and - as much as feasible - incorporate the instructor's feedback in the final project report.

4.3 Final project report

At the end of the semester, students will be required to deliver a final project report to the instructor. The project report should be structured as a research paper, including abstract, introduction, background, related work, one or more technical sections, evaluation, and conclusion (sections does not have to appear in this specific order or have these specific titles; this description is purely meant as guidelines for what is expected from the report). The project report should be approximately 12 pages in length and must be written using either Word or LaTex. Students should use either the LaTex or Word IEEE conference template:

https://www.ieee.org/conferences_events/conferences/publishing/templates.html

Student must deliver both a PDF version of the report, and the sources (i.e. the original Word or LaTex documents) in a single tar.gz file.

No guidance will be provided on using Word or LaTex, and project reports using formats and/or templates other than the ones specified above will not be accepted.

4.4 Other implementation material

Students should deliver all implementation material (including source code, datasets, virtual machines, etc.) to the instructor together with the project report. In this case, place the implementation material in the same tar.gz file used to upload the final project report, unless the overall size of the implementation material is above 40MB. In that case, students should upload a copy of the implementation material on an online storage service (e.g., Dropbox) and provide a download link to the instructor. Other delivery methods must be discussed with and approved by the instructor.

5 Submitting your work

All deliverables (except large implementation materials, as discussed above) must be submitted using the course Canvas page by the deadlines stated above. An assignment group has been created for the second class project. Students must upload their materials to the appropriate assignments. Note that it is enough that one person per team performs the upload (i.e. different team members do not need to upload the material individually).

6 Grading

  • No credit will be given to students that fail to provide all deliverables (deliverables include: having the project description approved by the instructor and submitted by the deadline; producing the final presentation; delivering final project report and all implementation-related materials)
  • 15% Project description: does the project description precisely and convincingly motivated the project, describes the project plan, and lists project goals? Is the project idea original?
  • 15% Project presentation: was the student able to present the work in an informative and concise way?
  • 40% Final project report: does the project report presents an exhaustive and informative exposition of the project's goals and results?
  • 15% Project organization and management: was the student able to set reasonable intermediate goals for herself/himself, and how timely and completely were those goals achieved?
  • 15% Quality of results: was the student able to successfully achieve the expected results (or, if not, did the student learn valuable insights into the problem that could lead to success in future research)?

This project description may change at the discretion of the instructor. Good luck!


Author: Lorenzo De Carli

Created: 2018-04-12 Thu 13:00