📚 Exam Technique and Marking Criteria for Year 11 CIE Computer Science | Year 11 CIE 计算机：答题技巧与评分标准
Mastering the CIE IGCSE Computer Science exam requires more than just knowing the syllabus content. You need to understand how marks are awarded, what examiners look for, and how to present your answers in a way that clearly demonstrates your knowledge under time pressure. This article breaks down the key techniques and marking principles that will help you convert your understanding into high marks.
在 CIE IGCSE 计算机科学考试中取得好成绩，不仅需要掌握课程内容。你还需要了解评分方式、考官关注的重点，以及在时间压力下如何清晰地呈现答案。这篇文章将解析关键的答题技巧和评分原理，帮助你把所学知识转化为高分。
1. Understanding the Exam Structure | 了解考试结构
The CIE IGCSE Computer Science (0478/0984) consists of two papers: Paper 1 (Theory) and Paper 2 (Problem-solving and Programming). Paper 1 is a written exam lasting 1 hour 45 minutes, worth 60% of the total marks. Paper 2 is also 1 hour 45 minutes, worth 40%, and requires you to write answers based on pre-release material as well as on-screen programming tasks.
CIE IGCSE 计算机科学（0478/0984）包含两份试卷：试卷一（理论）和试卷二（问题解决与编程）。试卷一是笔试，时长 1 小时 45 分钟，占总分的 60%。试卷二同样 1 小时 45 分钟，占 40%，要求根据预发材料作答并完成上机编程任务。
Knowing the structure helps you allocate revision time effectively. Paper 1 tests your theoretical knowledge across topics like data representation, hardware, software, networks, and security. Paper 2 focuses on algorithmic thinking, pseudocode, flowcharts, and practical programming skills in a high-level language such as Python, Java, or Visual Basic.
了解结构有助于你有效分配复习时间。试卷一考察数据表示、硬件、软件、网络和安全等理论知识。试卷二侧重于算法思维、伪代码、流程图以及使用 Python、Java 或 Visual Basic 等高级语言的实践编程技能。
Make sure you check your syllabus code and year, as slight variations exist between 0478 and 0984, but the assessment structure and content are identical. Always refer to the latest syllabus document from the CIE website for the most accurate information.
务必核对你的课程代码和年份，因为 0478 和 0984 之间存在细微差异，但评估结构和内容完全相同。请始终以 CIE 官方网站上的最新课程大纲为准，获取最准确的信息。
2. Marking Criteria and Assessment Objectives | 评分标准与评估目标
CIE uses three Assessment Objectives (AOs) to mark your papers: AO1 demonstrates knowledge and understanding of the principles and concepts of computer science. AO2 requires you to apply this knowledge and understanding to computational problems. AO3 asks you to analyse, evaluate, and draw conclusions, making reasoned judgements.
CIE 采用三个评估目标（AO）来评分：AO1 展示对计算机科学原理和概念的知识与理解。AO2 要求你将此知识与理解应用于计算问题。AO3 则要求你进行分析、评估、得出结论并做出合理判断。
In Paper 1, about 60% of the marks are for AO1, 30% for AO2, and 10% for AO3. In Paper 2, the weighting shifts significantly to application and analysis: roughly 20% AO1, 50% AO2, and 30% AO3. This means for Paper 2 you must focus on showing your working, explaining your reasoning, and evaluating your solutions.
在试卷一中，约 60% 的分数为 AO1，30% 为 AO2，10% 为 AO3。在试卷二中，权重显著转向应用与分析：大约 20% AO1，50% AO2，30% AO3。这意味着在试卷二中，你必须着重展示解题过程、解释推理并评估你的解决方案。
Examiners use a mark scheme with explicit points for each question. For longer written responses, marks are often awarded for stating the correct fact, giving a suitable example, or providing a clear link between cause and effect. Simply writing 'more' or 'faster' without context usually gains no credit.
考官使用评分方案，每个问题都有明确的得分点。对于较长的书面回答，分数通常会给予陈述正确的事实、给出适当的例子或提供清晰的因果关系。“更多”或“更快”这类没有上下文的简单表述通常无法得分。
3. Decoding Command Words | 解析命令词
Command words tell you exactly what the examiner wants. 'State' or 'Give' means provide a straightforward fact or name, with no explanation needed. 'Describe' requires you to write a detailed account of characteristics or steps. 'Explain' asks for reasons or causes, often linking ideas together.
命令词准确地告诉你考官想要什么。“State”或“Give”意味着提供一个直接的事实或名称，无需解释。“Describe”要求你详细叙述特征或步骤。“Explain”则要求说明原因或因果关系，通常需要将概念联系起来。
For example, if asked to state one type of storage device, 'SSD' is sufficient. If asked to describe an SSD, you might write 'An SSD uses flash memory to store data, has no moving parts, and is faster than an HDD.' If asked to explain why an SSD is faster, you need to link the lack of mechanical movement to reduced access time.
例如，如果要求 state 一种存储设备，“SSD”就足够了。如果要求 describe SSD，你可以写“SSD 使用闪存存储数据，没有移动部件，比 HDD 更快。”如果要求 explain 为什么 SSD 更快，你需要将没有机械运动与减少访问时间联系起来。
Other common command words include 'Identify' (point out from a given set of information), 'Compare' (give similarities and/or differences), 'Justify' (give reasons for a choice), and 'Evaluate' (discuss strengths and weaknesses and form a conclusion). Practice recognising these in past papers so you answer precisely.
其他常见的命令词包括“Identify”（从给定信息中指出）、“Compare”（给出相似点和/或差异）、“Justify”（为某个选择给出理由）和“Evaluate”（讨论优缺点并得出结论）。在历年真题中练习识别这些词，以确保答题精准。
4. Reading Questions Precisely | 精准阅读题目
Many marks are lost simply because students misread the question. Look for qualifiers like 'two reasons', 'one example', or 'apart from storage'. If the question says 'tick two boxes' do not tick three. If it asks for 'one advantage and one disadvantage' do not write three advantages and forget the disadvantage.
很多失分仅仅是因为学生误读了问题。注意像“两个原因”、“一个例子”或“除了存储”这样的限定词。如果题目说“勾选两个方框”，不要勾三个。如果要求“一个优点和一个缺点”，不要写三个优点而忘记缺点。
Underline or circle key terms and numbers in the question. This helps you focus on exactly what is required. When a question includes a scenario, always relate your answer back to that scenario. Generic answers that ignore the context often score lower marks.
在问题中用下划线或圆圈标出关键术语和数字。这有助于你准确聚焦要求。当问题包含情景时，始终将你的答案与情景联系起来。忽略上下文的通用答案通常得分较低。
Pay close attention to negative phrasing such as 'identify one method that is NOT suitable'. Students frequently write the suitable method instead. Take a moment to mentally rephrase the question in your own words before you start writing.
密切注意否定表述，例如“指出一种不合适的方案”。学生经常写成合适的方案。在动笔之前，花点时间用自己的话在心里复述问题。
5. Data Representation and Calculation Questions | 数据表示与计算题
When converting between binary, denary, and hexadecimal, always show your working. Even if your final answer is wrong, you can earn method marks if the examiner can see a correct intermediate step. Use clear layout and label your columns with place values.
在二进制、十进制和十六进制之间转换时，一定要展示你的计算过程。即使最终答案错误，如果考官能看到正确的中间步骤，你也可以获得方法分。使用清晰的布局，并用位值标注你的列。
For binary addition or shifting, write the carries above the bits. For two's complement, explicitly state how you invert bits and add one. In logic gate questions, draw a truth table with all input combinations and show your intermediate columns. A systematic approach reduces careless errors.
对于二进制加法或移位，将进位写在比特上方。对于二进制补码，明确说明你是如何反转位并加一的。在逻辑门问题中，画出包含所有输入组合的真值表，并展示你的中间列。系统的方法可以减少粗心错误。
When calculating file sizes, always write out the formula or the proportional relationship. For example, 'sample rate x bit depth x duration in seconds' or 'number of pixels x colour depth'. Keep track of units (bits, bytes, kilobytes) and show the conversion steps clearly.
在计算文件大小时，一定要写出公式或比例关系。例如“采样率 × 位深度 × 以秒为单位的时长”或“像素数 × 色彩深度”。注意单位（比特、字节、千字节）并清晰展示转换步骤。
6. Algorithm Design and Trace Tables | 算法设计与跟踪表
Algorithm questions often require you to complete a trace table or identify errors. When completing a trace table, follow the pseudocode line by line, updating variables exactly as the code dictates. Do not make assumptions or skip steps. Use a new row for each change in any variable value.
算法题通常要求你完成跟踪表或找出错误。完成跟踪表时，逐行遵循伪代码，严格按照代码指示更新变量。不要假设或跳过步骤。每当任何变量值发生变化时，就使用新的一行。
If you are asked to identify errors in an algorithm, think about typical issues: missing initialisation, infinite loops, incorrect loop conditions, off-by-one errors, or logic that does not match the specification. State the error and suggest a correction explicitly.
如果要求你找出算法中的错误，考虑典型问题：缺少初始化、无限循环、错误的循环条件、偏移一位错误或与规格不符的逻辑。明确陈述错误并提出修改意见。
For writing your own algorithms, use the exact pseudocode style described in the syllabus. The CIE pseudocode guide provides keywords like INPUT, OUTPUT, IF...THEN...ELSE...ENDIF, FOR...TO...NEXT, WHILE...DO...ENDWHILE. Stick closely to this syntax to avoid ambiguity.
在编写你自己的算法时，使用课程大纲中描述的伪代码风格。CIE 伪代码指南提供了 INPUT、OUTPUT、IF...THEN...ELSE...ENDIF、FOR...TO...NEXT、WHILE...DO...ENDWHILE 等关键字。严格遵循此语法以避免歧义。
7. Pseudocode and Flowchart Best Practices | 伪代码与流程图最佳实践
Flowcharts must use standard symbols: ovals for start/stop, rectangles for processes, diamonds for decisions, and parallelograms for input/output. Make sure arrows show the direction of flow clearly. Any missing arrow or incorrect symbol can lose marks.
流程图必须使用标准符号：椭圆形表示开始/结束，矩形表示处理，菱形表示判断，平行四边形表示输入/输出。确保箭头清晰标示流向。任何缺失箭头或错误的符号都可能导致失分。
When a question gives you a choice between pseudocode and a flowchart, pick the one you are most confident with. If you have space, a rough sketch before drawing the final flowchart helps you avoid messy corrections. Use a ruler and pencil so your diagram is neat and readable.
当问题让你在伪代码和流程图之间选择时，选择你最有信心的一种。如果有空间，在画最终流程图之前先画一个草图，可以避免凌乱的修改。使用尺子和铅笔，让你的图表整洁清晰。
In pseudocode, meaningful variable names like 'TotalMarks' or 'StudentName' are preferred over single letters, unless the problem specifies brevity. Indent code blocks under IF statements and loops to show structure. Consistent indentation often earns marks for clarity even if the logic is slightly flawed.
在伪代码中，有意义的变量名如“TotalMarks”或“StudentName”比单个字母更受青睐，除非题目要求简洁。在 IF 语句和循环下缩进代码块以展示结构。即使逻辑略有缺陷，一致的缩进往往也能因清晰而得分。
8. Programming Question Techniques | 编程题技巧
In Paper 2 programming tasks, read the pre-release material thoroughly before the exam. You will not have time to understand it completely on the day. Annotate the pseudocode and try to predict what types of questions could be asked, such as validation, searching, sorting, or file handling.
在试卷二的编程任务中，考前要彻底阅读预发材料。考试当天你没有时间完全弄懂它。注释伪代码，并尝试预测可能会出哪些类型的问题，比如验证、搜索、排序或文件处理。
During the exam, build your solution step by step. Start with the simplest functionality and test it mentally before moving on. Use meaningful comments to explain your code. Examiners can award marks for comments that demonstrate understanding even if the code does not run perfectly.
考试期间，逐步构建你的解决方案。从最简单的功能开始，在心里测试后再继续。使用有意义的注释来解释你的代码。即使代码不能完美运行，考官也可以为展示理解的注释给分。
When a question asks you to write a function or procedure, ensure you include the correct parameters and return types if applicable. A common mistake is to write a whole program when only a module is required. Answer only what is asked; extra code that is wrong can sometimes invalidate previously correct sections.
当问题要求你写一个函数或过程时，确保包含正确的参数和返回类型（如果适用）。常见的错误是当只需要一个模块时却写了整个程序。仅回答所要求的内容；多余的代码如果错误，有时会使之前正确的部分失效。
9. Theory Question Strategies | 理论题答题策略
For long-answer theory questions, structure your response logically. Start with a clear topic sentence, then add supporting detail, an example, and finally a link back to the question if possible. For example, when explaining how a firewall works, state its purpose, describe packet filtering, and give a simple example of a rule.
对于长篇理论题，逻辑清晰地组织你的回答。以明确的主题句开始，然后添加支持细节、一个例子，最后如果可能，再与问题联系起来。例如，在解释防火墙如何工作时，陈述其目的，描述数据包过滤，并给出一个简单的规则示例。
Use technical vocabulary precisely. Terms like 'encryption', 'protocol', 'topology', and 'abstraction' have very specific meanings. The examiner is looking for evidence that you understand these terms, not just that you can repeat a dictionary definition. Embed them in a meaningful explanation.
精确使用技术词汇。像“加密”、“协议”、“拓扑”和“抽象”这样的术语有非常具体的含义。考官在寻找你理解这些术语的证据，而不仅仅是你能够重复字典定义。将它们嵌入有意义的解释中。
When comparing two technologies, use a table if the question allows it. A table with clear headings like 'Feature', 'Technology A', 'Technology B' makes it easy for examiners to tick the marks. If you write in prose, make sure each comparative point is explicit: 'A is faster, whereas B uses less power.'
在比较两种技术时，如果题目允许，使用表格。带有清晰标题的表格，如“特性”、“技术 A”、“技术 B”，便于考官标记分数。如果你用文字表述，确保每个比较点都明确：“A 更快，而 B 耗电更少。”
10. Time Management in the Exam | 考试时间管理
Both papers are 1 hour 45 minutes long. Paper 1 has 75 marks and Paper 2 has 50 marks. A rough guide is to spend about 1.4 minutes per mark on Paper 1 and 2.1 minutes per mark on Paper 2. However, programming questions may take longer per mark, so adjust accordingly.
两份试卷均长 1 小时 45 分钟。试卷一有 75 分，试卷二有 50 分。大致指导是试卷一每分约花费 1.4 分钟，试卷二每分约 2.1 分钟。然而，编程题每分可能花费更长时间，因此要相应调整。
Start with the questions you find easiest. This builds confidence and secures marks quickly. Circle any difficult question numbers and come back to them later. Never spend 15 minutes wrestling with a 3-mark question while a 6-mark question remains unseen.
从你觉得最容易的问题开始。这样可以建立信心并快速获得分数。把难题的题号圈起来，稍后再回来看。绝不要在一个 3 分的问题上纠缠 15 分钟，而一个 6 分的问题还没看到。
Leave about 10-15 minutes at the end to check your answers. Focus first on the questions carrying high marks, and verify calculations, keywords, and whether you followed the command word. A quick final scan can catch silly spelling errors or missing units.
最后留出 10 至 15 分钟检查答案。首先关注分值高的问题，检查计算、关键词以及你是否遵循了命令词。快速的最后扫描可以发现拼写错误或遗漏的单位。
11. Common Pitfalls and How to Avoid Them | 常见丢分点及避免方法
One major pitfall is not providing enough depth. When a question says 'Describe three measures to protect data', do not just name them. Describe means what the measure is, how it works, and maybe why it is effective. A single-line answer rarely gets full marks.
一个主要的丢分点是深度不够。当问题说“描述三种保护数据的措施”时，不要只是列出名称。描述意味着这项措施是什么、它是如何工作的，也许还有为什么它有效。单行回答很少能获得满分。
Another common error is misreading the mark allocation. A question with 6 marks usually expects at least three well-developed points, or six simple points, or a combination. Look at the number of marks as a clue to how much detail the examiner wants.
另一个常见错误是误读分数分配。一个 6 分的问题通常期望至少三个发展充分的要点，或六个简单要点，或两者的组合。将分数数量视为考官期望多少细节的线索。
Students often lose marks by writing answers that are too vague. Instead of 'the computer processes data', say 'the CPU fetches instructions from RAM, decodes them, and executes the required operations using the ALU'. Being specific demonstrates knowledge and earns marks.
学生经常因答案过于模糊而失分。与其写“计算机处理数据”，不如写“CPU 从 RAM 中取指令，解码，并使用 ALU 执行所需的操作”。具体化能展示知识并获得分数。
Forgetting to link back to the scenario is another frequent mistake. If the question is about a robotic arm in a factory, your answer must relate to that context. Mention sensors, actuators, or safety implications specific to a factory; do not give a generic robotics answer.
忘记联系情景是另一个常见错误。如果问题是关于工厂中的机械臂，你的答案必须与那个语境相关。提及特定于工厂的传感器、执行器或安全影响；不要给出通用的机器人学答案。
12. Final Review and Exam Day Mindset | 最终检查与考试心态
In the final minutes, verify that all parts of the question have been attempted. Look at the question numbers and check for any blanks. If you have time left for a long question, add another point or elaborate on an existing one, but do not change your answer completely unless you are absolutely certain it is wrong.
在最后几分钟，确认问题的所有部分都已作答。查看题号，检查是否有空白。如果对于一个长问题还有剩余时间，再添加一点或详细阐述已有的要点，但不要完全改变你的答案，除非你完全确定它是错的。
Stay calm and focused. Computer Science exams can seem technical and demanding, but careful reading and methodical answering will secure a solid result. Trust your preparation, use the reading time wisely, and remember that the examiners want to see you succeed.
保持冷静和专注。计算机科学考试可能看起来技术性强且要求高，但仔细阅读和有条理的回答将确保一个扎实的成绩。相信你的准备，明智地使用阅读时间，并记住考官希望看到你成功。
After the exam, do not dwell on perceived mistakes. You may have interpreted a question differently than a friend, but there is often more than one way to score marks. Focus on what you did well and use the experience to refine your technique for future assessments.
考试结束后，不要纠结于想象中的错误。你可能对某个问题的解释与朋友不同，但得分的途径往往不止一种。专注于你做得好的地方，并利用这次经验为未来的评估完善你的技巧。
Published by TutorHao | 计算机 Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
或截图后用「扫一扫 → 相册」选择本图