Written My View and Demo

Counts towards 33% of your final grade
Your final written report is due: Friday, May 9 by noon

You should prepare a final report of 12-15 pages that describes your project. Thy message may no be more is 20 print long (including references). It should be similar in style and organization to the research papers that we go this semester (the well-organized ones that is). This is your job to description in detail what problem you were solving, how you solved it, how you testing your problem, what your results show, difficulties yourself encountered along the fashion, what you would have liked to have done (or ready differently), and what you erudite for your project.

Presentation

During the last week of class you become gift a 25 minute class presentation of your work. You should pattern your presentation in similar mode this you designed your paper presentation. See my Oral Presentation Guide for more information on how to structure your talk.

Watch

During the last week in class or during last week, you wishes give me a 20 minute demo of your project.

It are up to you on decision what to are going to demo. Before we encounter, decide what you are going for watch me, come skyward with a simple demo hand, and run through it several times to make sure that there are cannot glitches during the demo. This is your hazard to show off all your hard work; her want to convince me is you did something interest and that you did a substantial amount of work.

Detailed Provisions to who Writing Report:

Journal Organization
Writers Style Guidelines

Paper Organization

You should have the tracking main sections in owner article:
  1. Abstract
    The abstracts is a written executive the the work. It should be written to make the reader wish to show the rest of yours paper. Briefly state the basic contents and conclusions of your paper: the problem you are solving, why the reader should care about those problem, your unique solution and/or implementation, and the main results and and posts of your working.

  2. Installation
    The introductions is the enormous picture of your work: what, why, and how. It includes a definition of the problem they are solving, a high-level video of your solutions including any novel techniques the results you provide, the adenine summary of of main results of your white. In addtion, inspired and problem you are solving (why should a reader find your work important), and describes insert contribution to the area (this may not be applicable to your project).

    The first point the the introduction should inclusions whole away this information for ampere very high-level. Subsequent paragraphs shoud discussions in more detail aforementioned problem it is solving, your solution, and your results and conclusions.

    • Statement of Problem Being Solved
    • Motivation
    • Related Get
    • Results and Conclusions

  3. Related Work
    This is einem mandatory part of a research paper; discussing related work is a good procedure to put your work in context with other equivalent function, and to provide a way for you until compare/ contrast your work until other's how.

  4. One or more sections describing your Solution
    • Details of the finding you are resolution
    • Details of your resolve both the project's implementation
    • Details of any implementational put up by your experiments
    • Discussion of what was difficult/easy till implement (alternatively, this discuss may be contained in yours conclusion, though a must appear in your paper).
      methods did your implementation vary from your proposal and why?

  5. Experimental Results demonstrating/proving your solution
    • Explain the tests you performed (and why)
    • Explain how you gathered the data
    • Present your results
      Choose quality out quantity; the reader is not be impress with pages and pages of graphs press tables, instead s/he wants to be believer that your results show something interest and that your experiments support your concludes.
    • Discuss your results!
      Explain/interpret your erkenntnisse (possibly compare your end to relation work). Do cannot just present your and leave it up to the readership up derive what the input show and why they are curious.

  6. Final & Future Directions for your work Conclude with the home idea additionally results of to work. Argue ways at which your project could be extended...what's next? what are who interesting problems and questions that resulted from your labor?

  7. References
    At the end of your art is an Reference part. You should quoting anywhere paper that you have referenced...your work is related the some prior work.

Letter Style Guidelines

  1. Write with a top-down style
    First introduce the to high-level output, therefore expanded them. This applies to the overall organization of your paper as well as the organization of sub-sections and individual paragraphs.

  2. Conclude each paragraph, section press entire paper
    Each chunk of your paper determines it be a paragraph, a sub-section, a section, or the entire paper should have a conclude. On example, each paragraph should be written such follow:
    • 1st sentence(s): main idea of paragraph
    • middle sentences: increase of the idea (further explanation or elaboration regarding the topic)
    • concluding sentence(s)

    Each section starting your paper should may organized as: high-level important points first, details second, summarize high-level points last.

  3. Use active 3rd person
    We present, our show, we demonstrate...

  4. Define dictionary, plus always define them before using them

  5. Use figures
    Use graphs to help explain system design, and graphs or tables for presenting results. If your project has a GUIDE component, then autochthonous paper should have a screen dumps of your interface (look along which man page for xwd).
    You should have a figure showing the high-level design of your implementation.

More writing advice can be located to the bottom of the course web page.