Section 2 of the Group Final Report (due Monday October 22, 2007 by 5PM via email)
This section covers basic need and problem statement as well as information about your team, faculty advisor, and sponsors.
- Email your completed section 2 .doc file to your your advisor, the writing Comm. TA, your class TA and if appropriate post to your Wiki Group?
- If you post it to your wikiGroup, just send a link to its location on the wiki to the above recipients. The writing Comm. TA (Tina Dyer) will be grading this section and give you feedback on the structure and organization, grammar and syntax. Your class TA will also give you comments and may give grading input.
You should consider having 2 people work on this and list there names. It will be worth the equivalent of writing a weekly memo for 2 people in your group. (mainly just because these will be the first people figuring out how the word template works, but this should otherwise be a straight forward section to write).
This is just to get you exposed to the ME 4000 Final report template. For more details about the report, refer to Group Final Report.
The Final Group report is broken up into files based on sections in the report. A good example to follow can be found in the Precision Kiting Report. Note that we are making changes to the way we are writing up design requirements and design specifications in 2007 that follow more closely with what is outlined in Ulrich and Eppinger’s text. So the Precision Kiting Report and other examples that are linked off the Group Final Report page will have slightly different organization in the requirements/needs and specification sections than we will follow this year.
Section 1 of the final report includes the executive summaries you already started on, plus a table of contents that will self-generate if you use the files in the provided template.
Section 2 is primarily content that you already have and includes the following sections (Section 2 template is here, explanation of what goes in this section is here, example of section 2 here, 2nd example here):
2. Context
2.1. Need Statement
Again use “Body Text Indent” for the body of the text.
2.2. Problem Statement
Text, Text…. (you should already have this!!!)
2.3. Design Team
2.3.1. Student Design Team Members [“Heading 3”]
2.3.2. Teaching Team
2.3.3. Corporate Liaisons and Sponsors
Include if appropriate
2.4. Team Circumstances