Learning evidence
A requirements table, alternative sketches, dimensioned model, test report and version comparison
Combines problem definition, constraints, criteria, sketching, 3D modelling, tolerance, materials, print orientation, testing and iteration in one design cycle.
Completion evidence for this pathway is a requirements table, alternative sketches, dimensioned model, test report and version comparison. Page count or time spent alone does not demonstrate competence.
The intended capstone is a measured, safe and repairable prototype for a real user problem, tested across two versions. It should connect the lessons in one artefact and retain failed tests as evidence.
A requirements table, alternative sketches, dimensioned model, test report and version comparison
A measured, safe and repairable prototype for a real user problem, tested across two versions
When a new user need, measurement, failure, print defect, material change or feedback appears.
Lesson · Many 3D models can be constructed by combining, subtracting and transforming simple solids with clear parameters. This lesson includes a worked example, pr
Open page →Lesson · Material selection balances strength, stiffness, toughness, mass, cost, manufacturability, safety and environmental context. This lesson includes a worked
Open page →Lesson · Constraints set limits; success criteria describe measurable qualities a design should achieve within those limits. This lesson includes a worked example,
Open page →Lesson · Dimensioning communicates size and position with units, references and enough information to make or inspect a part. This lesson includes a worked example,
Open page →Lesson · Front, top and side views describe a three-dimensional object through aligned two-dimensional projections. This lesson includes a worked example, practice
Open page →Lesson · Holes, slots and connection features must match the fastener, movement, assembly direction and surrounding material. This lesson includes a worked example,
Open page →Lesson · Print orientation, supports, layer direction, wall thickness and process settings influence strength, finish, time and failure risk. This lesson includes a
Open page →Project · This project develops a protective micro:bit case that preserves access to buttons, pins, power, visibility and ventilation. This lesson includes a worked
Open page →Project · This project creates a reusable cable organiser that guides cables without sharp bending, accidental release or unnecessary material. This lesson includes
Open page →Project · This project designs an adjustable sensor mount with controlled angle, secure fastening, cable clearance and repeatable assembly. This lesson includes a wo
Open page →Lesson · Sketches make ideas visible quickly, while design alternatives prevent the first idea from becoming the only option considered. This lesson includes a work
Open page →Lesson · Engineering design is an iterative cycle of defining a need, generating alternatives, building evidence, testing and revising. This lesson includes a worke
Open page →Lesson · Tolerance defines acceptable dimensional variation, while fit describes how two parts should move or hold together. This lesson includes a worked example,
Open page →Lesson · A useful engineering problem translates what a person needs into a function, context and measurable outcome without assuming the solution too early. This l
Open page →Lesson · Different prototypes answer different questions: appearance, size, mechanism, interaction, manufacturing or durability. This lesson includes a worked examp
Open page →Quiz · A 12-question interactive assessment for Engineering Design and 3D Making, with explanations and a newly shuffled option order on every start. This lesson
Open page →No week closes with reading alone. Use one session for concept and example, a second for practice, and a short third session for testing and explanation. Do not accelerate when a prerequisite is missing.
| Week | Focus | Evidence to produce |
|---|---|---|
| 1 | Building 3D Models from Basic Shapes, Front, Top and Side Views, Project: A Reusable Cable Organiser, Tolerance and Part Fit | A requirements table, alternative sketches, dimensioned model, test report and version comparison |
| 2 | Choosing Materials: Strength, Weight and Cost, Holes, Slots and Connection Points, Project: Designing an Adjustable Sensor Mount, Turning a User Need into an Engineering Problem | A measured, safe and repairable prototype for a real user problem, tested across two versions |
| 3 | Constraints and Success Criteria, Orientation, Supports and 3D Print Quality, Sketching and Design Alternatives, Types of Prototypes and Choosing the Right One | Error log and second version |
| 4 | Dimensioning and Working in Millimetres, Project: A Protective Case for micro:bit, The Engineering Design Cycle | Quiz result, misconception and next application |
The pathway's distinctive question is: How do you turn an idea from measurable requirements into a tested and manufacturable prototype? A first response may be a definition, but completion requires a requirements table, alternative sketches, dimensioned model, test report and version comparison. If input, method, limits and review date are unclear, the result is not traceable even when it looks strong.
Start with two different activities among Building 3D Models from Basic Shapes, Orientation, Supports and 3D Print Quality, Holes, Slots and Connection Points, Sketching and Design Alternatives. In one, explain the concept in your own words; in the other, perform an application, measurement or user test. The two activities should not close with the same type of evidence. This distinction shows that Engineering Design and 3D Making has been tested through different forms of production.
Later connect Project: Designing an Adjustable Sensor Mount, Types of Prototypes and Choosing the Right One, Front, Top and Side Views, Tolerance and Part Fit to the capstone: A measured, safe and repairable prototype for a real user problem, tested across two versions Keep failed tests as well as successful ones. For every error, record conditions, expected result, actual result, possible cause and the single change made.
Check these traps separately: Treating the first idea as the only solution; Thinking about dimensions and tolerance after printing; Writing “looks good” as a success criterion; Recording only successful tests. Reading a trap is insufficient; find an example from your own work and state which evidence made the problem visible.
Return rule: When a new user need, measurement, failure, print defect, material change or feedback appears. Do not delete the previous record; add a date, changed tool or source, new evidence and the next mini trial. Progress is therefore tracked through the quality of explanation, application and correction—not the number of pages completed.
The answer must produce evidence, not only a definition: A requirements table, alternative sketches, dimensioned model, test report and version comparison.
Keep it with conditions, expected result, actual result and the correction.
No. Sources define method and limits; practice evidence must be produced separately.
When a new user need, measurement, failure, print defect, material change or feedback appears.
A measured, safe and repairable prototype for a real user problem, tested across two versions
Primary or institutional source for method and technical limits.
Open source →Primary or institutional source for method and technical limits.
Open source →Primary or institutional source for method and technical limits.
Open source →