How do you prove whether your finished product actually solved the problem you set out to solve?
Test a finished product against each point of the specification and record clear pass or fail results
A focused answer to the N(A)-Level D&T outcome on testing a product. How to turn each specification point into a fair test, record clear pass or fail results, and use them to judge whether the product solved the problem.
Reviewed by: AI editorial process; not yet individually human-reviewed
Have a quick question? Jump to the Q&A page
Jump to a section
What this dot point is asking
SEAB wants you to test a finished product against each point of its specification and record clear pass or fail results. This is the heart of evaluation: the specification said what success looked like, and testing proves whether you reached it. The skill is designing a fair test for each point and recording the results clearly.
The answer
The specification is the test list
Back at the start you wrote a specification of measurable points. Now those points become your test list. For each point you ask: did the product meet it, yes or no? Because the points were measurable, you can give a clear answer rather than an opinion.
Designing a fair test
Each point needs a matching test:
- A function point ("holds 10 books") is tested by doing it: put 10 books in and see if they fit.
- A size point ("no taller than 400 mm") is tested by measuring with a rule.
- A safety point ("no sharp edges") is tested by checking every edge and corner.
- A strength point ("supports 5 kg without bending") is tested by loading it.
A fair test checks the real thing in realistic conditions, not a guess.
Recording the results
Record results in a simple table: the specification point, the test you did, the result (pass or fail), and a note on anything to improve. A table makes your evaluation clear and lets the marker see exactly which points were met.
Using the results
Testing is not just a tick-box. Each fail points to an improvement, and each pass confirms a good decision. The overall pattern tells you whether the product solved the original problem, which is the real question. Honest results, including the fails, earn more than pretending everything passed.
Examples in context
Example 1. A lunch bag. The specification said it must keep food cool for two hours and hold a drink bottle. The student fills it, waits two hours and checks the temperature, then tests the bottle fits, recording each as a clear pass or fail rather than guessing.
Example 2. A fail drives improvement. A desk tidy passes every point except "stays put on the desk", which fails because it slides. The honest fail leads the student to add a non-slip base, a stronger evaluation than claiming it all worked.
Try this
Q1. State what you use as your test list when evaluating a product. [1 mark]
- Cue. The specification, point by point.
Q2. Describe a fair test for the point "the stool supports a 60 kg person without bending". [2 marks]
- Cue. Have a person of about 60 kg sit on it (or load an equivalent weight) and check it does not bend or break; pass if it holds, fail if it bends.
Q3. Explain why honest pass and fail results make a better evaluation. [3 marks]
- Cue. Because fails point to clear improvements and passes confirm good decisions, giving real evidence of how well the product solved the problem, which earns more than pretending everything passed.
Exam-style practice questions
Practice questions written in the style of SEAB exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.
Original6 marksA student made a storage box with this specification: (1) holds at least 10 books, (2) no taller than 400 mm, (3) no sharp edges. Describe how the student would test each point, and how the results would be recorded.Show worked answer →
Point 1: place 10 average books in the box and check they all fit. Pass if they fit, fail if not.
Point 2: measure the height with a rule and check it is 400 mm or less. Pass if 400 mm or under, fail if over.
Point 3: run a hand carefully over the edges and corners (or check by eye) for sharp parts. Pass if all edges are smooth and rounded, fail if any are sharp.
Recording: put the results in a simple table with the specification point, the test, and a clear pass or fail, plus a note on anything to improve.
What markers reward: a sensible, fair test for each point matched to how it is measured (count, measure, check), and recording as a clear pass or fail, ideally in a table.
Original4 marksExplain why a product should be tested against the original specification rather than just asking 'does it look good?'Show worked answer →
The specification lists the exact requirements the product was meant to meet, so testing against it shows whether the product actually solves the problem. Asking only whether it looks good is an opinion and ignores function, size and safety. Testing each point gives clear evidence of success or failure and points to what needs improving.
What markers reward: the idea that the specification defines success, that testing against it gives objective evidence across function, size and safety, and that "looks good" alone is a vague opinion.
Related dot points
- Write a design specification as a list of clear, measurable requirements drawn from research, and use it to guide and later test the design
A focused answer to the N(A)-Level D&T outcome on writing a specification. How to turn research into measurable requirements covering function, size, materials, safety, cost and appearance, and how the specification is used to test the product.
- Gather feedback from users on a finished product and use it to suggest realistic improvements
A focused answer to the N(A)-Level D&T outcome on user feedback. How to gather honest feedback through trials and questions, separate opinion from useful data, and turn feedback into realistic suggested improvements.
- Evaluate a product for its impact on the environment and society, using ideas such as the 6 Rs and material life cycle
A clear answer to the N(A)-Level D&T outcome on sustainability. Judging a product against the 6 Rs, thinking about a material's life cycle from source to disposal, and balancing environmental and social impact with cost.
- Make models and prototypes from quick materials to test ideas in three dimensions and inform the final design
A practical answer to the N(A)-Level D&T outcome on modelling and prototyping. Why models are made, suitable quick materials such as card and foam, what tests a model can run, and how results feed back into the design.
- Describe the stages of the design process from a design situation to a finished product, and explain why the process is a loop rather than a straight line
A clear, step-by-step answer to the N(A)-Level D&T outcome on the design process. The ordered stages from situation to evaluation, what each stage produces, and why designers loop back to improve their work.