Difference between revisions of "Final Report"
From PDP/Grid Wiki
Jump to navigationJump to search| Line 10: | Line 10: | ||
Briefly discuss the purpose of the project (i.e. review the original motivation). Include a one-or-two-sentence summary of the overall result(s)�kind of like an abstract. | Briefly discuss the purpose of the project (i.e. review the original motivation). Include a one-or-two-sentence summary of the overall result(s)�kind of like an abstract. | ||
| − | * | + | * Work Done |
| − | Talk about methods and tests | + | Talk about work done. In some cases this will be a summary of what was produced, in others a summary of methods and tests used. Remember, no jargon�this section should include a simple (short) explanation of the work done, and why this approach was the most appropriate given the motivation and starting situation. |
* Findings | * Findings | ||
| − | A summary of the results. Include relevant numbers / conclusions and what they mean in the real world. Although several different approaches may have been taken during the project, the main body of the report (in the | + | A summary of the results. Include relevant numbers / conclusions and what they mean in the real world. Although several different approaches may have been taken during the project, the main body of the report (in the Work Done or Findings sections) do not need to describe all of them; most important are the results that you consider to be the most accurate and/or relevant to the project. All other tests and results should go in an appendix |
* Recommendations | * Recommendations | ||
| − | This section and the Findings section are definitely the most important and should constitute the bulk of the report. This section is where, based on the methods and results, the original project motivation is addressed, questions raised there are answered and recommendations are made for future activities or deployments. | + | This section and the Findings section are definitely the most important and should constitute the bulk of the report. This section is where, based on the work done, methods, and results, the original project motivation is addressed, questions raised there are answered and recommendations are made for future activities or deployments. |
* Limitations / conclusion | * Limitations / conclusion | ||
| Line 28: | Line 28: | ||
* Appendix | * Appendix | ||
| − | Everything else goes here | + | Everything else goes here. It might be documentation of configurations, pointers to code repositories, detailed explanations of algorithms, details relevant to the final results and recommendations. You can reference the appendix in the report, but do not depend on it�most readers external to the project should be able to know everything he or she wants to know without ever looking at the appendix. Recommendation: do not write the appendix after you have finished the report�treat it like a log or a field journal. Include the relevant tables and graphs to document how the final result was arrived at. This document becomes your appendix and will make it infinitely easier to write the final report, which summarizes the project. |
Summary: | Summary: | ||
