Structured Programming — common mistakes

In exams, when asked to use stepwise refinement, clearly state the problem and then list the broken-down steps numerically. For example: '1. Initialise variables', '2. Loop through inputs', '3. Calculate result'. You can then refine each step further, e.g., '2.1. Use a FOR loop from 1 to 30', '2.2. Input score', '2.3. Add to total'. This demonstrates the process clearly.

In the context of the A-Level syllabus, they are treated as the same concept. Both refer to the process of breaking a large, complex problem into a hierarchy of smaller, more manageable sub-problems.

GOTO statements create unconditional jumps in the program's execution path. This makes the code's logic incredibly difficult to follow, debug, and maintain, a problem often called 'spaghetti code'. Structured programming replaces this with clear, predictable control structures like loops and conditionals.

Yes, absolutely. Nesting is a key part of building complex logic from simple blocks. For example, you can have a FOR loop (iteration) that contains an IF statement (selection) to process items in a list, or even another loop inside the first one.

Yes. Procedures and functions are the primary way to implement the modules identified during top-down design. They encapsulate a specific piece of logic, making the program modular, reusable, and easier to understand.