Question 5 of 5: The engineering design process

Question 5: The engineering design process (20 marks)

Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.

The engineering design process is an iterative sequence that turns an identified need into a validated, manufacturable solution. While practitioners describe it with varying numbers of stages, the core skeleton is consistent: define the problem, generate and select concepts, develop and analyze the chosen concept in detail, then build, test, and refine it — looping back to earlier stages whenever a later stage exposes a flaw.

Problem definition and requirements. The process begins by clarifying the actual need (often starting from a vague customer complaint or opportunity) into a written problem statement, then translating that statement into measurable engineering requirements and constraints (performance, cost, safety, regulatory, schedule). Tools commonly used here include stakeholder interviews, benchmarking against competitor or precedent products, and Quality Function Deployment (QFD) / the “house of quality” to map customer wants onto quantifiable engineering targets.

Concept generation and selection. With requirements fixed, the team generates a broad set of candidate solutions before narrowing — deliberately deferring judgement to avoid anchoring on the first idea. Brainstorming, morphological charts (which decompose the design into sub-functions and combine independent solution options for each), and functional decomposition are typical generation tools. Selection then uses structured comparison methods such as a Pugh (datum) matrix or a weighted decision matrix, scoring each concept against the requirements relative to a baseline, so the choice is traceable rather than a matter of opinion.

Embodiment and detail design. The selected concept is developed into a full geometric definition using CAD, with dimensions, tolerances, and materials assigned. Engineering analysis is applied at this stage — hand calculations, finite element analysis (FEA) for stress/deflection, tolerance-stack analysis to confirm parts will assemble, and a Design Failure Mode and Effects Analysis (DFMEA) to systematically anticipate how each component could fail and rank the risk by severity, occurrence, and detectability. Design-for-manufacture and design-for-assembly (DFM/DFA) reviews are folded in here, checking that the part can actually be made economically (draft angles, standard tooling, minimizing unique fasteners) rather than only that it works on paper.

Prototyping, testing, and validation. Physical or virtual prototypes (3D-printed models, bench mock-ups, or simulation) are built to validate assumptions made during detail design before committing to production tooling. Testing verifies the design against the original requirements — and any gap discovered here (a failed load test, a poor ergonomic fit) sends the process back to an earlier stage, which is why the process is drawn as a loop, not a straight line, in most textbook diagrams.

Documentation, review, and iteration. Throughout, formal engineering drawings, a bill of materials (BOM), and change-control records are maintained so the design intent is communicated unambiguously to manufacturing and can be revised traceably. Staged design reviews (concept review, preliminary design review, critical design review) act as gates where the team and stakeholders formally agree the design is ready to proceed, preventing an unvalidated concept from reaching production. Plan-Do-Check-Act (PDCA) framing captures the overall iterative character: every stage’s output is checked against requirements, and shortfalls trigger a deliberate return to an earlier stage rather than an ad-hoc patch.