Design a Robot That Helps

Planning

• Planning briefRequiredMission, requirements, and constraints written before building.
• Labeled sketchRequiredA drawing of the robot with its parts labeled.
• Input-processing-output diagramRequiredA diagram of what the robot senses, decides, and does.
• FlowchartRequiredA step-by-step flowchart of the program.

Mechanical

• Mechanical design that movesRequiredA stable base that moves reliably.
• At least one sensorRequiredThe robot uses a sensor as an input.

Programming

• A sequenceRequiredThe program runs steps in a planned order.
• A loopRequiredThe program repeats an action or check.
• A conditionRequiredThe program makes a decision from a sensor reading.
• Safe stopping behaviorRequiredThe robot stops safely when done or blocked.
• A second sensor or counter (stretch)StretchAn extra sensor or a counter variable for a harder mission.

Testing

• Three test runsRequiredThe mission is run and recorded three times.
• One documented improvementRequiredOne change is made after testing and its effect recorded.

Communication

• Final explanationRequiredA short explanation of how the robot helps and how you know it works.

A clear problem and user, plus the brief, sketch, IPO diagram, and flowchart.

Beginning:

Little or no plan; started building without a clear problem, brief, or diagrams.

Developing:

The problem is stated but some planning documents are incomplete or vague.

Proficient:

A clear problem and user, with a complete brief, sketch, IPO diagram, and flowchart that match the build.

Exemplary:

Planning is complete and clear and shows thoughtful requirements, constraints, and trade-offs.

How well the robot (or the configured simulator mission) is built to move and do the job.

Beginning:

Robot does not move reliably or falls apart; or the mission setup does not fit the goal.

Developing:

Robot moves but is wobbly or inconsistent; or the mission map is only roughly set up.

Proficient:

Stable base that moves reliably and carries its sensor; or a mission map that suits the goal.

Exemplary:

Sturdy, well-balanced design (or a thoughtfully configured mission) that fits the job cleanly.

Use of a sequence, a loop, a condition, and a safe stop.

Beginning:

Program is missing most required parts or does not run.

Developing:

Program runs but is missing a loop, condition, or safe stop.

Proficient:

Program uses a sequence, a loop, a condition, and a safe stop correctly.

Exemplary:

Program is efficient and well-structured, handling the mission cleanly.

Whether the robot senses the world and uses that reading to decide what to do.

Beginning:

No sensor is used, or the reading is never used to make a decision.

Developing:

A sensor is read, but the reading barely affects what the robot does.

Proficient:

At least one sensor is read and a threshold or condition uses it to steer the mission.

Exemplary:

Sensor use is calibrated and reliable, driving the robot's decisions accurately.

Three recorded runs and one documented improvement.

Beginning:

Little testing; results not recorded.

Developing:

Some runs recorded but no clear improvement made.

Proficient:

Three runs recorded and one improvement documented with its effect.

Exemplary:

Thorough testing with clear evidence that the improvement increased reliability.

Explaining how the robot helps, how you know it works, and how it is used safely and responsibly.

Beginning:

Cannot clearly explain what the robot does.

Developing:

Explains the robot but not how it helps, how it was tested, or how it stays safe.

Proficient:

Clearly explains the mission, how the robot works, the test evidence, and its safe stop.

Exemplary:

Explains the design, decisions, evidence, and responsible use convincingly to an audience.