This is a posting of the documentation that we created last year that won us the design award at worlds last year. Part of the purpose of our club is to improve not only our own engineering skills, but also those of other vex teams across the world.
Included are our Requirements Document, our Design Document, a short presentation that we gave to the design award judges at worlds, and a design memo that we leave with judges to give a quick, concise recap of what our team is and does.
We encourage the use of these documents, especially the design and requirements documents as they are standard in the engineering field. Following is a description of the purpose of each document.
Requirements Document - States what the system shall and should do in order to be considered an acceptable product. These requirements include both Vex game rules and team requirements that we decided upon as a team.
Design Document - The purpose of the design document is to lay out the team’s designs for each subsystem, including variations as the system evolves. The document also includes our system for determining which design to use. The last part of the design document is the testing and verification section where we determine through both physical experimentation and mathematical analysis whether each subsystem fulfills each requirement put forth in the requirements document.
Presentation - This is a short presentation we gave to the design judges at worlds to attempt to control the discussion and highlight what we choose about the robot, while providing answers for the more generic questions such as “What does your robot do?”
Design Memo - This is a memo designed to be short and concise and remind judges about what makes our robot stand out among the hundreds of teams.
designDocGateway1.pdf (119 KB)
gatewayprezismall.pdf (422 KB)
reqDocGateway.pdf (86.1 KB)
Robot Design Memo.pdf (77.2 KB)
