The Engineering Design Process
A Structured Approach to Solving Engineering Problems
Contents
1. Introduction
2. 1. Problem Definition
3. 2. Requirements Gathering
4. 3. Research and Concept Generation
5. 4. Analysis and Modeling
6. 5. Prototyping
7. 6. Testing and Validation
8. 7. Iteration and Refinement
9. 8. Documentation and Handoff
10. Key Terms
11. Summary
The Engineering Design Process Page 1
Introduction
The engineering design process is a systematic, iterative approach used to develop solutions to
technical problems. Unlike a purely linear recipe, real design work loops back on itself as new
information emerges from testing, prototyping, and stakeholder feedback.
This document walks through the commonly recognized stages of the design process and highlights
practical considerations at each stage.
1. Problem Definition
Every design project begins with a clear statement of the problem to be solved. This includes
identifying the end users, the operating environment, and any constraints such as budget, available
materials, timeline, and regulatory requirements.
A well-defined problem statement typically answers: what is the need, who is affected, why does the
current situation fall short, and what does success look like.
2. Requirements Gathering
Requirements translate the problem statement into specific, measurable criteria the final design must
satisfy. These are often split into functional requirements (what the system must do), performance
requirements (how well it must do it), and constraints (limits on cost, size, weight, safety, and
compliance).
For electrical or electronic projects, requirements might include voltage ratings, current limits,
isolation requirements, and applicable safety standards such as those governing residual current
devices.
3. Research and Concept Generation
Engineers research existing solutions, relevant physics or chemistry, applicable standards, and
available components before generating multiple candidate concepts. Brainstorming and sketching a
wide range of ideas, even unconventional ones, increases the odds of finding an efficient solution.
Concepts are typically evaluated against the requirements using a decision matrix that scores each
option on criteria like cost, feasibility, safety, and performance.
4. Analysis and Modeling
Before committing resources to a physical build, engineers analyze candidate designs mathematically
or through simulation. This might include structural load calculations, circuit simulation, thermal
analysis, or control system modeling.
The Engineering Design Process Page 2
Analysis at this stage catches many problems early and cheaply, such as identifying that a
dimmer-based control circuit would produce fault currents unsuitable for a standard Type AC residual
current device, prompting a design change before hardware is purchased.
5. Prototyping
A prototype is a preliminary version of the design used to test key assumptions. Prototypes range
from simple breadboard circuits and 3D-printed mockups to full-scale functional units, depending on
the risk and cost of the final system.
Rapid, low-cost prototyping allows engineers to fail safely and cheaply, refining the design before
committing to final production.
6. Testing and Validation
Testing verifies that the prototype meets the requirements defined earlier. This includes functional
testing (does it work as intended), stress testing (does it survive expected extremes), and safety
testing (does it fail safely under fault conditions).
For projects involving mains-level electrical hardware, testing should include verification of galvanic
isolation, correct operation of protective devices, and confirmation that fault currents are within the
detection capability of installed protection.
7. Iteration and Refinement
Test results almost always reveal issues or opportunities for improvement. Engineers cycle back to
earlier stages, refining requirements, generating new concepts, or adjusting the design, and re-testing
until the solution reliably meets its requirements.
This iterative loop is the defining feature of real engineering work, distinguishing it from a simple linear
checklist.
8. Documentation and Handoff
Once a design is finalized, thorough documentation ensures it can be manufactured, maintained, and
safely operated by others. This includes technical drawings, wiring diagrams, bills of materials, and
operating instructions.
Good documentation is especially important for DIY and hobbyist projects that mix mains-level
electrical work with low-voltage electronics, since future maintainers need to understand both
domains to work safely.
The Engineering Design Process Page 3
Key Terms
The following terms are commonly encountered when working in this area:
Requirement A specific, measurable criterion a design must satisfy.
Prototype A preliminary version of a design used to test key
assumptions.
Iteration Repeating a design step with refinements based on new
information.
Validation Confirming a design meets the intended user need.
Verification Confirming a design meets its stated technical
requirements.
Decision matrix A scoring table used to compare design concepts
against criteria.
Summary
A disciplined, iterative design process consistently produces more reliable and cost-effective
outcomes than an ad hoc approach, whether the project is a large infrastructure system or a small
personal electronics build. Revisiting earlier steps as new information emerges is a sign of good
practice, not failure.
The Engineering Design Process Page 4