Hey guys, I was referring some documents on how we could prepare our final report. I found some points which, I think, are worth including in our final piece. I organized the whole idea as shown below. Please Read and suggest.
Our Final report would include the following sections:
-Title and full author and team info on the first page
-Abstract (short summary of the Project)
-Introduction (motivates the project)
-Approach and methods
-Results from the project tests (how well it worked)
-Strengths and weaknesses (the good and bad parts, and why)
-Summary
-References
-Appendix
It would also be a good practice if we would be able to remember the following points while writing our final report:
- Use graphics (i.e., diagrams, graphs, tables) to illustrate our approach, but also explain it clearly in words.
- When we describe our approach, we should relate it to the key principles and ideas we learned in class. Feel free to add any other relevant references you have read which helped us with the project.
- Our references to other books/readings should be done as professionally as those in the textbook.
- Explain any original ideas and additions that are a part of our design. For failed versions of the design we would describe them briefly and explain why we eliminated them.
- We should reference the manual for some information.
- Write the report for an informed lay audience; that means we need to provide enough detail so our project could be replicated by the reader.We should explain and justify all of the important design choices.
Wednesday, 24 March 2010
Subscribe to:
Post Comments (Atom)
Well, yesterday we were also discussing the length of the report. Do we know how many pages we need. Usually when you design some product, manual and prototype matters and not the length of the report?
ReplyDelete