Grading Policy
  Tools and Data
  Course Folder

Don't see the menu?

  1. Project Timeline:

    • Week 3:
      • Thu, 09/19: Contract Due

    • Week 7:
      • Thu, 10/17: Prototype Presentation and Report Due

    • Weeks 14 & 15:
      • Thu, 12/05: Final Presentation Due
      • Tue, 12/10: Final Report and Poster Due

    We will use the first two weeks' discussion hours to help you refine your project ideas and to form groups. We will use subsequent discussion hours to discuss your progress and to resolve any issues you may have.

  2. Project Grading

    You can consult the Project Ideas below, but are highly encouraged to define your own topic of interest.

    Report format: To make it easier for me to carry around, read, and comment on your reports, please use 11-point size, single column, 1.5 or double spaced, with at least 1" margins on all sides, and printed double sided. I only accept hardcopy, not electronic copy, of reports. There is no page limit requirement, use as many or as few pages as you need, but be concise in your wordings, don't make me read long rambling prose. Recall also that I deduct 2 points for each occurrence of a typo, 3 points for each grammatical error, and 5 points for each unfinished sentence.

    A Project Contract in hardcopy is due the third week of the semester. Each group is required to give a 5-min presentation of its project contract. The project contract should contain:

    1. A description and scope of the project.
    2. A project schedule with milestones and a Gantt chart. You can draw a Gantt chart either using a simple drawing tool, a spreadsheet program, a specialize Gantt chart app such as GannProject, SmartDraw, Edraw Max, or a web-based tool such as Gantter, Tom's Planner, or Creately's.
    3. A grading scale for the project, i.e. what constitutes a C, B, A, etc.
    4. For group projects:
      • Members of your group. You are encouraged to form a group of 2. If you want to work by yourself or in a group larger than 2, please come talk to me first.
      • Your group's weekly meeting time.
      • An optional schedule delineating the responsibilities of each member. With such a schedule, each member is graded for his/her part of the project. Without such a schedule, the default is for every member of the group to receive the same grade.

    If you'd like to do a joint project with another course, past or present, or as part of your directed study or research work, you must first get permission from the other instructor or your research advisor and you must include in your contract which part of your project is for which course.

    A Project Prototype is due around the middle of the semester. If you are implementing a new algorithm, protocol, or tool, I expect a working prototype by mid term. If you are doing performance study, I expect an initial collection of traces and set of analysis scripts by the same time. Each group is expected to present a 10-minute midterm prototype presentation. Where applicable, these are the things I expect to see submitted as part of your midterm prototype:

    1. Your project contract with my markup.
    2. An online copy of your code or analysis scripts uploaded to your folder on the course MFile/AFS directory.
    3. A draft of your final project report in hardcopy (see below for an outline of the report contents), including:
      1. Any proposed changes to the project contract: milestones, schedule, and/or grading scale (for instructor's consideration and approval).
      2. An initial set of data showing the correctness of your code.
      3. Experimental setup: how you will evaluate the performance of your project.
      4. An initial set of performance figures.

    Final Presentation, Report, and Demo are due the last week of class. The following should be part of your final report:

    1. Your project contract and midterm report draft with my markup.
    2. Your final project report, in hardcopy, consisting of:
      1. Problem motivation.
      2. Design goals or performance questions.
      3. Design architecture or performance metrics.
      4. Description of code or scripts: major data structures and control flows.
      5. Description of difficulties in coding or performance measurement and analysis: whether, why, and how the original goals, architecture, and/or metrics needed to be changed.
      6. Data showing the correctness of implementation.
      7. Description of your experimental setup to evaluate the performance of your implementation.
      8. Performance evaluation data and analysis showing (non-)achievement of goals.
      9. Future work.
      10. Related work and references.
    3. A 20-min presentation of your final report and, if applicable, an optional 10-min demo.
    4. An online copy of your code or analysis scripts and a pdf copy of your final report and presentation, uploaded to your folder on the course MFile/AFS directory. Also submit an online copy of your final report and presentation source document (preferrably the report is in latex or plain text format with a separate image file for each figure---MS Word doc is acceptable, if you must; the presentation can be in MS PowerPoint or Apple Keynote).

    Poster Session gives you a chance to show off your work to the campus community at large. I will stop by your poster to collect your final project report, ask you questions about your work, and listen to how well you answer questions by others. What goes onto your poster could simply be a selection of your final presentation slides laid out, with additional material from your final report. The department has easels and poster boards (40"x60") you can borrow. If you have a demo, you can also give your demo during the poster session.

  3. Project Ideas:

    To see topics that are currently "hot" in a computer-related research community, scan through the latest proceedings of the conferences and workshops of the community. For computer networks largely defined, check out:

    For your course project, it is perfectly fine to try to reproduce published research. You could view several such projects completed by students in the Stanford's graduate-level computer networks course.

  4. There are also survey papers identifying research topics in computer networks and cloud computing: