The Design Process: how Singapore O-Level Design and Technology designers move from a situation and need to a tested, evaluated solution through an iterative cycle

What this module covers

The Design Process module is the backbone of O-Level Design and Technology (SEAB 7059). Everything else, from research to materials to fabrication, hangs off the structured method a designer uses to turn a real problem into a tested solution. SEAB assesses this through the written paper, which asks you to explain and apply the stages, and through the Design Project coursework, where you actually work the process from a given situation to a finished artefact and evaluation. This overview ties the four dot points together and links to each in full.

See the full set of dot points for this module under /sg-o-level/design-and-technology/syllabus/the-design-process.

The stages in order

Designing is not guessing. The stages of the design process run from identifying a situation and need, through a brief, research, specification, idea generation, development, realisation and finally evaluation. Each stage feeds the next: without a clear need the brief is vague, without research the specification is guesswork, and without a specification you cannot judge whether an idea is any good. O-Level answers must treat research, specification, development and evaluation as distinct stages rather than collapsing the whole thing into "design and make".

Starting from the situation and the need

The process begins by analysing the design situation and needs. You identify who the user is, what the problem is, and what the user actually needs, carefully separating a need (a user requirement) from a proposed solution. Distinguishing needs from wants and from solutions is the single most rewarded skill at this stage, because it keeps the design open to a range of answers rather than locking in the first product that comes to mind.

Brief and specification

Once the situation is understood, the designer writes a direction-setting statement and then a testable yardstick. The design brief and specification dot point draws the line between the two: the brief is a short, general statement of what is to be designed and for whom, while the specification is a list of measurable requirements built from research. The specification is what every later idea and the finished product are judged against, so vague aims like "must be safe and easy to use" lose marks where measurable points like "must support a 5 kg load" earn them.

Why the process loops

The arrows do not only point forward. The iterative nature of design is that testing and evaluation feed back into earlier stages, usually development, so the design is refined over several cycles. Each loop improves the solution, and problems caught early, on paper or in a model, are far cheaper to fix than problems found in a finished product. SEAB specifically rewards the word "iterative" used correctly: looping back to improve, not a one-way line.

How this module is examined

• Explain the stages in order. Name each stage and say what happens in it, keeping research, specification, development and evaluation as distinct steps.
• Separate need from solution and brief from specification. State the need as a user requirement, and write specification points as measurable, testable statements.
• Use "iterative" correctly. Show that testing feeds back into development and that the design improves over several cycles, not in a single pass.
• Apply it in the Design Project. Make your Design Journal follow the process visibly, with at least one documented loop where testing changed the design.

Check your knowledge

Short questions across the module. Attempt them, then check the worked solutions.

1. List, in order, the main stages of the design process from situation to evaluation. (3 marks)
2. State the difference between a design brief and a design specification. (2 marks)
3. Explain why the design process is described as iterative rather than linear. (2 marks)
4. Rewrite this need so it does not name a solution: "the user needs a shelf reacher". (1 mark)
5. Give one reason a fault found in a finished product is more costly than one found in a model. (1 mark)