Final demo/discussion Slots

• You will have to submit your code by May 5 (Wednesday) midnight. During the demo, you will copy this submitted code back to your demo directory, compile it and then run it for the demo.
• It is important both partners be present for the demo.
• You have 30 minutes for the demo/discussion. So please plan accordingly.
• The goal will be to spend about 15-20 minutes doing the demo, and the remaining 10-15 minutes question/answer session.
• You may find it convenient to define scenarios, to demonstrate that different parts of your project is working. Most of the grade will be based on what you can demonstrate. For example in the e-CHIMP project, you may want to prepare a demo for a 1-server system, a 3-server system, and a 10-server system. In the 10-server system you may want to demonstrate that routing works! If its useful, draw the topology on which you plan to demonstrate your system on a separate piece of paper and bring it with you. Prior to the demo, we will give you our suggested toplogies on which we will run the interactive demos. Try them out and have them ready.
  If the entire project does not work, plan out demo scenarios that indicate parts of the system works.
• You may find it convenient to prepare some quick startup scripts to demonstrate how different parts of the project is working.
• For the research projects, I would also like to see demos of the system that you have implemented / evaluated (depending on what our pre-discussed objectives were). Additionally each student doing a research project will need to submit a research report. The report should contain the following: what the problem you had started out with, adjustments made to the problems (if any) due to various reasons, and why, what you accomplished, i.e., what you implemented, what your observations are about the system, what are the logical next steps to explore in this process and how you might go about doing it.
  The writeup will be important especially in the case where you do not have a well-defined demo during the meeting. Focus more on the details on what you achieved, what you could not achieve (and explain why not), and what the next steps are (and how you can go about doing them).

May 6: Thursday