📚 AS Eduqas Computer Science: Exam Technique and Marking Criteria | AS Eduqas 计算机：答题技巧与评分标准
Mastering the content is only half the battle in AS Eduqas Computer Science. To turn your knowledge into high marks, you must understand exactly how examiners award points and what they expect in your answers. This article breaks down the crucial exam techniques and marking criteria for Components 1 and 2, helping you write answers that hit every mark point.
掌握知识内容只是 AS Eduqas 计算机考试成功的一半。要把知识转化为高分，你必须准确理解考官如何给分以及他们期望看到什么样的答案。本文详细拆解了试卷一和试卷二中关键的答题技巧与评分标准，帮助你写出每一分都到位的答案。
1. Understanding Command Words | 理解指令词
Every question contains a command word that tells you the style and depth of answer required. Misreading this word is the most common reason students lose marks, as a 'describe' answer cannot score full marks if the question demands 'explain'. Learn the exact meaning of each command word used by Eduqas.
每一道题都包含一个指令词，它告诉你答案的风格和深度。误读指令词是学生们失分最常见的原因——如果题目要求“解释”，而你只写了“描述”，就无法得到满分。务必准确掌握 Eduqas 使用的每条指令词的含义。
- State / Give – Provide a brief definition, fact, or single piece of information. No explanation or development is needed.
陈述/给出：提供简短的定义、事实或单项信息，不需要解释或展开。 - Describe – Give a detailed account of characteristics, steps, components, or how something works. Focus on 'what' and 'how', not 'why'.
描述：详细说明特性、步骤、组成部分或运作方式。重点在于“是什么”和“怎样做”，不是“为什么”。 - Explain – Give reasons or causes, often using linking words like 'because', 'therefore', or 'this means that'. You must show understanding of why something happens or why it is done that way.
解释：给出理由或原因，常使用“因为”、“因此”、“这意味着”等连接词。必须展示对事物发生原因或为何如此设计的理解。 - Compare – Identify similarities and differences. You must cover both aspects. Use comparative phrases such as 'whereas', 'on the other hand', or 'similarly'. A table or side-by-side points can help.
比较：找出相同点和不同点，两方面都要写到。使用“然而”、“另一方面”、“类似地”等比较性短语。用表格或并列要点会有帮助。 - Discuss / Evaluate – Present different viewpoints, weigh up advantages and disadvantages, and reach a justified conclusion. Do not just list; you need to make a judgement based on evidence.
讨论/评价：呈现不同观点，权衡优缺点，并得出有理有据的结论。不要只罗列，需要基于证据做出判断。 - State and explain – This two-part instruction requires you to first give a clear point and then explain why or how that point is relevant. Always separate the two clearly in your answer.
陈述并解释：这个两部分的指令要求你先给出明确的观点，然后解释该观点为何或如何具有关联性。在答案中务必把两部分清楚分开。 - Suggest – Put forward a plausible solution or reason based on your knowledge, even if the exact scenario was not covered in class. Use logical reasoning.
建议：根据你的知识提出合理的解决方案或理由，即使课堂未涉及该具体情景。使用逻辑推理。 - Identify / Name – Simply recognise and write down the required item or concept. No further comment is expected.
识别/命名：只需认出并写下所要求的事项或概念，不需要进一步评论。
2. Structuring Your Answers | 构建答案结构
A well-structured answer makes it easy for the examiner to find mark points. Scattered or rushed answers often hide correct knowledge. Always mirror the organisation implied by the question, and use clear separators like bullet points or numbered lists when suitable.
结构清晰的答案能让考官轻松找到给分点。散乱或仓促的答案常常埋没了正确的知识。始终遵循问题暗示的组织方式，并在合适时使用项目符号或编号列表等清晰的分隔手段。
For 'explain' questions, adopt a simple Point – Evidence/Example – Explanation chain. State your point, back it with a concrete example or technical detail, then explain the consequence or reason. For instance: 'Increasing the clock speed improves performance (Point). A 3.5 GHz processor can execute more fetch-decode-execute cycles per second than a 2.0 GHz processor (Evidence). This means more instructions are processed in the same time, reducing program execution time (Explanation).'
对于“解释”类问题，采用简单的观点—证据/例子—解释链条。陈述观点，用具体例子或技术细节支持，然后解释结果或原因。例如：“提高时钟频率能改善性能（观点）。3.5 GHz 处理器每秒执行的取指-译码-执行周期数比 2.0 GHz 处理器更多（证据）。这意味着相同时问内可处理更多指令，从而缩短程序执行时间（解释）。”
For programming or algorithm questions, use indentation consistently. Even on paper, clear indentation signals logical blocks to the examiner. Write variable names meaningfully (e.g., 'total' instead of 'x'). If you need to correct a mistake, cross it out cleanly and write the correct code nearby; do not create a messy spider web of arrows.
对于编程或算法题，要始终如一地使用缩进。即使在纸上作答，清晰的缩进也能向考官明确逻辑块。变量名要有意义（例如用“total”而不是“x”）。如果需要改正错误，干净地划掉，并在旁边写出正确代码；不要画出杂乱无章的箭头网。
3. Algorithms and Pseudocode | 算法与伪代码
Eduqas does not enforce a single pseudocode standard. You may use structured English, flowcharts, or a generic pseudocode style as long as it is unambiguous and clearly shows sequence, selection, and iteration. The marking focus is on logical correctness, not syntactic perfection.
Eduqas 不强制使用单一的伪代码标准。你可以使用结构化英语、流程图或通用伪代码风格，只要表述清晰无歧义，且明确展示了顺序、选择和迭代即可。评分的重点在于逻辑正确性，而非句法完美。
Best practices for any algorithm answer:
- Clearly show the start and end of the algorithm.
清晰标示算法的开始与结束。 - Use consistent indentation for loops and conditions.
循环和条件结构使用一致的缩进。 - Initialise variables explicitly.
显式初始化变量。 - Use meaningful identifiers.
使用有意义的标识符。 - Comment key steps if it helps clarity.
如果有助于清晰表达，可为关键步骤加上注释。
Example pseudocode for a factorial calculation:
INPUT number
factorial ← 1
FOR i ← 1 TO number
factorial ← factorial × i
ENDFOR
OUTPUT factorial
中文示例：
输入 number
factorial ← 1
FOR i ← 1 TO number
factorial ← factorial × i
ENDFOR
输出 factorial
Notice that even without a strict syntax, the logic is transparent. In trace table questions, remember to update every variable step by step and show the state after each iteration clearly.
注意，即使没有严格的语法，逻辑也是透明的。在跟踪表类题目中，务必逐步更新每一个变量，并清晰显示每次迭代后的状态。
4. Programming Questions | 编程题
Programming questions in the written paper typically ask you to complete, correct, or write short code snippets. Mark schemes award points for:
- Correct declaration and initialisation of variables.
正确的变量声明和初始化。 - Correct use of selection (IF) and iteration (FOR/WHILE) constructs.
正确使用选择（IF）和循环（FOR/WHILE）结构。 - Appropriate data types.
合适的数据类型。 - Logical steps that solve the problem.
解决问题的逻辑步骤。 - Correct syntax for the assumed language or pseudocode.
对假定语言或伪代码的正确语法。
Even if you make a small syntax error, a logically sound answer can still receive the majority of the logic marks. Therefore, never leave a coding question blank: write down your plan in comments first, then flesh out the code.
即便出现小的语法错误，逻辑正确的答案仍然能获得大部分逻辑分。因此，编程题绝对不能留空：先用注释写下计划，然后再细化代码。
Common pitfalls include:
- Confusing assignment (=) with comparison (== or = depending on context).
混淆赋值（=）与比较（视上下文为 == 或 =）。 - Forgetting to handle edge cases (e.g., empty input, zero).
忘记处理边缘情况（如空输入、零）。 - Off-by-one errors in loop boundaries.
循环边界差一错误（off-by-one）。 - Using vague variable names that obscure the logic.
变量名模糊，逻辑难以辨认。
5. Data Representation | 数据表示
Questions on binary, denary, hexadecimal, binary addition, two's complement, and text/sound/image representation regularly appear. For any conversion or calculation, you must show your working. A correct final answer without working may only receive part of the marks if the markscheme specifies method marks.
有关二进制、十进制、十六进制、二进制加法、二进制补码以及文本/声音/图像表示的问题经常出现。任何转换或计算都必须展示过程。如果评分方案指定了方法分，没有过程仅有正确最终答案可能只得部分分数。
₂ = 1×2³ + 0×2² + 1×2¹ + 1×2⁰ = 8 + 0 + 2 + 1 = 11. Use superscripts: 2³, 2², etc. For two' ts: -1×2⁷ + 1×2⁶ + 1×2⁵ + 1×2⁴ + 1×2³ + 0×2² + 1×2¹ + 0×2⁰ = -128 + 64+32+16+8+0+2+0 = -6.
二进制转十进制：按 2 的幂展开。例如 1011₂ = 1×2³ + 0×2² + 1×2¹ + 1×2⁰ = 8 + 0 + 2 + 1 = 11。使用上标：2³、2² 等。对于二进制补码，牢记最高有效位是负数。8 位模式 11111010₂ 表示：-1×2⁷ + 1×2⁶ + 1×2⁵ + 1×2⁴ + 1×2³ + 0×2² + 1×2¹ + 0×2⁰ = -128 + 64+32+16+8+0+2+0 = -6。
nicode has a larger character set and uses more bits per character, enabling global scripts. Image file size = resolution × colour depth; sound file size = sample rate × sample resolution × duration. Always include units.
二进制加法时，清晰显示进位。十六进制按四位一组分组。ASCII 和 Unicode 题目需记住 Unicode 字符集更大，每字符使用更多位，从而支持全球文字。图像文件大小 = 分辨率 × 颜色深度；声音文件大小 = 采样率 × 采样分辨率 × 时长。始终标明单位。
6. Systems Architecture and Hardware | 系统架构与硬件
Questions on the CPU, Von Neumann architecture, fetch-decode-execute cycle, registers (MAR, MDR, PC, CIR, ACC), cache, and clock speed require precise terminology. Examiners expect you to use the full register names and accurately describe data flow between components.
关于 CPU、冯·诺依曼架构、取指-译码-执行周期、寄存器（MAR、MDR、PC、CIR、ACC）、高速缓存和时钟频率的题目需要精确术语。考官期望你使用完整的寄存器名称，并准确描述组件间的数据流向。
When explaining the effect of increasing clock speed, state that more fetch-decode-execute cycles are completed per second, which increases the number of instructions processed. However, also mention that it may lead to overheating and cannot overcome bottlenecks caused by slow memory (the Von Neumann bottleneck). When discussing cache, say that it is faster than RAM and stores frequently accessed instructions/data, reducing the need to fetch from slower main memory.
解释提高时钟频率的影响时，说明每秒完成的取指-译码-执行周期数更多，从而增加处理的指令数量。但也要指出这可能导致过热，且无法克服由慢速内存引起的瓶颈（冯·诺依曼瓶颈）。讨论高速缓存时，说明它比 RAM 更快，存储频繁使用的指令/数据，减少从较慢主存抓取的需要。
Compare Von Neumann and Harvard architectures: in Harvard, instructions and data use separate buses/memories, allowing simultaneous access and improving performance in certain embedded systems.
Published by TutorHao | AS Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
或截图后用「扫一扫 → 相册」选择本图