📚 Year 9 CIE Computer Science: Exam Techniques and Marking Criteria | Year 9 CIE 计算机：答题技巧与评分标准
Starting your IGCSE Computer Science journey in Year 9 is the perfect time to understand not just the subject content, but also how your knowledge will be assessed. The Cambridge IGCSE Computer Science (0478) examination rewards precise answers, logical thinking, and a clear understanding of command words. By learning exam techniques early and becoming familiar with marking criteria, you can avoid common pitfalls and score higher marks. This article will walk you through essential strategies for both Paper 1 (Theory) and Paper 2 (Problem‑solving and Programming), and show you exactly what examiners expect from candidates at this level.
在 Year 9 开始 IGCSE 计算机科学的学习，正是理解学科内容并熟悉评估方式的最佳时机。剑桥 IGCSE 计算机科学（0478）考试看重精确的答案、逻辑思维以及对指令词的正确把握。早一点掌握答题技巧、了解评分标准，你就能避开常见错误，拿到更高分数。本文将为 Paper 1（理论）和 Paper 2（问题解决与编程）提供关键策略，并清楚说明考官对考生的期望。
1. Understanding Command Words | 理解指令词
CIE exam questions use a set of standard command words that tell you exactly how to answer. 'State' simply requires a single word, phrase or short sentence – no explanation is needed. For example, 'State one type of network topology' only expects 'Star' or 'Bus', not a description. 'Describe' asks you to say what something is like; you must give characteristics, often in a sequence. If asked to 'Describe how the fetch–decode–execute cycle works', you should write a step‑by‑step account. 'Explain' is a step up – you must give reasons or causes, usually linking an outcome to a condition. 'Calculate' means show your working and give the final numeric answer. Recognizing these differences can save you time and stop you from over‑writing or under‑answering.
CIE 考题使用一套标准的指令词，它们明确告诉你如何作答。“State”只需要一个词、短语或短句，无需解释。例如，“State one type of network topology”只需回答“Star”或“Bus”，不应描述。“Describe”要求说出某事物的特征，通常需要按顺序列出特性。如果题目是“Describe how the fetch–decode–execute cycle works”，你就应该一步一步写过程。“Explain”要求更高——你必须给出原因或因果关系，往往需要把结果和条件联系起来。“Calculate”则要展示计算步骤，给出最终数值答案。认清这些区别，就能节省时间，避免过度书写或答题不足。
2. Time Management and Question Selection | 时间管理与选题策略
Paper 1 lasts 1 hour 45 minutes and carries 75 marks. A rough guide is to spend about one minute per mark. Start with the short‑answer questions in Section A, as they are usually straightforward and build confidence. In Section B, choose the two 15‑mark questions you feel most comfortable with; read all three before deciding. Never spend 20 minutes on a single 4‑mark question – leave it, move on, and come back later. For Paper 2, you have 1 hour 45 minutes for 50 marks of mostly programming and problem‑solving tasks. Use the reading time before writing to understand pre‑release material or scenario descriptions thoroughly. Allocate the last 10 minutes for checking pseudocode syntax and debugging logic errors.
Paper 1 时长 1 小时 45 分钟，总分 75 分。粗略指导是每个分值花费约一分钟。先做 Section A 的简答题，它们通常比较直接，有助于建立信心。Section B 要求选做两道 15 分大题，在决定前先把三道题都读一遍。不要在 4 分小题上花 20 分钟——先跳过，做完其他再回来。Paper 2 也是 1 小时 45 分钟，50 分，主要是编程和问题解决任务。动笔前利用阅读时间彻底理解预发布材料或情境描述。最后留 10 分钟检查伪代码语法和逻辑错误。
3. Structuring Long-Answer Theory Questions | 结构化理论长答题
For 6‑mark or 15‑mark 'Describe/Explain' questions, a clear structure is essential. Start with a general statement, then break the process or concept into logical steps. Use linking words such as 'firstly', 'next', 'then', 'as a result', and 'finally'. If the question is about data transmission, you might set out: 'The sender's device breaks the data into packets, adds header information containing destination address and sequence number, and sends them via the network. Routers read the destination address and forward each packet along the best available path. The receiver reassembles the packets using sequence numbers and checks for missing data.' This structured approach mirrors the mark scheme, where marks are often allocated for each distinct point.
对于 6 分或 15 分的“描述/解释”题，清晰的结构至关重要。先用一句话总领，然后把过程或概念拆分成逻辑步骤。使用“首先”“其次”“然后”“因此”“最后”等连接词。如果题目是关于数据传输，你可以写：“发送端设备将数据拆成数据包，添加包含目标地址和序列号的首部信息，然后通过网络发出。路由器读取目标地址，将每个数据包沿最佳可用路径转发。接收端利用序列号重新组装数据包并检查是否有缺失数据。”这种结构化写法与评分方案高度吻合，因为分数通常就分配给每一个独立的要点。
4. Writing Clear and Precise Answers | 写出清晰准确的答案
Vague statements rarely gain marks. Instead of writing 'the computer processes data quickly', say 'the CPU fetches an instruction from RAM, decodes it to determine the operation, and executes it using the ALU, all within a single clock cycle of, say, 3 GHz, enabling billions of operations per second.' Be specific with terminology: use 'ASCII', not just 'code'; 'volatile', not just 'memory is deleted when power is off'. Avoid repeating the question in your answer and do not write in note form – full sentences are expected unless the command word is 'State'. Keep your handwriting legible or take care with on‑screen typing; if the examiner cannot read your answer, marks cannot be awarded.
含糊的表述很难得分。不要写“计算机快速处理数据”，而应写“CPU 从 RAM 取指令，经译码确定操作，再通过 ALU 执行，整个过程在比方说 3 GHz 的一个时钟周期内完成，每秒可执行数十亿次操作。”术语要准确：用“ASCII”而不仅是“编码”；用“易失性”而不只是“断电后数据消失”。不要在答案中重复题目，也不要用笔记体——除了指令词是“State”的情况，官方要求写完整句子。笔迹清晰，或机考时注意打字体整；如果考官看不懂你的答案，就无法给分。
5. Tackling Algorithm Design Questions | 应对算法设计题
In Paper 2, you may be asked to design an algorithm for a given problem. Always begin by identifying inputs, processes, and outputs (IPO). Write down a simple plan before starting your pseudocode or flowchart. Use consistent indentation and capitalise keywords like IF, ELSE, WHILE, FOR. When using pseudocode, CIE expects a high‑level language style – you are not required to use perfect syntax from a specific programming language, but logic must be transparent. For example, a linear search could be written as:
在 Paper 2 中，你可能需要为给定问题设计算法。始终先确定输入、处理和输出（IPO）。开始写伪代码或流程图前先列出简单计划。保持一致的缩进，并用大写写出关键字，如 IF、ELSE、WHILE、FOR。使用伪代码时，CIE 期望一种高级语言的风格——你不需要使用某个特定编程语言的完美语法，但逻辑必须清晰。例如，线性搜索可以这样写：
FOR Index ← 1 TO LENGTH(List)
IF List[Index] = SearchItem THEN
OUTPUT "Found at ", Index
EXIT LOOP
ENDIF
ENDFOR
Always include error handling or a 'not found' message to show thoroughness.
一定要包含错误处理或“未找到”提示，以体现思维的全面性。
6. Mastering Pseudocode and Flowcharts | 掌握伪代码与流程图
u to read or write pseudocode and flowcharts. Flowchart symbols must be drawn correctly: a rectangle for processes, a diamond for decisions, a parallelogram for input/output, and a rounded terminal for start/end. Decision diamonds must have two exit lines labelled 'Yes' and 'No'. In pseudocode, variable assignment should use ← input uses INPUT; output uses OUTPUT or PRINT. Never mix flowchart syntax into pseudocode – racing, use a trace table with columns for each variable and condition; update row by row.
Paper 1 和 Paper 2 都可能要求你阅读或编写伪代码及流程图。流程图形状必须画得正确：矩形表示处理过程，菱形表示判断，平行四边形表示输入/输出，圆角矩形表示开始/结束。判断菱形必须有两条出口线，标注“是”和“否”。在伪代码中，变量赋值统一使用 ← 或 =；用户输入用 INPUT；输出用 OUTPUT 或 PRINT。绝不要把流程图符号混入伪代码——两者要保持分明。做跟踪表时，用表格为每个变量和条件设立列，逐行更新。
7. Programming for Paper 2: Syntax and Logic | Paper 2 编程：语法与逻辑
If your school uses a high‑level language like Python for Paper 2, you must be familiar with its syntax: correct indentation, colons after loops and conditionals, and proper use of functions. However, CIE marks logic rather than memorised syntax. Even if you forget a colon, you may still earn full marks if the algorithm’s logic is clear. More important is to validate inputs, handle data types correctly, and add comments (// or #) to explain your thinking. For instance, converting an integer to a string before concatenation is a common mistake – use STR(Number) or str(). Always test your algorithm mentally with typical, boundary, and erroneous data.
如果你的学校在 Paper 2 中使用像 Python 这样的高级语言，你必须熟悉其语法：正确的缩进、循环和条件后的冒号，以及函数的合理使用。不过，CIE 更看重逻辑而非死记硬背的语法。即使你漏掉一个冒号，只要算法逻辑清晰，仍可能得满分。更重要的是：验证输入、正确处理数据类型，并添加注释（// 或 #）说明思路。例如，在拼接字符串前忘记把整数转为字符串是常见错误——应使用 STR(Number) 或 str()。始终用正常数据、边界数据和错误数据在脑中测试算法。
8. Dealing with Trace Tables | 处理跟踪表
Trace table questions appear frequently, often requiring you to complete columns for variables, conditions, and outputs. Read the algorithm carefully and replicate its structure in the table. Add a new row each time a variable changes value or output occurs. If a loop runs three times, your table should have at least three new rows for each iteration. Use the exact variable names shown in the question. For example, given:
跟踪表题频繁出现，通常要求你填写变量、条件和输出的列。仔细阅读算法，在表格中重建其结构。每当变量值变化或产生输出，就新增一行。如果循环运行三次，你的表格至少要为每次迭代增加三行。使用题目给出的准确变量名。例如，给定：
Total ← 0
FOR Count ← 1 TO 3
Total ← Total + Count
ENDFOR
OUTPUT Total
Your trace table would include columns for Count, Total, and Output, updating step by step until the final output 6 is shown.
你的跟踪表应包含 Count、Total 和 Output 列，逐步更新，直至最终输出 6。
9. Common Mistakes to Avoid | 应避免的常见错误
One of the biggest mistakes is ignoring the number of marks allocated. A 1‑mark 'State' question should not have a paragraph of explanation; conversely, a 4‑mark 'Describe' question needs more than a single bullet point. Another error is writing pseudocode when the question asks for an explanation – read the command word carefully. Many students also lose marks by not showing working in calculation questions, such as file size or sound bit depth sums. In programming tasks, initialising variables with the wrong data type, forgetting to close files, or missing a loop termination condition can cost several marks. Finally, in theory papers, confusing 'ROM' with 'RAM' or 'hub' with 'switch' shows a lack of precision.
最大的错误之一就是忽略题目分值。1 分的“State”题不需要写一段解释；相反，4 分的“Describe”题也不能只写一个要点。另一个错误是题目要求解释却写成了伪代码——务必读懂指令词。许多学生还因计算题（如文件大小或声音位深度计算）没有展示计算步骤而失分。编程任务中，用错误的数据类型初始化变量、忘记关闭文件，或缺失循环终止条件，都会导致丢分。最后，在理论卷中混淆“ROM”与“RAM”，或“集线器”与“交换机”，说明概念不精确。
10. Using Mark Schemes for Revision | 利用评分方案复习
CIE publishes mark schemes for past papers, and these are goldmines of information. After attempting a question, check the mark scheme to see exactly which points are available. You will notice that marks are often given for specific keywords such as 'checksum', 'protocol', 'index', 'embedded system'. Create a glossary of these high‑frequency terms and learn their precise meanings. Also study how the mark scheme allocates partial marks for longer questions – you might earn 3 out of 6 even without a perfect answer if you include key steps. This knowledge encourages you to attempt every question, even when you feel uncertain.
CIE 会公布历年试卷的评分方案，它们是信息的宝库。自己尝试答完一道题后，查看评分方案，清楚地了解哪些要点可以得分。你会发现，分数往往分配给特定的关键词，如“校验和”“协议”“索引”“嵌入式系统”。为这些高频术语制作词汇表，并学习它们的准确含义。还要研究评分方案如何在长题中给出部分分——只要包含了关键步骤，即使答案不完美，也可能拿到 6 分中的 3 分。了解这一点，能鼓励你在所有题目上都尝试作答，哪怕心里没有十足把握。
11. Examiner Reports: Learning from Others’ Errors | 考官报告：从他人错误中学习
Alongside mark schemes, examiner reports provide a summary of how candidates performed on each question. They highlight typical mistakes: for example, 'Many candidates could state the name of a sensor but could not explain how it is used in the given context.' Use these reports to identify which topics are poorly understood across the cohort and then focus your revision on those areas. If an examiner reports that candidates often confuse lossy and lossless compression, create flashcards with precise definitions and a clear example for each. This proactive approach turns others’ errors into your strengths.
除了评分方案，考官报告还总结了考生在每道题上的整体表现，并指出典型错误：例如，“许多考生能说出传感器名称，却无法解释它在给定情境下如何使用。”利用这些报告，找出整体掌握薄弱的知识点，然后把复习重点放在那些地方。如果考官提到考生经常混淆有损压缩和无损压缩，就制作闪卡，分别给出准确定义和清晰例子。这种主动学习的方法，能把别人的错误转化为你的优势。
12. Final Tips Before the Exam | 考前最后提示
In the days before your exam, consolidate your knowledge rather than trying to learn new topics. Practise with timed past papers under exam conditions. Have a clear strategy: for Paper 1, answer all short questions first, then tackle your two chosen long questions; for Paper 2, read the scenario thoroughly, plan algorithms on scrap paper, write pseudocode, and finally test your logic. On exam day, bring a clear ruler for drawing flowcharts and a good pen. Stay calm, read questions twice, and remember that every mark counts. Good luck!
考试前的几天，重在巩固已有知识，不要试图学习新内容。在模拟考试环境下进行限时的历年真题练习。制定清晰策略：Paper 1 先做完所有简答题，再攻选定的两道大题；Paper 2 彻底读透情境，在草稿纸上规划算法，写出伪代码，最后检验逻辑。考试当天，带好清晰画图用的直尺和好用的笔。保持冷静，把题目读两遍，记住每一分都很宝贵。祝你好运！
Published by TutorHao | Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
或截图后用「扫一扫 → 相册」选择本图