CIE IGCSE | TOPIC 4 ASSESSMENT
SOFTWARE: END OF TOPIC REVIEW
Check your understanding of software types, operating systems, startup, interrupts, languages, translators and IDEs. Work independently before checking your answers.
BEFORE YOU BEGIN
Suggested time: 25–35 minutes. Complete sections A and B without notes. Write section C answers in your exercise book before revealing the marking guidance.
Sections A and B provide an automatic score out of 11, one point for each fully correct item. Section C has 10 suggested written marks, assessed separately. These are original practice questions, not an official Cambridge paper or grade boundary.
For calculations, show working in your book and enter the answer in the unit requested. Calculator use can follow your teacher’s instructions. Your answers remain only while this page is open.
C | EXAM-STYLE WRITING
Write in your exercise book before revealing the guidance. Section C assesses subject knowledge and gives you practice expressing it clearly. The first table reproduces the command-word meanings supplied from the Cambridge syllabus. The second gives practical writing guidance for this review.
| CIE command word | Meaning from the specification |
|---|---|
| Calculate | work out from given facts, figures or information |
| Compare | identify/comment on similarities and/or differences |
| Define | give precise meaning |
| Demonstrate | show how or give an example |
| Describe | state the points of a topic / give characteristics and main features |
| Evaluate | judge or calculate the quality, importance, amount, or value of something |
| Explain | set out purposes or reasons / make the relationships between things clear / say why and/or how and support with relevant evidence |
| Give | produce an answer from a given source or recall/memory |
| Identify | name/select/recognise |
| Outline | set out the main points |
| Show (that) | provide structured evidence that leads to a given result |
| State | express in clear terms |
| Suggest | apply knowledge and understanding to situations where there are a range of valid responses in order to make proposals / put forward considerations |
The command applies to the subject context. A brief identification does not need an essay; an explanation needs accurate links. Use the guidance below for the four commands in this written review.
| Command word | What your answer should do | Useful writing pattern |
|---|---|---|
| Describe | State the main features or relevant points; for a process, make the sequence clear. | First… Next… Finally… |
| Explain | Give reasons, purposes or clear relationships, supported by relevant subject knowledge. | …because…; therefore…; resulting in…; leading to… |
| Compare | Identify similarities and/or differences, addressing both things on the same basis. | Both…; whereas…; unlike… |
| Evaluate | Make a reasoned judgement about suitability or value in the given context. | A benefit is…; however…; therefore, for this purpose… |
BUILD A CLEAR EXPLANATION
Point → reason or mechanism → consequence. Connectives help show the relationship, but the technical link must be accurate. Adding “because” to an unsupported claim does not make it a good explanation.
Thin answer: “The task continues.”
Developed answer: “Because the interrupt handler may change registers, the original state is saved before it runs. Restoring those values afterwards allows the task to continue correctly.”
Use because or because of to introduce a cause; therefore, resulting in or leading to to show a consequence. For comparison, use both and whereas. For evaluation, use however and finish with a justified judgement.
Write enough relevant detail for the marks available. Clear, concise sentences are better than padding. These are writing supports, not compulsory phrases or separate official language marks.
12 | STARTING A COMPUTER
[3 suggested marks]
Describe a simplified sequence from powering on a computer to running an application, including firmware, the bootloader and the operating system.
Sample answer: First, the processor executes initial firmware stored in non-volatile memory to prepare the system and begin startup. The bootloader then loads the OS, or starts the next loading stage, and transfers control. The OS starts its services and manages resources, providing the platform on which a compatible application can be launched.
- Initial firmware prepares hardware and starts the boot process: one mark.
- Bootloader loads the OS or its next stage and transfers control: one mark.
- OS supplies services and resources enabling the application to run: one mark.
Writing focus: make the sequence clear. Firmware and the OS are software; the processor executes their instructions.
13 | PRESERVING AN INTERRUPTED TASK
[3 suggested marks]
An interrupt service routine uses registers also needed by the current task. Explain why the task’s state is saved before the routine runs and restored afterwards.
Sample answer: The current task needs its register values and return position to continue correctly. Because the ISR may change those registers, the required original state is saved before it executes. Restoring the state afterwards reinstates the task’s values and return position, therefore allowing normal execution to resume without using the handler’s temporary values.
- Identify required execution information, such as register values and return position: one mark.
- Link saving before the ISR to avoiding loss of state when registers change: one mark.
- Link restoration to correct continuation: one mark.
Writing focus: show the cause and consequence. This is execution-state preservation, not saving the user’s document to disk.
14 | TRANSLATION AND EXECUTION
[2 suggested marks]
Compare a compiler and an interpreter in terms of when translation and execution occur and whether a separate executable is produced. Use the syllabus models.
Sample answer: A compiler translates the whole program before the resulting executable runs, whereas an interpreter translates and executes code as it goes. After successful compilation, a separate executable is produced in this model; the interpreter model runs through its translation/execution system without first producing a standalone executable.
- Linked comparison of whole-program translation before execution and translation/execution as it goes: one mark.
- Linked comparison of separate executable output: one mark.
Writing focus: compare both approaches on the same points. Real implementations can combine techniques; answer using the stated models.
15 | AN IDE FOR A NEW PROGRAMMER
[2 suggested marks]
A new programmer wants to rely on auto-completion, auto-correction and diagnostics instead of testing a quiz program. Evaluate this approach and give a justified recommendation.
Sample answer: The IDE features can reduce typing mistakes and draw attention to detected problems, helping the programmer work efficiently. However, valid code can still contain logic errors, such as calculating the wrong score, and an accepted suggestion may not match the programmer’s intention. Therefore the programmer should use these features as support, but test the quiz against expected results and inspect important changes rather than relying on the IDE alone.
- Weigh a relevant benefit against the limit that logic errors or unintended suggestions can remain: one mark.
- Give a justified recommendation to combine IDE support with testing and checking: one mark.
Writing focus: weigh the benefit and limitation, then conclude for the stated user and task.
CHECK YOUR WRITTEN COMMUNICATION
- Did I answer the command word, rather than just name facts?
- For explain, did I show an accurate reason or cause-and-effect link?
- For compare, did I address both things on the same point?
- For evaluate, did I weigh relevant factors and justify my judgement?
- Did I use precise terms and connectives naturally, without repeating or padding?
Self-assess using the suggested content marks, keeping the written total separate from your automatic score. Use the writing checklist to improve an answer rather than adding unofficial language marks.
YOUR NEXT REVISION STEP
Submit sections A and B to see suggested lessons to revisit.
For written work, revisit firmware and startup, interrupts, compilers and interpreters and IDE features where needed.
This review samples the topic. Also check all nine OS functions, software examples, language-level trade-offs, error reporting, and the seven IDE features using the full Topic 4 revision page.
Choose two weak areas, revisit their explanations and attempt fresh examples. Repeating these questions after feedback shows learning rather than an independent assessment.