Title of Your Paper

Abstract

Summarize what you have done. Abstracts should contain neither references nor equations. The total report should be no more than about 10 pages printed.

Introduction

Provide a brief introduction to what you have done and lay out the organization of the remainder of the report, with hyperlinks to each section.

Citations should be of the form:

In earlier work [1], we showed that HTML is a Turing machine.

Each paragraph should start with

   <p>

You may use all of the HTML 3.2 or HTML 4.0 elements, including tables. Avoid frames and aninmated GIF lines for the report. Do not use Microsoft Word to generate HTML, as the output is only viewable on Microsoft browsers. If you need to use an HTML editor, consider Netscape or Frontpage.

For ease of printing, the report should be a single HTML file, with all images in the same directory.

Related Work

Who else has been doing something similar and how your effort is different.

Background

Provide background on the subject and components. The title of this section is likely to differ from project to project and you may have several of these sections.

Architecture

If applicable to your project, give an overview of the architecture of the software, i.e., which modules do what. Justify the overall architecture and briefly discuss alternatives, if you have considered (and discarded) them. From your description, a reader should be able to understand what the various components do and which one would need to be modified to extend the software's functionality. Also indicate the rough complexity (in lines of code) and language used.

Program Documentation

This is a link to another stand-alone set of HTML files that describe:

• Authors, affiliations and contact information (similar to the style of this document)
• an abstract describing briefly what the program does
• system requirements, such as operating system version, hardware, any multimedia devices
• installation instructions
• configuration (if any)
• operation (similar in detail to a Unix "man" page); provide examples and screen dumps where applicable
• program internal operation
• things that do not work or other restrictions, such as the size of the problem, network properties
• useful enhancements that you can think of
• acknowledgements for code and ideas borrowed

Note: Do not use JPEG for screen dumps, as they will make the writing illegible. Use GIF or PNG.

This part is meant to be part of the program documentation, while parts of this document might become a technical report or a conference paper.

Measurements

Where applicable, this describes any measurements or tests conducted.

Task List

This describes who did what and what was copied from somewhere else.

References

1

Jane FirstAuthor, Yet Another Book on HTML, Podunk University Press, Podunk, NY, 1976.

2

International Telecommunications Union, G.764: General Aspects of Digital Transmission Systems; Terminal Equipment: Voice Packetization, Geneva, 1996.