Apply the engineering problem-solving process to a machine or mechanism brief, explaining how data, prototyping and evaluation against criteria drive the development of a justified solution

What this dot point is asking

QCAA wants you to apply the engineering problem-solving process to a machine or mechanism brief and explain how each phase contributes to a justified solution. This is the skill assessed directly in the internal project work: defining the problem, generating ideas, developing and testing, and evaluating against criteria using data rather than opinion. It ties the technical content of Unit 4 to how engineers actually work.

The answer

An iterative process, not a recipe

The engineering problem-solving process is a structured but iterative approach. Engineers rarely move cleanly from start to finish; they loop back when testing reveals a weakness. The phases below describe the work, but in practice they overlap and repeat.

Explore the problem

The first phase defines what the problem actually is. Engineers identify the need, the stakeholders, the constraints (budget, materials, size, safety, regulations) and the criteria a solution must meet. They research existing machines and mechanisms that solve similar problems. The output of this phase is a clear problem statement and a set of measurable design criteria, such as "must lift $50\,\text{kg}$" or "must fit within $300\,\text{mm}$".

Develop ideas

Here engineers generate a range of possible concepts rather than committing to the first idea. Sketches, mechanism diagrams and rough calculations let several options be compared early, before time is spent on detail. Divergent thinking widens the field; the design criteria then narrow it.

Generate the solution

The promising concept is developed into a working solution through modelling, calculation and prototyping. Free-body diagrams, gear-ratio and mechanical-advantage calculations, material selection and CAD models all belong here. A prototype lets the design be tested physically. This is where the technical content of Units 3 and 4 is applied directly.

Evaluate against criteria

The solution is judged against the measurable criteria set in the first phase, using data collected from testing. Evaluation asks whether the solution meets each criterion, by how much, and at what cost. Where it falls short, the process loops back to refine the design. A recommendation is justified by the evidence: test data, calculations and the criteria comparison, not by assertion.

Justifying with data

The thread running through every phase is evidence-based decision making. Each choice (this mechanism, this gear ratio, this material) is defended by data: a calculation, a test result or a comparison table. This is what distinguishes an engineering justification from an opinion and is exactly what the internal assessment rewards.

Why this matters for engineered solutions

The internal project asks you to run this whole process on a real brief and document it. Markers look for a clear problem definition, a genuine range of ideas, technical development with calculations, and an evaluation that uses data against criteria. Showing the evidence behind each decision is the difference between a described solution and a justified one.