This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
mec325:design_project [2021.07.07 19:09] Fil Salustri [Establishing Design Teams] |
mec325:design_project [2021.12.05 15:21] (current) Fil Salustri [Executive Summary] |
||
---|---|---|---|
Line 37: | Line 37: | ||
All teams in a given section will do the same project. By section, links to project design briefs are given below: | All teams in a given section will do the same project. By section, links to project design briefs are given below: | ||
+ | |||
+ | /* | ||
<WRAP alert> | <WRAP alert> | ||
Line 42: | Line 44: | ||
</ | </ | ||
- | /* | + | */ |
^ **SECTION(S)** ^ **PROJECT** ^ | ^ **SECTION(S)** ^ **PROJECT** ^ | ||
- | | 1 | [[https:// | + | | 1, 8 | [[https:// |
- | | 2 | [[https:// | + | | 2, 5 | [[https:// |
- | | 5 | [[https:// | + | | 3, 11 | [[https:// |
- | | 6, 11 | [[https:// | + | | 6 | [[https:// |
- | | 7 | [[https:// | + | | 7 | [[https:// |
- | | 8 | [[https:// | + | | 9 | [[https:// |
- | | 9, 13 | [[https:// | + | | 10 | [[https:// |
- | | 10 | [[https:// | + | | 12 | [[https:// |
- | | 12 | [[https:// | + | |
- | + | ||
- | */ | + | |
===== Project Deliverables ===== | ===== Project Deliverables ===== | ||
- | The deliverables of a project are those " | + | The deliverables of a project are those " |
+ | |||
+ | **A complete | ||
+ | |||
+ | Templates for the various reports are available in the [[https:// | ||
+ | |||
+ | Each team will keep all these deliverables in a single [[teaching: | ||
Reports should be written as technical documents targeted at upper management and technical staff, not a sales or marketing tool to convince prospective customers to " | Reports should be written as technical documents targeted at upper management and technical staff, not a sales or marketing tool to convince prospective customers to " | ||
- | See the page on [[teaching: | + | See the page on [[teaching: |
The format (including fonts, colours, pagination, headers & footers, etc.) is very important. **The report format must not be changed**. I will apply [[teaching: | The format (including fonts, colours, pagination, headers & footers, etc.) is very important. **The report format must not be changed**. I will apply [[teaching: | ||
- | |||
- | Each team will keep all these deliverables in a single [[teaching: | ||
The whole project will require several documents, as listed in the table below. You may update, refine, and correct these documents throughout the semester such that the final set of all documents by the end of the semester are as good as you can make them. | The whole project will require several documents, as listed in the table below. You may update, refine, and correct these documents throughout the semester such that the final set of all documents by the end of the semester are as good as you can make them. | ||
Line 80: | Line 83: | ||
| [[# | | [[# | ||
| [[# | | [[# | ||
- | | [[#Detailed Design]] | '' | + | | [[#Detailed Design Specification|Detailed Design]] | '' |
| [[# | | [[# | ||
| [[#CAD Files]] | '' | | [[#CAD Files]] | '' | ||
- | | [[design: | + | | [[design: |
**NOTES** | **NOTES** | ||
Line 105: | Line 108: | ||
* a properly named and shared PRS document, | * a properly named and shared PRS document, | ||
* a properly named and shared Appendices document, | * a properly named and shared Appendices document, | ||
- | * a properly named and uploaded (to the LMS) PDF version | + | * a properly named PDF of the above documents, |
- | * completion of the corresponding tab of the [[design: | + | * a Turnitin report of the PRS document, //stored in your team's Shared Google Folder//, |
+ | * (One team member can upload the PRS PDF to the LMS, wait for the Turnitin report, then download that report | ||
+ | * (The name of the Turnitin report would be the same as the PRS PDF with '' | ||
+ | * completion of the corresponding tab of the [[design: | ||
+ | |||
+ | The Turnitin report is due within 48 hours after the deadline for the Milestone, to accommodate foreseeable delays by Turnitin. | ||
==== Milestone 2 ==== | ==== Milestone 2 ==== | ||
Line 118: | Line 126: | ||
* a properly named and shared PCS document, | * a properly named and shared PCS document, | ||
* a properly named and shared Appendices document, | * a properly named and shared Appendices document, | ||
- | * a properly named and uploaded | + | * if you changed the contents of the PRS, you must have a revised PRS document available too, |
- | * completion of the corresponding | + | * properly named PDFs of the above documents, //stored in your team's Shared Google Folder//, |
+ | * Turnitin reports of the PAS and PCS documents, //stored in your team's Shared Google Folder//, | ||
+ | * (One team member can upload the PDFs to the LMS, wait for the Turnitin reports, then download those reports | ||
+ | * (The name of the Turnitin report would be the same as the PDF with '' | ||
+ | * completion of the MS2 tab of the [[design: | ||
+ | |||
+ | The Turnitin report is due within 48 hours after the deadline for the Milestone, to accommodate foreseeable delays by Turnitin. | ||
==== Executive Summary ==== | ==== Executive Summary ==== | ||
Line 130: | Line 144: | ||
* a summary of your team goals (from your [[design: | * a summary of your team goals (from your [[design: | ||
* a review of key requirements of your intervention, | * a review of key requirements of your intervention, | ||
- | * a full page sketch of your refined final concept, | + | * a full page sketch of your refined final concept, |
- | * a summary of the highlights of your detailed design, and | + | * a summary of the highlights of your detailed design. |
- | * completion of the corresponding tab of the [[design: | + | |
- | The executive summary can be no longer than 7 pages (cover page, team declaration page, and five pages of text as outlined above). | + | The executive summary can be no longer than 7 pages total (cover page, team declaration page, and five pages of text as outlined above). |
+ | |||
+ | Use full paragraphs in this deliverable; | ||
+ | |||
+ | Do not have any references in your Executive Summary. | ||
==== Detailed Design Specification ==== | ==== Detailed Design Specification ==== | ||
Line 143: | Line 160: | ||
References in [[https:// | References in [[https:// | ||
- | ==== Appendix 1 ==== | + | ==== Appendices ==== |
+ | === Appendix 1 === | ||
Solidworks Drawings - a //set of working drawings// of your product, sufficient to allow someone to actually assemble it. | Solidworks Drawings - a //set of working drawings// of your product, sufficient to allow someone to actually assemble it. | ||
* Insert drawings into your report in landscape mode, ensuring correct aspect ratio. | * Insert drawings into your report in landscape mode, ensuring correct aspect ratio. | ||
Line 154: | Line 173: | ||
* The CAD Drawings in this appendix are NOT " | * The CAD Drawings in this appendix are NOT " | ||
- | ==== Appendix 2 etc. ==== | + | === Appendix 2 etc. === |
Whatever other ancillary material you need to demonstrate and justify your design, such as data sheets on components you found on the web or in hard-copy catalogues, or for calculations you wish to include about how you designed your product (e.g. calculating forces, loads, velocities, component sizes, etc.) | Whatever other ancillary material you need to demonstrate and justify your design, such as data sheets on components you found on the web or in hard-copy catalogues, or for calculations you wish to include about how you designed your product (e.g. calculating forces, loads, velocities, component sizes, etc.) | ||
==== Report tips ==== | ==== Report tips ==== | ||
+ | |||
+ | **Update documents frequently**\\ | ||
+ | Since all documents will be reviewed at the end of the semester, a team should feel free to continually update their reports until the final deadline per the Weekly Schedule. | ||
**Length of the report**\\ | **Length of the report**\\ |