POSTER 05 · FUNDAMENTALS
The Engineering Design Process
A disciplined, iterative loop for turning a need into a working, tested solution. Engineering rarely runs straight through — expect to loop back as you learn.
The Iterative Loop
1
Define the problemState the need, constraints and success criteria. Who is it for?
2
Research & gather requirementsPrior art, standards, user needs, materials, budget.
3
Brainstorm & concept designGenerate many options before judging any.
4
Select & developScore concepts against criteria; detail the chosen one.
5
PrototypeBuild the cheapest model that can answer the open question.
6
Test & evaluateMeasure against criteria. Did it work? Why / why not?
7
Iterate or deliverLoop back with what you learned, or release & document.
Guiding Principles
- Fail cheap, fail early — find flaws when they cost least.
- One variable at a time — so a test tells you something.
- Constraints breed creativity — define them up front.
- Requirements are testable — “fast” is not; “< 2 s” is.
- Trade-offs are explicit — cost vs weight vs time vs risk.
- Document as you go — the design is only as good as its record.
Review Checklist
- My problem statement names the user & constraints.
- Every requirement is measurable.
- I generated >1 concept before choosing.
- My prototype targets the riskiest unknown.
- Test results trace back to the criteria.
Executive Summary
Good engineering is structured iteration: define the real problem precisely, explore broadly, then converge through prototypes and tests that each retire a specific risk. Treating design as a loop — not a line — is what turns requirements into reliable, manufacturable solutions on time and on budget.