For Implementation Projects your project report should be from 10 to 20 pages (double spaced with 1" margins and 12pt font) and must have the following structure and content. (Deviations from this structure may be accommodated for specific projects by discussing them with me in advance.)

1. Title Page
   Name the project, list all team members, identify the client, give the date of the report.
2. Introduction
   Describe the general area to which your project applies and describe the need for the application being developed and its intended uses. This section will also discuss any non-functional requirements that were established by the client. Assume that the reader is not familiar with your specific project or the area to which your project applies. Thus, you must provide enough information and organize it in such a way that the reader comes away knowing what it is you are doing and why you are doing it.
3. Background
   This section must discuss at least 5 similar products that have/will influence your design. You identified these products in an earlier document. Now you must review each of them, focusing on the details relevant to your application. I recommend including a sub-section for each product. Compare and contrast the strengths and weaknesses of the products as appropriate. You must also provide at least one reference for each product that you review.
4. Architecture & Implementation
   This section should be split into two sub-sections. The first sub-section describes the overall architecture of your system. It describes the major technologies that you are using, the roles that they are playing and how they fit together to create the application that you have described earlier. This should be high-level description of the architecture. Be sure to include a discussion of your testing methodology as well. The second sub-section provides additional technical details that are necessary to understand your implementation. You must discuss any critical, unique or interesting techniques, data structures, algorithms or other technical details that you have used. This section should be written with the assumption that the reader has taken courses on Data Structures, Computer Organization and Discrete Mathematics.
5. Status, Challenges and Future Work
   Describe the current state of your project, any significant challenges that you face in going forward and outline the work that you intend to complete during the next semester.
6. References
   All works that have been cited in the text must be listed as references in this section (do not use footnotes for references). See the Honors thesis style guide for a suggested format for citations and references. If you prefer you may use another standard citation and reference format (e.g. AMA, MLA).

For Research Projects your project report should be from 10 to 20 pages (double spaced with 1" margins and 12pt font) and must have the following structure and content. (Deviations from this structure may be accommodated for specific projects by discussing them with me in advance.) Students pursuing departmental honors in Computer Science may use their Research Report as their semester project report.

1. Title Page
   Name the project, list all team members, identify the research advisor, give the date of the report.
2. Introduction
   Describe the general area to which your project applies and describe the specific research question that you are investigating. Assume that the reader is not familiar with your specific research area or your research question. Thus, you must provide enough information and organize it in such a way that the reader comes away understanding what your research question is and also why it is important and interesting within its area.
3. Background
   This section provides a context and foundation for your work. The context is set by reviewing the relevant details from the work performed by other researchers that have laid the foundation for your work. Your annotated bibliography will provide the raw material for this section. You will likely have mentioned and very briefly described some of this work in the introduction but here you delve deeper into the relevant nuts-and-bolts of what has been done as it relates to your work. The foundation is established by discussing specific components, concepts, techniques, data structures and/or algorithms that you are making use of in your work. This section should be written so that a reader who has taken courses on Data Structures, Computer Organization and Discrete Mathematics will have the background to follow the remainder of your paper.
4. Methods
   This section describes how specifically you will answer your research question. It presents the overall structure of your approach, the structure of your system and the structure of your experiments. If there are specific techniques that you will use in the analysis of your data, those are described here as well.
5. Preliminary Results
   Present and discuss any preliminary results that you have obtained from your experiments. You should use graphs, charts, tables, etc. as appropriate to efficiently and effectively communicate your results.
6. Status, Challenges and Future Work
   Describe the current state of your project, any significant challenges that you face in going forward and outline the work that you intend to complete during the next semester.
7. References
   All works that have been cited in the text must be listed as references in this section (do not use footnotes for references). See the Honors thesis style guide for a suggested format for citations and references. If you are not working toward honors and you prefer you may use another standard citation and reference format (e.g. AMA, MLA).

Give a 20 minute presentation summarizing your project report. You will not be be able to cover everything that appears in your research report in your presentation. You should be sure to focus on the following:

• Give a clear introduction to your project. Assume that the audience is knowledgeable about computer science, but do not assume that they know anything about your project area or your project specifically. After the introduction, everyone should know precisely what it is you have set out to do and why it is worth doing.
• Cover only the background that is absolutely essential and cover it at as high a level as possible while still being useful and effective. The interested audience member can always read your paper if they want a greater level of detail.
• Discuss the architecture (for implementation projects) or methods (for research projects).
• Give a demo of your application (for implementation projects) or present your preliminary results (for research projects).
• Discuss the current status of your project, the challenges that you face in going forward and what your plan is for the next semester.