Individual Final Wiki report
What makes a good topic (Here are some examples)
- Detailed design and analysis. Completing a detailed design and analysis of a component or sub-assembly of your project. A complete report would include concept generation, benchmarking, concept selection (with defined selection criteria/justification), detailed design (with drawings), and applicable analyses.
- Building prototype & documentation. Completing a prototype of a component of sub-assembly of your project. A complete report would include a summary of some of the topics in 1 above (including drawing(s)), plus details of the manufacturing details and justification for why the prototype was made in this manner. You should also discuss any issues/difficulties you encountered while completing the prototype and comment on the functionality of the prototype (is it a good design and would you suggest design modifications or different manufacturing methods). Discuss what you learned from making the prototype.
- Validating simulation. Put together a simple experiment to produce results that will validate your simulation/analysis. This could be an experiment to validate structural, thermal, fluid, dynamical, or other simulation or analysis results. You could complete your experiment on an actual prototype or construct a special or simplfied version of the thing you are simulating.
- Develop analysis tools. First off, you should have a reason for developing analysis tools, rather than just analyzing a part and moving on. There should be a long standing purpose for developing these tools. You will outline the purpose and functionality of the analysis and discuss formulation you used and assumptions that were made. You should also prepare instructions for users of your software, including the limitations and possible issues users will experience (most likely based on your assumptions). Since simulation tools are only as good as the validity of the results they produce, it would be best if you can validate your simulation results. If this will be very involved, it may be best to work with someone else, see 3 above.
- In-depth research. If your project warrants extremely thorough research on a particular component (via benchmarking) or any other aspect, you could focus your report on explaining the need for this research and summarizing the findings of your research, including references (pictures of other designs, articles, etc.).
- Some combination of the above.
Keep in mind that your topic should be distinct from your team-mates. It is important that only 1 person per group lay claim to given top, or else you will split the grade with that person, i.e., since your report is worth 15% of your grade, your maximum grade will be a 50% of 15%)
What you’re pages should include
- You should have a summary page with an index of links to sub-pages.
- The summary page should inlude
- Your problem statment (what you’re report is documenting), including why this was important and relevant to work on.
- Summary of your approach
- Summary of results
- Lessons learned
- Some nice pictures on your summary page might be nice too.
- Put details of your report on sub-pages that are linked from your summary page
- Good style would include links on your subpages, so that you can go back to your summary page or other related pages (Optionally, you could have your report table of contents on each of your reports pages)
- List references (either on the web or upload files and create local links).
- Make sure to include proper citations, plagerism will be penalized in your report grade.
What you’ll turn in
- A print-out of the summary page for your wiki report (click the \”printable view\” tab in the upper right before printing.
- Make sure this page has your name and project name on it.
When your report is due (by 5PM, Wednesday, Dec. 7)
- Please hand in the printout of your summary page by Wednesday, December 7, 2005. Feel free to turn it in early, I would appreciate this since I’ll have a lot of these to review.
How you’ll be graded
- Depth and completeness of your topic
- Clarity and organization of how your topic is presented
- Appearance of your report pages
- Perceived usefulness of your topic for your team and future teams
Page last modified on November 03, 2005, at 10:44 PM