Once a prototype has been built, the next step is to test and evaluate how well it actually addresses the original problem. This stage is where theory meets reality. As an engineering student, you’ve likely had experiences where something worked in theory but not quite as expected in practice—this is exactly why testing is essential.
Testing connects back to problem identification because it asks: Does the solution we built really solve the problem we set out to address? At the very beginning of the process, you defined a specific problem, along with requirements and constraints. Now is the time to measure your prototype against those expectations. Without this feedback loop, it would be impossible to know if your design is truly successful or if it needs refinement.
What does testing involve?
Evaluation is more than just running tests—it’s about interpreting the results. This is where you compare data to your original problem statement, requirements, and constraints. If the design falls short, it doesn’t mean failure—it means you’ve gained valuable insights to guide improvements. In fact, most real-world engineering projects go through multiple cycles of testing and redesign before reaching a final product.
By systematically testing and evaluating, engineers ensure that they are not just creating “a” solution, but the right solution to the identified problem. This keeps the engineering design process grounded and ensures that problem-solving remains tied to real needs rather than assumptions.