The Design Process module quiz: Singapore O-Level Design and Technology (SEAB 7059) quiz

Situation and need, brief, research, specification, ideas, development, realisation, evaluation

Design, make, sell, repair

Sketch, paint, build, present

Buy materials, cut, glue, finish

A shelf reacher is too expensive to be a need

It states a solution rather than the user requirement

Needs must always be written as measurements

Needs cannot involve elderly users

The brief is measurable; the specification is general

They are the same document with different names

The brief is a general direction-setting statement; the specification is a list of measurable requirements

The specification is written before any research

It is completed in one straight pass from start to finish

Ideas are generated only once at the start

Each stage is done by a different person

The designer loops back through earlier stages to refine the design over several cycles

Faults caught on paper or in a model cost far less to change than faults in a finished product

Early prototypes are made from gold

Materials are free at the start of a project

Customers pay for early changes

To make the project take longer

So ideas can be judged against clear, measurable targets rather than personal preference

Because ideas are not allowed before a specification by law

To avoid having to do any research

Must be nice and easy to use

Must support a load of at least 5 kg without bending

Should look good

Must be the best product ever

Only at the very end as a summary

Hidden so the marker cannot follow it

Visibly structuring the Design Journal, with at least one documented loop where testing changed the design

Replaced entirely by a single final drawing

To decorate the Design Journal

To copy a finished product exactly

To delay starting the real work

To gather evidence about users, existing products and materials that informs the specification

Developing and refining the chosen idea

Writing the design brief

Identifying the situation

Selling the product

To fill more pages

Because each plays a different role and collapsing them into 'design and make' loses the structure O-Level rewards

Because SEAB bans short journals

So the project can be done without testing

The whole project is abandoned

The problem is ignored to save time

The designer loops back, usually to development, to modify and test again

The specification is deleted

It lists every measurable requirement in detail

It is the same as the evaluation

It is written only after the prototype is built

It is a short statement of what is to be designed and for whom, setting the direction

There is no iterative refinement, so faults that testing would reveal go uncorrected

The product is guaranteed to be perfect

The product will be too cheap

The brief becomes unnecessary