Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
Notes on this paper
Basic Studies / 04-BS-15 — Engineering Graphics & Design Process, undated. Closed-book, no calculator, 3 hours, 100 marks; five questions constitute a complete exam paper (answer ALL five). All sketches are freehand technical drawings following third-angle projection (CSA B78.1 / ASME Y14.5) unless the question calls for isometric pictorial or sectioning conventions.
The engineering design process is an iterative sequence of stages that carries a project from a recognized need through to a working, producible solution. While textbooks vary in how finely they subdivide it, the same nine functional stages recur:
Fig. Q5 — the engineering design process as a sequence of nine stages; testing failures feed back to concept evaluation or requirements rather than proceeding straight to production.
1. Identify the need. A problem, market gap, or client requirement is recognized. Purpose: without a real, validated need, the rest of the process has no target — this stage answers "why build anything at all?"
2. Define the problem and requirements. The vague need is translated into explicit, measurable engineering requirements (performance targets, constraints, codes/standards to satisfy, budget, schedule). Purpose: converts a fuzzy want into criteria the team can actually design and test against.
3. Research and gather information. Existing solutions, patents, applicable codes, material properties, and failure histories of similar products are studied. Purpose: avoids re-inventing a solved problem and surfaces constraints the team would otherwise discover the hard (expensive) way later.
4. Concept generation. Multiple candidate solutions are brainstormed and sketched, deliberately kept broad at this stage. Purpose: the first idea is rarely the best one; generating several concepts avoids anchoring on a mediocre solution.
5. Concept evaluation and selection. Concepts are scored against the requirements (a weighted decision/Pugh matrix is a common tool) and the strongest one (or a hybrid) is selected. Purpose: makes the down-selection traceable and defensible rather than a gut call.
6. Preliminary design and analysis. The chosen concept is developed enough to run first-pass engineering analysis (stress, thermal, cost estimates) and confirm feasibility. Purpose: catches fundamental flaws (undersized, over budget, code-non-compliant) before committing to full detailed design effort.
7. Detailed design. Every part is fully dimensioned and toleranced, materials and finishes are specified, and a complete drawing/model package (and bill of materials) is produced. Purpose: this package is what a shop or vendor actually builds from — it must be complete and unambiguous.
8. Prototype and test. A physical (or, increasingly, a high-fidelity virtual) prototype is built and tested against the original requirements. Purpose: validates that the real object behaves as the analysis predicted; this is where design assumptions get checked against reality.
9. Production / implementation. Once testing confirms the design meets requirements, the design is released to manufacturing (or construction, or deployment) at full scale. Purpose: delivers the validated solution to the end user.
The process is drawn with a feedback loop rather than a straight line because it is genuinely iterative: if prototype testing (stage 8) reveals a shortfall, the team returns to concept evaluation (stage 5) — or, for a more fundamental problem, all the way back to the requirements (stage 2) — rather than pressing on to production with a design known to be deficient. This willingness to iterate, rather than treating each stage as a one-way gate, is what separates a genuine engineering design process from a simple linear checklist.
