📚 IGCSE Computer Science: Exam Techniques for Top Marks | IGCSE 计算机：满分答题技巧
Scoring full marks in IGCSE Computer Science is not just about memorising facts — it requires a strategic approach to interpreting questions, structuring answers, and managing time under pressure. This guide covers the essential techniques for both theory and practical papers, designed to help you avoid common pitfalls and maximise your score.
在 IGCSE 计算机科学中获得满分，不仅需要记忆知识点，更需要一套策略：解读题目要求、组织答案结构以及在压力下管理时间。本指南覆盖理论与问题求解卷的关键技巧，帮助你避开常见失分点，最大化得分。
1. Understand the Mark Scheme Inside Out | 彻底吃透评分标准
Before attempting past papers, read the official mark scheme for each question. It shows exactly what examiners reward: key terms, phrasing, and the level of detail expected. Often one mark corresponds to one specific point or a correct definition — nothing more, nothing less.
在刷真题之前，先仔细阅读每道题的官方评分标准。它明确展示了考官奖励的要点：关键词、措辞和所需细节程度。通常一个分数对应一个具体观点或一个正确定义，不多不少。
For explain questions, marks are usually allocated for a cause AND an effect, or a step followed by its consequence. If you write a long paragraph but miss the cause-effect link, you lose half the marks. Study how the scheme splits marks for 'state', 'describe', 'explain', and 'justify'.
对于解释类问题，分数通常分配给原因和结果，或某步骤及其后果。如果你写了一大段却漏掉因果联系，就会损失一半分数。研究评分标准如何对“陈述”“描述”“解释”和“论证”分配分数。
2. Command Words Decoded | 指令词解析
IGCSE Computer Science questions use precise command words. 'State' requires a short, factual answer; 'Describe' needs a step-by-step account or characteristics; 'Explain' asks for reasons or how something works, often with 'because'; 'Discuss' requires arguments for and against. Knowing these differences prevents irrelevant detail.
IGCSE 计算机科学题目使用精确的指令词。“State”要求简短的事实性答案；“Describe”需要逐步描述或特征说明；“Explain”要求给出原因或工作原理，常带“because”；“Discuss”需要正反论点。理解这些区别可以避免无关细节。
| Command Word | What You Must Do | Mark Allocation Tip |
|---|---|---|
| State | Give a single term or fact | 1 mark = one correct term |
| Describe | Write the step-by-step process | Each step with its result counts |
| Explain | Give reason(s) and effect(s) | Awarded for 'cause THEN effect' |
| Discuss | Present both sides and a conclusion | Marks for each justified viewpoint |
3. Perfecting Your Timing | 完美掌控时间
In Paper 1 (1hr 45min for 75 marks), aim to spend roughly 1.2 minutes per mark. This means a 6-mark question should get about 7 minutes. Paper 2 (1hr 45min for 50 marks) allows 2.1 minutes per mark, but the programming questions need extra thinking time.
在 Paper 1（1小时45分钟/75分）中，目标每分用时约1.2分钟。6 分题大约用 7 分钟。Paper 2（1小时45分钟/50分）每分2.1分钟，但编程题需要更多思考时间。
Start with the short-answer sections to bank quick marks and build confidence. Skip any question that stalls you for more than 2 minutes; mark it and return later. Always keep 10 minutes at the end for reviewing — especially the trace table and pseudocode questions in Paper 2, where small slips cost entire marks.
从简答题入手，快速赚分并建立信心。如果某题卡住超过2分钟，先跳过、标记并回头再做。最后务必留出10分钟检查，尤其是 Paper 2 的跟踪表和伪代码题，一个小笔误可能丢掉整题分数。
4. Crafting Theory Answers for Full Marks | 构建满分理论答案
For 'describe' and 'explain' questions, use bullet points where possible to make marking easy. Each bullet should contain one complete idea: a fact, a reason, or an effect. Avoid writing a dense paragraph that hides the key points.
对于“描述”和“解释”题，尽量使用要点分列，让阅卷清晰易判。每个要点包含一个完整想法：一个事实、一个原因或一个结果。避免写一大段密集文字，把关键点淹没。
Always link your answer back to the scenario given. For example, if the question describes a school library database, don't just define 'validation' in general — say 'presence check on the book ID ensures no record is left blank in the library system'. This shows application, which is essential for the highest marks.
始终将答案联系到题目给出的场景。比如，题目描述学校图书馆数据库，不要只泛泛定义“验证”，而要说“对图书 ID 进行存在性检查，确保图书馆系统中没有空白记录”。这展现了应用能力，是高分的必要条件。
5. Tackling Algorithm and Pseudocode Questions | 攻克算法与伪代码题
Read the pseudocode line by line, and use a variable table on your exam paper to track changes as you step through. For trace tables, begin by listing all variables in the header row, even if they appear later. Update them progressively — one per column — and never skip an iteration.
逐行阅读伪代码，在试卷空白处画变量表格，边读边记录变量变化。对于跟踪表，先在表头列出所有变量（即使后面才出现）。每次迭代逐一更新变量，不可跳过任何循环。
When writing your own pseudocode or flowchart, use standard notation: 'INPUT', 'OUTPUT', 'WHILE...DO...ENDWHILE', 'IF...THEN...ELSE...ENDIF'. Keep it simple and unambiguous. A variable name like 'total_score' is better than 'ts'. If you need to initialise a total, write 'total ← 0' — the left arrow shows assignment clearly.
当需要自己编写伪代码或流程图时，使用标准符号：INPUT、OUTPUT、WHILE...DO...ENDWHILE、IF...THEN...ELSE...ENDIF。保持简单、无歧义。变量名如 total_score 比 ts 更好。若要初始化总和，写作 total ← 0，左箭头明确表示赋值。
6. Mastering Trace Tables and Dry Runs | 精通跟踪表与手动运行
A trace table question typically requires you to complete a grid showing variable values after each line of execution. Start by identifying the variable set, then walk through the algorithm line by line. After a statement like 'x ← x + 2', write the new value immediately in the next column.
跟踪表题通常要求你填写一张网格，展示每一行执行后变量的值。先识别变量集，然后逐行遍历算法。当执行到类似 x ← x + 2 的语句时，立刻在下一列写入新值。
Pay special attention to loops: ensure you run the body exactly the specified number of times. Also note that assignment is not an equation — 'x ← y' changes x to the value y currently holds, nothing else. This is a common trap where students mistakenly think it also updates y.
特别注意循环：确保执行循环体次数准确无误。还要注意赋值不是等式——x ← y 将 x 更改为 y 当前的值，仅此而已。常有学生误以为这也会更新 y，这是一个常见陷阱。
7. Data Representation: Precision and Conversions | 数据表示：精度与转换
010110₂ → 1101 0110 → D6₁₆. Always label your bases to avoid confusion, and double-check that 'D6' is a valid hex number (digits 0-9, A-F).
二进制、十进制和十六进制转换只要写出完整步骤就稳拿分。二进制转十六进制时，从右往左四位一组：11010110₂ → 1101 0110 → D6₁₆。务必标注基数以免混淆，并复查“D6”是否为有效十六进制数（数字 0-9、A-F）。
In questions about overflow or logical shifts, show the bits before and after the shift, and note whether a carry bit is generated. For two's complement, keep the sign bit consistent: if the number is negative after an operation using 8 bits, the most significant bit must be 1. Use 1/2 byte boundary rules precisely.
在关于溢出或逻辑移位的题目中，展示移位前后的比特，并标注是否产生进位。对于二进制补码，保持符号位一致：如果运算后是负数且使用 8 位，最高有效位必须是 1。精确使用 1/2 字节的边界规则。
8. Networks, Security, and Scenario Linking | 网络、安全与场景结合
When asked to 'explain how a firewall protects a network', don't just define a firewall — describe what it does in the context: it inspects incoming data packets, compares them against a set of rules, and blocks or allows traffic. This transforms a vague response into a mark-winning, application-rich answer.
当被问到“解释防火墙如何保护网络”时，不要仅仅定义防火墙——要描述其在具体场景中的作用：它检查传入数据包，与一组规则进行比对，然后决定阻断还是允许流量。这样就把模糊的回答变成了应用性强的得分答案。
For cybersecurity questions, always couple the threat with the defence. For instance, mention 'phishing' and then how user training or email filters can reduce the risk. Use proper terminology — 'asymmetric encryption', 'SSL/TLS', 'SQL injection', 'DDoS' — and refer to real-world conventions where possible.
对于网络安全题，始终将威胁与防御措施配对。例如，提到“钓鱼攻击”，接着说明用户培训或邮件过滤器如何降低风险。使用规范术语——“非对称加密”、“SSL/TLS”、“SQL 注入”、“DDoS”——并尽可能引用现实中的常规做法。
9. The Art of Drawing Diagrams and Screenshots | 绘图与界面描述的技巧
When required to draw a logic circuit given a Boolean expression, first write the expression as (A AND B) OR (NOT C), then convert step by step: draw AND gate for A and B, a NOT gate for C, then an OR gate combining them. Label all inputs and outputs clearly.
当需要根据布尔表达式绘制逻辑电路时，先写出表达式如 (A AND B) OR (NOT C)，然后逐步转换：为 A 和 B 画与门，为 C 画非门，再用或门连接。所有输入端和输出端都清楚标注。
For user interface or flowchart sketching, use simple rectangles, parallelograms (I/O), and diamonds (decisions). The examiner doesn't expect artistic talent but expects correct flow and symbols. A neat, labelled diagram can earn full marks even if it looks basic.
对于用户界面或流程图绘制题，用简单的矩形、平行四边形（输入/输出）和菱形（判断）。考官不要求艺术功底，但要求流程和符号正确。一幅整洁、带标注的简单图示也能获得满分。
10. Avoiding Common Pitfalls That Lose Easy Marks | 避开常见的失分陷阱
A frequent mistake is writing vague answers like 'it makes it safer' without specifying what 'it' is or how. Always name the exact technology or concept and state its specific mechanism. For example: 'SSL encrypts data during transmission, preventing eavesdropping.'
常见错误是答案含糊，如“它让它更安全”，却不说明“它”指什么或如何做到。务必说出确切的技术或概念名称并阐明其具体机制。例如：“SSL 在传输过程中加密数据，防止窃听。”
Another pitfall is confusing similar terms: HTTP vs HTTPS, ROM vs RAM, LAN vs WAN, compiler vs interpreter. Create a comparison table during revision so you can recall precise differences on exam day. Also, double-check the number of marks — a 2-mark question rarely expects more than 2 distinct, correct points.
另一个陷阱是混淆相似术语：HTTP 与 HTTPS，ROM 与 RAM，LAN 与 WAN，编译器与解释器。复习时制作对比表格，就能在考试时准确回忆区别。还要反复检查分值——2 分题很少期望超过两个独立且正确的要点。
11. Exam-Day Routine: From Reading Time to Final Check | 考试日流程：从阅卷到终检
Use the reading time to identify easier short questions and to carefully read the programming scenario in Paper 2. Plan which questions to answer first — but do not start writing. Mentally list the command words so you know the type of response required for each.
利用阅卷时间标记较容易的简答题，并仔细阅读 Paper 2 的编程情境。计划答题顺序，但不要动笔。在心里记下每个问题的指令词，这样你就清楚每道题需要什么类型的答案。
Once you start writing, stick to the time plan. If you finish early, check units (e.g., bytes vs kilobytes, bps vs Mbps) and that you haven't accidentally missed the back of the page. For Paper 2, re-run your trace table with a different test value to ensure it works.
一旦开始答题，就要坚持时间计划。如果提前完成，检查单位（如字节 vs 千字节，bps vs Mbps），并确认没有遗漏试卷背面。Paper 2 中，尝试用一个不同的测试值重新手动运行跟踪表，确保逻辑正确。
12. Practice, Resources, and the Revision Loop | 练习、资源与复习闭环
No technique substitutes for consistent practice. Work through at least 5 full past papers under timed conditions, then mark them yourself using the mark scheme before reading the examiner's report. The reports often reveal what most candidates got wrong, giving you a chance to avoid those mistakes.
任何技巧都无法替代持续练习。在限时条件下完成至少五套完整的历年真题，然后用评分标准自行批改，再阅读考官报告。报告通常会揭示大多数考生出错的地方，让你有机会避免类似错误。
Create a 'mistake log' — a simple notebook where you record each error, the correct answer, and a keyword hint. Review this log in the last week before the exam to rapidly consolidate weak areas. Targeted revision is far more efficient than re-reading the entire textbook.
制作一个“错题日志”——一个简单笔记本，记录每次错误、正确答案和一个关键词提示。考前最后一周复习这个日志，快速巩固薄弱环节。有针对性的复习远比通读整本教材高效。
Published by TutorHao | Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
或截图后用「扫一扫 → 相册」选择本图