By Cyril KimbiICT is widely treated as the easy subject on a GCE timetable. The results do not support that, and the reason is specific: it is examined as a body of precise terminology, and candidates who understand a concept perfectly still lose marks because they wrote an everyday description instead of the term the scheme wanted.
Why candidates underperform
Everyone uses a phone, so the subject feels familiar. Familiarity is exactly the trap: knowing how to use technology is not the same as being able to define, classify and compare it in examination language.
Consider a question asking you to define backup. “Keeping a second copy in case something happens” describes the idea and usually scores nothing. “A copy of data stored separately so it can be restored if the original is lost, corrupted or damaged” is the answer. Same understanding, different marks.
This is the single largest source of avoidable loss in the subject, and it is fixable in weeks rather than months.
Build a definitions list and test it backwards
Go through the syllabus and list every term it names. For each, write the definition in the syllabus’s own language rather than your own.
Then test yourself in the direction the exam uses: given the definition, produce the term. Most candidates revise term to definition, which is the easier direction and the wrong one — an examination question gives you a scenario or a description and asks what it is called.
Terms worth being ruthless about: hardware categories, types of software, storage media and their capacities, network types and topologies, transmission media, input and output devices, file organisation methods, security threats and countermeasures, and the components of an information system.
The classification questions
A large share of the paper asks you to place something in a category, or to distinguish two categories. Get the boundaries right:
| Distinction | What actually separates them |
|---|---|
| System vs application software | Manages the computer itself vs performs a user task |
| RAM vs ROM | Volatile and writable vs non-volatile and normally read-only |
| Primary vs secondary storage | Directly accessible by the processor vs not |
| LAN vs WAN | Geographic scope and ownership of the transmission medium |
| Data vs information | Raw facts vs data processed into meaning |
| Virus vs worm | Requires a host file and user action vs self-replicating across a network |
When a question says compare or distinguish, both items must appear in the same sentence, on the same axis. Two separate descriptions is not a comparison and is marked as one point rather than two.
Scenario and application questions
These carry the highest marks and the widest spread of scores. You are given a situation — a school, a clinic, a small business — and asked to recommend hardware, software, a network arrangement or a security measure, and to justify it.
The structure that scores: name the thing, then justify it against the scenario. “A local area network, because all the computers are in one building and the school owns the cabling, so there is no recurring line cost.” The clause after “because” is the mark, and it must reference the scenario rather than a general advantage.
The common failure is recommending something generically good without connecting it to the situation described. Read the scenario for its constraints — budget, distance, number of users, sensitivity of the data — and justify against those.
Diagrams
Network topologies, the components of a computer system and data-flow arrangements all appear as diagram questions, and the marks are in the labels rather than the drawing.
Draw large, label every element, use a ruler for connections, and add a title. An unlabelled topology diagram, however neat, earns little. Practise drawing bus, star, ring and mesh from memory until they are automatic.
Where ICT and Computer Science differ
Students frequently confuse the two subjects and revise the wrong material.
ICT is about using and applying information technology — systems, their components, their uses, their social and security implications. Computer Science goes further into how computers work and how to program them, including algorithms and code.
If you are taking both, keep the revision separate. If you are taking Computer Science, the practical paper guide covers the programming component, which ICT does not test in the same way.
A revision routine that works
- Build the definitions list from the syllabus in week one. This is the highest-return task in the subject.
- Test definition to term, on a blank page, twice a week.
- Work past-paper questions timed, then mark yourself strictly against the marking scheme. If the scheme required a term and you described it, you did not earn the mark.
- Log recurring losses. After ten papers the list will be short and almost entirely terminology.
- Practise scenario questions last, once the vocabulary is secure — they depend on it.
The ICT past questions supply the material, and the syllabus guide tells you which topics are examinable at all.
Frequently asked questions
Is GCE ICT an easy subject?
It is approachable but precision-dependent. Candidates lose marks on terminology rather than on understanding.
Do I need a computer to revise ICT?
Not for most of the paper. It is examined on paper, and definitions, classifications, diagrams and scenario answers all practise without a machine.
What is the difference between ICT and Computer Science?
ICT covers using and applying technology; Computer Science covers how computers work and how to program them.
Why do I lose marks when my answer is right?
Almost always because the required term was missing, or because a comparison was written as two separate descriptions.
How many past papers should I do?
Fewer, marked strictly, beats many skimmed. Ten fully marked papers with a logged loss list is a serious programme.
