Inidividual wiki report
- what to turn in
- please just turn in a hardcopy of the first page of your wiki report
- you’ll need to hit print preview to print out multisheets if your first page prints out to more than one page
- please just turn in a hardcopy of the first page of your wiki report
- It’s worth 10% of your final grade
- Show the design development cycle for your “thing”
- Collection of lab assignments + writeup
- Lab 3 – brainstorming and sketching ideas
- Lab 6 – initial downselect andCAD refinement utilizing COTS parts
- Lab 8 – design selection (trade matrix), associated calculations and data/part sources, and assembly drawing
- Collection of lab assignments + writeup
Report Writeup
- Problem definition and summary
- Requirements
- Specifications
- Concept generation and sketches (lab 3)
- Initial downselect & design refinement (lab 6)
- Final selection, supporting calculations or data, and assembly drawing (lab 8)
- Conclusions
I will especially be looking to understand how your designs work and why you made the decisions you did. Clear communication, calculations, data, etc., will be extremely useful to help me gain this understanding.
For good examples of inidividual wiki reports, please see the Precision Kiting team from 05-06 or Hexaball team from 05-06. As an example, I have posted a template from last year’s Hexaball team here.
Report scoring
Here’s the breakdown for grading these reports that I used last year. I haven’t decided exactly the breakdown for this year, but it will be close to this:
| Technical content & clarity | 40 |
| Organization & Appearance | 25 |
| Syntax & grammar | 20 |
| Links, x-refs & citations | 15 |
| Total | 100 |
Other info on wiki reports
Also see the presentation from Oct. 4, 2006
- Oct. 4 Lecture PPT posted It included info on:
- 2nd and 3rd presentation,
- Individual wikiReport
- Grading
Tips for making wikireports
- Have someone on your team make up a team template. See example (here).
- Be carefull not to loose text when writing at the edit window
- Sometimes your connection may \”time out\” and you could lose your current edit.
- I recommend copying the contents of the edit window to your a text editor before you hit save on the wiki. This way you won’t lose data.
- Don’t wait till the last minute to finish your report. The server will get slow if there are lots of people logged in. It tends to be slower when accessing the wiki from off campus too.
- See Will’s Wiki Tips or PDF of Will’s Wiki Tips
Page last modified on November 25, 2006, at 04:23 PM
