Home >  T.A >  cs179 ( Fall 2002 ) >  Binder

  What should the final report look like?
Print this Page   
 [  Main ::   Calendar  ::   Groups  ::   Readings  ::   Topology Generator  ::   Final Binder  ::   FAQ]

Since this is a group project, my intention is to give you detailed or step-by-step description on how to design/implement the various components of the protocol. This is your job! I will simply provide you with some general directions as well as pointers to various related tools so that you can grasp the project and accomplish it.

  1. Cover Sheets

    Here you would provide details of who you are, why you are qualified for doing this project (what are the pre-requisites you have taken), a brief bibliography including your accomplishments and finally but most importantly an abstract which summarizes what the project is about a why it is important, what it is about etc.


  2. Introduction
    In this section you would :
    1) Motivate the problem (why multicast?) – high level
    2) Evaluate the trade-offs between various approaches in doing multicast
    3) Motivate the solution (why application layer multicast?)
    4) Estimate the Economics of doing application layer multicast – how much would you expect it to cost
    5) in terms of large-scale deployment (changes required in the Internet, performance degradation versus what you think of it in terms of its use).
    6) A brief introduction to what you have done and how you have done it.


  3. Design Document
    This would essentially be what you submit on October 31st. You can edit it and make it better for the final report based on my comments. Include both the preliminary version and the final version so that I can see how you have learned along the way.
    1) Detailed design including finite state diagrams.
    2) Assumptions and the conditions under which this design would perform the best.
    3) Assumptions and the conditions under which the design would perform the worst.
    4) Justification for choosing the trade-offs – why you chose certain features as opposed to others.
    5) Explain clearly what you might expect from your protocol


  4. Implementation Details
    Give a description of your implementation in simple words here. What are the main function modules and how they are used ought to be described. I would expect a close corroboration between the design you described in the previous chapter and your implementation. Explain what functions you implemented to achieve what goals.


  5. Your Source Code – Hard Copy


  6. Testing
    1. In this section you describe how you tested your protocol to see that it actually worked. If you made any measurements, tabulate the results.
    2. Clearly list the applications that you used, the scenarios that you might have created, simulated or emulated and what you expected to see.
    3. State whether you managed to corroborate the design claims that you made in your earlier section.


  7. Lessons Learned along the way
    In this section you describe what your experiences were including:
    1) What did you learn along the way?
    2) What were the obstacles you faced and how did you overcome them?
    3) How did you go about doing your project? How did you share your workload?


  8. Additional features
    In this section you describe any additional features that either enhance the protocol either in terms of performance features or even in terms of usability like building a cool user interface.


  9. Your Final Presentation in Power Point – Hard Copy


  10. Miscellaneous notes – Anything else you might wish to add.


  11. CD-ROMs that include your software – These should be attached to the folder.


Clearly have tabs for each section that is listed.

If you have any questions on this format please contact me immediately. As you can see this is a considerable report. So you would need to plan ahead.

The binder is due on DECEMBER 7th 5 P.M. I cannot grant any extensions beyond this point.


Top