Criteria and constraints are always developed with the end client/stakeholder in mind. As students set up tests, they must pull back to the criteria to make sure that the outcomes they are getting meet those criteria.
For example, if an engineer is tasked with designing and constructing a bridge that allows big, heavy grain trucks to carry cargo across the river, but the engineer designs a bridge for a bicyclist, the criteria and constraints identified for the outcome were totally ignored. The bridge will be useless for its intended purpose. It seems the engineer didn’t test a prototype against the criteria and constraints at all.
It's understood that the design process is not linear. During the testing phase, it might become quite evident that the steps do not stay in order. As students test their solution against the criteria and constraints, they may realize that they need to go back to the drawing board to develop their iteration to best meet client needs.
Look at the following graphic of the Design process:
What did you notice about how the steps would inform students for re-design? How might you convey that to your students?
Look at the decision tree below on How to Test a Solution. How might you develop a plan or decision tree in order to help students understand the importance of testing?
As you see, the tests can inform the decisions that students need to make for the final solution design.
With your bite-size experience team, brainstorm possible solutions students may test and how the data will inform their re-design. Record your brainstorms on your team note-taking document and let your School Liaison know you are ready for feedback.