Design processes The use of a design process - Prototype development — AQA A-Level Design and Technology: Product Design
Verified courseTeaching note checked against the official specification.
Design processes The use of a design process - Prototype development explained
Prototype development turns a design proposal into a physical or digital model that can be tested and refined.
Read the full explanation
Students should know the purpose of prototypes: to check function, ergonomics, aesthetics, materials and manufacture before committing to production. They should be able to discuss how a proposal becomes a prototype, for example by selecting materials, choosing a making method such as 3D printing or card modelling, and building a version that answers a specific question. They should also demonstrate the skill by actually making and iterating a prototype. This knowledge should shape NEA design ideas so that final products are high quality and meet the needs of identified users. Each prototype cycle should record what was tested, what was learned and what changed.
Your focus
- Explain the purpose of prototyping in product development.
- Describe and carry out the development of a prototype from a design proposal.
- Use prototype findings to refine design ideas so the final product meets identified user needs.
Design processes The use of a design process - Prototype development exam tips
Marking Points
- Explains the purpose of a prototype, such as testing function, ergonomics, aesthetics, materials or manufacture before production.
- Describes how a design proposal is developed into a prototype, including material selection and an appropriate making method.
- Demonstrates the iterative cycle: build, test, evaluate, refine, and records what was learned and changed.
- Links prototype decisions to the needs of identified users and to the quality of the final NEA product.
- Uses a concrete example, such as a card model to check ergonomics before a 3D-printed version.
- Distinguishes low-fidelity prototypes for quick concept checks from higher-fidelity prototypes for detailed testing.
Examiner Tips
- 💡Use a specific product example and name the question each prototype version was built to answer.
- 💡Show the iteration explicitly: state what was tested, what the result was and what changed as a result.
- 💡Connect prototype findings to the final NEA outcome and to identified user needs to show purpose.
Common Mistakes
- Treating a prototype as a finished product: correct this by explaining that a prototype is a testable model built to answer specific questions.
- Describing prototyping as a single step: explain the iterative cycle of build, test, evaluate and refine.
- Ignoring the user: link every prototype decision to the needs of identified users and the design specification.