Understand the benefits of using subprograms

The idea

A subprogram is a named block of code that performs one task and can be called whenever that task is needed. It may take parameters and may return a value. The benefits follow from decomposition: a large program is split into smaller, self-contained parts, so each part is easier to write, read, test and debug. A subprogram that works correctly can be reused many times instead of rewriting the same code, which shortens programs and reduces the chance of inconsistent errors. If a fault is found, it can be fixed once inside the subprogram rather than in every copy. Teams can also divide work by assigning different subprograms to different programmers, and a well-named subprogram makes the overall program easier to follow.

What earns the marks

• A subprogram is a named block of code that carries out a specific task and can be called when required.
• Subprograms make a program easier to read and understand because each one has a single clear purpose.
• Code can be reused by calling the same subprogram many times instead of rewriting it.
• Testing and debugging are easier because each subprogram can be checked in isolation.
• A fault fixed once inside a subprogram is corrected everywhere it is called.
• Subprograms support teamwork, since different people can develop different parts of a program.

Common mistakes and how to put them right

• Saying subprograms make a program run faster.

  Put it right: The main benefits are readability, reuse, easier testing and easier maintenance, not guaranteed speed.

• Thinking a subprogram must always return a value.

  Put it right: Some subprograms perform an action and return nothing; returning a value is optional.

• Believing reuse means copying the code into each place it is needed.

  Put it right: Reuse means calling the same subprogram, so the code exists only once.

• Assuming subprograms remove the need to test.

  Put it right: Each subprogram still needs testing, but it can be tested separately before being combined.

Exam tips

• Link each benefit to a concrete effect, such as fixing one fault in one place instead of many.
• Use the scenario in the question to name a task that could become a subprogram.
• If asked for benefits, give distinct points rather than repeating the same idea in different words.