Skip to main content
EnglandEngineeringSyllabus dot point

How does an engineering design move from a problem to a working solution?

The stages of the design process, the role of the design brief and specification, and how designs are evaluated and improved iteratively.

A focused answer to AQA GCSE Engineering on the design process, from brief and specification through research, ideas, development, modelling and testing, and the role of iterative evaluation.

Generated by Claude Opus 4.89 min answer

Reviewed by: AI editorial process; not yet individually human-reviewed

Have a quick question? Jump to the Q&A page

Jump to a section
  1. What this dot point is asking
  2. Stages of the design process
  3. Brief versus specification
  4. Why design is iterative
  5. Try this

What this dot point is asking

AQA wants you to describe the stages of the design process, explain the difference between the brief and the specification, and explain why design is iterative, with evaluation feeding back into improvement. Expect questions that ask you to order the stages, write a specification point that is measurable, or justify why an engineer loops back rather than working straight through.

Stages of the design process

Each stage has a job. Research gathers facts about users, existing products, materials and standards so the design is informed. Generating ideas produces several different concepts, not one, so the best can be chosen rather than the first. Developing and modelling turns the chosen idea into something concrete, on paper, in CAD or as a physical model. Testing and evaluating measures that model against the specification to decide what works and what must change.

Brief versus specification

The key difference is that a brief is general and a specification is specific and testable. "Design a portable lamp" is a brief; "must run for at least 4 hours on one charge, weigh under 300 g300 \text{ g} and cost under five pounds to make" are specification points. A measurable specification point can be checked with a clear yes or no, which is exactly what makes evaluation possible.

Why design is iterative

Try this

Q1. Name three stages of the design process. [3 marks]

  • Cue. Any three of: brief, research, specification, ideas, development, modelling, testing, evaluation.

Q2. State what "iterative" means in design. [1 mark]

  • Cue. Repeatedly making, testing and improving the solution rather than finishing in one pass.

Exam-style practice questions

Practice questions written in the style of AQA exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.

AQA 20194 marksExplain the difference between a design brief and a design specification, and why both are needed.
Show worked answer →

A good answer defines each clearly and links them.

A design brief is a short statement of the problem to be solved and who it is for; it sets the direction but stays general (for example "design a bottle opener for people with weak grip").

A design specification is a detailed, measurable list of requirements the solution must meet (size, mass, cost, materials, safety, performance), written so that each point can later be tested.

Both are needed because the brief gives the purpose and scope while the specification turns that purpose into measurable targets used to judge ideas and the finished product. Markers reward a clear definition of each and the point that the specification makes the brief testable.

AQA 20236 marksDiscuss how using an iterative design process helps an engineer develop a better product than working through the stages only once.
Show worked answer →

A 6 mark Discuss question rewards reasoning with examples, not a list of stages.

Iterative design means looping back to test and improve rather than finishing in one pass. After modelling and testing a prototype against the specification, the engineer finds weaknesses (for example a handle that is too small to grip) and feeds them back into new ideas and prototypes.

This produces a better product because faults are found and fixed early, while changes are cheap, rather than after tooling is committed; user feedback shapes later versions; and each cycle measures the product against the specification so progress is evidenced, not assumed.

A balanced answer notes the cost: iteration takes time and money, so the number of cycles is limited by the budget and deadline. Markers reward the loop-and-improve idea, a concrete example and a sense of the trade-off.

Related dot points

Sources & how we know this