📚 Year 10 AQA Computer Science: High-Frequency Topics and Common Misconceptions | Year 10 AQA 计算机：高频考点与易错题分析
Mastering Year 10 AQA Computer Science requires not only remembering facts but also avoiding subtle traps that many students fall into. This article walks through the most frequently assessed topics and highlights the common errors examiners see year after year, helping you sharpen your understanding and boost your marks.
掌握 Year 10 AQA 计算机科学不仅需要记忆知识点，还需要避开许多学生容易落入的陷阱。本文梳理了考试中最高频的主题，并重点分析了阅卷官年年都会看到的常见错误，帮助你加深理解、提高分数。
1. Binary to Hexadecimal Conversions – Misreading and Misalignment | 二进制与十六进制转换：误读与位对齐
Converting between binary and hexadecimal is a guaranteed exam technique. Students often slip up by not grouping binary digits into nibbles (groups of four) correctly from the right, or by confusing the hex symbols A–F with decimal values.
二进制与十六进制之间的转换是必考项。学生常犯的错误是没有从右边开始正确地将二进制位分组为半字节（每四位一组），或者混淆十六进制符号 A–F 与十进制数值。
Always pad the binary number on the left with zeros so the total number of bits is a multiple of four before grouping. For instance, 1011012 becomes 0010 11012, giving hex 2D, not 2D but careful with the left-most nibble. Another typical mistake is writing 2D as 213 because they treat D as 13 and concatenate digits.
始终在二进制数的左侧补零，使总位数成为四的倍数，然后再分组。例如 1011012 应变为 0010 11012，得到十六进制 2D。另一个典型错误是将 2D 写成 213，因为他们把 D 当作 13 并直接拼接数字。
When converting hex to binary, make sure each hex digit expands to exactly four bits. Writing A as 1010 but forgetting to write leading zeros for small digits like 3 as 0011 can ruin the whole binary value.
从十六进制转二进制时，确保每个十六进制位恰好展成四位。把 A 写成 1010 没问题，但如果忘记给较小的数字如 3 补前导零写成 0011，就会毁掉整个二进制值。
2. Binary Arithmetic and Overflow Detection | 二进制算术与溢出检测
Binary addition problems appear frequently. The classic error is forgetting to carry into the next column or misapplying the overflow rule. Overflow occurs when the result of an addition exceeds the range that can be represented with the given number of bits.
二进制加法题频繁出现。经典错误是忘记进位到下一列，或者错误应用溢出规则。当加法结果超出给定位数能表示的范围时，就会发生溢出。
For two’s complement representation (AQA expects understanding of 8-bit signed integers), the overflow flag is set if the carry into the most significant bit (MSB) is different from the carry out. Many students only check the final carry out, which is insufficient.
对于二进制补码表示（AQA 要求理解 8 位有符号整数），当最高有效位（MSB）的进位输入与进位输出不同时，溢出标志置位。许多学生只检查最终进位输出，这是不够的。
Practice tracing: 011111112 (127) + 000000012 (1) gives 100000002. The carry into MSB is 1, carry out is 0, so overflow occurs and the result is incorrect as a signed integer (-128). Misidentifying this as a valid positive number is a common pitfall.
练习追踪：011111112（127）+ 000000012（1）得到 100000002。MSB 进位输入为 1，进位输出为 0，因此发生溢出，结果作为有符号整数是错误的（-128）。将其误认为有效正数是常见陷阱。
3. Character Encoding – ASCII vs Unicode Conflicts | 字符编码：ASCII 与 Unicode 的混淆
Students often mix up the bit length and purpose of ASCII and Unicode. The exam may ask why Unicode is needed, or to compare storage implications.
学生经常将 ASCII 和 Unicode 的位长度及用途混为一谈。考试可能问到为什么需要 Unicode，或者比较存储影响。
Standard ASCII uses 7 bits, extended ASCII uses 8 bits, while Unicode typically uses 16 or 32 bits per character. A common mistake is saying ASCII can represent 256 characters – that’s extended ASCII; standard ASCII can represent only 128. Another error is assuming Unicode always uses 16 bits; UTF-8, for example, uses variable length, but AQA focuses on the idea that Unicode provides a unique code point for every character globally.
标准 ASCII 使用 7 位，扩展 ASCII 使用 8 位，而 Unicode 通常每个字符使用 16 位或 32 位。常见错误是说 ASCII 能表示 256 个字符——那是扩展 ASCII；标准 ASCII 只能表示 128 个。另一个错误是假设 Unicode 总是使用 16 位；例如 UTF-8 使用变长，但 AQA 关注的是 Unicode 为全球每个字符提供唯一的码点这一思想。
When comparing file sizes, clearly state: storing a text in Unicode may double or quadruple the size compared to ASCII, but Unicode avoids character corruption across languages.
在比较文件大小时要明确说明：用 Unicode 存储文本，大小可能是 ASCII 的两倍或四倍，但 Unicode 避免了跨语言的字符损坏。
4. Image & Sound Representation – Calculations Gone Wrong | 图像与声音表示：计算走偏
n bits). Common slip: using colour depth in bytes directly or forgetting to convert bits to bytes when asked for file size in bytes or kilobytes.
位图图像大小和声音文件大小的计算是高频考点。图像文件大小公式：分辨率宽度 × 高度 × 颜色深度（以位为单位）。常见失误：直接用字节数作为颜色深度，或者在要求以字节或千字节为单位时忘记将位转换为字节。
ts often omit the number of channels for stereo sound, or confuse sample rate with bit rate.
声音文件大小 = 采样频率 × 采样分辨率（位）× 时长（秒）× 声道数。学生经常忽略立体声的声道数，或者混淆采样频率与比特率。
Metadata (headers) might need to be added in some exam questions, but always check the question wording. A very frequent error is dividing by 1000 instead of 1024 when converting bytes to kilobytes, or using 1000 for kibi (KiB) but AQA generally uses powers of 2 (1024) for data storage calculations unless told otherwise.
某些考题可能需要加上元数据（文件头），但务必审题。非常常见的错误是在字节转换千字节时除以 1000 而不是 1024，或者在考试一般使用 2 的幂（1024）时用了 1000（除非题目另有说明）。
5. Lossy vs Lossless Compression – Confusing When to Use Which | 有损与无损压缩：混淆适用场景
Students can recite definitions but often fail to select the correct compression type for a given scenario, e.g., a text document or a high-quality photograph for a website.
学生能背诵定义，但往往在给定场景（如文本文档或网站上的高质量照片）中选错压缩类型。
Lossless compression preserves all data and is essential for text, code, and executables. Lossy compression removes some data permanently and is suitable for images (JPEG), audio (MP3), and video where perceptual quality can be reduced without noticeable loss. A common misconception is that lossy compression simply runs a more aggressive algorithm; the key is that the original data cannot be recovered.
无损压缩保留全部数据，对文本、代码和可执行文件至关重要。有损压缩会永久移除一些数据，适用于图像（JPEG）、音频（MP3）和视频，这些场景下可以降低感知质量而不产生明显损失。常见误解是有损压缩只是采用了更激进的算法；关键点在于原始数据无法复原。
When explaining run-length encoding (RLE) for images, ensure you can demonstrate lossless compression of repeating colours. Examiners often set tasks like “Compress the following stream using RLE” – watch out for large runs that require multi-byte encoding; stick to the format given in the question.
在为图像解释游程编码（RLE）时，确保能演示对重复颜色的无损压缩。考官常出题如“用 RLE 压缩以下数据流”，注意处理长游程可能需要多字节编码；严格遵循题目给定的格式。
6. Pseudocode Pitfalls – Assignment vs Comparison, and Loop Boundaries | 伪代码易错点：赋值与比较、循环边界
nd tracing pseudocode is a core skill. In AQA exam reference language, assignment uses the '←' symbol, and comparison uses '='. A very common mistake is using '=' for both, making logic ambiguous and losing marks.
编写和追踪伪代码是核心技能。在 AQA 考试参考语言中，赋值使用 '←' 符号，比较使用 '='。非常常见的错误是两者都用 '='，使逻辑模糊并丢分。
When tracing loops, count the iterations precisely. For a FOR i ← 1 TO n loop, the loop body executes exactly n times. But for a WHILE condition, the loop might exit without executing if the condition is initially false; forgetting this can cause trace table errors.
在追踪循环时，精确计算迭代次数。FOR i ← 1 TO n 循环体恰好执行 n 次。但对于 WHILE 条件，如果初始条件为假，循环可能根本不执行；忘记这点会导致跟踪表错误。
Array indexing starts at 0 in many implementations, but AQA pseudo-language allows the specification to be given; students should follow the convention in the question. Going out of bounds by one index is a frequent error in trace tables. Also, structure diagrams and flowcharts must match the pseudo-code – ensure decision diamonds have a clear yes/no path.
数组索引在许多实现中从 0 开始，但 AQA 伪语言允许题目指定；学生应遵循题目中的约定。在跟踪表中越界一个索引是常见错误。此外，结构图和流程图必须与伪代码匹配——确保判断菱形有明确的是/否路径。
7. Control Structures – Misusing Selection and Nested Conditions | 控制结构：滥用选择与嵌套条件
IF-ELSE-ENDIF and CASE (switch) statements are straightforward, but students often forget that an ELSE branch is optional and may incorrectly assume an IF must always have an ELSE. Another error is nesting IFs without proper indentation, leading to dangling ELSE problems – always match the innermost unpaired IF.
IF-ELSE-ENDIF 和 CASE（开关）语句很简单，但学生经常忘记 ELSE 分支是可选的，并可能错误地假设 IF 必须总有 ELSE。另一个错误是嵌套 IF 时没有正确缩进，导致悬空 ELSE 问题——始终与最内层未配对的 IF 匹配。
In iteration, repeat-until loops execute at least once, unlike while loops. Confusing the two in algorithmic thinking can produce different outputs. Exam questions may ask you to rewrite a while loop as a repeat-until and vice versa – always adjust the condition logic carefully.
在迭代中，repeat-until 循环至少执行一次，与 while 循环不同。在算法思维中混淆两者会产生不同的输出。考题可能要求你将 while 循环改写为 repeat-until，反之亦然——务必仔细调整条件逻辑。
Syntax errors in pseudocode, such as missing ENDIF or ENDWHILE, are heavily penalised. Practise writing structured, well-indented code even in rough work.
伪代码中的语法错误，如缺失 ENDIF 或 ENDWHILE，会被严重扣分。即使在草稿中，也要练习编写结构良好、缩进得当的代码。
8. CPU Architecture – Clock Speed, Cores, Cache and Their Limits | CPU 体系结构：时钟速度、核心数、缓存及其限制
The fetch-decode-execute cycle, von Neumann architecture, and factors affecting CPU performance are guaranteed marks, but misconceptions abound. Many students think doubling the clock speed doubles program execution time – actually it reduces the time, but not always linearly because of other bottlenecks.
取指-解码-执行周期、冯·诺依曼体系结构以及影响 CPU 性能的因素是必考点，但误解也很多。许多学生认为将时钟速度翻倍会使程序执行时间翻倍——实际上它减少了时间，但由于其他瓶颈，并不总是线性变化。
Multiple cores allow true parallel processing, but if software is not written to take advantage of multiple cores, performance may not improve. Cache memory is extremely fast, small-capacity memory located inside the CPU; its size and speed greatly affect performance by reducing the need to fetch data from slower RAM. A typical error is confusing cache with RAM or ROM.
多核允许真正的并行处理，但如果软件未编写为利用多核，性能可能得不到提升。缓存是位于 CPU 内部的速度极快、容量很小的存储器；其大小和速度通过减少从较慢 RAM 取数据的需要而极大地影响性能。典型错误是将缓存与 RAM 或 ROM 混淆。
When comparing embedded systems with general-purpose systems, emphasise that embedded systems are designed for a specific task, often have low power consumption, limited resources, and may use ROM for firmware. Students sometimes wrongly claim embedded systems have an operating system with a full GUI like a desktop.
在比较嵌入式系统与通用系统时，要强调嵌入式系统是为特定任务设计的，通常功耗低、资源有限，并可能用 ROM 存储固件。学生有时错误地声称嵌入式系统配有像桌面系统一样的全图形界面操作系统。
9. Networks – Topologies, Protocols, and the Role of Hardware | 网络：拓扑结构、协议与硬件角色
Networking questions often test the ability to draw and label star and bus topologies, describe their advantages and disadvantages, and identify the correct protocol for a given application. Confusing TCP with IP is a common error: IP handles routing and addressing, TCP ensures reliable, ordered delivery. HTTP/HTTPS is for web pages, FTP for file transfer, SMTP/IMAP for email.
网络题常测试绘制并标注星形和总线拓扑结构的能力，描述其优缺点，以及为给定应用确定正确的协议。混淆 TCP 和 IP 是常见错误：IP 负责路由和寻址，TCP 确保可靠、有序的传输。HTTP/HTTPS 用于网页，FTP 用于文件传输，SMTP/IMAP 用于电子邮件。
When explaining how data travels across a network, students often forget the encapsulation process. Mention that data is split into packets, each with a header containing source and destination IP addresses and sequence numbers. Routers use IP addresses to forward packets along the best path, not switches which use MAC addresses within a LAN.
在解释数据如何在网络中传输时，学生经常忘记封装过程。要提到数据被分割成数据包，每个包带有包含源和目标 IP 地址及序列号的头部。路由器使用 IP 地址沿最佳路径转发数据包，而交换机在局域网内使用 MAC 地址。
Network security in this context: firewalls monitor incoming and outgoing traffic based on predetermined rules, but they do not remove viruses. Proxy servers act as intermediaries and can cache web pages; they help preserve anonymity but aren't a substitute for encryption.
此背景下的网络安全：防火墙根据预定规则监控进出流量，但不能清除病毒。代理服务器充当中介，可以缓存网页；它们有助于保持匿名性，但不能代替加密。
10. Cybersecurity Threats – Distinguishing Malware Types and Social Engineering | 网络安全威胁：区分恶意软件类型与社会工程学
Students frequently mix up malware categories: virus (attaches to legitimate files, spreads when executed), worm (self-replicating across networks without user action), trojan (disguised as legitimate software), spyware (secretly collects information), adware (unwanted ads), ransomware (encrypts files for ransom). Failing to distinguish these in a scenario question loses easy marks.
学生经常混淆恶意软件类别：病毒（附着于合法文件，执行时传播）、蠕虫（无需用户操作即可通过网络自我复制）、特洛伊木马（伪装为合法软件）、间谍软件（秘密收集信息）、广告软件（不必要的广告）、勒索软件（加密文件索要赎金）。在场景题中无法区分这些类别会丢分。
Social engineering techniques like phishing, blagging, and shouldering heavily feature. Phishing emails trick users into revealing personal information by masquerading as trustworthy entities. Blagging is inventing a convincing scenario to extract information over the phone, while shouldering is simply looking over someone’s shoulder for passwords. Many students miss the nuance and lump all deceit under 'hacking'.
社会工程学技术如网络钓鱼（phishing）、电话诈骗（blagging）和肩窥（shouldering）频繁出现。网络钓鱼邮件伪装成可信实体，诱骗用户泄露个人信息。Blagging 是编造令人信服的情景以通过电话获取信息，shouldering 则是偷看他人输入密码。许多学生忽略了这些细微差别，把所有欺骗行为都归为“黑客攻击”。
Prevention methods should be specific: biometrics prevent unauthorised physical access, strong passwords and two-factor authentication prevent password cracking, penetration testing identifies vulnerabilities. Simply writing 'install antivirus' without linking to a specific threat is often insufficient for full marks.
防范方法需具体：生物识别防止未经授权的物理访问，强密码和双因素身份验证防止密码破解，渗透测试识别漏洞。仅仅写“安装杀毒软件”而不与具体威胁关联，往往不足以拿到满分。
11. Legal and Ethical Considerations – Applying Legislation to Contexts | 法律与伦理考量：将立法应用于情境
The Data Protection Act 2018, Computer Misuse Act 1990, Copyright Designs and Patents Act 1988, and Freedom of Information Act are the main pieces of legislation. Students often fail to correctly match the law to a scenario – e.g., accessing files without permission is a Computer Misuse Act offence, not a Data Protection issue. Data Protection governs how personal data is collected, stored, and processed.
《2018 年数据保护法》、《1990 年计算机滥用法》、《1988 年版权、设计和专利法》以及《信息自由法》是主要立法。学生经常无法将法律与情景正确匹配——例如，未经许可访问文件是《计算机滥用法》的违法行为，而不是数据保护问题。《数据保护法》规范个人数据的收集、存储和处理方式。
Key principles of the Data Protection Act: data must be processed lawfully, fairly, and transparently; collected for specified, explicit purposes; adequate, relevant, and limited; accurate and up to date; kept no longer than necessary; processed securely. In exam answers, citing even one or two principles accurately demonstrates understanding.
《数据保护法》的关键原则：数据必须合法、公平、透明地处理；为特定、明确的目的收集；充分、相关且有限；准确、及时更新；保存时间不超过必要；安全处理。在考试答案中，即使准确引用一两条原则也能展示理解。
Ethical considerations: privacy versus security, digital divide, environmental impact of computing (e-waste, energy consumption of data centres). Mention the balance between surveillance and civil liberties, or the responsibility of developers to create inclusive software.
伦理考量：隐私与安全、数字鸿沟、计算的环境影响（电子垃圾、数据中心能耗）。提及监控与公民自由之间的平衡，或开发者创建包容性软件的责任。
Published by TutorHao | Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
或截图后用「扫一扫 → 相册」选择本图