Welcome to Testing and Evaluation (CCEA A2 Unit 2)
Hello and welcome! In this chapter, we explore the final, vital phase of your A2 2 Coursework: Product–System Design and Manufacture portfolio. Unit A2 2 makes up 30% of your total A Level (and 50% of your A2 award), and your written/graphical design portfolio (usually presented in an A3 folio) must conclude with a rigorous, honest, and evidence-based appraisal of what you have designed and made.
Many students make the mistake of thinking evaluation is just writing a quick paragraph saying "My project went well and I liked making it." In A Level Technology and Design, testing and evaluation is an engineering investigation! You are acting as a real-world designer who collects measurable data, gathers authentic client feedback, checks performance against technical requirements, and plans future commercial improvements.
Don't worry if this seems a bit daunting at first. We will break the entire process down into simple, manageable steps so you can gain top marks in your portfolio.
1. The Core Technological Requirement: Testing the Whole System
For your CCEA A2 2 project, your product cannot just be a static model or a simple wooden box. It must be a fully functioning technological product or system that incorporates an energy source and an integrated control system based on the classic systems model:
Input \(\rightarrow\) Process \(\rightarrow\) Output
Depending on your chosen project area, this control system might be:
• Electronic / Microelectronic: Sensors (inputs) feeding into microcontrollers or timing circuits (process) driving motors, solenoids, or LEDs (outputs).
• Mechanical: Linkages, cams, gears, or pulleys transferring motion and mechanical advantage.
• Pneumatic: Cylinders, valves, and air lines regulating fluid power to do physical work.
Key Rule for Testing: You must evaluate both the mechanical enclosure/casing and the underlying technological control system. Testing only how nice the acrylic looks while ignoring whether the circuit handles the current draw correctly is a major pitfall!
2. Two Types of Testing: Formative vs. Summative
To secure high marks, your portfolio must demonstrate testing at every stage of the build, not just at the very end.
A. Formative (In-Process) Testing
Formative testing happens during manufacture. It is the testing of individual sub-systems, components, and code routines before you put everything together.
Analogy: Think of baking a cake. Formative testing is tasting the batter before it goes into the oven to make sure you didn't forget the sugar!
Examples of formative testing in your A3 portfolio:
• Prototyping a circuit on a breadboard to verify resistor and capacitor values before soldering onto stripboard or a PCB.
• Running modular subroutines in your microcontroller code to ensure sensor triggers are read accurately.
• Testing a 3D-printed mechanical linkage or gear train by hand to check for friction, backlash, or alignment issues before final assembly.
B. Summative (Final) Testing
Summative testing takes place once your entire prototype is fully assembled. This is rigorous, functional testing conducted under real-life or simulated operating conditions.
Analogy: Summative testing is serving the finished, decorated cake to the guests and measuring how well it holds its shape and tastes.
In summative testing, you must record objective, measurable data rather than vague descriptions. Examples include:
• Timing: "The automatic clamping mechanism engaged in \(1.2\text{ s}\), which meets the target time of under \(2.0\text{ s}\)."
• Load & Weight Tolerance: "The mechanical arm safely supported a load of \(500\text{ g}\) without deflection."
• Sensor Response: "The light sensor triggered the output circuit reliably at an ambient light level of \(150\text{ lux}\)."
• Energy Draw & Battery Life: "Under full load, the circuit draws \(220\text{ mA}\) from the \(9\text{ V}\) supply."
Section Takeaway: Formative testing proves your sub-circuits and parts work during the build; summative testing proves your complete, assembled product works in real operating conditions with measurable numbers.
3. Evaluating Against the Product Design Specification (PDS)
At the start of your project, you created a detailed Product Design Specification (PDS). In your evaluation, you must return to this document and systematically assess your final outcome against every single specification point.
The Three-Tier Rating System
For every single criterion in your original PDS, clearly state whether it has been:
1. Fully Met: The product completely satisfies the measurable target.
2. Partially Met: The product works or fits to some extent, but fell short of the full technical benchmark.
3. Not Met: The product failed to achieve this specific requirement.
Qualitative vs. Quantitative Verification
To provide high-level evaluation, balance both types of verification:
• Quantitative Verification: Uses numerical measurements, physical tests, and performance data (e.g., dimensions, weight, operating voltage, response speed, load capacity).
• Qualitative Verification: Uses descriptive assessments backed by visual and ergonomic criteria (e.g., ease of grip, aesthetic appearance, surface finish, clarity of user indicators).
The Evidence Rule: Photos and Data
Never just tick a box and claim a criterion is met. You must provide photographic evidence and recorded test data. For instance, if your specification states: "The device must weigh less than \(1.5\text{ kg}\) and fit within a \(200\text{ mm} \times 150\text{ mm} \times 100\text{ mm}\) footprint," your portfolio should include:
• A photograph of the product sitting on digital scales showing the readout (e.g., \(1.18\text{ kg}\)).
• A photograph of digital callipers or a rule measuring the physical enclosure dimensions alongside the recorded numbers.
Section Takeaway: Treat your PDS as a legal checklist. Go point-by-point, grade each criterion as fully, partially, or not met, and justify every claim with photographic or numerical proof.
4. Third-Party and Client Feedback
As a designer, you are naturally biased because you built the product yourself! That is why CCEA requires direct testing and feedback from your intended client or target user group.
What Should the Client Test?
Have your client or representative users interact with the real product in its intended environment while evaluating:
• Usability & Human Factors: Is the product intuitive to operate? Are switches, buttons, and handles placed in comfortable, logical positions?
• Ergonomics: Does the product feel comfortable during extended use? Is the weight balanced?
• Aesthetics: Does the styling, colour palette, and material finish suit the target environment?
• Fitness for Purpose: Does the product actually solve the original problem identified in your design brief?
How to Present Client Feedback in Your Portfolio
• Questionnaires & Rating Scales: Use clear rating tables (e.g., 1 to 5 scale) accompanied by open-ended written comments from the user.
• Photographic Proof: Include high-quality photographs showing the actual client or user testing the product in real time.
• Critical Analysis: Summarise what the client loved and, crucially, what they found difficult or suggested changing.
Section Takeaway: Authentic client feedback gives your evaluation real credibility. Show real users operating your product and document their honest reactions.
5. Modifications and Future Commercial Development
An incomplete or imperfect prototype is not a disaster in A Level Technology and Design—as long as you can critically identify the flaws and engineer realistic solutions!
Examiners award high marks when candidates show mature self-reflection by detailing design weaknesses, manufacturing inaccuracies, and proposals for commercial or batch production.
How to Propose Modifications (The Right Way)
A major error is writing: "If I had more time, I would make it out of lighter plastic and make it smaller." This is too vague for A Level standard.
Instead, your proposals for future development must be technical and graphical:
• Annotated 2D and 3D Sketches: Draw clear conceptual sketches illustrating revised mechanical joints, snap-fit casings, or repositioned user controls.
• CAD Models: Present 3D CAD renders showing how the casing could be re-engineered for injection moulding (including draft angles, ribs, or screw bosses).
• Circuit & System Diagrams: Provide updated circuit schematics showing upgraded components, PCB layouts, surface-mount components, or improved sensor filtering.
• Design for Manufacture (DFM): Explain how moving from bespoke workshop tools to industrial batch techniques (such as CNC machining, automated SMD assembly, or vacuum forming) would reduce unit cost and improve build consistency.
Section Takeaway: Don't just talk about improvements—draw them! Use annotated sketches, circuit diagrams, and CAD models to demonstrate how your prototype could transition to commercial manufacture.
6. Summary: Key Pitfalls to Avoid
Review this quick checklist before submitting your A2 2 Testing and Evaluation folio pages:
1. Avoid Superficial / Narrative Testing
Wrong: Writing a story about how the project was built.
Right: Presenting tables of recorded quantitative data (timing, voltages, loads) collected during live testing.
2. Avoid Disconnected Evaluations
Wrong: Making broad, general remarks about how good the project looks.
Right: Appraising every individual criterion of your original PDS using "Fully Met", "Partially Met", or "Not Met".
3. Do Not Forget Photographic Evidence
Wrong: Submitting text-only evaluation tables.
Right: Backing up every test with clear photographs of the complete prototype working in real conditions with the client.
4. Avoid Text-Only Future Modifications
Wrong: Short, speculative paragraphs with no engineering detail.
Right: Richly annotated 2D/3D sketches and CAD models showing specific technical and commercial improvements.
5. Test the Whole Integrated System
Wrong: Only evaluating the aesthetic casing and ignoring the electronics or mechanics.
Right: Thoroughly testing the full Input \(\rightarrow\) Process \(\rightarrow\) Output energy and control system alongside the housing.