This explains the semester-long team design project.
Here's a really good design project by a MEC723 team from 2016. If you can match their quality, you'll do fine.
Teams will be determined in the Week 1 lab.
Once the teams have been assigned, you should:
You will be tracking your responsibility as part of the major project. This information will be used when assigning grades to the group project.
You must have and use a design journal for this project.
In 2021, all students worked together on a single project - an Organic Home - which was defined here.
In 2020, all students worked on the project Addressing Food Deserts in Northern Canada.
In 2019, all students worked together on a single project - Redesigning the Ryerson PTECH Station.
The deliverables of a project are those “concrete” things that must be presented to a client (in this case, the instructors) to constitute a completed project. The deliverables for this project include:
The final written report will use this template. Deviations in formatting, font selection, etc. without the express written permission of the instructor will result in a grade penalty.
You can read about Salustri's grading policy.
Two milestone reports will be expected from each team. See the weekly schedule for their due dates.
Each milestone report will cover specific topics and is intended to demonstrate progress made toward finishing your design.
The milestones will be written reports, but there is no particular format. Use point form extensively. No full paragraphs are required. You may write prose if you believe it is necessary, but there is no obligation to do so. Be clear, concise, complete, and accurate.
All members of a given team will get the same mark for the milestone.
The details of what is expected in each progress report is listed below.
The first milestone will be graded according to the Milestone 1 Rubric. It must include:
The second milestone will be graded according to the Milestone 2 Rubric. It must include:
Refer to the weekly schedule for the deadline of the final report.
Refer to the reporting guide for general guidelines on writing reports.
The report should be written as a technical report targeted at upper management and technical staff, not a sales or marketing tool to convince prospective customers to “buy” your product.
See the page on grading team reports for details on the rubric used.
The format (including fonts, colours, pagination, headers & footers, etc.) is very important. The report format must not be changed. I will apply deductions and penalties for changes to the report format. The following notes explain what goes into each part of the report.
You may remove optional section headings if you have nothing to report. Optional sections are indicated below.
When you upload your final report as a PDF to the LMS, make very sure the filename is
SSTT Report MEC325 YYYY.pdf.
TITLE OF PRODUCTwith the name of the product you have designed.
“TEAM SSTT”with your team's actual ID number.
SSTTin the footer of pages with your team's actual ID number.
design brief addenda) of how your team has decided to interpret vague terms or conditions as defined in the design brief;
Provide an up to date product requirements specification, including:
Provide an up to date product architecture specification for the overall product system. Include:
Provide an up to date product concept specification for the product. There is no need to develop a PCS for each system within it. Include:
No more than 5 pages of text explaining how you did the detailed design of the product.
No more than 2 pages summarizing the benefits of your design intervention itself, it's key features, etc.
No more than 2 pages summarizing and explaining any points about the project and how your team did it that you think is noteworthy.
No more than 1 page summarizing the entire intervention and project.
Properly cited list of references using the ASME Reference Style.
) in the body of your work, the number (
12in this case) needs to link to the item in your References section that gives the full reference of the source.
Solidworks Drawings - a set of working drawings of your product, sufficient to allow someone to actually assemble it.
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.)
Length of the report
Irrelevant. It must be as long as necessary and no longer.
We're engineers. We don't do “style.” We want factual, dry, simple, easy to read reports. Like a Vulcan would write. The design is hard enough to understand; you mustn't make the reader's job even harder by using difficult language.
Keep is short and simple, and keep it as precise as possible.
You can write “we” if it's obvious from the context who “we” are. Otherwise, use “the team.” You can refer to individual team members by their surnames without titles5)
The report must demonstrate that
you followed the Roadmap correctly and
justified your decisions.
Example: You spend 2 hours working on an idea that ends up being removed from the final design. You must (a) count those hours, and (b) briefly describe (a couple of sentences is enough) that work in an appropriate discussion section of the report.
Unnecessary material is BAD
To include any unnecessary material will be considered an error.
Example: If you’re designing a stapler, you don’t need to include a whole page about the history of stapling unless there’s some specific information that directly informs/justifies decisions you made in your project.
Example: do not explain what the Roadmap process is; we already know.
Along with your final report, each team must submit a full set of Solidworks files of their design.
Refer to the weekly schedule for the timing of oral presentations.
Suits and ties are not required, but a clean, well-groomed appearance is an important part of being a professional engineer.
Presentations will start promptly. Each team will be given EXACTLY 10 minutes to make their presentation.
A PC & data projector will be available, with PowerPoint installed. You will expect to have your presentation on a USB key or a CD.
The presentation should summarize your project in a professional and technical manner. You are not trying to sell your product.
Refer to the reporting guide for further information and tips on presentations.
During the presentations, you will be graded on your ability to present and not on the technical content of your presentation or the merit of your design. Among other things, this includes: