NSSCAS Design and Technology (8256) common mistakes
NSSCAS Design and Technology (8256) · Understand the traps and how to avoid them.
When writing a design specification, candidates list vague aspirations such as 'must be strong', 'must be attractive', or 'easy to use' without any measurable criterion or test method, so the specification cannot be used to evaluate the final outcome.
Candidates confuse a design brief (a general statement of intent) with a specification (a set of testable requirements). They have not been taught to convert each need into a parameter with a value, unit, and method of verification, and they rush to the making stage because they see specification writing as paperwork.
What to do instead
Use a specification table with columns: requirement, measurable criterion, test/verification method, and priority (must/should/could). Force every entry to contain a number, a named standard, or a binary pass/fail test. For example, replace 'must be strong' with 'must support a 15 kg static load for 60 s without permanent deflection greater than 2 mm, tested by...'. Before making, check each specification point against at least one concept and record the evidence.
Candidates describe a single idea as their 'design process' and omit divergence, evaluation of alternatives, and iteration; the folio shows one concept, one model, and one final product with no evidence of testing or modification.
The linear 'idea → make' model is easier and faster, and candidates believe a neat final product is what earns marks. They do not realise that the assessment rewards evidence of exploring, comparing, and improving, and they leave no time for iteration because making starts too late.
What to do instead
Structure the folio around explicit stages: problem clarification, research, specification, at least three distinct concepts, weighted decision matrix, development of the chosen concept through mock-ups or CAD, testing against specification, and a recorded modification with before/after evidence. Keep a dated design log so iteration is visible. Allocate roughly one third of project time to exploration and one third to development and testing before final manufacture.
In materials selection, candidates justify a choice only by saying a material is 'strong', 'cheap', or 'light' without naming the property, its value, and the service conditions; they also ignore the manufacturing process compatibility and the available stock forms.
Everyday adjectives are learned before technical properties, and candidates do not connect material data to the actual load case, environment, or process. They also select from a mental shortlist of familiar materials rather than from data.
What to do instead
For each candidate material, record density, tensile or flexural strength, modulus, hardness, thermal expansion, moisture resistance, cost per kilogram, and available stock forms (sheet, rod, tube, extruded section). Match the property to the dominant failure mode and environment of the product, then check process compatibility (for example, a thermoset cannot be reshaped after curing; some polymers are unsuitable for load-bearing threads). Justify the final choice against at least two rejected alternatives with data.
When describing manufacturing processes, candidates give a generic sequence such as 'cut, drill, sand, assemble' without specifying the tool, speed, feed, joint type, or quality check, and they do not distinguish between a one-off prototype method and a mass-production method.
Candidates memorise process names but not parameters, and they have limited workshop experience of the decisions that determine quality. They also treat all processes as interchangeable because the school workshop mostly uses hand tools.
What to do instead
For each process, write the operation sheet with material, machine or tool, tool size, speed/feed or temperature/pressure where relevant, setup, safety control, and inspection point. Compare at least one alternative process for the same feature (for example, injection moulding versus vacuum forming for a housing) in terms of tooling cost, cycle time, finish, and volume. State why the chosen process suits the batch size.
Candidates produce third-angle orthographic drawings with missing or wrongly placed hidden detail, inconsistent line types, no dimensioning convention, and views that do not align; they also submit pictorial sketches as if they were working drawings.
Drawing conventions are learned visually and are easily confused between first-angle and third-angle projection. Candidates often draw freehand without construction lines and do not check projection alignment, and they have not practised reading their own drawing to make the part.
What to do instead
Adopt a fixed checklist for every drawing: title block, projection symbol, scale, all three views aligned on construction lines, visible outlines thick, hidden detail dashed, centre lines chain-dotted, dimensions with arrowheads and units, no double dimensioning, and no dimension on a hidden line. Practise by making a part from your own drawing and noting where the drawing was ambiguous. Use CAD only after the convention is secure by hand.
In sustainability answers, candidates write that a product is 'eco-friendly' or 'recyclable' without naming the material, the end-of-life route, the energy or carbon implication, or the trade-off against function and cost; they ignore the full life cycle.
Sustainability is often reduced to a slogan, and candidates lack a structured framework for comparing options. They also assume a natural material is always better, ignoring processing energy, durability, and transport.
What to do instead
Use a life-cycle checklist: raw material extraction, processing energy, manufacture, distribution, use-phase energy and consumables, maintenance, and end-of-life (reuse, remanufacture, recycle, energy recovery, landfill). For each design decision, state the material or process, the environmental impact, the functional or cost penalty, and the net judgement. Quantify where possible, for example mass of material, recycled content percentage, or estimated lifetime. Compare two complete options rather than listing generic virtues.
In structures and mechanisms questions, candidates draw a free-body diagram with missing reactions or wrong force directions, and calculate a mechanism's output without checking the constraint, the direction of motion, or the effect of friction and toggle positions.
Candidates apply formulas by rote without drawing the system, and they confuse input and output members or forget that a four-bar linkage has two possible assemblies. They also ignore units and sign conventions.
What to do instead
Always draw the isolated body, mark every applied load and reaction with an assumed direction, and state the equilibrium equations before substituting numbers. For mechanisms, sketch the linkage at the input and output positions, mark the fixed pivots, check Grashof condition or the degrees of freedom, and trace the motion through a full cycle to identify dead-centre and toggle positions. Carry units through every step and sanity-check the magnitude of the answer.
In control-system questions, candidates describe a system as 'automatic' without identifying the sensor, the controller, the actuator, and the feedback path, and they cannot distinguish open-loop from closed-loop behaviour or explain what happens when a sensor fails.
Block diagrams are treated as decoration rather than as a model of signal flow, and candidates have not built or tested a simple control system, so the roles of comparator, set point, and error signal remain abstract.
What to do instead
For every system, draw the block diagram with set point, comparator, controller, actuator, process, sensor, and feedback line labelled with the signal type (analogue voltage, digital pulse, etc.). Then answer: what is measured, what is compared, what is adjusted, and what is the failure mode if the sensor reads high or low. Practise with a familiar example such as a thermostat or a line-following robot, and state whether the system is open-loop or closed-loop and why.
In the design-and-make coursework, candidates present a product that does not meet the specification and cannot explain the deviations; the evaluation lists what went well but gives no measured evidence, no client or user feedback, and no realistic proposal for the next iteration.
Evaluation is written at the end under time pressure, and candidates are reluctant to admit shortcomings. They also fail to collect test data during making, so there is nothing to evaluate against.
What to do instead
During making, record test results against each specification point in a table with the criterion, measured value, pass/fail, and evidence (photograph, measurement, user comment). In the evaluation, address every specification point, explain each deviation with its cause, report user or client feedback, and propose specific, feasible modifications with a sketch and a reason. Treat the evaluation as evidence-based argument, not as a diary.
In health and safety and ethical/social answers, candidates list hazards in general terms ('sharp tools', 'electricity') without assessing likelihood and severity, without naming the control measure at the point of use, and without discussing who is affected or the ethical trade-off.
Risk assessment is often copied from a template and not applied to the candidate's own product or workshop. Ethical and social issues are treated as opinions rather than as design constraints with stakeholders and consequences.
What to do instead
Use a risk matrix: hazard, who is exposed, likelihood, severity, risk rating, control measure (eliminate, substitute, engineer control, administrate, PPE), and residual risk. Apply it to your own process, not a generic list. For ethical and social questions, identify the stakeholders (user, maker, community, environment), state the competing values, and justify a design decision with its consequence and any mitigation, for example accessibility, planned obsolescence, or data privacy in a smart product.