Embedded Files
Break it Down Into Subsystems
Break it Down Into Subsystems
Each of the tasks you identified in the previous stage represents a different subsystem of your robot. A subsystem is another word for "part" of the "whole." Let's think about all of the tasks your robot needs to perform and assign it a subsystem type based on it's function.
Drivetrain - Transports the robot to different locations.
Object Manipulator - Interacts with an object to perform a specific action.
Accumulator - Storage for objects that the robot has interacted with.
Moving The Robot
Drivetrain
Button Release
Object Manipulator
Picking up Rings
Object Manipulator
Storing Rings
Accumualtor
Turning Rings
Object Manipulator
Depending on your team, you might split into smaller groups, with each group in charge of researching, brainstorming, and coming up with ideas for one subsystem of the robot. Team members can work on researching for the different subsystems of the robot at the same time to help build it faster. For this website, we’re going to focus on just one subsystem of the robot and show you how to go through the design process for that part. When you work with your team, it will be important to discuss together how all the subsystems will work together in the final design.
Let's take a look at the criteria for a quality notebook entry for the developing solutions stage of the engineering design process.
Brainstorm, Diagram, Prototype Solutions Notebook Entry Criteria
Exceeds
Lists three or more possible solutions to the challenge with labeled diagrams. Citations provided for ideas that came from outside sources such as online videos or other teams.
Meets
Lists one or two possible solutions to the challenge. Citations provided for ideas that came from outside sources.
Below
Does not list any solutions to the challenge.
Day 3:
Read your team's initial list of desired qualities for the task.
Discuss with your team to add new ideas or make changes to the list.
Write a clear and simple design statement that includes all the important details from your list.
Use the internet to research different ideas and solutions that already exist.
Write down what you find, and remember to give credit to your sources by listing them in APA format.
Day 4:
Look over the information your team found during the research phase.
Talk with your team about each solution you found. Point out the good parts (strengths) and the not-so-good parts (weaknesses) of each one.
Some of the solutions you found online might solve your problem right away. Others might need a few changes to work.
Using your research as inspiration, draw sketches of at least three solutions your team thinks are worth trying. You can also mix different ideas from your research to create better solutions!
Label your solutions with the important parts that are being used in your design.
For each of your three designs, write down an evaluation of how well the robot addresses the design's goals. Your team should complete this part together.
Select Best Solution & Plan Criteria:
Exceeds
Explains why the solution was selected through testing and/or a decision matrix. Fully describes the plan to implement the solution.
Meets
Explains why the solution was selected. Mentions the plan.
Below
Does not explain any plan or why the solution or plan was selected.
Day 5 (Part 1):
Create a decision matrix for your solutions. A decision matrix is a tool that is used by engineers to help you evaluate competing design solutions.
How to Make A Decision Matrix
First, list the different designs or ideas you are thinking about across the top of a table.
Then, list the important things you care about (like speed, strength, or how easy it is to build) down the side.
For each design, give a score for how well it meets each important thing. A lower score means it is better.
After you score everything, add up the numbers for each design.
The design with the lowest total score is usually the best choice!
After you have completed the matrix, select the design your team will commit to buidling for this portion of the cycle. Write down why your team is choosing the design.
Later, after testing the design, your team can always decide to try a different approach if this solution didn't quite work out the way your team envisioned.
Day 5 (Part 2):
Develop an implementation plan for your solution.
Your plan should include:
How long will each phase of the project take?
Who should work on what things?
How does the plan fit into the overall project timeline?
What are any additional concerns your team needs to pay attention to (e.g., upcoming tournaments or deadlines)
Why are we discussing the plan so late?
We are talking about the team’s plan at this point because we want to show you how to focus on notebooking for each part of the robot. It also matches the order that VEX uses in their engineering notebook rubric.
Even though we are mentioning "the plan" now, it might actually help your team to talk about the overall plan earlier in your engineering process. For example, your team could create a timeline that covers building the whole robot, not just one part like the drivetrain.
At Waiakea Intermediate, we always think about the big picture of what we want our robot to look like in the end. But we also find it easier to set smaller goals and timelines for each part of the robot. This helps our team stay on track and not feel overwhelmed.
Page updated
Google Sites
Report abuse