Design Process and Problem Solving
The iterative cycle
The design process is rarely a straight line. A candidate must know the stages: identifying a need or problem, writing a design brief, producing a specification, generating and evaluating ideas, developing a chosen solution, planning manufacture, making, testing and evaluating. Understand that evaluation feeds back into earlier stages, so the cycle repeats.
Brief versus specification
A design brief is a short statement of intent: what is to be made and for whom. A specification is a detailed list of measurable requirements: dimensions, materials, cost, safety, ergonomics, environmental impact and finish. The most common trap is confusing the two, or writing a specification full of vague words such as 'strong' or 'nice' that cannot be tested. Every specification point should be measurable, for example 'must support a 5 kg load without permanent deformation'.
Analysis and evaluation
Questions often ask you to analyse an existing product or to evaluate a proposed solution. Use structured criteria rather than personal opinion: function, safety, cost, aesthetics, ergonomics, sustainability and manufacture. AccessFM (aesthetics, cost, customer, environment, size, safety, function, material, manufacture) is a useful checklist, but name the criteria you actually apply.
Worked example: writing a testable specification
Problem: a school needs a storage rack for 20 art portfolios. Weak point: 'must be strong'. Improved point: 'must hold 20 portfolios each up to 2 kg (40 kg total) with no visible deflection; must fit a 900 mm wide alcove; must cost under the given budget using workshop stock; edges must be rounded to a 3 mm radius for safety'. Each clause can be checked by measurement or inspection.
Rule of thumb
If you cannot describe how you would test a specification point, rewrite it until you can.