Iterative design as a repeating cycle of explore, create and evaluate: how it differs from linear design, why testing and feedback drive refinement, and how it underpins the J310 design challenge.

What this dot point is asking

Iterative design is the idea at the centre of the whole J310 course, and the NEA is literally called the "Iterative Design Challenge." OCR wants you to understand it as a repeating cycle of explore, create and evaluate, to contrast it with linear design, and to explain why testing and feedback at every loop produce a better product. In the written exam this appears as questions describing the stages and explaining why iterating beats a single straight-line process.

The three stages

The point examiners reward most is that these stages loop. After evaluating, you go back to explore or create with what you have learned, and round again, each pass improving the design.

Iterative versus linear design

In a linear process, problems often surface only at the end, when they are expensive and difficult to fix. In an iterative process, early models are tested and faults are caught and corrected while changes are still cheap and easy. Iteration trades a little extra time early for a much more reliable, well-fitting product.

Why iterating works

How it underpins the NEA

The J310 NEA asks you to respond to a context by working the cycle repeatedly and documenting it in a chronological portfolio. Markers look for evidence that you explored, created and evaluated more than once, with testing feeding genuine improvements, leading to one final prototype. A portfolio that marches straight from brief to product, with no looping or testing, scores poorly because it is not iterative.

Try this

Q1. Name the three stages of the iterative design cycle. [3 marks]

• Cue. Explore, create, evaluate.

Q2. State one advantage of an iterative approach over a linear one. [1 mark]

• Cue. Problems are caught early, feedback shapes the design, or the final product is more fit for purpose.