There are some guidelines on the expectations on the quality and scope of your term project for CS217.
A list of suggested project topics will be handed out in class. The exact topic of the project is up to each project team. The basic requirements for choosing the project topic are that it must be networking related and the work original, and it should lead to some programming effort.
The topics may range from synthesis projects, where you implement a new system, to analysis/measurement projects where the performance of some network or networking related system is evaluated. You are highly encouraged to choose a protocol/system based project, although a cool original idea backed up with simulation results is also acceptable. Project proposals must be approved by the instructor prior to undertaking work.
You should get your team organized and nail down a specific topic by April 16th. Please email me about your team members and the topic chosen ASAP. The project proposal is due before class on Tuesday, April 20. The proposal should contain a high level description of the project topic, together with a reference list of previous and related work. It should describe clearly what the team plans to do and why that is new and interesting. The proposal should also identify the major issues in carrying out the project, with a schedule of projected progress. The proposal should demonstrate that your project is worthwhile and that your team has the competence to carry it out on schedule.
The project progress report is due in class before class on Tuesday, May 11, 3 weeks after the proposal due. This report serves as a checking point to show that your project has indeed been successfully launched. The report should identify what you have accomplished so far, what new roadblocks, if any, have been identified, and how you plan to solve them. In case that you encounter difficulties that were unforeseen at the time the topic was chosen, this report gives you an opportunity to re-evaluate and readjust your original goals and schedules. If you make any significant changes from the original proposal, however, you should discuss those changes with the instructor before the progress report due.
The project presentations will be scheduled in class during the last week of class.
The final project report is due 4:00pm Monday, June 14th (the final exam week). The report should be 10-20 pages in length, giving a complete, self contained, description of your project, along with all references, related and prior work that pertain to your project.
Start work early! Ideally, all projects should strive for resulting in a conference paper. As such, it is expected that a significant amount of research effort to be exhibited in the project. While I will always be available to provide high-level consultation, it is up to you and your team to pick a right topic, budget your time, and put in your sincere effort to make it a success.
|
Decide on the topic |
due 4/16 |
|
|
Project proposal |
due 4/20 |
10% |
|
Progress report |
due 5/11 |
5% |
|
Final project report |
due 6/14 |
25% |
|
Project presentation |
last week of class |
10% |
|
Project demo |
last week of class |
|
The percentage values in the table are the percentage in your final grade.
Please include the email addresses of all the project team members in all your
reports.
From this list you may find pointers to IETF related
information, interesting/useful tools, or even inspiring ideas that broaden
your search on a good project topic.
I will add more pointers as they come along. If you have suggestions on what more to add to this list, send my way.