Engineering Design: Testing, Improving, and Explaining Solutions
Core ideas
Engineering design is a process for solving problems. Engineers define the problem, identify criteria for success, and list constraints such as cost, time, materials, and safety. They brainstorm possible solutions, choose one, build a prototype or model, test it, collect data, and improve the design. Testing should be a fair test: change only one variable at a time and keep all other conditions the same. Measurements should be repeated to check reliability. A design that fails a test is still useful because the failure shows what to change. Tradeoffs are common: making a structure stronger may make it heavier or more expensive. The best design depends on the criteria and constraints, not on one feature alone.
Models represent parts of a system and help engineers predict how a design will behave. Models are not exact copies, so their limits matter. Communication matters too: clear drawings, labels, data tables, and explanations let others evaluate and improve a design.
Traps to avoid
Do not confuse criteria, the goals a design must meet, with constraints, the limits on the design. Do not change several variables at once in a fair test. Do not treat a prototype as a final product or a failed test as a failure of the engineer. Do not choose a design without checking it against all criteria and constraints.
Worked example
A class must build a paper bridge that spans 20 cm and holds 100 g using at most five sheets of paper. They test flat paper, folded paper, and rolled paper, changing only the shape while keeping span, materials, and test method the same. Rule of thumb: compare designs with one variable changed and measure success against the stated criteria.