The Final Report is the formal write up of your project. It should walk through your project from conception to completion. The document should clearly state the problem you were interested in solving and guide the reader through a high-level explanation of your approach to solving the problem. Finally, you should present the results that you were able to demonstrate and provide an assessment of the project as a whole. Appendices will be items such as your SRS, Design, Test Plan, Test Report and so on.
A sample outline for the document follows here. Note within the sample heading structure, furhter sub headings may develop at your discretion depending upon the clarity given by and length of the sub section.
Cover Page: Include the project title, your name, document title, and document date.
Table of Contents: Providing a table of contents will help readers navigate your document efficiently.
Abstract: The abstract is a very short summary of the report. The abstract is generally written after the rest of the document has been completed, since its purpose is to provide a summary of the document that follows. When you write the abstract, imagine that the reader will not read anything else. You must present the core ideas from your paper completely and succinctly. Remember, the abstract represents a very short summary of the entire report and should not simply be an excerpt of the introduction and/or conclusion. The abstract should contain the following at the very least.
Introduction: The introduction should set the stage for the rest of the document. It should include a description of the problem statement, a reference to background or related work that will be applicable, an analysis of why you are doing this project, and a discussion of what significance it has relative to other relevant works. In addition, state your solution to the problem and how it differs and expands existing works.
Glossary: If you are going to be using any technical terms in your document, define them here. Do not make assumptions about the experience or expertise of the reader.
Problem Domain: Describe the area of digital arts and sciences, computer science, engineering, or general science in which your problem occurs. Explain how your solution also fits into this area.
Literature Search: Provide a more involved discussion of previous work and literature that support your work.
Solution: Provide a high-level conceptual description of your solution to the problem. Avoid using large code fragments. If a large portion of code is necessary, refer to it and provide a complete listing in an appendix. Keep the discussion abstract and avoid implementation details; instead, describe your solution in terms of algorithms, pseudocode, and mathematical reasoning. You should also endeavor to use figures and tables as well, especially if the information you are trying to convey fits naturally in the visual domain. There may be several sub-sections to the Solution section and it is likely to comprise the bulk of your rerport.
Results: This section is where you will present and analyze the results of your work. Always focus on metrics and results which can be quantified. Be careful when discussing the results of subjective material such as User Interfaces. Provide test cases, screenshots of your software executing, and the corresponding results.
Conclusion: Your conclusion will sum up your project experience and provide a self assessment of your work. It should give a summary of what you accomplished and what you learned along the way. Analyze not only the advantages and disadvantages of the system developped, but also the process used in your development. Hypothesize about future work and direction for this system and the area of study. Identify any remaining unsolved problems or errors within your system.
Acknowledgements: Recognize individuals and organizations who helped you during the course of the project.
References: Provide the list of resources that you referred to throughout the life of your project. You may use any style, but be consistent and complete in your reference list.
Biography: Include a biography of yourself. Include a brief history of relevant places that you have worked and state your goals for employment or graduate study. Since this document is technical in nature, you should not include anecdotal information about your pets, family, relations, or pasttimes. Your focus will be on personalizing the work in relation to your own interests, desires, and goals.
Appendices: Include any related information or documentation created during the development of the project that does not fit into the sections above.
Index: Common indices include an alphabetical listing of relevant terms, an index of tables, an index of figures, and an index of functions to assist the reader in finding information efficiently.