Because of the large varity of potential projects there is a correspondingly large number of report formats. The following report format is recommended; however, other formats are fine, but should be discussed with the instructor.
Title page
This contains the project title, author, date, and an "Executive Summary." The latter is a brief description of the project and its results, all of which should not take up more than one page.
Introduction
Purpose of the project: what problem was solved? Importance of the project: Background on prior work, special features, description of the product and how it solves the purpose.
Methodology
How did you solve the problem. This should contain information about how you designed your project, constructed it, and operate it. For software projects this section should discuss your software architecture or algorithm. You should discuss the software architecture, similar algorithms, etc. which lead to your final program.
Results
This section should contain performance data in an appropriate useful form such as graphs, (as an example for a temperature controller, temperature vs. time could be presented), comparison of results with specifications, etc.
Conclusions
Have the project goals been achieved? If not, why not?
Recommendations
What should be done next? Is this ready for production, or can improvements be made? If so, what?
Appendices
Use appendices for detailed information, e.g., circuit diagrams, program listings, flow charts and so forth which were not previously included in the report.
Download a copy of the evaluation form (PDF, 8kB) I will use to grade your final report.
Download sample final reports similar to that described above.
Medical Astronaut Monitoring System (PDF, 105kB)
Optical Process Monitor(PDF, 187kB)
Design of a Convolutional Code Simulator(PDF, 328kB)
Automated S-Parameter Analyzer(PDF, 3.5MB)
This report does not follow the above format but is excellently written nevertheless.