The engineering design cycle — Engineering, 11–13 years
Engineers turn a need into a tested solution by defining the problem, imagining options, building, testing and improving.
A solution grows through testing
Engineering is a way to make something that meets a real need, such as a bridge, a water filter or a safer bike light. You define the goal, sketch several ideas, build a model, test it and use what you learn to improve the next version.
Why engineers repeat the process
The first idea is rarely best because real materials, people and weather behave in complicated ways. The cycle grew from the need to solve problems reliably instead of trusting a clever guess. Testing reveals failures while they are still small, cheap and safe to fix.
A paper bridge
The challenge is to span two books with one sheet of paper and hold 20 coins. First, make a flat bridge and test it: it holds 4 coins. Next, fold the paper into a zigzag beam, test again and count 22 coins. The result meets the target, so you record the fold pattern and its limit.
A clever first try is not proof
It is tempting to stop when a model works once, especially if the idea looks elegant. But one successful test may be luck: the load, angle or material may have been unusual. Repeat fair tests and change one feature at a time, so you know what caused the improvement.
Where the cycle is used
Product designers use this cycle for wheelchairs, games and kitchen tools; civil engineers use it for roads and buildings. You can use the same thinking when making a phone stand or planning a school garden, as long as you name the need, test the result and accept that revision may be necessary.
Keep exploring
Other languages
Loading MyLeoNes™…