CS523 Assignments: Project
Deliverables Due Date (11:59:59pm) Percentage Submit project groups to TA January 23 1% Survey of literature and formal project proposal February 6 5% Submit detailed report specifying minimal functionality of the system, your system's "hello world" February 17 5% Midterm workshop March 15-17 10% Submit report specifying experiment goals April 3 5% Draft of intro and related work sections of paper April 10 3% Draft of system design sections of paper April 17 3% Revised draft of intro/RW/design and first draft of results section April 24 3% Final presentation April 26, 28 & May 3 5% Polished, complete final draft, includes analysis section May 10 20% Total percentages 60%
Each assignment should be submitted in a single file, named as <group#>.zip or <group#>.pdf.
The proposal should be about four-five pages in length and should include at least the following information:
Names of Investigators
Abstract (~150 words)
IntroductionWhat problem are you addressing?Goals and objectives
Why is wrong with the current state-of-the-art?
Why is this problem significant?
What is the lasting impact your work will have on the operating system research community?What do you want to have implemented or shown by the end of the semester?Related Work
What are the major milestones you expect to meet?
What happens if some of those milestones are not met?
What will you deliver to us at the end of the semesterWhat are the most seminal peices of work related to your project? (List and briefly describe about 10)Method
Why is your work different from these existing works?
If you are extending previous work, explain why it needs to be extended. Is there a new need? Was the old method flawed?What is your overall research plan?Evaluation
Give details about the first steps you have taken/will be taking
Are there members with specical skills assigned to specific tasks? If so, what are they?
What scientific/engineering principles will you employ in your project?How will you be evaluating your system?Special Hardware/Software
What is a "good" outcome and what is a "bad" outcome?
What is the impact of the evalaution? What will it tell you?
How will/could your evalaution be used for future work?
Are there any broader implications of the results?What special hardware or software will need?Please use the ACM SIG Template.
Will you be building new hardware as part of your project?
What is special about the equipment you are using?
Is there any special significance to the hardwarware or software you are using?
You need to submit a detailed report which describes the minimal functionality which your proposed system should support. This is the Hello World! of your project.
Compared to your proposal, we expect see in this report more mature and detailed information about your implementation. If your project requires a test environment to be created, it should also be discussed in your report.
Remember, while you are specifying the minimal functionality of your system, it should provide a compelling demonstration of how you are moving towards your project's goals.
You will be expected to demonstrate your system's minimal functionality in your midterm presentation.
Prof. Campbell would like to structure the midterm presentations as a mid-semester workshop. For those who have not participated in workshops, the basic premise behind them is that they are a venue for presenting "work-in-progress" where you can get critical feedback about your research relatively early.
To participate in a workshop, a prospective participant needs to prepare a position statement. Usually these are short (no more that 4 pages) and describe your motivation, work-to-date and future plans for the work. This is what you need to prepare for next week.
The document should not go into elaborate detail about your current implementation efforts. A good position paper is a lot like a good sale pitch, your job is not to tell us *how* to do it your way, but *why* we should do it your way.
Your position papers will be made available to the class and each person will be expected to review your paper and give you critical feedback on the progress that you have made thus far.
If necessary, the TA can point you to a few good examples of position papers.
Once a position paper has been accepted, the first thing that is normally done at a workshop is participants are allowed to give a presentation of their work and to demo some of their tools. You will be doing the same thing. We will split the groups in half; half will go Wednesday and the other half on Friday. For lack of a more appropriate reasoning, will have groups present in the order that the proposals were turned in:
Wed: Xen-ARM, Peer-to-Peer home networking, Choices Hypervisor
Fri: Nooks Choices, Choices system interface, Equitable Collaborative Storage
Position papers are due Wednesday 3/15 at 8 AM. The handin email address should be used.
In your project proposal, you described how you intend to evaluate your new system. In this report, you need to update your plan, and provide more details on your evaluation.
Your report should contain at least the following sections:
Reports are due April 3 at 11:59:59 PM. The handin email address should be used.
- Motivation - What is the purpose of your evlaution? How does it relate to the goals of your project?
- Overview of your procedure - give a timeline or outline of the steps you will perform.
- Equipment and experimental environment - Under what conditions are you testing your system? Is there any special equipment?
- Metrics - What will you be measuring and how?
- Expected results - What do you hope to find in your evlauation?
- Broader impact - what can others take away from your experiment? Does it impact other work than just your own?
Files should be sent via email to cs523handin [at] ad <dot> uiuc <dot> edu.