Apply a structured design process of exploring, generating, producing and evaluating to develop a digital solution from a real-world problem

What this dot point is asking

QCAA frames the whole subject around a structured approach to solving problems, often described as exploring, generating, producing and evaluating. This dot point is about the process itself: how a developer moves from a real-world problem to a justified, tested solution. The process is iterative, not linear, and it is the spine of both IA1 and IA2. Understanding it lets you organise your project work and explains why design artefacts (requirements, algorithms, prototypes, tests) appear in the order they do.

Exploring the problem

The first stage is understanding the problem before solving it. You investigate the real-world context, identify the users and their needs, and specify the requirements and constraints (see the solution requirements dot point). You gather and analyse information, including how existing solutions work and what data is involved. The output is a clear problem definition and a set of requirements that every later decision is judged against. Rushing this stage is the root cause of most weak projects.

Generating ideas

With the problem understood, you generate possible solutions and evaluate them against the requirements and constraints. This includes sketching interface ideas, considering data models, choosing structures and technologies, and weighing alternatives. The point is to make and justify design decisions deliberately rather than building the first idea. You document the options you considered and why you chose one, because that reasoning is exactly what IA1 rewards.

Producing the solution

Producing is where design becomes a working artefact. For a digital solution this means prototyping interfaces, writing and testing algorithms, building the database, and integrating the components into a running solution. Prototyping is central: you build progressively more complete versions, testing as you go, rather than attempting the whole solution at once. Each prototype is evaluated and refined, which is the iterative loop in action. Version control of your work and incremental testing keep the build manageable.

Evaluating the solution

The final stage judges the solution against the requirements using test evidence (see testing and evaluation strategies). Evaluation is reasoned: it states which requirements are met, which are not, what the limitations are, and what would improve the solution. A genuine evaluation acknowledges weaknesses rather than claiming perfection, and it feeds back into the next iteration. In a finished project, evaluation closes the loop opened by exploring, answering whether the original problem was solved.

Why a process matters

A structured process makes the work traceable: each artefact justifies the next, and the finished solution can be traced back to the original requirements. It also makes the project manageable within a deadline by breaking it into stages with clear outputs. QCAA assesses your reasoning across the process, not just the final product, so documenting decisions at each stage is as important as the code.

How this appears in assessment

IA1 (the technical proposal) is largely the explore and generate stages: investigating the problem, specifying requirements, and designing and justifying a solution. IA2 (the digital solution) is the produce and evaluate stages: building, testing and evaluating a working solution. IA3 applies the same process to a data exchange. The external exam can ask you to identify a stage or describe what happens in it. Use the process to structure your project documentation end to end.