Understand the benefit of using decomposition and abstraction to model aspects of the real world and to analyse, understand and solve problems, and understand the benefits of using subprograms.

What this dot point is asking

Edexcel wants you to explain how the two core computational thinking skills, decomposition and abstraction, let you model a real-world situation and break a hard problem into solvable pieces, and to give the benefits of dividing a program into subprograms.

Decomposition

Decomposition is the first move when a problem is too big to solve in one go. Take a program that manages a library: rather than tackling everything at once, you split it into parts such as "search for a book", "issue a book to a member", "return a book" and "calculate overdue fines". Each part is small enough to think about clearly, and once each works you assemble them into the finished system.

The benefits Edexcel rewards are concrete. Smaller sub-problems are easier to understand than the whole, easier to test because you can check each one in isolation, and easier to share out, so several people can work on different parts of a large project at the same time. They also make reuse possible: a "validate a date" sub-problem written once can be used wherever a date is entered.

Abstraction

Abstraction is how a program models the real world. The real world is far too detailed to represent completely, so you keep only the relevant features. A map of a train network is a classic abstraction: it shows the stations and which lines connect them, but deliberately ignores the exact distances, the bends in the track and the scenery, because a traveller only needs the connections and the order of stops.

In a program, abstraction shows up when you decide what data to store. A school timetable system stores a lesson as a subject, a teacher, a room and a time. It does not store the colour of the classroom door or the weather, because those details do not help build the timetable. Choosing the right level of abstraction, enough detail to solve the problem but no more, is a key design skill.

Subprograms

The benefits of subprograms map directly onto the benefits of decomposition, and Edexcel expects them stated precisely:

• They avoid repetition. Code written once in a subprogram can be called many times, instead of being copied out repeatedly, so the program is shorter.
• They are easier to test and debug. A subprogram can be tested on its own, and a fault is isolated to one place. Fixing it once fixes every call.
• They make programs easier to read and maintain. A sensible name such as calculate_charge documents what the code does, so the main program reads as a clear sequence of tasks.
• They support teamwork and reuse. Different people can write different subprograms, and a useful subprogram can be reused in other programs.

This is also why Edexcel pairs subprograms with decomposition in the same specification line: subprograms are the practical tool that turns a decomposed design into well-structured code.

Try this

Q1. State what is meant by decomposition. [1 mark]

• Cue. Breaking a problem into smaller, more manageable sub-problems.

Q2. Give two benefits of using subprograms in a program. [2 marks]

• Cue. Any two of: avoids repeating code; easier to test or debug; easier to read or maintain; can be reused; lets several people work on different parts.