Testing and evaluation

The most-cited AC7 weakness: candidates do test against the specification but then stop, giving no proposals for further development. Testing tells you how well the product did; the evaluation is complete only when it turns those findings into specific improvements. End with concrete, justified proposals as annotated sketches: name a weakness, then draw the change that fixes it.

To describe is to say what the product is or does ('four legs and a shelf'); to evaluate is to judge how well it meets its purpose, weighing positive AND negative features and justifying it. Candidates repeatedly describe — restating features — when the task wants evaluation. This recurs on Paper 1 part (d). Give judgement, reason and evidence, not a feature list.

A test proves little if it is not realistic. Candidates try the product briefly on the bench and record their own impression, rather than testing it in its intended environment with real user feedback. Carry the tests out where the product will really be used — a chopping board in a kitchen, a display stand with items on it, a toy with a target-age child.

An unjustified assertion scores nothing. 'It works well', 'the user liked it' — stated flat, with no reason and no evidence — is not evaluation, even though it sounds like a verdict. Every judgement needs a reason and the test result or feedback behind it: it meets the stability point because it did not tip when knocked. The evidence is where the mark sits, not the verdict.

'It could be improved' is not a proposal for further development. A proposal must name the change and justify it: widen the base by 20 mm so the stand does not tip, round the top edge so it is safe at hand height, swap to a cheaper material to cut cost. The best proposals are drawn as annotated sketches. Vague, unjustified improvement ideas leave the top-band marks unclaimed.

Comments must be anchored to specification points. Candidates judge the product in general — 'it looks nice', 'I like it' — instead of checking each requirement in turn. Take the specification point by point: state whether the product meets each, and cite the test result that shows it. General impressions are not a check against the criteria.

A specific wrong belief: that an evaluation is where you say what is good, so a confident positive conclusion completes the task. It does not. Evaluating means weighing strengths AND weaknesses against the specification, then proposing development. Reporting only positives, or assertions with no evidence, misses the balance and the proposals the top band needs.