The engineering design process is a series of iterative steps. This means that the steps are sometimes sequential. For example, when beginning to build a robot for the first time with your team, you start with Step #1 through Step #7. Once you begin to test or assemble the robot's subsystems, you may find that your design needs to be revised. THIS IS NORMAL!
Then, as a group, you need to decide what to do next. For example, do you return to the brainstorming and research stage, or do you go back and develop more ideas using the brainstorming and research that has already been accomplished?
Often teams will go back and forth between #7, test and evaluate, and #8, make improvements for most of the time building a robot. This is the iterative approach when the robot or code is tested and improved in repeated cycles. All design processes occur in this same way.
A common mistake is for teams to break down a robot entirely and start over when something needs to be fixed. This defeats the purpose of using the engineering design process and engineering notebooks. Successful teams have a plan and stick to it. They document their engineering design process in their notebooks and use their notebooks as a tool to help them succeed. They keep the parts that work and fix the parts with problems.
Please only make significant changes, break down, or tear apart a robot with a team consensus and approval from your coach!
Read the game manual carefully and prioritize the problems in the game your team wants to solve. Then, list all criteria and constraints, including size requirements, number of motors, and significant rules to the game that will affect the design of the robot.
Generate as many different ideas as possible. All ideas should be sketched and recorded, even if they seem crazy. Crazy ideas can sometimes lead to amazing ideas! This could be done individually or as a group and should be done before you begin researching. Often students will find a robot online that they like and lose their own creative thinking process.
The best way to research is to Google Search different robot subsystems. Once teams post their robots for the season, YouTube is an excellent source of robot ideas. Vex forums and Discord servers are other resources.
Using your brainstorms and research, develop multiple solutions that acknowledge criteria and constraints. Each team member should do this individually and then contribute at least two ideas to the group for discussion. Students can hand sketch their ideas or use a CAD program like Autodesk Fusion 360, Google Sketch Up, or TinkerCAD.
Come to a consensus as a team on the design that best meets the criteria, fits within the constraints, and has the least amount of negative characteristics. An unbiased system, such as a decision matrix, will help your team make effective and efficient decisions in the team's best interest. Often students will like their ideas the best. Make sure to remain open to all ideas when presented.
Begin to build the robot using the notebook as your guide. At first, many team members can get in on the action of the building since there is no robot to program, and tournaments may be a long way off. Consider dividing the team up to build the different subsystems of the robot.
Test the robot and gather data on performance. All testing data should be recorded in the notebook using data tables and appropriate units of measure.
Based on testing results, design changes are made. Then, models and prototypes are rebuilt and tested again. As a result, many teams spend most of their time moving between steps 7 and 8.
All results must be documented in an engineering notebook to be shared with the robotics community.
Read the game manual carefully and prioritize the problems in the game your team wants to solve. Then, list all criteria and constraints, including size requirements, number of motors, and significant rules to the game that will affect the design of the robot.
Generate as many different ideas as possible. All ideas should be sketched and recorded, even if they seem crazy. Crazy ideas can sometimes lead to amazing ideas! This could be done individually or as a group and should be done before you begin researching. Often students will find a robot online that they like and lose their own creative thinking process.
The best way to research is to Google Search different robot subsystems. Once teams post their robots for the season, YouTube is an excellent source of robot ideas.
Using your brainstorms and research, develop multiple solutions that acknowledge criteria and constraints. Each team member should do this individually and then contribute at least two ideas to the group for discussion. Students can hand sketch their ideas or use a CAD program like Autodesk Fusion 360, Google Sketch Up, OnShape or TinkerCAD.
Come to a consensus as a team on the design that best meets the criteria, fits within the constraints, and has the least amount of negative characteristics. An unbiased system, such as a decision matrix, will help your team make effective and efficient decisions in the team's best interest. Often students will like their ideas the best. Make sure to remain open to all ideas when presented.
Begin to build the robot using the notebook as your guide. At first, many team members can get in on the action of the building since there is no robot to program, and tournaments may be a long way off. Consider dividing the team up to build the different subsystems of the robot.
Test the robot and gather data on performance. All testing data should be recorded in the notebook using data tables and appropriate units of measure.
Based on testing results, design changes are made. Then, models and prototypes are rebuilt and tested again. Many teams spend most of their time moving between steps 7 and 8.
All results must be documented in an engineering notebook to be shared with the robotics community.